Losing Instance data

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

Losing Instance data

Ryan Puddephatt

Hi all,

            I have created a page which takes the input of an XQuery expression, checks against the server and brings back the results. This is then sent off the an XSL formatted page. My problem occurs when a user returns to the page to change their XQuery, all the instance data is lost. I have three instances XQueryResult, tests, and UIData, which all lose their data, so the user has to refresh their page to use the page again.

 

All the database interaction is done within a pipeline file, which then comes back to the original page and the data is sent off to the showgrid.xsl using the submission below:

 

<xforms:submission ref="instance('XQueryResult')" id="showAsGrid-submission" method="post" replace="all" action="/utilities/showGrid"></xforms:submission>

 

Is my instance losing its data because the showgrid is an XSL only file rather than being XForms, or should I be doing this another way? I have tried processing the showgrid.xsl within the pipeline and displaying it on the page, but I can’t get XForms to parse the child nodes as XHTML.

 

Any help on this would be great

 

Ryan Puddephatt

Web Developer

TFX Group

1 Michaelson Square

Livingston

West Lothian

Scotand

EH54 7DP

 

* [hidden email]

( 01506 407 110

7  01506 407 108

 

 



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Losing Instance data

Erik Bruchez
Administrator
Ryan,

XForms instances are not automatically kept between pages. While you
are on an XForms page, and interacting with the server though XForms
submissions using <xforms:submission replace="instance"/> or
<xforms:submission replace="none"/>, instances are of course kept, as
they are part of the XForms engine state. As soon as you move to
another page (for example with <xforms:submission replace="all"/> like
you are doing here, or <xforms:load show="replace"/>), that is it,
unless you do some extra work to keep your instances somewhere and to
restore them when you get back to that initial page, they are lost.

Let's say your XForms page is called "page-1" and your other page is
called "page-2".

What you should be doing here is keeping the state necessary to
restore page-1. Ideally, for convenience, this would be either a
single XForms instance which you can submit.

Then keep that XML document as you navigate to page-2, by using a PFC
XML submission. When you come back to page-1, again submit your XML
document as a PFC XML submission, and use that data, in the page model
of page-1, to restore the XForms instances of page-1 in the page view
of page-1.

I hope this makes some sense!

-Erik

Ryan Puddephatt wrote:
 > Hi all,
 >
 > I have created a page which takes the input of an XQuery expression,
 > checks against the server and brings back the results. This is then
 > sent off the an XSL formatted page. My problem occurs when a user
 > returns to the page to change their XQuery, all the instance data is
 > lost. I have three instances XQueryResult, tests, and UIData, which
 > all lose their data, so the user has to refresh their page to use
 > the page again.
 >
 > All the database interaction is done within a pipeline file, which
 > then comes back to the original page and the data is sent off to the
 > showgrid.xsl using the submission below:
 >
 > <xforms:submission ref="instance('XQueryResult')"
 > id="showAsGrid-submission" method="post" replace="all"
 > action="/utilities/showGrid"></xforms:submission>
 >
 > Is my instance losing its data because the showgrid is an XSL only
 > file rather than being XForms, or should I be doing this another
 > way? I have tried processing the showgrid.xsl within the pipeline
 > and displaying it on the page, but I can$(Bt (Bget XForms to parse the
 > child nodes as XHTML.
 >
 > Any help on this would be great



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

RE: Losing Instance data

Ryan Puddephatt
Erik,
        I have tried sending one instance to my XSLT page, but unfortunately
it requires more than one. The problem is occurring when I use the browser
back button to return to my page, I have checked the instances and can see
that they are empty, but the textarea still has the original text I entered,
I then click a button after changing the text, but it still doesn't amend
the instance element that the textarea is linked to. Do I have to change the
XSLT file into an XForms file or would it be better to display the HTML on
the same page, if so how do I use the saxon-serilizer for an instance
element where the children are XHTML?

Thanks for your help

Ryan Puddephatt
Web Developer
TFX Group
1 Michaelson Square
Livingston
West Lothian
Scotand
EH54 7DP
 
* [hidden email]
( 01506 407 110
7  01506 407 108
 

-----Original Message-----
From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
Sent: 25 October 2005 11:00
To: [hidden email]
Subject: Re: [ops-users] Losing Instance data

Ryan,

XForms instances are not automatically kept between pages. While you
are on an XForms page, and interacting with the server though XForms
submissions using <xforms:submission replace="instance"/> or
<xforms:submission replace="none"/>, instances are of course kept, as
they are part of the XForms engine state. As soon as you move to
another page (for example with <xforms:submission replace="all"/> like
you are doing here, or <xforms:load show="replace"/>), that is it,
unless you do some extra work to keep your instances somewhere and to
restore them when you get back to that initial page, they are lost.

Let's say your XForms page is called "page-1" and your other page is
called "page-2".

What you should be doing here is keeping the state necessary to
restore page-1. Ideally, for convenience, this would be either a
single XForms instance which you can submit.

Then keep that XML document as you navigate to page-2, by using a PFC
XML submission. When you come back to page-1, again submit your XML
document as a PFC XML submission, and use that data, in the page model
of page-1, to restore the XForms instances of page-1 in the page view
of page-1.

I hope this makes some sense!

-Erik

Ryan Puddephatt wrote:
 > Hi all,
 >
 > I have created a page which takes the input of an XQuery expression,
 > checks against the server and brings back the results. This is then
 > sent off the an XSL formatted page. My problem occurs when a user
 > returns to the page to change their XQuery, all the instance data is
 > lost. I have three instances XQueryResult, tests, and UIData, which
 > all lose their data, so the user has to refresh their page to use
 > the page again.
 >
 > All the database interaction is done within a pipeline file, which
 > then comes back to the original page and the data is sent off to the
 > showgrid.xsl using the submission below:
 >
 > <xforms:submission ref="instance('XQueryResult')"
 > id="showAsGrid-submission" method="post" replace="all"
 > action="/utilities/showGrid"></xforms:submission>
 >
 > Is my instance losing its data because the showgrid is an XSL only
 > file rather than being XForms, or should I be doing this another
 > way? I have tried processing the showgrid.xsl within the pipeline
 > and displaying it on the page, but I can$(Bt (Bget XForms to parse the
 > child nodes as XHTML.
 >
 > Any help on this would be great





--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Losing Instance data

Erik Bruchez
Administrator
Ryan Puddephatt wrote:

 > I have tried sending one instance to my XSLT page, but unfortunately
 > it requires more than one. The problem is occurring when I use the
 > browser back button to return to my page, I have checked the
 > instances and can see that they are empty, but the textarea still
 > has the original text I entered, I then click a button after
 > changing the text, but it still doesn't amend the instance element
 > that the textarea is linked to. Do I have to change the XSLT file
 > into an XForms file or would it be better to display the HTML on the
 > same page, if so how do I use the saxon-serilizer for an instance
 > element where the children are XHTML?

What are the exact steps that lead to the problem? Are you saying that
submitting a form on page-1, which ends up displaying page-2, and then
pressing the browser's back button while viewing page-2 causes the
XForms on page-1 to stop functioning?

-Erik



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

RE: Losing Instance data

Ryan Puddephatt
Yes, using the browsers back button to navigate from page-2 to page-1 causes
the instance to lose its data.

Ryan Puddephatt
Web Developer
TFX Group
1 Michaelson Square
Livingston
West Lothian
Scotand
EH54 7DP
 
* [hidden email]
( 01506 407 110
7  01506 407 108
 
-----Original Message-----
From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
Sent: 25 October 2005 21:03
To: [hidden email]
Subject: Re: [ops-users] Losing Instance data

Ryan Puddephatt wrote:

 > I have tried sending one instance to my XSLT page, but unfortunately
 > it requires more than one. The problem is occurring when I use the
 > browser back button to return to my page, I have checked the
 > instances and can see that they are empty, but the textarea still
 > has the original text I entered, I then click a button after
 > changing the text, but it still doesn't amend the instance element
 > that the textarea is linked to. Do I have to change the XSLT file
 > into an XForms file or would it be better to display the HTML on the
 > same page, if so how do I use the saxon-serilizer for an instance
 > element where the children are XHTML?

What are the exact steps that lead to the problem? Are you saying that
submitting a form on page-1, which ends up displaying page-2, and then
pressing the browser's back button while viewing page-2 causes the
XForms on page-1 to stop functioning?

-Erik





--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Losing Instance data

Erik Bruchez
Administrator
Ryan,

What web browser are you using?

Typically, with Ajax-style applications, most browsers by default lose
everything on a "back". More modern browsers like Opera or the latest
Firefox (1.5 beta) do restore the state of Ajax pages. In OPS, we have a
restore mechanism meant to work with those traditional browsers that do
not restore state, but there may be a bug.

-Erik

Ryan Puddephatt wrote:

> Yes, using the browsers back button to navigate from page-2 to page-1 causes
> the instance to lose its data.
>
> Ryan Puddephatt
> Web Developer
> TFX Group
> 1 Michaelson Square
> Livingston
> West Lothian
> Scotand
> EH54 7DP
>  
> * [hidden email]
> ( 01506 407 110
> 7  01506 407 108
>  
> -----Original Message-----
> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
> Sent: 25 October 2005 21:03
> To: [hidden email]
> Subject: Re: [ops-users] Losing Instance data
>
> Ryan Puddephatt wrote:
>
>  > I have tried sending one instance to my XSLT page, but unfortunately
>  > it requires more than one. The problem is occurring when I use the
>  > browser back button to return to my page, I have checked the
>  > instances and can see that they are empty, but the textarea still
>  > has the original text I entered, I then click a button after
>  > changing the text, but it still doesn't amend the instance element
>  > that the textarea is linked to. Do I have to change the XSLT file
>  > into an XForms file or would it be better to display the HTML on the
>  > same page, if so how do I use the saxon-serilizer for an instance
>  > element where the children are XHTML?
>
> What are the exact steps that lead to the problem? Are you saying that
> submitting a form on page-1, which ends up displaying page-2, and then
> pressing the browser's back button while viewing page-2 causes the
> XForms on page-1 to stop functioning?
>
> -Erik
>
>
>
>
>
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Losing Instance data

Ryan Puddephatt
I have been using IE 6.0 and Firefox latest version, both lose the
instance. I taken to displaying the XSLT page within the XForms output
using saxon serilizer and xxforms:html so I keep the instance data.

This is working fine in Firefox, but IE displays the HTML tags as text
and gives me a Javascript error, is this a common problem?

Thanks
Ryan

Erik Bruchez wrote:

> Ryan,
>
> What web browser are you using?
>
> Typically, with Ajax-style applications, most browsers by default lose
> everything on a "back". More modern browsers like Opera or the latest
> Firefox (1.5 beta) do restore the state of Ajax pages. In OPS, we have
> a restore mechanism meant to work with those traditional browsers that
> do not restore state, but there may be a bug.
>
> -Erik
>
> Ryan Puddephatt wrote:
>
>> Yes, using the browsers back button to navigate from page-2 to page-1
>> causes
>> the instance to lose its data.
>>
>> Ryan Puddephatt
>> Web Developer
>> TFX Group
>> 1 Michaelson Square
>> Livingston
>> West Lothian
>> Scotand
>> EH54 7DP
>>  
>> * [hidden email]
>> ( 01506 407 110
>> 7  01506 407 108
>>  
>> -----Original Message-----
>> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
>> Sent: 25 October 2005 21:03
>> To: [hidden email]
>> Subject: Re: [ops-users] Losing Instance data
>>
>> Ryan Puddephatt wrote:
>>
>>  > I have tried sending one instance to my XSLT page, but unfortunately
>>  > it requires more than one. The problem is occurring when I use the
>>  > browser back button to return to my page, I have checked the
>>  > instances and can see that they are empty, but the textarea still
>>  > has the original text I entered, I then click a button after
>>  > changing the text, but it still doesn't amend the instance element
>>  > that the textarea is linked to. Do I have to change the XSLT file
>>  > into an XForms file or would it be better to display the HTML on the
>>  > same page, if so how do I use the saxon-serilizer for an instance
>>  > element where the children are XHTML?
>>
>> What are the exact steps that lead to the problem? Are you saying that
>> submitting a form on page-1, which ends up displaying page-2, and then
>> pressing the browser's back button while viewing page-2 causes the
>> XForms on page-1 to stop functioning?
>>
>> -Erik
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> --
>> You receive this message as a subscriber of the
>> [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>
>------------------------------------------------------------------------
>
>
>--
>You receive this message as a subscriber of the [hidden email] mailing list.
>To unsubscribe: mailto:[hidden email]
>For general help: mailto:[hidden email]?subject=help
>ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>  
>


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Losing Instance data

Erik Bruchez
Administrator
This should work. What version of OPS are you using? 3.0 beta 3? A
nightly build? You should probably try a nightly, as many bugs have been
fixed since beta 3.

-Erik

Ryan Puddephatt wrote:

> I have been using IE 6.0 and Firefox latest version, both lose the
> instance. I taken to displaying the XSLT page within the XForms output
> using saxon serilizer and xxforms:html so I keep the instance data.
>
> This is working fine in Firefox, but IE displays the HTML tags as text
> and gives me a Javascript error, is this a common problem?
>
> Thanks
> Ryan
>
> Erik Bruchez wrote:
>
>> Ryan,
>>
>> What web browser are you using?
>>
>> Typically, with Ajax-style applications, most browsers by default lose
>> everything on a "back". More modern browsers like Opera or the latest
>> Firefox (1.5 beta) do restore the state of Ajax pages. In OPS, we have
>> a restore mechanism meant to work with those traditional browsers that
>> do not restore state, but there may be a bug.
>>
>> -Erik
>>
>> Ryan Puddephatt wrote:
>>
>>> Yes, using the browsers back button to navigate from page-2 to page-1
>>> causes
>>> the instance to lose its data.
>>>
>>> Ryan Puddephatt
>>> Web Developer
>>> TFX Group
>>> 1 Michaelson Square
>>> Livingston
>>> West Lothian
>>> Scotand
>>> EH54 7DP
>>>  
>>> * [hidden email]
>>> ( 01506 407 110
>>> 7  01506 407 108
>>>  
>>> -----Original Message-----
>>> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
>>> Sent: 25 October 2005 21:03
>>> To: [hidden email]
>>> Subject: Re: [ops-users] Losing Instance data
>>>
>>> Ryan Puddephatt wrote:
>>>
>>>  > I have tried sending one instance to my XSLT page, but unfortunately
>>>  > it requires more than one. The problem is occurring when I use the
>>>  > browser back button to return to my page, I have checked the
>>>  > instances and can see that they are empty, but the textarea still
>>>  > has the original text I entered, I then click a button after
>>>  > changing the text, but it still doesn't amend the instance element
>>>  > that the textarea is linked to. Do I have to change the XSLT file
>>>  > into an XForms file or would it be better to display the HTML on the
>>>  > same page, if so how do I use the saxon-serilizer for an instance
>>>  > element where the children are XHTML?
>>>
>>> What are the exact steps that lead to the problem? Are you saying that
>>> submitting a form on page-1, which ends up displaying page-2, and then
>>> pressing the browser's back button while viewing page-2 causes the
>>> XForms on page-1 to stop functioning?
>>>
>>> -Erik
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> --
>>> You receive this message as a subscriber of the
>>> [hidden email] mailing list.
>>> To unsubscribe: mailto:[hidden email]
>>> For general help: mailto:[hidden email]?subject=help
>>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> --
>> You receive this message as a subscriber of the
>> [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>  
>>
>
>
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Losing Instance data

Ryan Puddephatt
I'm using 3.0.beta3.200510091802, after a bit of investigation I think
I'm having problems in IE because i've stripped all the spaces, is this
likely to cause a problem?

Ryan

Erik Bruchez wrote:

> This should work. What version of OPS are you using? 3.0 beta 3? A
> nightly build? You should probably try a nightly, as many bugs have
> been fixed since beta 3.
>
> -Erik
>
> Ryan Puddephatt wrote:
>
>> I have been using IE 6.0 and Firefox latest version, both lose the
>> instance. I taken to displaying the XSLT page within the XForms
>> output using saxon serilizer and xxforms:html so I keep the instance
>> data.
>>
>> This is working fine in Firefox, but IE displays the HTML tags as
>> text and gives me a Javascript error, is this a common problem?
>>
>> Thanks
>> Ryan
>>
>> Erik Bruchez wrote:
>>
>>> Ryan,
>>>
>>> What web browser are you using?
>>>
>>> Typically, with Ajax-style applications, most browsers by default
>>> lose everything on a "back". More modern browsers like Opera or the
>>> latest Firefox (1.5 beta) do restore the state of Ajax pages. In
>>> OPS, we have a restore mechanism meant to work with those
>>> traditional browsers that do not restore state, but there may be a bug.
>>>
>>> -Erik
>>>
>>> Ryan Puddephatt wrote:
>>>
>>>> Yes, using the browsers back button to navigate from page-2 to
>>>> page-1 causes
>>>> the instance to lose its data.
>>>>
>>>> Ryan Puddephatt
>>>> Web Developer
>>>> TFX Group
>>>> 1 Michaelson Square
>>>> Livingston
>>>> West Lothian
>>>> Scotand
>>>> EH54 7DP
>>>>  
>>>> * [hidden email]
>>>> ( 01506 407 110
>>>> 7  01506 407 108
>>>>  
>>>> -----Original Message-----
>>>> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
>>>> Bruchez
>>>> Sent: 25 October 2005 21:03
>>>> To: [hidden email]
>>>> Subject: Re: [ops-users] Losing Instance data
>>>>
>>>> Ryan Puddephatt wrote:
>>>>
>>>>  > I have tried sending one instance to my XSLT page, but
>>>> unfortunately
>>>>  > it requires more than one. The problem is occurring when I use the
>>>>  > browser back button to return to my page, I have checked the
>>>>  > instances and can see that they are empty, but the textarea still
>>>>  > has the original text I entered, I then click a button after
>>>>  > changing the text, but it still doesn't amend the instance element
>>>>  > that the textarea is linked to. Do I have to change the XSLT file
>>>>  > into an XForms file or would it be better to display the HTML on
>>>> the
>>>>  > same page, if so how do I use the saxon-serilizer for an instance
>>>>  > element where the children are XHTML?
>>>>
>>>> What are the exact steps that lead to the problem? Are you saying that
>>>> submitting a form on page-1, which ends up displaying page-2, and then
>>>> pressing the browser's back button while viewing page-2 causes the
>>>> XForms on page-1 to stop functioning?
>>>>
>>>> -Erik
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>>
>>>> --
>>>> You receive this message as a subscriber of the
>>>> [hidden email] mailing list.
>>>> To unsubscribe: mailto:[hidden email]
>>>> For general help: mailto:[hidden email]?subject=help
>>>> ObjectWeb mailing lists service home page:
>>>> http://www.objectweb.org/wws
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>>
>>> --
>>> You receive this message as a subscriber of the
>>> [hidden email] mailing list.
>>> To unsubscribe: mailto:[hidden email]
>>> For general help: mailto:[hidden email]?subject=help
>>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>>  
>>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> --
>> You receive this message as a subscriber of the
>> [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>
>------------------------------------------------------------------------
>
>
>--
>You receive this message as a subscriber of the [hidden email] mailing list.
>To unsubscribe: mailto:[hidden email]
>For general help: mailto:[hidden email]?subject=help
>ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>  
>


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Losing Instance data

Ryan Puddephatt
I'm still having problems, I've put the HTML output straight into and
instance and run it through the saxon:serializer, below is part of the
HTML I'm using

                        <span>
                            <h1>result</h1>
                            <table class="downTable">
                                <tbody>
                                    <tr>
                                        <td>outstanding-approvals</td>
                                        <td>
                                            <table class="downTable">
                                                <tbody>
                                                    <tr>
                                                        <td>pea-details</td>
                                                        <td>
                                                            <table
class="acrossTable">
                                                                <thead>
                                                                    <tr
class="headingsRow">
                                                                       
<th/>
                                                                       
<th>id</th>
                                                                       
<th>name</th>
                                                                       
<th>profitCenter</th>
                                                                       
<th>statusHistory</th>
                                                                       
<th>authorizationRoles</th>
                                                                    </tr>
                                                                </thead>
                                                                <tbody>
                                                                    <tr>
                                                                       
<td class="rowNumber">1</td>
                                                                       
<td class="gridCell">3173</td>
                                                                       
<td class="gridCell">IBM Notebook Computer</td>
                                                                       
<td class="gridCell">
                                                                           
<table class="downTable">
                                                                               
<tbody>
                                                                                   
<tr>
                                                                                       
<td>facilityName</td>
                                                                                       
<td>SHENYANG</td>
                                                                                   
</tr>
                                                                                   
<tr>
                                                                                       
<td>facilityID</td>
                                                                                       
<td>114</td>
                                                                                   
</tr>
                                                                                   
<tr>
                                                                                       
<td>financialHierarchyPosition</td>
                                                                                       
<td>
                                                                                           
<table class="downTable">
                                                                                               
<tbody>
                                                                                                   
<tr>
                                                                                                       
<td>topLevelFinancialGroup</td>
                                                                                                       
<td>TOTAL OPERATIONS</td>
                                                                                                   
</tr>
                                                                                                   
<tr>
                                                                                                       
<td>divisionName</td>
                                                                                                       
<td>TFX AUTOMOTIVE</td>
                                                                                                   
</tr>
                                                                                                   
<tr>
                                                                                                       
<td>subdivisionName</td>
                                                                                                       
<td>SHIFTERS AND CABLES</td>
                                                                                                   
</tr>
                                                                                               
</tbody>
                                                                                           
</table>
                                                                                       
</td>
                                                                                   
</tr>
                                                                               
</tbody>
                                                                           
</table>
                                                                       
</td>
                                                                    </tr>
                                                                </tbody>
                                                            </table>
                                                        </td>
                                                    </tr>
                                                </tbody>
                                            </table>
                                        </td>
                                    </tr>
                                </tbody>
                            </table>
                        </span>

This draws nicely in firefox, but gives me a unknown runtime error in
IE, I've run the code through the debugger and its breaks at the snippet
below within the updateRelevantReadonly function

if (className == "xforms-output-html") { if (element.firstChild != null)
element.innerHTML = element.firstChild.data; element.style.display =
"inline"; }

any ideas why?

Ryan

Ryan Puddephatt wrote:

> I'm using 3.0.beta3.200510091802, after a bit of investigation I think
> I'm having problems in IE because i've stripped all the spaces, is
> this likely to cause a problem?
>
> Ryan
>
> Erik Bruchez wrote:
>
>> This should work. What version of OPS are you using? 3.0 beta 3? A
>> nightly build? You should probably try a nightly, as many bugs have
>> been fixed since beta 3.
>>
>> -Erik
>>
>> Ryan Puddephatt wrote:
>>
>>> I have been using IE 6.0 and Firefox latest version, both lose the
>>> instance. I taken to displaying the XSLT page within the XForms
>>> output using saxon serilizer and xxforms:html so I keep the instance
>>> data.
>>>
>>> This is working fine in Firefox, but IE displays the HTML tags as
>>> text and gives me a Javascript error, is this a common problem?
>>>
>>> Thanks
>>> Ryan
>>>
>>> Erik Bruchez wrote:
>>>
>>>> Ryan,
>>>>
>>>> What web browser are you using?
>>>>
>>>> Typically, with Ajax-style applications, most browsers by default
>>>> lose everything on a "back". More modern browsers like Opera or the
>>>> latest Firefox (1.5 beta) do restore the state of Ajax pages. In
>>>> OPS, we have a restore mechanism meant to work with those
>>>> traditional browsers that do not restore state, but there may be a
>>>> bug.
>>>>
>>>> -Erik
>>>>
>>>> Ryan Puddephatt wrote:
>>>>
>>>>> Yes, using the browsers back button to navigate from page-2 to
>>>>> page-1 causes
>>>>> the instance to lose its data.
>>>>>
>>>>> Ryan Puddephatt
>>>>> Web Developer
>>>>> TFX Group
>>>>> 1 Michaelson Square
>>>>> Livingston
>>>>> West Lothian
>>>>> Scotand
>>>>> EH54 7DP
>>>>>  
>>>>> * [hidden email]
>>>>> ( 01506 407 110
>>>>> 7  01506 407 108
>>>>>  
>>>>> -----Original Message-----
>>>>> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
>>>>> Bruchez
>>>>> Sent: 25 October 2005 21:03
>>>>> To: [hidden email]
>>>>> Subject: Re: [ops-users] Losing Instance data
>>>>>
>>>>> Ryan Puddephatt wrote:
>>>>>
>>>>>  > I have tried sending one instance to my XSLT page, but
>>>>> unfortunately
>>>>>  > it requires more than one. The problem is occurring when I use the
>>>>>  > browser back button to return to my page, I have checked the
>>>>>  > instances and can see that they are empty, but the textarea still
>>>>>  > has the original text I entered, I then click a button after
>>>>>  > changing the text, but it still doesn't amend the instance element
>>>>>  > that the textarea is linked to. Do I have to change the XSLT file
>>>>>  > into an XForms file or would it be better to display the HTML
>>>>> on the
>>>>>  > same page, if so how do I use the saxon-serilizer for an instance
>>>>>  > element where the children are XHTML?
>>>>>
>>>>> What are the exact steps that lead to the problem? Are you saying
>>>>> that
>>>>> submitting a form on page-1, which ends up displaying page-2, and
>>>>> then
>>>>> pressing the browser's back button while viewing page-2 causes the
>>>>> XForms on page-1 to stop functioning?
>>>>>
>>>>> -Erik
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> You receive this message as a subscriber of the
>>>>> [hidden email] mailing list.
>>>>> To unsubscribe: mailto:[hidden email]
>>>>> For general help: mailto:[hidden email]?subject=help
>>>>> ObjectWeb mailing lists service home page:
>>>>> http://www.objectweb.org/wws
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>>
>>>> --
>>>> You receive this message as a subscriber of the
>>>> [hidden email] mailing list.
>>>> To unsubscribe: mailto:[hidden email]
>>>> For general help: mailto:[hidden email]?subject=help
>>>> ObjectWeb mailing lists service home page:
>>>> http://www.objectweb.org/wws
>>>>  
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>>
>>> --
>>> You receive this message as a subscriber of the
>>> [hidden email] mailing list.
>>> To unsubscribe: mailto:[hidden email]
>>> For general help: mailto:[hidden email]?subject=help
>>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> --
>> You receive this message as a subscriber of the
>> [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>  
>>
>
>------------------------------------------------------------------------
>
>
>--
>You receive this message as a subscriber of the [hidden email] mailing list.
>To unsubscribe: mailto:[hidden email]
>For general help: mailto:[hidden email]?subject=help
>ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>  
>


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Losing Instance data

Erik Bruchez
Administrator
In reply to this post by Ryan Puddephatt
What do you mean by stripping all the spaces?

-Erik

Ryan Puddephatt wrote:

> I'm using 3.0.beta3.200510091802, after a bit of investigation I think
> I'm having problems in IE because i've stripped all the spaces, is this
> likely to cause a problem?
>
> Ryan
>
> Erik Bruchez wrote:
>
>> This should work. What version of OPS are you using? 3.0 beta 3? A
>> nightly build? You should probably try a nightly, as many bugs have
>> been fixed since beta 3.
>>
>> -Erik
>>
>> Ryan Puddephatt wrote:
>>
>>> I have been using IE 6.0 and Firefox latest version, both lose the
>>> instance. I taken to displaying the XSLT page within the XForms
>>> output using saxon serilizer and xxforms:html so I keep the instance
>>> data.
>>>
>>> This is working fine in Firefox, but IE displays the HTML tags as
>>> text and gives me a Javascript error, is this a common problem?
>>>
>>> Thanks
>>> Ryan
>>>
>>> Erik Bruchez wrote:
>>>
>>>> Ryan,
>>>>
>>>> What web browser are you using?
>>>>
>>>> Typically, with Ajax-style applications, most browsers by default
>>>> lose everything on a "back". More modern browsers like Opera or the
>>>> latest Firefox (1.5 beta) do restore the state of Ajax pages. In
>>>> OPS, we have a restore mechanism meant to work with those
>>>> traditional browsers that do not restore state, but there may be a bug.
>>>>
>>>> -Erik
>>>>
>>>> Ryan Puddephatt wrote:
>>>>
>>>>> Yes, using the browsers back button to navigate from page-2 to
>>>>> page-1 causes
>>>>> the instance to lose its data.
>>>>>
>>>>> Ryan Puddephatt
>>>>> Web Developer
>>>>> TFX Group
>>>>> 1 Michaelson Square
>>>>> Livingston
>>>>> West Lothian
>>>>> Scotand
>>>>> EH54 7DP
>>>>>  
>>>>> * [hidden email]
>>>>> ( 01506 407 110
>>>>> 7  01506 407 108
>>>>>  
>>>>> -----Original Message-----
>>>>> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
>>>>> Bruchez
>>>>> Sent: 25 October 2005 21:03
>>>>> To: [hidden email]
>>>>> Subject: Re: [ops-users] Losing Instance data
>>>>>
>>>>> Ryan Puddephatt wrote:
>>>>>
>>>>>  > I have tried sending one instance to my XSLT page, but
>>>>> unfortunately
>>>>>  > it requires more than one. The problem is occurring when I use the
>>>>>  > browser back button to return to my page, I have checked the
>>>>>  > instances and can see that they are empty, but the textarea still
>>>>>  > has the original text I entered, I then click a button after
>>>>>  > changing the text, but it still doesn't amend the instance element
>>>>>  > that the textarea is linked to. Do I have to change the XSLT file
>>>>>  > into an XForms file or would it be better to display the HTML on
>>>>> the
>>>>>  > same page, if so how do I use the saxon-serilizer for an instance
>>>>>  > element where the children are XHTML?
>>>>>
>>>>> What are the exact steps that lead to the problem? Are you saying that
>>>>> submitting a form on page-1, which ends up displaying page-2, and then
>>>>> pressing the browser's back button while viewing page-2 causes the
>>>>> XForms on page-1 to stop functioning?
>>>>>
>>>>> -Erik
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> You receive this message as a subscriber of the
>>>>> [hidden email] mailing list.
>>>>> To unsubscribe: mailto:[hidden email]
>>>>> For general help: mailto:[hidden email]?subject=help
>>>>> ObjectWeb mailing lists service home page:
>>>>> http://www.objectweb.org/wws
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>>
>>>> --
>>>> You receive this message as a subscriber of the
>>>> [hidden email] mailing list.
>>>> To unsubscribe: mailto:[hidden email]
>>>> For general help: mailto:[hidden email]?subject=help
>>>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>>>  
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> --
>>> You receive this message as a subscriber of the
>>> [hidden email] mailing list.
>>> To unsubscribe: mailto:[hidden email]
>>> For general help: mailto:[hidden email]?subject=help
>>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> --
>> You receive this message as a subscriber of the
>> [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>  
>>
>
>
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Losing Instance data

Ryan Puddephatt
Sorry I meant I've stripped the namespaces from all the elements

Erik Bruchez wrote:

> What do you mean by stripping all the spaces?
>
> -Erik
>
> Ryan Puddephatt wrote:
>
>> I'm using 3.0.beta3.200510091802, after a bit of investigation I
>> think I'm having problems in IE because i've stripped all the spaces,
>> is this likely to cause a problem?
>>
>> Ryan
>>
>> Erik Bruchez wrote:
>>
>>> This should work. What version of OPS are you using? 3.0 beta 3? A
>>> nightly build? You should probably try a nightly, as many bugs have
>>> been fixed since beta 3.
>>>
>>> -Erik
>>>
>>> Ryan Puddephatt wrote:
>>>
>>>> I have been using IE 6.0 and Firefox latest version, both lose the
>>>> instance. I taken to displaying the XSLT page within the XForms
>>>> output using saxon serilizer and xxforms:html so I keep the
>>>> instance data.
>>>>
>>>> This is working fine in Firefox, but IE displays the HTML tags as
>>>> text and gives me a Javascript error, is this a common problem?
>>>>
>>>> Thanks
>>>> Ryan
>>>>
>>>> Erik Bruchez wrote:
>>>>
>>>>> Ryan,
>>>>>
>>>>> What web browser are you using?
>>>>>
>>>>> Typically, with Ajax-style applications, most browsers by default
>>>>> lose everything on a "back". More modern browsers like Opera or
>>>>> the latest Firefox (1.5 beta) do restore the state of Ajax pages.
>>>>> In OPS, we have a restore mechanism meant to work with those
>>>>> traditional browsers that do not restore state, but there may be a
>>>>> bug.
>>>>>
>>>>> -Erik
>>>>>
>>>>> Ryan Puddephatt wrote:
>>>>>
>>>>>> Yes, using the browsers back button to navigate from page-2 to
>>>>>> page-1 causes
>>>>>> the instance to lose its data.
>>>>>>
>>>>>> Ryan Puddephatt
>>>>>> Web Developer
>>>>>> TFX Group
>>>>>> 1 Michaelson Square
>>>>>> Livingston
>>>>>> West Lothian
>>>>>> Scotand
>>>>>> EH54 7DP
>>>>>>  
>>>>>> * [hidden email]
>>>>>> ( 01506 407 110
>>>>>> 7  01506 407 108
>>>>>>  
>>>>>> -----Original Message-----
>>>>>> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
>>>>>> Bruchez
>>>>>> Sent: 25 October 2005 21:03
>>>>>> To: [hidden email]
>>>>>> Subject: Re: [ops-users] Losing Instance data
>>>>>>
>>>>>> Ryan Puddephatt wrote:
>>>>>>
>>>>>>  > I have tried sending one instance to my XSLT page, but
>>>>>> unfortunately
>>>>>>  > it requires more than one. The problem is occurring when I use
>>>>>> the
>>>>>>  > browser back button to return to my page, I have checked the
>>>>>>  > instances and can see that they are empty, but the textarea still
>>>>>>  > has the original text I entered, I then click a button after
>>>>>>  > changing the text, but it still doesn't amend the instance
>>>>>> element
>>>>>>  > that the textarea is linked to. Do I have to change the XSLT file
>>>>>>  > into an XForms file or would it be better to display the HTML
>>>>>> on the
>>>>>>  > same page, if so how do I use the saxon-serilizer for an instance
>>>>>>  > element where the children are XHTML?
>>>>>>
>>>>>> What are the exact steps that lead to the problem? Are you saying
>>>>>> that
>>>>>> submitting a form on page-1, which ends up displaying page-2, and
>>>>>> then
>>>>>> pressing the browser's back button while viewing page-2 causes the
>>>>>> XForms on page-1 to stop functioning?
>>>>>>
>>>>>> -Erik
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> You receive this message as a subscriber of the
>>>>>> [hidden email] mailing list.
>>>>>> To unsubscribe: mailto:[hidden email]
>>>>>> For general help: mailto:[hidden email]?subject=help
>>>>>> ObjectWeb mailing lists service home page:
>>>>>> http://www.objectweb.org/wws
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> You receive this message as a subscriber of the
>>>>> [hidden email] mailing list.
>>>>> To unsubscribe: mailto:[hidden email]
>>>>> For general help: mailto:[hidden email]?subject=help
>>>>> ObjectWeb mailing lists service home page:
>>>>> http://www.objectweb.org/wws
>>>>>  
>>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>>
>>>> --
>>>> You receive this message as a subscriber of the
>>>> [hidden email] mailing list.
>>>> To unsubscribe: mailto:[hidden email]
>>>> For general help: mailto:[hidden email]?subject=help
>>>> ObjectWeb mailing lists service home page:
>>>> http://www.objectweb.org/wws
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>>
>>> --
>>> You receive this message as a subscriber of the
>>> [hidden email] mailing list.
>>> To unsubscribe: mailto:[hidden email]
>>> For general help: mailto:[hidden email]?subject=help
>>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>>  
>>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> --
>> You receive this message as a subscriber of the
>> [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>
>------------------------------------------------------------------------
>
>
>--
>You receive this message as a subscriber of the [hidden email] mailing list.
>To unsubscribe: mailto:[hidden email]
>For general help: mailto:[hidden email]?subject=help
>ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>  
>


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Losing Instance data

Erik Bruchez
Administrator
Do you mean you stripped namespaces in the resulting HTML sent to the
browser? If so, how? Or do you send XHTML?

This said, I don't think there should be namespaces present in the first
place in the case of plain HTML. But the easiest way to know if this is
a problem is to try NOT to do what and see what happens ;-)

-Erik

Ryan Puddephatt wrote:

> Sorry I meant I've stripped the namespaces from all the elements
>
> Erik Bruchez wrote:
>
>> What do you mean by stripping all the spaces?
>>
>> -Erik
>>
>> Ryan Puddephatt wrote:
>>
>>> I'm using 3.0.beta3.200510091802, after a bit of investigation I
>>> think I'm having problems in IE because i've stripped all the spaces,
>>> is this likely to cause a problem?
>>>
>>> Ryan
>>>
>>> Erik Bruchez wrote:
>>>
>>>> This should work. What version of OPS are you using? 3.0 beta 3? A
>>>> nightly build? You should probably try a nightly, as many bugs have
>>>> been fixed since beta 3.
>>>>
>>>> -Erik
>>>>
>>>> Ryan Puddephatt wrote:
>>>>
>>>>> I have been using IE 6.0 and Firefox latest version, both lose the
>>>>> instance. I taken to displaying the XSLT page within the XForms
>>>>> output using saxon serilizer and xxforms:html so I keep the
>>>>> instance data.
>>>>>
>>>>> This is working fine in Firefox, but IE displays the HTML tags as
>>>>> text and gives me a Javascript error, is this a common problem?
>>>>>
>>>>> Thanks
>>>>> Ryan
>>>>>
>>>>> Erik Bruchez wrote:
>>>>>
>>>>>> Ryan,
>>>>>>
>>>>>> What web browser are you using?
>>>>>>
>>>>>> Typically, with Ajax-style applications, most browsers by default
>>>>>> lose everything on a "back". More modern browsers like Opera or
>>>>>> the latest Firefox (1.5 beta) do restore the state of Ajax pages.
>>>>>> In OPS, we have a restore mechanism meant to work with those
>>>>>> traditional browsers that do not restore state, but there may be a
>>>>>> bug.
>>>>>>
>>>>>> -Erik
>>>>>>
>>>>>> Ryan Puddephatt wrote:
>>>>>>
>>>>>>> Yes, using the browsers back button to navigate from page-2 to
>>>>>>> page-1 causes
>>>>>>> the instance to lose its data.
>>>>>>>
>>>>>>> Ryan Puddephatt
>>>>>>> Web Developer
>>>>>>> TFX Group
>>>>>>> 1 Michaelson Square
>>>>>>> Livingston
>>>>>>> West Lothian
>>>>>>> Scotand
>>>>>>> EH54 7DP
>>>>>>>  
>>>>>>> * [hidden email]
>>>>>>> ( 01506 407 110
>>>>>>> 7  01506 407 108
>>>>>>>  
>>>>>>> -----Original Message-----
>>>>>>> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
>>>>>>> Bruchez
>>>>>>> Sent: 25 October 2005 21:03
>>>>>>> To: [hidden email]
>>>>>>> Subject: Re: [ops-users] Losing Instance data
>>>>>>>
>>>>>>> Ryan Puddephatt wrote:
>>>>>>>
>>>>>>>  > I have tried sending one instance to my XSLT page, but
>>>>>>> unfortunately
>>>>>>>  > it requires more than one. The problem is occurring when I use
>>>>>>> the
>>>>>>>  > browser back button to return to my page, I have checked the
>>>>>>>  > instances and can see that they are empty, but the textarea still
>>>>>>>  > has the original text I entered, I then click a button after
>>>>>>>  > changing the text, but it still doesn't amend the instance
>>>>>>> element
>>>>>>>  > that the textarea is linked to. Do I have to change the XSLT file
>>>>>>>  > into an XForms file or would it be better to display the HTML
>>>>>>> on the
>>>>>>>  > same page, if so how do I use the saxon-serilizer for an instance
>>>>>>>  > element where the children are XHTML?
>>>>>>>
>>>>>>> What are the exact steps that lead to the problem? Are you saying
>>>>>>> that
>>>>>>> submitting a form on page-1, which ends up displaying page-2, and
>>>>>>> then
>>>>>>> pressing the browser's back button while viewing page-2 causes the
>>>>>>> XForms on page-1 to stop functioning?
>>>>>>>
>>>>>>> -Erik
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> You receive this message as a subscriber of the
>>>>>>> [hidden email] mailing list.
>>>>>>> To unsubscribe: mailto:[hidden email]
>>>>>>> For general help: mailto:[hidden email]?subject=help
>>>>>>> ObjectWeb mailing lists service home page:
>>>>>>> http://www.objectweb.org/wws
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> You receive this message as a subscriber of the
>>>>>> [hidden email] mailing list.
>>>>>> To unsubscribe: mailto:[hidden email]
>>>>>> For general help: mailto:[hidden email]?subject=help
>>>>>> ObjectWeb mailing lists service home page:
>>>>>> http://www.objectweb.org/wws
>>>>>>  
>>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> You receive this message as a subscriber of the
>>>>> [hidden email] mailing list.
>>>>> To unsubscribe: mailto:[hidden email]
>>>>> For general help: mailto:[hidden email]?subject=help
>>>>> ObjectWeb mailing lists service home page:
>>>>> http://www.objectweb.org/wws
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>>
>>>> --
>>>> You receive this message as a subscriber of the
>>>> [hidden email] mailing list.
>>>> To unsubscribe: mailto:[hidden email]
>>>> For general help: mailto:[hidden email]?subject=help
>>>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>>>  
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> --
>>> You receive this message as a subscriber of the
>>> [hidden email] mailing list.
>>> To unsubscribe: mailto:[hidden email]
>>> For general help: mailto:[hidden email]?subject=help
>>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> --
>> You receive this message as a subscriber of the
>> [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>  
>>
>
>
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Losing Instance data

Ryan Puddephatt
I used a pipeline, I get an XQuery result from Tamino, run this through
an XSLT sheet which gives me XHTML with all the xhtml: prefixes, I then
use the XSLT below to strip the namespace as it was Saxon was giving an
error :

"Namespace nodes must be created before the children of an element node"

the only way I could get rid of this error was to strip the namespaces

<xsl:stylesheet version="2.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                xmlns:xhtml="http://www.w3.org/1999/xhtml">
                   
                    <xsl:import href="oxf:/oxf/xslt/utils/copy.xsl"/>
                   
                    <xsl:template match="/">
                        <xhtml:div xmlns="http://www.w3.org/1999/xhtml">
                            <xsl:apply-templates/>
                        </xhtml:div>
                    </xsl:template>
                   
                    <xsl:template match="xhtml:html/xhtml:body |
xhtml:html">
                        <xsl:apply-templates/>
                    </xsl:template>
                   
                    <xsl:template match="xhtml:html/xhtml:head">
                       
                    </xsl:template>
                </xsl:stylesheet>

Erik Bruchez wrote:

> Do you mean you stripped namespaces in the resulting HTML sent to the
> browser? If so, how? Or do you send XHTML?
>
> This said, I don't think there should be namespaces present in the
> first place in the case of plain HTML. But the easiest way to know if
> this is a problem is to try NOT to do what and see what happens ;-)
>
> -Erik
>
> Ryan Puddephatt wrote:
>
>> Sorry I meant I've stripped the namespaces from all the elements
>>
>> Erik Bruchez wrote:
>>
>>> What do you mean by stripping all the spaces?
>>>
>>> -Erik
>>>
>>> Ryan Puddephatt wrote:
>>>
>>>> I'm using 3.0.beta3.200510091802, after a bit of investigation I
>>>> think I'm having problems in IE because i've stripped all the
>>>> spaces, is this likely to cause a problem?
>>>>
>>>> Ryan
>>>>
>>>> Erik Bruchez wrote:
>>>>
>>>>> This should work. What version of OPS are you using? 3.0 beta 3? A
>>>>> nightly build? You should probably try a nightly, as many bugs
>>>>> have been fixed since beta 3.
>>>>>
>>>>> -Erik
>>>>>
>>>>> Ryan Puddephatt wrote:
>>>>>
>>>>>> I have been using IE 6.0 and Firefox latest version, both lose
>>>>>> the instance. I taken to displaying the XSLT page within the
>>>>>> XForms output using saxon serilizer and xxforms:html so I keep
>>>>>> the instance data.
>>>>>>
>>>>>> This is working fine in Firefox, but IE displays the HTML tags as
>>>>>> text and gives me a Javascript error, is this a common problem?
>>>>>>
>>>>>> Thanks
>>>>>> Ryan
>>>>>>
>>>>>> Erik Bruchez wrote:
>>>>>>
>>>>>>> Ryan,
>>>>>>>
>>>>>>> What web browser are you using?
>>>>>>>
>>>>>>> Typically, with Ajax-style applications, most browsers by
>>>>>>> default lose everything on a "back". More modern browsers like
>>>>>>> Opera or the latest Firefox (1.5 beta) do restore the state of
>>>>>>> Ajax pages. In OPS, we have a restore mechanism meant to work
>>>>>>> with those traditional browsers that do not restore state, but
>>>>>>> there may be a bug.
>>>>>>>
>>>>>>> -Erik
>>>>>>>
>>>>>>> Ryan Puddephatt wrote:
>>>>>>>
>>>>>>>> Yes, using the browsers back button to navigate from page-2 to
>>>>>>>> page-1 causes
>>>>>>>> the instance to lose its data.
>>>>>>>>
>>>>>>>> Ryan Puddephatt
>>>>>>>> Web Developer
>>>>>>>> TFX Group
>>>>>>>> 1 Michaelson Square
>>>>>>>> Livingston
>>>>>>>> West Lothian
>>>>>>>> Scotand
>>>>>>>> EH54 7DP
>>>>>>>>  
>>>>>>>> * [hidden email]
>>>>>>>> ( 01506 407 110
>>>>>>>> 7  01506 407 108
>>>>>>>>  
>>>>>>>> -----Original Message-----
>>>>>>>> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of
>>>>>>>> Erik Bruchez
>>>>>>>> Sent: 25 October 2005 21:03
>>>>>>>> To: [hidden email]
>>>>>>>> Subject: Re: [ops-users] Losing Instance data
>>>>>>>>
>>>>>>>> Ryan Puddephatt wrote:
>>>>>>>>
>>>>>>>>  > I have tried sending one instance to my XSLT page, but
>>>>>>>> unfortunately
>>>>>>>>  > it requires more than one. The problem is occurring when I
>>>>>>>> use the
>>>>>>>>  > browser back button to return to my page, I have checked the
>>>>>>>>  > instances and can see that they are empty, but the textarea
>>>>>>>> still
>>>>>>>>  > has the original text I entered, I then click a button after
>>>>>>>>  > changing the text, but it still doesn't amend the instance
>>>>>>>> element
>>>>>>>>  > that the textarea is linked to. Do I have to change the XSLT
>>>>>>>> file
>>>>>>>>  > into an XForms file or would it be better to display the
>>>>>>>> HTML on the
>>>>>>>>  > same page, if so how do I use the saxon-serilizer for an
>>>>>>>> instance
>>>>>>>>  > element where the children are XHTML?
>>>>>>>>
>>>>>>>> What are the exact steps that lead to the problem? Are you
>>>>>>>> saying that
>>>>>>>> submitting a form on page-1, which ends up displaying page-2,
>>>>>>>> and then
>>>>>>>> pressing the browser's back button while viewing page-2 causes the
>>>>>>>> XForms on page-1 to stop functioning?
>>>>>>>>
>>>>>>>> -Erik
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> You receive this message as a subscriber of the
>>>>>>>> [hidden email] mailing list.
>>>>>>>> To unsubscribe: mailto:[hidden email]
>>>>>>>> For general help: mailto:[hidden email]?subject=help
>>>>>>>> ObjectWeb mailing lists service home page:
>>>>>>>> http://www.objectweb.org/wws
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> You receive this message as a subscriber of the
>>>>>>> [hidden email] mailing list.
>>>>>>> To unsubscribe: mailto:[hidden email]
>>>>>>> For general help: mailto:[hidden email]?subject=help
>>>>>>> ObjectWeb mailing lists service home page:
>>>>>>> http://www.objectweb.org/wws
>>>>>>>  
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> You receive this message as a subscriber of the
>>>>>> [hidden email] mailing list.
>>>>>> To unsubscribe: mailto:[hidden email]
>>>>>> For general help: mailto:[hidden email]?subject=help
>>>>>> ObjectWeb mailing lists service home page:
>>>>>> http://www.objectweb.org/wws
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> You receive this message as a subscriber of the
>>>>> [hidden email] mailing list.
>>>>> To unsubscribe: mailto:[hidden email]
>>>>> For general help: mailto:[hidden email]?subject=help
>>>>> ObjectWeb mailing lists service home page:
>>>>> http://www.objectweb.org/wws
>>>>>  
>>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>>
>>>> --
>>>> You receive this message as a subscriber of the
>>>> [hidden email] mailing list.
>>>> To unsubscribe: mailto:[hidden email]
>>>> For general help: mailto:[hidden email]?subject=help
>>>> ObjectWeb mailing lists service home page:
>>>> http://www.objectweb.org/wws
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>>
>>> --
>>> You receive this message as a subscriber of the
>>> [hidden email] mailing list.
>>> To unsubscribe: mailto:[hidden email]
>>> For general help: mailto:[hidden email]?subject=help
>>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>>  
>>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> --
>> You receive this message as a subscriber of the
>> [hidden email] mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>
>------------------------------------------------------------------------
>
>
>--
>You receive this message as a subscriber of the [hidden email] mailing list.
>To unsubscribe: mailto:[hidden email]
>For general help: mailto:[hidden email]?subject=help
>ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>  
>


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Losing Instance data

Alessandro  Vernet
Administrator
In reply to this post by Ryan Puddephatt
Ryan,

You have hit a bug. This only happens on IE and versions of Firefox
older than 1.5, as those browsers only restores form values instead of
the complete DOM when you go back to a page. At this point I recommend
you either test your page on Firefox only, or make sure to do reload
after you go back to a page in IE. This is a major issue, and we will
make sure to fix it for the final release. Here is the corresponding
bug:

http://forge.objectweb.org/tracker/index.php?func=detail&aid=304216&group_id=168&atid=350207

Alex

On 10/27/05, Ryan Puddephatt <[hidden email]> wrote:

> I have been using IE 6.0 and Firefox latest version, both lose the
> instance. I taken to displaying the XSLT page within the XForms output
> using saxon serilizer and xxforms:html so I keep the instance data.
>
> This is working fine in Firefox, but IE displays the HTML tags as text
> and gives me a Javascript error, is this a common problem?
>
> Thanks
> Ryan
>
> Erik Bruchez wrote:
>
> > Ryan,
> >
> > What web browser are you using?
> >
> > Typically, with Ajax-style applications, most browsers by default lose
> > everything on a "back". More modern browsers like Opera or the latest
> > Firefox (1.5 beta) do restore the state of Ajax pages. In OPS, we have
> > a restore mechanism meant to work with those traditional browsers that
> > do not restore state, but there may be a bug.
> >
> > -Erik
> >
> > Ryan Puddephatt wrote:
> >
> >> Yes, using the browsers back button to navigate from page-2 to page-1
> >> causes
> >> the instance to lose its data.
> >>
> >> Ryan Puddephatt
> >> Web Developer
> >> TFX Group
> >> 1 Michaelson Square
> >> Livingston
> >> West Lothian
> >> Scotand
> >> EH54 7DP
> >>
> >> * [hidden email]
> >> ( 01506 407 110
> >> 7  01506 407 108
> >>
> >> -----Original Message-----
> >> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
> >> Sent: 25 October 2005 21:03
> >> To: [hidden email]
> >> Subject: Re: [ops-users] Losing Instance data
> >>
> >> Ryan Puddephatt wrote:
> >>
> >>  > I have tried sending one instance to my XSLT page, but unfortunately
> >>  > it requires more than one. The problem is occurring when I use the
> >>  > browser back button to return to my page, I have checked the
> >>  > instances and can see that they are empty, but the textarea still
> >>  > has the original text I entered, I then click a button after
> >>  > changing the text, but it still doesn't amend the instance element
> >>  > that the textarea is linked to. Do I have to change the XSLT file
> >>  > into an XForms file or would it be better to display the HTML on the
> >>  > same page, if so how do I use the saxon-serilizer for an instance
> >>  > element where the children are XHTML?
> >>
> >> What are the exact steps that lead to the problem? Are you saying that
> >> submitting a form on page-1, which ends up displaying page-2, and then
> >> pressing the browser's back button while viewing page-2 causes the
> >> XForms on page-1 to stop functioning?
> >>
> >> -Erik
> >>
> >>
> >>
> >>
> >>
> >> ------------------------------------------------------------------------
> >>
> >>
> >> --
> >> You receive this message as a subscriber of the
> >> [hidden email] mailing list.
> >> To unsubscribe: mailto:[hidden email]
> >> For general help: mailto:[hidden email]?subject=help
> >> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
> >
> >
> >
> >------------------------------------------------------------------------
> >
> >
> >--
> >You receive this message as a subscriber of the [hidden email] mailing list.
> >To unsubscribe: mailto:[hidden email]
> >For general help: mailto:[hidden email]?subject=help
> >ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
> >
> >
>
>
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet