remote div diff behavior in 2.1.x
hi,
I fed up guessing so looked at the sources.
The key parameters in this issue are these:
- delay: "How long to wait before fetching the content (in milliseconds)"
- updateFreq: "How often to reload the content (in milliseconds)"
- preload: "Load content when page is loaded"
The closest I could get to the "would be" a BUG was in file:
plugins/dojo/src/main/resources/org/apache/struts2/static/dojo/struts/widget/BindDiv.js
line 258
***
if(this.isShowing() && this.preload && this.updateFreq <= 0 &&
this.delay <= 0) {
this.refresh();
}
***
Obviously if you set either updateFreq or delay > 0 then it would not
refresh upon startup.
I tried modifying that source to:
if(this.isShowing() && (this.preload || (this.updateFreq <= 0 &&
this.delay <= 0))) {
this.refresh();
}
but did not work either, from there on I need more understanding of the
intrinsics of the DOJO library. I will keep digging it further as soon
as I have
a chance.
Any help greatly appreciated.
regards,
Giovanni
PS: will this require to open a JIRA issue?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
remote div diff behavior in 2.1.x
hi, Sorry I tested example1.jsp and it is not the same use-case as mine. If you try example4.jsp in the showcase under Ajax remote DIV you will see the same problem I have happening there i.e. you have to wait 5 seconds while it displays "loading now" which I think is wrong. Now I strongly SUSPECT this is what's going on: - There was a new "delay" parameter which I suppose means to not render the DIV until "delay" time has elapsed. example4.jsp sets "delay" to 1000 millisecs but the delay is of 5000 sharp smells like a BUG. - The updateFreq means after first render how long to wait for the next render which is 5 secs and works fine. By observation I think there is a BUG that "delay" is being ignored and updateFreq is being used as "delay" instead, which explains why you have to wait initially 5 seconds in example4.jsp and not 1 second. Fixing example4.jsp will also fix my problem TIA, Regards, Giovanni - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: remote div diff behavior in 2.1.x
It would be helpful to know a bit more detail such as whether or not you're using XhrPost and progid for XMLHttpRequest connection objectWhich Version of Dojo are you implementing with?Which version Browser?Bedankt Martin __Disclaimer and confidentiality noteEverything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission.> > hi!> > In version 2.0.x the remote DIV UI tag was initially rendering the > content of the DIV by immediately invoking the target action. In version > 2.1.x on the other hand, remote DIV does not initially render the > content of the target action, I did some research and tried using the > new parameter autoStart="true" but does not work either. In version > 2.1.x you have to wait the updateFreq before you see anything rendered ...> > Please have a look at the example with title *"Ajax UI tags were moved > to the new dojo plugin ..."* placed under:> http://cwiki.apache.org/confluence/display/S2WIKI/Troubleshooting+guide+migrating+from+Struts+2.0.x+to+2.1.x> > The example illustrates using the remote DIV in a JSP before and after > migrating to 2.1.x I experience the problem described in exactly that > example.> > TIA,> regards,> Giovanni> > > -> To unsubscribe, e-mail: [EMAIL PROTECTED]> For additional commands, e-mail: [EMAIL PROTECTED]> _ Your smile counts. The more smiles you share, the more we donate. Join in. www.windowslive.com/smile?ocid=TXT_TAGLM_Wave2_oprsmilewlhmtagline
Re: remote div diff behavior in 2.1.x
The showcase 2.1.1 remote DIV example1.jsp works just fine. It immediately calls the action that renders the DIV upon start i.e. you never see the "Initial Content" message because the DIV is rendered immediately. The only difference between my code and the showcase example AFAICT is that I use Tiles but I will need to investigate more ... regards, Giovanni Giovanni Azua wrote: btw Sorry I missed including that I experience this issue with Struts 2.1.1 build yesterday from svn ... I know, I love living on the edge :) no seriously for my app I have only found this little small issue everything else works like a dream :) Best regards, Giovanni Giovanni Azua wrote: hi! In version 2.0.x the remote DIV UI tag was initially rendering the content of the DIV by immediately invoking the target action. In version 2.1.x on the other hand, remote DIV does not initially render the content of the target action, I did some research and tried using the new parameter autoStart="true" but does not work either. In version 2.1.x you have to wait the updateFreq before you see anything rendered ... Please have a look at the example with title *"Ajax UI tags were moved to the new dojo plugin ..."* placed under: http://cwiki.apache.org/confluence/display/S2WIKI/Troubleshooting+guide+migrating+from+Struts+2.0.x+to+2.1.x The example illustrates using the remote DIV in a JSP before and after migrating to 2.1.x I experience the problem described in exactly that example. TIA, regards, Giovanni - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: remote div diff behavior in 2.1.x
btw Sorry I missed including that I experience this issue with Struts 2.1.1 build yesterday from svn ... I know, I love living on the edge :) no seriously for my app I have only found this little small issue everything else works like a dream :) Best regards, Giovanni Giovanni Azua wrote: hi! In version 2.0.x the remote DIV UI tag was initially rendering the content of the DIV by immediately invoking the target action. In version 2.1.x on the other hand, remote DIV does not initially render the content of the target action, I did some research and tried using the new parameter autoStart="true" but does not work either. In version 2.1.x you have to wait the updateFreq before you see anything rendered ... Please have a look at the example with title *"Ajax UI tags were moved to the new dojo plugin ..."* placed under: http://cwiki.apache.org/confluence/display/S2WIKI/Troubleshooting+guide+migrating+from+Struts+2.0.x+to+2.1.x The example illustrates using the remote DIV in a JSP before and after migrating to 2.1.x I experience the problem described in exactly that example. TIA, regards, Giovanni - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
remote div diff behavior in 2.1.x
hi! In version 2.0.x the remote DIV UI tag was initially rendering the content of the DIV by immediately invoking the target action. In version 2.1.x on the other hand, remote DIV does not initially render the content of the target action, I did some research and tried using the new parameter autoStart="true" but does not work either. In version 2.1.x you have to wait the updateFreq before you see anything rendered ... Please have a look at the example with title *"Ajax UI tags were moved to the new dojo plugin ..."* placed under: http://cwiki.apache.org/confluence/display/S2WIKI/Troubleshooting+guide+migrating+from+Struts+2.0.x+to+2.1.x The example illustrates using the remote DIV in a JSP before and after migrating to 2.1.x I experience the problem described in exactly that example. TIA, regards, Giovanni - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
