[OS-webwork] WW-222: Same Id created twice?

Hi, Just by watching the issue about jasper (former WW-222) I just recognized, that the same issue id was used to create a new one. Bug or feature? If the former issue was deleted, then Jira should not reuse the same key for something different or all watchers should be notified about the

[OS-webwork] Multipart SaveDir

Hi WebWork Guys, Seems com.opensymphony.webwork.dispatcher.ServletDispatcher class is caching the value of webwork.multipart.saveDir property (at init() of servlet) and it causes problems when I want to change this prop's value after initialization (at runtime). Attached is the changes I've made

Re: [OS-webwork] WW-222: Same Id created twice?

Scott, thanks for your quick reply. Shall I resubmit the issue or wait until you could track down the problem? cheers, Rainer -- Rainer Hermanns [EMAIL PROTECTED] Woperstr. 34 tel: +49 (0)170 - 3432 912 D-52134 Herzogenrath

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

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

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.

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

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

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

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

[OS-webwork] accessing TreeMap from Velocity page

Hi, Anybody got this problem. Iam gettig velocity exception HashMap class cast exception if i try to access TreeMap like this simpleMap.get($key). Iam not getting error if use the HashMap. Is it something like webwork supporst only accessing HashMaps. Thanks, Ajmal

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

Re: [OS-webwork] Multipart SaveDir

Hey Armond, I recommend that you open a JIRA issue for this and attach the patch. We'll get to it real soon. - Original Message - From: Armond Avanes [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 11:33 PM Subject: [OS-webwork] Multipart SaveDir Hi WebWork

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

Re: [OS-webwork] Re: Application

Watch out folks, Maurice has been infected! :) -Pat - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, June 26, 2003 6:12 PM Subject: [OS-webwork] Re: Application -- Virus Warning Message (on the network) Found virus WORM_SOBIG.E in

[OS-webwork] ScanMail Message: To Recipient virus found or matched file blocking setting.

ScanMail for Microsoft Exchange has taken action on the message, please refer to the contents of this message for further details. Sender = [EMAIL PROTECTED] Recipient(s) = [EMAIL PROTECTED]; Subject = [OS-webwork] Re: Application Scanning Time = 06/26/2003 18:27:17 Engine/Pattern =

[OS-webwork] Report to Recipient(s)

Incident Information:- Originator: [EMAIL PROTECTED] Recipients: [EMAIL PROTECTED] Subject:[OS-webwork] Re: Application The file your_details.zip (details.pif) you received was infected with the W32/[EMAIL PROTECTED] virus and was deleted.