RE: [OS-webwork] Displaying a progress page
Maybe with some kind of scheduler. Because I'm using an EJB container I'll try JMS. Thanks again ! Lars Well, for us we queue a JMS message. I'm not sure of another way to start an asynch process in the J2EE spec -Original Message- From: Lars Fischer [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 3:42 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Displaying a progress page Jason, thanks for the reply ! Any hint how you start the asynchronous process ? Lars If you can start it up as an asynchronous process, you can use the trick of having a progress page which checks some state, such as a database or something in the session, and shows the progress bar or just a processing... and have it refresh itself using a meta-refresh if things aren't done... If the process is done you can forward to a final status page. We've used this technique pretty successfully. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 8:31 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Displaying a progress page Does anyone have a good idea how to display a temporary progress page in WW 1.x ? I have a form where users can define paremeters for an import of data into the local database. After submitting the page the import method is started. This process may take a while so I want to show a general progress page saying that the import is running. After finishing the import I want to return to the original page where users can start an import. Does anyone know how to do this ? The problem seems to be that WW is displaying the result-view AFTER the whole action has finished. Thanks in advance Lars --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
RE: [OS-webwork] Displaying a progress page
I never use JavaScript because my application has to work the same way even if JavaScript is turned off. I haven't actually done this yet (but am planning to) -- however, can't you take care of this behavior with dhtml?? It seems like you could call a javascript function on submit that pulled a layer (actully css-pos) to the top. That layer would say in progress with a pretty animated gif or have some neat little javascript progress bar. The javascript would then submit the form. When it's done, the browser updates. This seems like it will work and is likely better than the server side solutions. Is there something I'm missing?? BTW, I think this is how expedia used to do it. LES -Original Message- From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 7:01 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Displaying a progress page Uhm, well why not just make your task runnable and run it in a new thread? :) Or you could use a util.Timer. Another (nicest IMHO) alternative is to make it a scheduled task and use something like Quartz to kick it off. M On 26/6/03 6:05 AM, Jason Carreira ([EMAIL PROTECTED]) penned the words: Well, for us we queue a JMS message. I'm not sure of another way to start an asynch process in the J2EE spec -Original Message- From: Lars Fischer [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 3:42 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Displaying a progress page Jason, thanks for the reply ! Any hint how you start the asynchronous process ? Lars If you can start it up as an asynchronous process, you can use the trick of having a progress page which checks some state, such as a database or something in the session, and shows the progress bar or just a processing... and have it refresh itself using a meta-refresh if things aren't done... If the process is done you can forward to a final status page. We've used this technique pretty successfully. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 8:31 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Displaying a progress page Does anyone have a good idea how to display a temporary progress page in WW 1.x ? I have a form where users can define paremeters for an import of data into the local database. After submitting the page the import method is started. This process may take a while so I want to show a general progress page saying that the import is running. After finishing the import I want to return to the original page where users can start an import. Does anyone know how to do this ? The problem seems to be that WW is displaying the result-view AFTER the whole action has finished. Thanks in advance Lars --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] Displaying a progress page
The in progress page is shown when the process is finished (the action has completed). As Jason said you have to start thew process asynchronous. Don't forget our cool new HTTP 204 trick that we just learned. Display the in progress page, and then have a refresh ping the server periodically. If its still in progress, just return the 204 header... so the page doesnt actually reload until its done. -Tim. - Original Message - From: Mike Cannon-Brookes [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 9:32 PM Subject: Re: [OS-webwork] Displaying a progress page Les, You could do it using DHTML, but I'm fairly sure that's not how Expedia do it. It's a LOT more error prone to do that way :) FWIW we're investigating creating a generic 'long running task' system for JIRA - used for tasks like reindexing and importing/exporting data which take a long time. I think using a WW action this should be relatively easy to do. Mike On 26/6/03 10:13 AM, [EMAIL PROTECTED] ([EMAIL PROTECTED]) penned the words: I haven't actually done this yet (but am planning to) -- however, can't you take care of this behavior with dhtml?? It seems like you could call a javascript function on submit that pulled a layer (actully css-pos) to the top. That layer would say in progress with a pretty animated gif or have some neat little javascript progress bar. The javascript would then submit the form. When it's done, the browser updates. This seems like it will work and is likely better than the server side solutions. Is there something I'm missing?? BTW, I think this is how expedia used to do it. LES -Original Message- From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 7:01 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Displaying a progress page Uhm, well why not just make your task runnable and run it in a new thread? :) Or you could use a util.Timer. Another (nicest IMHO) alternative is to make it a scheduled task and use something like Quartz to kick it off. M On 26/6/03 6:05 AM, Jason Carreira ([EMAIL PROTECTED]) penned the words: Well, for us we queue a JMS message. I'm not sure of another way to start an asynch process in the J2EE spec -Original Message- From: Lars Fischer [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 3:42 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Displaying a progress page Jason, thanks for the reply ! Any hint how you start the asynchronous process ? Lars If you can start it up as an asynchronous process, you can use the trick of having a progress page which checks some state, such as a database or something in the session, and shows the progress bar or just a processing... and have it refresh itself using a meta-refresh if things aren't done... If the process is done you can forward to a final status page. We've used this technique pretty successfully. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 8:31 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Displaying a progress page Does anyone have a good idea how to display a temporary progress page in WW 1.x ? I have a form where users can define paremeters for an import of data into the local database. After submitting the page the import method is started. This process may take a while so I want to show a general progress page saying that the import is running. After finishing the import I want to return to the original page where users can start an import. Does anyone know how to do this ? The problem seems to be that WW is displaying the result-view AFTER the whole action has finished. Thanks in advance Lars --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https
RE: [OS-webwork] Displaying a progress page
I see your point, Mike. I was thinking in terms of medium length tasks, not truly long running. You mentioned that the javascript approach is very error prone. Are you referring to differences between browsers, or is there something else? In terms of very long tasks, I actually did something like this with a retirement planning company that had to run monte-carlo simulations for a web app. From a backend perspective, we used jini and javaspaces to execute the actions and retrieve the results. In terms of the web side, which was not related to ww, we did not have the lack of javascript constraints. So, it was just a matter of having the browser's timeout long enough. Where javascript is not allowed, the 204 suggestion that Tim made seems like a pretty good idea. However, that may also violate the same requirement that motivates the banishment of javascript. Lars, just out of curiosity, what is driving the requirement for not supporting the complete browser model (no javascript)? -Original Message- From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 9:33 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Displaying a progress page Les, You could do it using DHTML, but I'm fairly sure that's not how Expedia do it. It's a LOT more error prone to do that way :) FWIW we're investigating creating a generic 'long running task' system for JIRA - used for tasks like reindexing and importing/exporting data which take a long time. I think using a WW action this should be relatively easy to do. Mike On 26/6/03 10:13 AM, [EMAIL PROTECTED] ([EMAIL PROTECTED]) penned the words: I haven't actually done this yet (but am planning to) -- however, can't you take care of this behavior with dhtml?? It seems like you could call a javascript function on submit that pulled a layer (actully css-pos) to the top. That layer would say in progress with a pretty animated gif or have some neat little javascript progress bar. The javascript would then submit the form. When it's done, the browser updates. This seems like it will work and is likely better than the server side solutions. Is there something I'm missing?? BTW, I think this is how expedia used to do it. LES -Original Message- From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 7:01 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Displaying a progress page Uhm, well why not just make your task runnable and run it in a new thread? :) Or you could use a util.Timer. Another (nicest IMHO) alternative is to make it a scheduled task and use something like Quartz to kick it off. M On 26/6/03 6:05 AM, Jason Carreira ([EMAIL PROTECTED]) penned the words: Well, for us we queue a JMS message. I'm not sure of another way to start an asynch process in the J2EE spec -Original Message- From: Lars Fischer [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 3:42 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Displaying a progress page Jason, thanks for the reply ! Any hint how you start the asynchronous process ? Lars If you can start it up as an asynchronous process, you can use the trick of having a progress page which checks some state, such as a database or something in the session, and shows the progress bar or just a processing... and have it refresh itself using a meta-refresh if things aren't done... If the process is done you can forward to a final status page. We've used this technique pretty successfully. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 8:31 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Displaying a progress page Does anyone have a good idea how to display a temporary progress page in WW 1.x ? I have a form where users can define paremeters for an import of data into the local database. After submitting the page the import method is started. This process may take a while so I want to show a general progress page saying that the import is running. After finishing the import I want to return to the original page where users can start an import. Does anyone know how to do this ? The problem seems to be that WW is displaying the result-view AFTER the whole action has finished. Thanks in advance Lars --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email
RE: [OS-webwork] Displaying a progress page
Lars, just out of curiosity, what is driving the requirement for not supporting the complete browser model (no javascript)? These are some of the reasons: - some IT departments do not allow JavaScript (Active Scripting) for security reasons - my applications should work with the most common browsers (e. g. I use Firebird with JavaScript turned off) and there are big differences between several browsers so it's not THE browser model - I don't want to mix user interfaces with application logic What do the others think about using JavaScript in J2EE applications ? Is it 'allowed' ? Cheers Lars -Original Message- From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 9:33 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Displaying a progress page Les, You could do it using DHTML, but I'm fairly sure that's not how Expedia do it. It's a LOT more error prone to do that way :) FWIW we're investigating creating a generic 'long running task' system for JIRA - used for tasks like reindexing and importing/exporting data which take a long time. I think using a WW action this should be relatively easy to do. Mike On 26/6/03 10:13 AM, [EMAIL PROTECTED] ([EMAIL PROTECTED]) penned the words: I haven't actually done this yet (but am planning to) -- however, can't you take care of this behavior with dhtml?? It seems like you could call a javascript function on submit that pulled a layer (actully css-pos) to the top. That layer would say in progress with a pretty animated gif or have some neat little javascript progress bar. The javascript would then submit the form. When it's done, the browser updates. This seems like it will work and is likely better than the server side solutions. Is there something I'm missing?? BTW, I think this is how expedia used to do it. LES -Original Message- From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 7:01 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Displaying a progress page Uhm, well why not just make your task runnable and run it in a new thread? :) Or you could use a util.Timer. Another (nicest IMHO) alternative is to make it a scheduled task and use something like Quartz to kick it off. M On 26/6/03 6:05 AM, Jason Carreira ([EMAIL PROTECTED]) penned the words: Well, for us we queue a JMS message. I'm not sure of another way to start an asynch process in the J2EE spec -Original Message- From: Lars Fischer [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 3:42 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Displaying a progress page Jason, thanks for the reply ! Any hint how you start the asynchronous process ? Lars If you can start it up as an asynchronous process, you can use the trick of having a progress page which checks some state, such as a database or something in the session, and shows the progress bar or just a processing... and have it refresh itself using a meta-refresh if things aren't done... If the process is done you can forward to a final status page. We've used this technique pretty successfully. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 8:31 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Displaying a progress page Does anyone have a good idea how to display a temporary progress page in WW 1.x ? I have a form where users can define paremeters for an import of data into the local database. After submitting the page the import method is started. This process may take a while so I want to show a general progress page saying that the import is running. After finishing the import I want to return to the original page where users can start an import. Does anyone know how to do this ? The problem seems to be that WW is displaying the result-view AFTER the whole action has finished. Thanks in advance Lars --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
RE: [OS-webwork] Displaying a progress page
IMO, if you want to create a web application that acts like a desktop application, JavaScript is your best buddy. If you want to create a web application that acts like a web site (click, wait, click, wait) then don't use it. Matt -Original Message- From: Lars Fischer [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2003 1:14 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Displaying a progress page Lars, just out of curiosity, what is driving the requirement for not supporting the complete browser model (no javascript)? These are some of the reasons: - some IT departments do not allow JavaScript (Active Scripting) for security reasons - my applications should work with the most common browsers (e. g. I use Firebird with JavaScript turned off) and there are big differences between several browsers so it's not THE browser model - I don't want to mix user interfaces with application logic What do the others think about using JavaScript in J2EE applications ? Is it 'allowed' ? Cheers Lars -Original Message- From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 9:33 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Displaying a progress page Les, You could do it using DHTML, but I'm fairly sure that's not how Expedia do it. It's a LOT more error prone to do that way :) FWIW we're investigating creating a generic 'long running task' system for JIRA - used for tasks like reindexing and importing/exporting data which take a long time. I think using a WW action this should be relatively easy to do. Mike On 26/6/03 10:13 AM, [EMAIL PROTECTED] ([EMAIL PROTECTED]) penned the words: I haven't actually done this yet (but am planning to) -- however, can't you take care of this behavior with dhtml?? It seems like you could call a javascript function on submit that pulled a layer (actully css-pos) to the top. That layer would say in progress with a pretty animated gif or have some neat little javascript progress bar. The javascript would then submit the form. When it's done, the browser updates. This seems like it will work and is likely better than the server side solutions. Is there something I'm missing?? BTW, I think this is how expedia used to do it. LES -Original Message- From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 7:01 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Displaying a progress page Uhm, well why not just make your task runnable and run it in a new thread? :) Or you could use a util.Timer. Another (nicest IMHO) alternative is to make it a scheduled task and use something like Quartz to kick it off. M On 26/6/03 6:05 AM, Jason Carreira ([EMAIL PROTECTED]) penned the words: Well, for us we queue a JMS message. I'm not sure of another way to start an asynch process in the J2EE spec -Original Message- From: Lars Fischer [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 3:42 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Displaying a progress page Jason, thanks for the reply ! Any hint how you start the asynchronous process ? Lars If you can start it up as an asynchronous process, you can use the trick of having a progress page which checks some state, such as a database or something in the session, and shows the progress bar or just a processing... and have it refresh itself using a meta-refresh if things aren't done... If the process is done you can forward to a final status page. We've used this technique pretty successfully. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 8:31 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Displaying a progress page Does anyone have a good idea how to display a temporary progress page in WW 1.x ? I have a form where users can define paremeters for an import of data into the local database. After submitting the page the import method is started. This process may take a while so I want to show a general progress page saying that the import is running. After finishing the import I want to return to the original page where users can start an import. Does anyone know how to do this ? The problem seems to be that WW is displaying the result-view AFTER the whole action has finished. Thanks in advance Lars --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL
Re: [OS-webwork] Displaying a progress page
Wow, are you the famous man who's name turned into a verb ? Well the two are completely unrelated. J2EE has no user interface guidelines, it is not specific to browsers (it does define servlets which deal with http though, but that's as 'browsery' as it gets). So the question of how well javascript and j2ee mix is akin to asking how well buildings and leather chairs mix. I guess you are right on this but what about JSP and MVC. Isn't it good practice not to mix the users interface with application logic ? You can use javascript if you want, it depends entirely on your target client. Is it an internal project where you can guarantee that everyone will be using IE? Do you care about supporting the 8% of people in the world who don't use IE? Yes I take care about myself ... and you know you're always lonesome at the top :-) How about the three people who use Opera (hehe)? I really don't care about Opera (hehehehe). Hani, I like your writings. Really refreshing ! On Thursday, June 26, 2003, at 03:13 PM, Lars Fischer wrote: Lars, just out of curiosity, what is driving the requirement for not supporting the complete browser model (no javascript)? These are some of the reasons: - some IT departments do not allow JavaScript (Active Scripting) for security reasons - my applications should work with the most common browsers (e. g. I use Firebird with JavaScript turned off) and there are big differences between several browsers so it's not THE browser model - I don't want to mix user interfaces with application logic What do the others think about using JavaScript in J2EE applications ? Is it 'allowed' ? Cheers Lars -Original Message- From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 9:33 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Displaying a progress page Les, You could do it using DHTML, but I'm fairly sure that's not how Expedia do it. It's a LOT more error prone to do that way :) FWIW we're investigating creating a generic 'long running task' system for JIRA - used for tasks like reindexing and importing/exporting data which take a long time. I think using a WW action this should be relatively easy to do. Mike On 26/6/03 10:13 AM, [EMAIL PROTECTED] ([EMAIL PROTECTED]) penned the words: I haven't actually done this yet (but am planning to) -- however, can't you take care of this behavior with dhtml?? It seems like you could call a javascript function on submit that pulled a layer (actully css-pos) to the top. That layer would say in progress with a pretty animated gif or have some neat little javascript progress bar. The javascript would then submit the form. When it's done, the browser updates. This seems like it will work and is likely better than the server side solutions. Is there something I'm missing?? BTW, I think this is how expedia used to do it. LES -Original Message- From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 7:01 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Displaying a progress page Uhm, well why not just make your task runnable and run it in a new thread? :) Or you could use a util.Timer. Another (nicest IMHO) alternative is to make it a scheduled task and use something like Quartz to kick it off. M On 26/6/03 6:05 AM, Jason Carreira ([EMAIL PROTECTED]) penned the words: Well, for us we queue a JMS message. I'm not sure of another way to start an asynch process in the J2EE spec -Original Message- From: Lars Fischer [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 3:42 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Displaying a progress page Jason, thanks for the reply ! Any hint how you start the asynchronous process ? Lars If you can start it up as an asynchronous process, you can use the trick of having a progress page which checks some state, such as a database or something in the session, and shows the progress bar or just a processing... and have it refresh itself using a meta-refresh if things aren't done... If the process is done you can forward to a final status page. We've used this technique pretty successfully. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 8:31 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Displaying a progress page Does anyone have a good idea how to display a temporary progress page in WW 1.x ? I have a form where users can define paremeters for an import of data into the local database. After submitting the page the import method is started. This process may take a while so I want to show a general progress page saying that the import is running. After
Re: [OS-webwork] Displaying a progress page
Nor should you, to be honest. You're trying to jam a square peg into a round hole. Yes, you can get pretty far, but in the end, a user will get an email with a link, and will click on it and boom, their browser window with all your lovely javascript is now replaced. Or maybe the user gets sick of it all and decides to just close the browser, or browse to another site. Sure, you could define an onunload, but that makes it an uncomfortable user interface, because it's surprising the user and doing something unexpected. On Thursday, June 26, 2003, at 05:55 PM, Lars Fischer wrote: These are good arguments. But I still think you can never reach the same functionality with a browser based app compared to 'traditional' (native) clients. IMO, if you want to create a web application that acts like a desktop application, JavaScript is your best buddy. If you want to create a web application that acts like a web site (click, wait, click, wait) then don't use it. Matt -Original Message- From: Lars Fischer [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2003 1:14 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Displaying a progress page Lars, just out of curiosity, what is driving the requirement for not supporting the complete browser model (no javascript)? These are some of the reasons: - some IT departments do not allow JavaScript (Active Scripting) for security reasons - my applications should work with the most common browsers (e. g. I use Firebird with JavaScript turned off) and there are big differences between several browsers so it's not THE browser model - I don't want to mix user interfaces with application logic What do the others think about using JavaScript in J2EE applications ? Is it 'allowed' ? Cheers Lars -Original Message- From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 9:33 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Displaying a progress page Les, You could do it using DHTML, but I'm fairly sure that's not how Expedia do it. It's a LOT more error prone to do that way :) FWIW we're investigating creating a generic 'long running task' system for JIRA - used for tasks like reindexing and importing/exporting data which take a long time. I think using a WW action this should be relatively easy to do. Mike On 26/6/03 10:13 AM, [EMAIL PROTECTED] ([EMAIL PROTECTED]) penned the words: I haven't actually done this yet (but am planning to) -- however, can't you take care of this behavior with dhtml?? It seems like you could call a javascript function on submit that pulled a layer (actully css-pos) to the top. That layer would say in progress with a pretty animated gif or have some neat little javascript progress bar. The javascript would then submit the form. When it's done, the browser updates. This seems like it will work and is likely better than the server side solutions. Is there something I'm missing?? BTW, I think this is how expedia used to do it. LES -Original Message- From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 7:01 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Displaying a progress page Uhm, well why not just make your task runnable and run it in a new thread? :) Or you could use a util.Timer. Another (nicest IMHO) alternative is to make it a scheduled task and use something like Quartz to kick it off. M On 26/6/03 6:05 AM, Jason Carreira ([EMAIL PROTECTED]) penned the words: Well, for us we queue a JMS message. I'm not sure of another way to start an asynch process in the J2EE spec -Original Message- From: Lars Fischer [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 3:42 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Displaying a progress page Jason, thanks for the reply ! Any hint how you start the asynchronous process ? Lars If you can start it up as an asynchronous process, you can use the trick of having a progress page which checks some state, such as a database or something in the session, and shows the progress bar or just a processing... and have it refresh itself using a meta-refresh if things aren't done... If the process is done you can forward to a final status page. We've used this technique pretty successfully. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 8:31 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Displaying a progress page Does anyone have a good idea how to display a temporary progress page in WW 1.x ? I have a form where users can define paremeters for an import of data into the local database. After submitting the page the import method is started. This process may take a while so I want to show a general progress page saying that the import is running. After finishing the import I want to return to the original page where users can start an import. Does anyone know how to do
RE: [OS-webwork] Displaying a progress page
Absolutely. We agree!! :) If you need truly rich functionality, you should be writing a client app. However, if you are required to be web and can do javascript, then use it. I'm just suggesting that something as simple as bringing a div to the front is very easy to make cross platform and may be a 10 minute fix to your problem (as opposed to an elaborate server solution). I am not suggesting to go ape wild and use it everywhere. :) -Original Message- From: Lars Fischer [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2003 5:55 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Displaying a progress page These are good arguments. But I still think you can never reach the same functionality with a browser based app compared to 'traditional' (native) clients. IMO, if you want to create a web application that acts like a desktop application, JavaScript is your best buddy. If you want to create a web application that acts like a web site (click, wait, click, wait) then don't use it. Matt -Original Message- From: Lars Fischer [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2003 1:14 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Displaying a progress page Lars, just out of curiosity, what is driving the requirement for not supporting the complete browser model (no javascript)? These are some of the reasons: - some IT departments do not allow JavaScript (Active Scripting) for security reasons - my applications should work with the most common browsers (e. g. I use Firebird with JavaScript turned off) and there are big differences between several browsers so it's not THE browser model - I don't want to mix user interfaces with application logic What do the others think about using JavaScript in J2EE applications ? Is it 'allowed' ? Cheers Lars -Original Message- From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 9:33 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Displaying a progress page Les, You could do it using DHTML, but I'm fairly sure that's not how Expedia do it. It's a LOT more error prone to do that way :) FWIW we're investigating creating a generic 'long running task' system for JIRA - used for tasks like reindexing and importing/exporting data which take a long time. I think using a WW action this should be relatively easy to do. Mike On 26/6/03 10:13 AM, [EMAIL PROTECTED] ([EMAIL PROTECTED]) penned the words: I haven't actually done this yet (but am planning to) -- however, can't you take care of this behavior with dhtml?? It seems like you could call a javascript function on submit that pulled a layer (actully css-pos) to the top. That layer would say in progress with a pretty animated gif or have some neat little javascript progress bar. The javascript would then submit the form. When it's done, the browser updates. This seems like it will work and is likely better than the server side solutions. Is there something I'm missing?? BTW, I think this is how expedia used to do it. LES -Original Message- From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 7:01 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Displaying a progress page Uhm, well why not just make your task runnable and run it in a new thread? :) Or you could use a util.Timer. Another (nicest IMHO) alternative is to make it a scheduled task and use something like Quartz to kick it off. M On 26/6/03 6:05 AM, Jason Carreira ([EMAIL PROTECTED]) penned the words: Well, for us we queue a JMS message. I'm not sure of another way to start an asynch process in the J2EE spec -Original Message- From: Lars Fischer [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 3:42 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Displaying a progress page Jason, thanks for the reply ! Any hint how you start the asynchronous process ? Lars If you can start it up as an asynchronous process, you can use the trick of having a progress page which checks some state, such as a database or something in the session, and shows the progress bar or just a processing... and have it refresh itself using a meta-refresh if things aren't done... If the process is done you can forward to a final status page. We've used this technique pretty successfully. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 8:31 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Displaying a progress page Does anyone have a good idea how to display a temporary progress page in WW 1.x ? I have a form where users can define paremeters
RE: [OS-webwork] Displaying a progress page
If you can start it up as an asynchronous process, you can use the trick of having a progress page which checks some state, such as a database or something in the session, and shows the progress bar or just a processing... and have it refresh itself using a meta-refresh if things aren't done... If the process is done you can forward to a final status page. We've used this technique pretty successfully. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 8:31 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Displaying a progress page Does anyone have a good idea how to display a temporary progress page in WW 1.x ? I have a form where users can define paremeters for an import of data into the local database. After submitting the page the import method is started. This process may take a while so I want to show a general progress page saying that the import is running. After finishing the import I want to return to the original page where users can start an import. Does anyone know how to do this ? The problem seems to be that WW is displaying the result-view AFTER the whole action has finished. Thanks in advance Lars --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
RE: [OS-webwork] Displaying a progress page
Jason, thanks for the reply ! Any hint how you start the asynchronous process ? Lars If you can start it up as an asynchronous process, you can use the trick of having a progress page which checks some state, such as a database or something in the session, and shows the progress bar or just a processing... and have it refresh itself using a meta-refresh if things aren't done... If the process is done you can forward to a final status page. We've used this technique pretty successfully. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 8:31 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Displaying a progress page Does anyone have a good idea how to display a temporary progress page in WW 1.x ? I have a form where users can define paremeters for an import of data into the local database. After submitting the page the import method is started. This process may take a while so I want to show a general progress page saying that the import is running. After finishing the import I want to return to the original page where users can start an import. Does anyone know how to do this ? The problem seems to be that WW is displaying the result-view AFTER the whole action has finished. Thanks in advance Lars --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
RE: [OS-webwork] Displaying a progress page
Well, for us we queue a JMS message. I'm not sure of another way to start an asynch process in the J2EE spec -Original Message- From: Lars Fischer [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 3:42 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Displaying a progress page Jason, thanks for the reply ! Any hint how you start the asynchronous process ? Lars If you can start it up as an asynchronous process, you can use the trick of having a progress page which checks some state, such as a database or something in the session, and shows the progress bar or just a processing... and have it refresh itself using a meta-refresh if things aren't done... If the process is done you can forward to a final status page. We've used this technique pretty successfully. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 8:31 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Displaying a progress page Does anyone have a good idea how to display a temporary progress page in WW 1.x ? I have a form where users can define paremeters for an import of data into the local database. After submitting the page the import method is started. This process may take a while so I want to show a general progress page saying that the import is running. After finishing the import I want to return to the original page where users can start an import. Does anyone know how to do this ? The problem seems to be that WW is displaying the result-view AFTER the whole action has finished. Thanks in advance Lars --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] Displaying a progress page
Uhm, well why not just make your task runnable and run it in a new thread? :) Or you could use a util.Timer. Another (nicest IMHO) alternative is to make it a scheduled task and use something like Quartz to kick it off. M On 26/6/03 6:05 AM, Jason Carreira ([EMAIL PROTECTED]) penned the words: Well, for us we queue a JMS message. I'm not sure of another way to start an asynch process in the J2EE spec -Original Message- From: Lars Fischer [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 3:42 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Displaying a progress page Jason, thanks for the reply ! Any hint how you start the asynchronous process ? Lars If you can start it up as an asynchronous process, you can use the trick of having a progress page which checks some state, such as a database or something in the session, and shows the progress bar or just a processing... and have it refresh itself using a meta-refresh if things aren't done... If the process is done you can forward to a final status page. We've used this technique pretty successfully. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 8:31 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Displaying a progress page Does anyone have a good idea how to display a temporary progress page in WW 1.x ? I have a form where users can define paremeters for an import of data into the local database. After submitting the page the import method is started. This process may take a while so I want to show a general progress page saying that the import is running. After finishing the import I want to return to the original page where users can start an import. Does anyone know how to do this ? The problem seems to be that WW is displaying the result-view AFTER the whole action has finished. Thanks in advance Lars --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
RE: [OS-webwork] Displaying a progress page
I haven't actually done this yet (but am planning to) -- however, can't you take care of this behavior with dhtml?? It seems like you could call a javascript function on submit that pulled a layer (actully css-pos) to the top. That layer would say in progress with a pretty animated gif or have some neat little javascript progress bar. The javascript would then submit the form. When it's done, the browser updates. This seems like it will work and is likely better than the server side solutions. Is there something I'm missing?? BTW, I think this is how expedia used to do it. LES -Original Message- From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 7:01 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Displaying a progress page Uhm, well why not just make your task runnable and run it in a new thread? :) Or you could use a util.Timer. Another (nicest IMHO) alternative is to make it a scheduled task and use something like Quartz to kick it off. M On 26/6/03 6:05 AM, Jason Carreira ([EMAIL PROTECTED]) penned the words: Well, for us we queue a JMS message. I'm not sure of another way to start an asynch process in the J2EE spec -Original Message- From: Lars Fischer [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 3:42 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Displaying a progress page Jason, thanks for the reply ! Any hint how you start the asynchronous process ? Lars If you can start it up as an asynchronous process, you can use the trick of having a progress page which checks some state, such as a database or something in the session, and shows the progress bar or just a processing... and have it refresh itself using a meta-refresh if things aren't done... If the process is done you can forward to a final status page. We've used this technique pretty successfully. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 8:31 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Displaying a progress page Does anyone have a good idea how to display a temporary progress page in WW 1.x ? I have a form where users can define paremeters for an import of data into the local database. After submitting the page the import method is started. This process may take a while so I want to show a general progress page saying that the import is running. After finishing the import I want to return to the original page where users can start an import. Does anyone know how to do this ? The problem seems to be that WW is displaying the result-view AFTER the whole action has finished. Thanks in advance Lars --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed
Re: [OS-webwork] Displaying a progress page
Les, You could do it using DHTML, but I'm fairly sure that's not how Expedia do it. It's a LOT more error prone to do that way :) FWIW we're investigating creating a generic 'long running task' system for JIRA - used for tasks like reindexing and importing/exporting data which take a long time. I think using a WW action this should be relatively easy to do. Mike On 26/6/03 10:13 AM, [EMAIL PROTECTED] ([EMAIL PROTECTED]) penned the words: I haven't actually done this yet (but am planning to) -- however, can't you take care of this behavior with dhtml?? It seems like you could call a javascript function on submit that pulled a layer (actully css-pos) to the top. That layer would say in progress with a pretty animated gif or have some neat little javascript progress bar. The javascript would then submit the form. When it's done, the browser updates. This seems like it will work and is likely better than the server side solutions. Is there something I'm missing?? BTW, I think this is how expedia used to do it. LES -Original Message- From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 7:01 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Displaying a progress page Uhm, well why not just make your task runnable and run it in a new thread? :) Or you could use a util.Timer. Another (nicest IMHO) alternative is to make it a scheduled task and use something like Quartz to kick it off. M On 26/6/03 6:05 AM, Jason Carreira ([EMAIL PROTECTED]) penned the words: Well, for us we queue a JMS message. I'm not sure of another way to start an asynch process in the J2EE spec -Original Message- From: Lars Fischer [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 3:42 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Displaying a progress page Jason, thanks for the reply ! Any hint how you start the asynchronous process ? Lars If you can start it up as an asynchronous process, you can use the trick of having a progress page which checks some state, such as a database or something in the session, and shows the progress bar or just a processing... and have it refresh itself using a meta-refresh if things aren't done... If the process is done you can forward to a final status page. We've used this technique pretty successfully. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 8:31 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Displaying a progress page Does anyone have a good idea how to display a temporary progress page in WW 1.x ? I have a form where users can define paremeters for an import of data into the local database. After submitting the page the import method is started. This process may take a while so I want to show a general progress page saying that the import is running. After finishing the import I want to return to the original page where users can start an import. Does anyone know how to do this ? The problem seems to be that WW is displaying the result-view AFTER the whole action has finished. Thanks in advance Lars --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http
Re: [OS-webwork] Displaying a progress page
Don't forget our cool new HTTP 204 trick that we just learned. Display the in progress page, and then have a refresh ping the server periodically. If its still in progress, just return the 204 header... so the page doesnt actually reload until its done. -Tim. - Original Message - From: Mike Cannon-Brookes [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 9:32 PM Subject: Re: [OS-webwork] Displaying a progress page Les, You could do it using DHTML, but I'm fairly sure that's not how Expedia do it. It's a LOT more error prone to do that way :) FWIW we're investigating creating a generic 'long running task' system for JIRA - used for tasks like reindexing and importing/exporting data which take a long time. I think using a WW action this should be relatively easy to do. Mike On 26/6/03 10:13 AM, [EMAIL PROTECTED] ([EMAIL PROTECTED]) penned the words: I haven't actually done this yet (but am planning to) -- however, can't you take care of this behavior with dhtml?? It seems like you could call a javascript function on submit that pulled a layer (actully css-pos) to the top. That layer would say in progress with a pretty animated gif or have some neat little javascript progress bar. The javascript would then submit the form. When it's done, the browser updates. This seems like it will work and is likely better than the server side solutions. Is there something I'm missing?? BTW, I think this is how expedia used to do it. LES -Original Message- From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 7:01 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Displaying a progress page Uhm, well why not just make your task runnable and run it in a new thread? :) Or you could use a util.Timer. Another (nicest IMHO) alternative is to make it a scheduled task and use something like Quartz to kick it off. M On 26/6/03 6:05 AM, Jason Carreira ([EMAIL PROTECTED]) penned the words: Well, for us we queue a JMS message. I'm not sure of another way to start an asynch process in the J2EE spec -Original Message- From: Lars Fischer [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 3:42 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] Displaying a progress page Jason, thanks for the reply ! Any hint how you start the asynchronous process ? Lars If you can start it up as an asynchronous process, you can use the trick of having a progress page which checks some state, such as a database or something in the session, and shows the progress bar or just a processing... and have it refresh itself using a meta-refresh if things aren't done... If the process is done you can forward to a final status page. We've used this technique pretty successfully. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 8:31 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Displaying a progress page Does anyone have a good idea how to display a temporary progress page in WW 1.x ? I have a form where users can define paremeters for an import of data into the local database. After submitting the page the import method is started. This process may take a while so I want to show a general progress page saying that the import is running. After finishing the import I want to return to the original page where users can start an import. Does anyone know how to do this ? The problem seems to be that WW is displaying the result-view AFTER the whole action has finished. Thanks in advance Lars --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10
