Hi, I have a problem where old instance data seems to come
back to my page, when I do the following. start the tomcat server go to my page fill in some user input, hit submit which invokes a chain of
xpl files giving me back some XML in an instance called retrievedSummaryInfo,
which the page displays – OK now flush the browser cache, kill the browser start a new invocation of the browser goto the page change one of the xforms input fields to a new value, the
old values of retrievedSummaryInfo are delivered back to my page (this is
confirmed by the debug messages in the Logging events window) I am guessing the data is being stored on the server side
and delivered back to my page. This happ3ens for IE and firefox. This did not happen under 3.0.beta3.200510091802. any ideas ? Doug Doug Young Software Engineer Teleflex IT
+44 (0) 1506 407107 -- 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 |
Administrator
|
Doug,
We haven't seen that behavior yet. At worst it could be a bug related to caching, but it is hard to guess what's happening without having a reproduceable example we can run on our side. Is there any way you can package such a case for us? -Erik Doug Young wrote: > > > Hi, > > I have a problem where old instance data seems to come back to my > page, when I do the following. > > > > start the tomcat server > > go to my page > > fill in some user input, hit submit which invokes a chain of xpl files > giving me back some XML in an instance called retrievedSummaryInfo, > which the page displays ? OK > > now flush the browser cache, kill the browser > > start a new invocation of the browser > > goto the page > > change one of the xforms input fields to a new value, the old values of > retrievedSummaryInfo are delivered back to my page (this is confirmed by > the debug messages in the Logging events window) > > > > I am guessing the data is being stored on the server side and delivered > back to my page. > > This happ3ens for IE and firefox. > > > > This did not happen under 3.0.beta3.200510091802. > > > > > > any ideas ? > > > > > > Doug > > > > Doug Young > > Software Engineer > > > > Teleflex IT > > 1 Michaelson Square > Livingston > West Lothian > Scotland > EH54 7DP > > +44 (0) 1506 407107 -- 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 |
Erik,
Here is a cut down example that shows the problem under .beta3.200511020401. the file locations are: resources/pages/allStatusSummary/getSummaryAndGraphInfo.xpl resources/pages/allStatusSummary/view.xsl start tomcat open a browser browse the view file blah blah/context name/view click the update button, this submits the retrievedSummaryInfo to the getSummaryAndGraphInfo.xpl file. The cut down getSummaryAndGraphInfo.xpl just uses xslt to insert xml into the instance. In the full version this calls other xpl files, talks to tamino and plays with charts. the instance comes back populated with data to display, the view page notices this and does some toggles to show the data. Take a note of the date and time in the summary title row. close the browser start a new browser window flush the browser cache browse the view file blah blah/context name/view -- looks OK clear the logging events window in eclipse click on the start date in the view page , pick a different start date, -- the view page does some of its toggles and displays some empty fields, now check the logging events window, check out the retrievedSummaryInfo instance, it's the one we had before (look at the value of the summaryDispStr element it's the same date and time as the previous one) server side caching ? this repeats with IE 6.0 and firefox 1.0.7. It also repeats using the two different browsers in the two different steps above. regards Doug -----Original Message----- From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez Sent: 07 November 2005 17:09 To: [hidden email] Subject: Re: [ops-users] old instance data coming back to a page -- version 3.0.beta3.200511020401 Doug, We haven't seen that behavior yet. At worst it could be a bug related to caching, but it is hard to guess what's happening without having a reproduceable example we can run on our side. Is there any way you can package such a case for us? -Erik Doug Young wrote: > > > Hi, > > I have a problem where old instance data seems to come back to my > page, when I do the following. > > > > start the tomcat server > > go to my page > > fill in some user input, hit submit which invokes a chain of xpl files > giving me back some XML in an instance called retrievedSummaryInfo, > which the page displays - OK > > now flush the browser cache, kill the browser > > start a new invocation of the browser > > goto the page > > change one of the xforms input fields to a new value, the old values of > retrievedSummaryInfo are delivered back to my page (this is confirmed by > the debug messages in the Logging events window) > > > > I am guessing the data is being stored on the server side and delivered > back to my page. > > This happ3ens for IE and firefox. > > > > This did not happen under 3.0.beta3.200510091802. > > > > > > any ideas ? > > > > > > Doug > > > > Doug Young > > Software Engineer > > > > Teleflex IT > > 1 Michaelson Square > Livingston > West Lothian > Scotland > EH54 7DP > > +44 (0) 1506 407107 -- 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 page-flow.xml (1K) Download Attachment view.xsl (23K) Download Attachment getSummaryAndGraphInfo.xpl (5K) Download Attachment |
Administrator
|
Doug,
I cannot reproduce this. A few questions below in your steps: > start tomcat > > open a browser > > browse the view file blah blah/context name/view > > click the update button, this submits the retrievedSummaryInfo to the > getSummaryAndGraphInfo.xpl file. The cut down getSummaryAndGraphInfo.xpl > just uses xslt to insert xml into the instance. In the full version this > calls other xpl files, talks to tamino and plays with charts. > the instance comes back populated with data to display, the view page > notices this and does some toggles to show the data. Take a note of the date > and time in the summary title row. > > close the browser > > start a new browser window > > flush the browser cache > > browse the view file blah blah/context name/view -- looks OK > > clear the logging events window in eclipse > > click on the start date in the view page , pick a different start date, -- > the view page does some of its toggles and displays some empty fields, now have clicked "Update" first? Do you mean that just changing the start date causes other things on the page to change? > check the logging events window, check out the retrievedSummaryInfo > instance, it's the one we had before (look at the value of the > summaryDispStr element it's the same date and time as the previous one) I would check it, but there is no debug attribute in your code. Do you mean I should be looking at the "data" output of getSummaryAndGraphInfo.xpl: > server side caching ? > > this repeats with IE 6.0 and firefox 1.0.7. It also repeats using the two > different browsers in the two different steps above. -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 |
Hi Erik,
Doug is away now, so I'm dealing with the problem. > Just changing the start date does not cause anything to toggle. Should I >have clicked "Update" first? Do you mean that just changing the start >date causes other things on the page to change? When we have tested it, just using the calendar to change the date activates the toggle and shows an empty output >I would check it, but there is no debug attribute in your code. Do you >mean I should be looking at the "data" output of >getSummaryAndGraphInfo.xpl: The output Doug was talking about is the 'resulting instance' within the Logging Events in Eclipse, this shows the previous instance when we haven't even submitted the page, or called the XPL. Any ideas? Thanks 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: 09 November 2005 21:37 To: [hidden email] Subject: Re: [ops-users] old instance data coming back to a page -- version 3.0.beta3.200511020401 Doug, I cannot reproduce this. A few questions below in your steps: > start tomcat > > open a browser > > browse the view file blah blah/context name/view > > click the update button, this submits the retrievedSummaryInfo to the > getSummaryAndGraphInfo.xpl file. The cut down getSummaryAndGraphInfo.xpl > just uses xslt to insert xml into the instance. In the full version this > calls other xpl files, talks to tamino and plays with charts. > the instance comes back populated with data to display, the view page > notices this and does some toggles to show the data. Take a note of the > and time in the summary title row. > > close the browser > > start a new browser window > > flush the browser cache > > browse the view file blah blah/context name/view -- looks OK > > clear the logging events window in eclipse > > click on the start date in the view page , pick a different start date, -- > the view page does some of its toggles and displays some empty fields, now have clicked "Update" first? Do you mean that just changing the start date causes other things on the page to change? > check the logging events window, check out the retrievedSummaryInfo > instance, it's the one we had before (look at the value of the > summaryDispStr element it's the same date and time as the previous one) I would check it, but there is no debug attribute in your code. Do you mean I should be looking at the "data" output of getSummaryAndGraphInfo.xpl: > server side caching ? > > this repeats with IE 6.0 and firefox 1.0.7. It also repeats using the two > different browsers in the two different steps above. -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 |
In reply to this post by Erik Bruchez
Erik,
I have noticed something new appearing in the Logging Events window, which could be of use! As the problem is occurring I see two events cacheContainingDocument and getContainingDocument, before this the instance is empty after this the form is changed and the instance is full again! Could this be a server-side thing? Or of some use? 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: 09 November 2005 21:37 To: [hidden email] Subject: Re: [ops-users] old instance data coming back to a page -- version 3.0.beta3.200511020401 Doug, I cannot reproduce this. A few questions below in your steps: > start tomcat > > open a browser > > browse the view file blah blah/context name/view > > click the update button, this submits the retrievedSummaryInfo to the > getSummaryAndGraphInfo.xpl file. The cut down getSummaryAndGraphInfo.xpl > just uses xslt to insert xml into the instance. In the full version this > calls other xpl files, talks to tamino and plays with charts. > the instance comes back populated with data to display, the view page > notices this and does some toggles to show the data. Take a note of the > and time in the summary title row. > > close the browser > > start a new browser window > > flush the browser cache > > browse the view file blah blah/context name/view -- looks OK > > clear the logging events window in eclipse > > click on the start date in the view page , pick a different start date, -- > the view page does some of its toggles and displays some empty fields, now have clicked "Update" first? Do you mean that just changing the start date causes other things on the page to change? > check the logging events window, check out the retrievedSummaryInfo > instance, it's the one we had before (look at the value of the > summaryDispStr element it's the same date and time as the previous one) I would check it, but there is no debug attribute in your code. Do you mean I should be looking at the "data" output of getSummaryAndGraphInfo.xpl: > server side caching ? > > this repeats with IE 6.0 and firefox 1.0.7. It also repeats using the two > different browsers in the two different steps above. -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 |
Administrator
|
Possibly. Are you trying with a (very) recent unstable build? You may
have been unlucky and hit the code in a buggy state while we were implementing some new caching features. To check that without redownloading, set the following in properties.xml: <property as="xs:boolean" name="oxf.xforms.cache.document" value="false"/> <property as="xs:boolean" name="oxf.xforms.cache.context" value="false"/> (The former is the current property name, the latter is obsolete.) -Erik Ryan Puddephatt wrote: > Erik, > I have noticed something new appearing in the Logging Events window, > which could be of use! > > As the problem is occurring I see two events cacheContainingDocument and > getContainingDocument, before this the instance is empty after this the form > is changed and the instance is full again! > > Could this be a server-side thing? Or of some use? > > 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: 09 November 2005 21:37 > To: [hidden email] > Subject: Re: [ops-users] old instance data coming back to a page -- version > 3.0.beta3.200511020401 > > Doug, > > I cannot reproduce this. A few questions below in your steps: > > >>start tomcat >> >>open a browser >> >>browse the view file blah blah/context name/view >> >>click the update button, this submits the retrievedSummaryInfo to the >>getSummaryAndGraphInfo.xpl file. The cut down getSummaryAndGraphInfo.xpl >>just uses xslt to insert xml into the instance. In the full version this >>calls other xpl files, talks to tamino and plays with charts. >>the instance comes back populated with data to display, the view page >>notices this and does some toggles to show the data. Take a note of the > > date > >>and time in the summary title row. >> >>close the browser >> >>start a new browser window >> >>flush the browser cache >> >>browse the view file blah blah/context name/view -- looks OK >> >>clear the logging events window in eclipse >> >>click on the start date in the view page , pick a different start date, -- >>the view page does some of its toggles and displays some empty fields, now > > > Just changing the start date does not cause anything to toggle. Should I > have clicked "Update" first? Do you mean that just changing the start > date causes other things on the page to change? > > >>check the logging events window, check out the retrievedSummaryInfo >>instance, it's the one we had before (look at the value of the >>summaryDispStr element it's the same date and time as the previous one) > > > I would check it, but there is no debug attribute in your code. Do you > mean I should be looking at the "data" output of getSummaryAndGraphInfo.xpl: > > >>server side caching ? >> >>this repeats with IE 6.0 and firefox 1.0.7. It also repeats using the two >>different browsers in the two different steps above. > > > -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 |
Erik,
I believe it is a fairly new one, Doug got an unstable build to fix a JavaScript problem recently. I have set the properties and it solved the problem! I guess it was just a problem with the caching Should I upgrade this to a newer unstable build? Thanks 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: 10 November 2005 12:48 To: [hidden email] Subject: Re: [ops-users] old instance data coming back to a page -- version 3.0.beta3.200511020401 Possibly. Are you trying with a (very) recent unstable build? You may have been unlucky and hit the code in a buggy state while we were implementing some new caching features. To check that without redownloading, set the following in properties.xml: <property as="xs:boolean" name="oxf.xforms.cache.document" value="false"/> <property as="xs:boolean" name="oxf.xforms.cache.context" value="false"/> (The former is the current property name, the latter is obsolete.) -Erik Ryan Puddephatt wrote: > Erik, > I have noticed something new appearing in the Logging Events window, > which could be of use! > > As the problem is occurring I see two events cacheContainingDocument and > getContainingDocument, before this the instance is empty after this the form > is changed and the instance is full again! > > Could this be a server-side thing? Or of some use? > > 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: 09 November 2005 21:37 > To: [hidden email] > Subject: Re: [ops-users] old instance data coming back to a page -- > 3.0.beta3.200511020401 > > Doug, > > I cannot reproduce this. A few questions below in your steps: > > >>start tomcat >> >>open a browser >> >>browse the view file blah blah/context name/view >> >>click the update button, this submits the retrievedSummaryInfo to the >>getSummaryAndGraphInfo.xpl file. The cut down getSummaryAndGraphInfo.xpl >>just uses xslt to insert xml into the instance. In the full version this >>calls other xpl files, talks to tamino and plays with charts. >>the instance comes back populated with data to display, the view page >>notices this and does some toggles to show the data. Take a note of the > > date > >>and time in the summary title row. >> >>close the browser >> >>start a new browser window >> >>flush the browser cache >> >>browse the view file blah blah/context name/view -- looks OK >> >>clear the logging events window in eclipse >> >>click on the start date in the view page , pick a different start date, -- >>the view page does some of its toggles and displays some empty fields, now > > > Just changing the start date does not cause anything to toggle. Should I > have clicked "Update" first? Do you mean that just changing the start > date causes other things on the page to change? > > >>check the logging events window, check out the retrievedSummaryInfo >>instance, it's the one we had before (look at the value of the >>summaryDispStr element it's the same date and time as the previous one) > > > I would check it, but there is no debug attribute in your code. Do you > mean I should be looking at the "data" output of > > >>server side caching ? >> >>this repeats with IE 6.0 and firefox 1.0.7. It also repeats using the two >>different browsers in the two different steps above. > > > -Erik > > > > > > ------------------------------------------------------------------------ > > > -- > You receive this message as a subscriber of the [hidden email] > 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 |
Administrator
|
Ryan Puddephatt wrote:
> Erik, > > I believe it is a fairly new one, Doug got an unstable build to fix a > JavaScript problem recently. I have set the properties and it solved the > problem! I guess it was just a problem with the caching > > Should I upgrade this to a newer unstable build? You can always give it a try, as my guess is that the cache problem you saw is now fixed. With the new build try to set the properties back to the default, i.e.: <property as="xs:boolean" name="oxf.xforms.cache.document" value="true"/> And remove this one: <property as="xs:boolean" name="oxf.xforms.cache.context" value="false"/> Just keep your current build somewhere just in case. -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 |
Administrator
|
In reply to this post by Ryan Puddephatt
On 11/10/05, Ryan Puddephatt <[hidden email]> wrote:
> I believe it is a fairly new one, Doug got an unstable build to fix a > JavaScript problem recently. I have set the properties and it solved the > problem! I guess it was just a problem with the caching > > Should I upgrade this to a newer unstable build? Ryan, A few days ago we have implemented a feature so that you could modify the value of an input field with your own JavaScript and get the same behavior as if the end-user had modified the text field. That code was causing IE to lock in certain situations. I still have to figure this out and in the meantime I have commented that code. So just be aware that if you get one of the latest unstable builds, that behavior is temporarily turned off. Alex -- 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 |
Alex,
Thanks for letting me know, all three problems unfortunately exist in the one application, so I will leave the production one as is until the JavaScript problem is resolved. Thanks Again 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: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro Vernet Sent: 11 November 2005 17:39 To: [hidden email] Subject: Re: [ops-users] old instance data coming back to a page -- version 3.0.beta3.200511020401 On 11/10/05, Ryan Puddephatt <[hidden email]> wrote: > I believe it is a fairly new one, Doug got an unstable build to fix a > JavaScript problem recently. I have set the properties and it solved the > problem! I guess it was just a problem with the caching > > Should I upgrade this to a newer unstable build? Ryan, A few days ago we have implemented a feature so that you could modify the value of an input field with your own JavaScript and get the same behavior as if the end-user had modified the text field. That code was causing IE to lock in certain situations. I still have to figure this out and in the meantime I have commented that code. So just be aware that if you get one of the latest unstable builds, that behavior is temporarily turned off. Alex -- 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 |
Administrator
|
Hi Ryan,
Sounds good; I will let you know as soon as this JavaScript issue is fixed. Alex On 11/11/05, Ryan Puddephatt <[hidden email]> wrote: > Alex, > Thanks for letting me know, all three problems unfortunately exist > in the one application, so I will leave the production one as is until the > JavaScript problem is resolved. > > Thanks Again > > 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: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro > Vernet > Sent: 11 November 2005 17:39 > To: [hidden email] > Subject: Re: [ops-users] old instance data coming back to a page -- version > 3.0.beta3.200511020401 > > On 11/10/05, Ryan Puddephatt <[hidden email]> wrote: > > I believe it is a fairly new one, Doug got an unstable build to fix a > > JavaScript problem recently. I have set the properties and it solved the > > problem! I guess it was just a problem with the caching > > > > Should I upgrade this to a newer unstable build? > > Ryan, > > A few days ago we have implemented a feature so that you could modify > the value of an input field with your own JavaScript and get the same > behavior as if the end-user had modified the text field. That code was > causing IE to lock in certain situations. I still have to figure this > out and in the meantime I have commented that code. So just be aware > that if you get one of the latest unstable builds, that behavior is > temporarily turned off. > > Alex > > > > > > > -- > 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 > > > -- Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/ -- 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 |
Hi Alex,
Any news on that JavaScript bug being fixed? Thanks 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: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro Vernet Sent: 15 November 2005 02:05 To: [hidden email] Subject: Re: [ops-users] old instance data coming back to a page -- version 3.0.beta3.200511020401 Hi Ryan, Sounds good; I will let you know as soon as this JavaScript issue is fixed. Alex On 11/11/05, Ryan Puddephatt <[hidden email]> wrote: > Alex, > Thanks for letting me know, all three problems unfortunately exist > in the one application, so I will leave the production one as is until the > JavaScript problem is resolved. > > Thanks Again > > 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: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro > Vernet > Sent: 11 November 2005 17:39 > To: [hidden email] > Subject: Re: [ops-users] old instance data coming back to a page -- > 3.0.beta3.200511020401 > > On 11/10/05, Ryan Puddephatt <[hidden email]> wrote: > > I believe it is a fairly new one, Doug got an unstable build to fix a > > JavaScript problem recently. I have set the properties and it solved the > > problem! I guess it was just a problem with the caching > > > > Should I upgrade this to a newer unstable build? > > Ryan, > > A few days ago we have implemented a feature so that you could modify > the value of an input field with your own JavaScript and get the same > behavior as if the end-user had modified the text field. That code was > causing IE to lock in certain situations. I still have to figure this > out and in the meantime I have commented that code. So just be aware > that if you get one of the latest unstable builds, that behavior is > temporarily turned off. > > Alex > > > > > > > -- > You receive this message as a subscriber of the [hidden email] > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws > > > -- Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/ -- 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 |
Administrator
|
Hi Ryan,
Good news: this is fixed. As usual, you can get that in the latest "unstable build". Alex On 11/16/05, Ryan Puddephatt <[hidden email]> wrote: > Hi Alex, > Any news on that JavaScript bug being fixed? > > Thanks > > 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: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro > Vernet > Sent: 15 November 2005 02:05 > To: [hidden email] > Subject: Re: [ops-users] old instance data coming back to a page -- version > 3.0.beta3.200511020401 > > Hi Ryan, > > Sounds good; I will let you know as soon as this JavaScript issue is fixed. > > Alex > > On 11/11/05, Ryan Puddephatt <[hidden email]> wrote: > > Alex, > > Thanks for letting me know, all three problems unfortunately exist > > in the one application, so I will leave the production one as is until the > > JavaScript problem is resolved. > > > > Thanks Again > > > > 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: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro > > Vernet > > Sent: 11 November 2005 17:39 > > To: [hidden email] > > Subject: Re: [ops-users] old instance data coming back to a page -- > version > > 3.0.beta3.200511020401 > > > > On 11/10/05, Ryan Puddephatt <[hidden email]> wrote: > > > I believe it is a fairly new one, Doug got an unstable build to fix a > > > JavaScript problem recently. I have set the properties and it solved the > > > problem! I guess it was just a problem with the caching > > > > > > Should I upgrade this to a newer unstable build? > > > > Ryan, > > > > A few days ago we have implemented a feature so that you could modify > > the value of an input field with your own JavaScript and get the same > > behavior as if the end-user had modified the text field. That code was > > causing IE to lock in certain situations. I still have to figure this > > out and in the meantime I have commented that code. So just be aware > > that if you get one of the latest unstable builds, that behavior is > > temporarily turned off. > > > > Alex > > > > > > > > > > > > > > -- > > 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 > > > > > > > > > -- > Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/ > > > > > > > -- > 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 > > > -- Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/ -- 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 |
Alex,
I've been playing around with the JavaScript trying to get it to work, but it doesn't seem to be setting the ID of the html:input control. I have looked at the source and xforms-to-ajax to try a get a better idea. I've noticed two things, the code appears to be surrounding the html:input with a html:span, which is given the id attribute. The html:input is given a name attribute rather than id! Is this what was intended, i.e. My Javascript will have to search for name rather than id or am I correct in saying this bug isn't fixed? ><xforms:input ref="ID" id="facilityID"> > >Then in JavaScript you set the value of this input with: > >document.getElementById("facilityID").value = "34" > >When this code runs, our JavaScript code notices that you are >programmatically modifying a value, it sends an event to the server, >and other controls bound to the same node are updated. Note that this >currently only works for the <xforms:input> control. But the hard code >is there, and I will leave making this work for other controls to >myself as an exercise for a later time :) . > >Alex 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: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro Vernet Sent: 17 November 2005 01:37 To: [hidden email] Subject: Re: [ops-users] old instance data coming back to a page -- version 3.0.beta3.200511020401 Hi Ryan, Good news: this is fixed. As usual, you can get that in the latest "unstable build". Alex On 11/16/05, Ryan Puddephatt <[hidden email]> wrote: > Hi Alex, > Any news on that JavaScript bug being fixed? > > Thanks > > 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: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro > Vernet > Sent: 15 November 2005 02:05 > To: [hidden email] > Subject: Re: [ops-users] old instance data coming back to a page -- > 3.0.beta3.200511020401 > > Hi Ryan, > > Sounds good; I will let you know as soon as this JavaScript issue is > > Alex > > On 11/11/05, Ryan Puddephatt <[hidden email]> wrote: > > Alex, > > Thanks for letting me know, all three problems unfortunately exist > > in the one application, so I will leave the production one as is until the > > JavaScript problem is resolved. > > > > Thanks Again > > > > 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: [hidden email] [mailto:[hidden email]] On Behalf Of > > Vernet > > Sent: 11 November 2005 17:39 > > To: [hidden email] > > Subject: Re: [ops-users] old instance data coming back to a page -- > version > > 3.0.beta3.200511020401 > > > > On 11/10/05, Ryan Puddephatt <[hidden email]> wrote: > > > I believe it is a fairly new one, Doug got an unstable build to fix a > > > JavaScript problem recently. I have set the properties and it solved > > > problem! I guess it was just a problem with the caching > > > > > > Should I upgrade this to a newer unstable build? > > > > Ryan, > > > > A few days ago we have implemented a feature so that you could modify > > the value of an input field with your own JavaScript and get the same > > behavior as if the end-user had modified the text field. That code was > > causing IE to lock in certain situations. I still have to figure this > > out and in the meantime I have commented that code. So just be aware > > that if you get one of the latest unstable builds, that behavior is > > temporarily turned off. > > > > Alex > > > > > > > > > > > > > > -- > > 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 > > > > > > > > > -- > Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/ > > > > > > > -- > You receive this message as a subscriber of the [hidden email] > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws > > > -- Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/ -- 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 |
Administrator
|
Ryan,
We are talking here about setting the *value* of a control. You cannot change the *id* of an XForms element from Javascript at the moment. -Erik Ryan Puddephatt wrote: > Alex, > I've been playing around with the JavaScript trying to get it to > work, but it doesn't seem to be setting the ID of the html:input control. I > have looked at the source and xforms-to-ajax to try a get a better idea. > I've noticed two things, the code appears to be surrounding the html:input > with a html:span, which is given the id attribute. The html:input is given a > name attribute rather than id! Is this what was intended, i.e. My Javascript > will have to search for name rather than id or am I correct in saying this > bug isn't fixed? > > >><xforms:input ref="ID" id="facilityID"> >> >>Then in JavaScript you set the value of this input with: >> >>document.getElementById("facilityID").value = "34" >> >>When this code runs, our JavaScript code notices that you are >>programmatically modifying a value, it sends an event to the server, >>and other controls bound to the same node are updated. Note that this >>currently only works for the <xforms:input> control. But the hard code >>is there, and I will leave making this work for other controls to >>myself as an exercise for a later time :) . >> >>Alex > > > Thanks > > 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: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro > Vernet > Sent: 17 November 2005 01:37 > To: [hidden email] > Subject: Re: [ops-users] old instance data coming back to a page -- version > 3.0.beta3.200511020401 > > Hi Ryan, > > Good news: this is fixed. As usual, you can get that in the latest > "unstable build". > > Alex > > On 11/16/05, Ryan Puddephatt <[hidden email]> wrote: > >>Hi Alex, >> Any news on that JavaScript bug being fixed? >> >>Thanks >> >>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: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro >>Vernet >>Sent: 15 November 2005 02:05 >>To: [hidden email] >>Subject: Re: [ops-users] old instance data coming back to a page -- > > version > >>3.0.beta3.200511020401 >> >>Hi Ryan, >> >>Sounds good; I will let you know as soon as this JavaScript issue is > > fixed. > >>Alex >> >>On 11/11/05, Ryan Puddephatt <[hidden email]> wrote: >> >>>Alex, >>> Thanks for letting me know, all three problems unfortunately > > exist > >>>in the one application, so I will leave the production one as is until > > the > >>>JavaScript problem is resolved. >>> >>>Thanks Again >>> >>>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: [hidden email] [mailto:[hidden email]] On Behalf Of > > Alessandro > >>>Vernet >>>Sent: 11 November 2005 17:39 >>>To: [hidden email] >>>Subject: Re: [ops-users] old instance data coming back to a page -- >> >>version >> >>>3.0.beta3.200511020401 >>> >>>On 11/10/05, Ryan Puddephatt <[hidden email]> wrote: >>> >>>>I believe it is a fairly new one, Doug got an unstable build to fix a >>>>JavaScript problem recently. I have set the properties and it solved > > the > >>>>problem! I guess it was just a problem with the caching >>>> >>>>Should I upgrade this to a newer unstable build? >>> >>>Ryan, >>> >>>A few days ago we have implemented a feature so that you could modify >>>the value of an input field with your own JavaScript and get the same >>>behavior as if the end-user had modified the text field. That code was >>>causing IE to lock in certain situations. I still have to figure this >>>out and in the meantime I have commented that code. So just be aware >>>that if you get one of the latest unstable builds, that behavior is >>>temporarily turned off. >>> >>>Alex >>> >>> >>> >>> >>> >>> >>>-- >>>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 >>> >>> >>> >> >> >>-- >>Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/ >> >> >> >> >> >> >>-- >>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 >> >> >> > > > > -- > Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/ > > > > > > ------------------------------------------------------------------------ > > > -- > 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 |
Erik,
I'm not trying to change the value of the id with JavaScript, I'm trying to change the value of an input control using JavaScript, which I have set and id for. Below is the XForms <xforms:input ref="summaryUnderPointInFinancialTreeID" id="facilityID"> </xforms:input> Rather than the input control having the id I have specified a span element has it, and my control has been given a name. <span id="facilityID" class="xforms-control xforms-input"><span class="xforms-date-display"></span><input type="text" name="facilityID" value="" class="xforms-type-string"><span class="xforms-showcalendar xforms-type-string"></span></span> Alex said we would be able to set the id of the input control. Also I have made a small work around for the time being, but the instance value of 'summaryUnderPointInFinancialTreeID' is not being changed even though the value of the control has changed via JavaScript So both bugs still appear to be there Thanks 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: 17 November 2005 15:57 To: [hidden email] Subject: Re: [ops-users] old instance data coming back to a page -- version 3.0.beta3.200511020401 Ryan, We are talking here about setting the *value* of a control. You cannot change the *id* of an XForms element from Javascript at the moment. -Erik Ryan Puddephatt wrote: > Alex, > I've been playing around with the JavaScript trying to get it to > work, but it doesn't seem to be setting the ID of the html:input control. I > have looked at the source and xforms-to-ajax to try a get a better idea. > I've noticed two things, the code appears to be surrounding the html:input > with a html:span, which is given the id attribute. The html:input is given a > name attribute rather than id! Is this what was intended, i.e. My Javascript > will have to search for name rather than id or am I correct in saying this > bug isn't fixed? > > >><xforms:input ref="ID" id="facilityID"> >> >>Then in JavaScript you set the value of this input with: >> >>document.getElementById("facilityID").value = "34" >> >>When this code runs, our JavaScript code notices that you are >>programmatically modifying a value, it sends an event to the server, >>and other controls bound to the same node are updated. Note that this >>currently only works for the <xforms:input> control. But the hard code >>is there, and I will leave making this work for other controls to >>myself as an exercise for a later time :) . >> >>Alex > > > Thanks > > 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: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro > Vernet > Sent: 17 November 2005 01:37 > To: [hidden email] > Subject: Re: [ops-users] old instance data coming back to a page -- > 3.0.beta3.200511020401 > > Hi Ryan, > > Good news: this is fixed. As usual, you can get that in the latest > "unstable build". > > Alex > > On 11/16/05, Ryan Puddephatt <[hidden email]> wrote: > >>Hi Alex, >> Any news on that JavaScript bug being fixed? >> >>Thanks >> >>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: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro >>Vernet >>Sent: 15 November 2005 02:05 >>To: [hidden email] >>Subject: Re: [ops-users] old instance data coming back to a page -- > > version > >>3.0.beta3.200511020401 >> >>Hi Ryan, >> >>Sounds good; I will let you know as soon as this JavaScript issue is > > fixed. > >>Alex >> >>On 11/11/05, Ryan Puddephatt <[hidden email]> wrote: >> >>>Alex, >>> Thanks for letting me know, all three problems unfortunately > > exist > >>>in the one application, so I will leave the production one as is until > > the > >>>JavaScript problem is resolved. >>> >>>Thanks Again >>> >>>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: [hidden email] [mailto:[hidden email]] On Behalf Of > > Alessandro > >>>Vernet >>>Sent: 11 November 2005 17:39 >>>To: [hidden email] >>>Subject: Re: [ops-users] old instance data coming back to a page -- >> >>version >> >>>3.0.beta3.200511020401 >>> >>>On 11/10/05, Ryan Puddephatt <[hidden email]> wrote: >>> >>>>I believe it is a fairly new one, Doug got an unstable build to fix a >>>>JavaScript problem recently. I have set the properties and it solved > > the > >>>>problem! I guess it was just a problem with the caching >>>> >>>>Should I upgrade this to a newer unstable build? >>> >>>Ryan, >>> >>>A few days ago we have implemented a feature so that you could modify >>>the value of an input field with your own JavaScript and get the same >>>behavior as if the end-user had modified the text field. That code was >>>causing IE to lock in certain situations. I still have to figure this >>>out and in the meantime I have commented that code. So just be aware >>>that if you get one of the latest unstable builds, that behavior is >>>temporarily turned off. >>> >>>Alex >>> >>> >>> >>> >>> >>> >>>-- >>>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 >>> >>> >>> >> >> >>-- >>Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/ >> >> >> >> >> >> >>-- >>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 >> >> >> > > > > -- > Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/ > > > > > > ------------------------------------------------------------------------ > > > -- > You receive this message as a subscriber of the [hidden email] > 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 |
Administrator
|
Ryan Puddephatt wrote:
> I'm not trying to change the value of the id with JavaScript Sorry, I misunderstood because your sentence was a little misleading: "[...] the JavaScript [...] doesn't seem to be setting the ID of the html:input control" > <span id="facilityID" class="xforms-control xforms-input"><span > class="xforms-date-display"></span><input type="text" name="facilityID" > value="" class="xforms-type-string"><span class="xforms-showcalendar > xforms-type-string"></span></span> Yes, that's still a feature, not a bug ;-) > Alex said we would be able to set the id of the input control. I think what he said is that you would be able to set the value of the control by doing something like (Alex, can you check this?): getElementById(id).value = myValue; This does not necessarily imply moving the id to the HTML <input> element... > Also I have made a small work around for the time being, but the > instance value of 'summaryUnderPointInFinancialTreeID' is not being > changed even though the value of the control has changed via > JavaScript > > So both bugs still appear to be there I think Alex should be able to confirm the following: 1) What Javascript syntax is supposed to work to update the value of the control. 2) Whether setting the value in fact causes it to be set in the instance - there may be a bug here. -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 |
Thanks Erik, sorry was rather misleading at first! We do use the code as you
suggested to set the value, but it doesn't appear to be setting the instance. Looking at Logging Events, OPS doesn't appear to notice the change, could I run something in JavaScript to alert OPS to the change? Or is it just a bug? Thanks 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: 17 November 2005 16:30 To: [hidden email] Subject: Re: [ops-users] old instance data coming back to a page -- version 3.0.beta3.200511020401 Ryan Puddephatt wrote: > I'm not trying to change the value of the id with JavaScript Sorry, I misunderstood because your sentence was a little misleading: "[...] the JavaScript [...] doesn't seem to be setting the ID of the html:input control" > <span id="facilityID" class="xforms-control xforms-input"><span > class="xforms-date-display"></span><input type="text" name="facilityID" > value="" class="xforms-type-string"><span class="xforms-showcalendar > xforms-type-string"></span></span> Yes, that's still a feature, not a bug ;-) > Alex said we would be able to set the id of the input control. I think what he said is that you would be able to set the value of the control by doing something like (Alex, can you check this?): getElementById(id).value = myValue; This does not necessarily imply moving the id to the HTML <input> element... > Also I have made a small work around for the time being, but the > instance value of 'summaryUnderPointInFinancialTreeID' is not being > changed even though the value of the control has changed via > JavaScript > > So both bugs still appear to be there I think Alex should be able to confirm the following: 1) What Javascript syntax is supposed to work to update the value of the control. 2) Whether setting the value in fact causes it to be set in the instance - there may be a bug here. -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 |
Hi Erik & Alex,
I have found a little work around, by calling the Xforms-dispatchEvent function after changing the value I have managed to update the instance. Would this be the only way of doing it or could it be included in OPS? Thanks 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: Ryan Puddephatt [mailto:[hidden email]] Sent: 17 November 2005 16:39 To: [hidden email] Subject: RE: [ops-users] old instance data coming back to a page -- version 3.0.beta3.200511020401 Thanks Erik, sorry was rather misleading at first! We do use the code as you suggested to set the value, but it doesn't appear to be setting the instance. Looking at Logging Events, OPS doesn't appear to notice the change, could I run something in JavaScript to alert OPS to the change? Or is it just a bug? Thanks 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: 17 November 2005 16:30 To: [hidden email] Subject: Re: [ops-users] old instance data coming back to a page -- version 3.0.beta3.200511020401 Ryan Puddephatt wrote: > I'm not trying to change the value of the id with JavaScript Sorry, I misunderstood because your sentence was a little misleading: "[...] the JavaScript [...] doesn't seem to be setting the ID of the html:input control" > <span id="facilityID" class="xforms-control xforms-input"><span > class="xforms-date-display"></span><input type="text" name="facilityID" > value="" class="xforms-type-string"><span class="xforms-showcalendar > xforms-type-string"></span></span> Yes, that's still a feature, not a bug ;-) > Alex said we would be able to set the id of the input control. I think what he said is that you would be able to set the value of the control by doing something like (Alex, can you check this?): getElementById(id).value = myValue; This does not necessarily imply moving the id to the HTML <input> element... > Also I have made a small work around for the time being, but the > instance value of 'summaryUnderPointInFinancialTreeID' is not being > changed even though the value of the control has changed via > JavaScript > > So both bugs still appear to be there I think Alex should be able to confirm the following: 1) What Javascript syntax is supposed to work to update the value of the control. 2) Whether setting the value in fact causes it to be set in the instance - there may be a bug here. -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 |
Free forum by Nabble | Edit this page |