[OS-webwork] Undeliverable: hello

2004-02-08 Thread System Administrator
Your message To: [EMAIL PROTECTED] Subject: hello Sent:Sun, 8 Feb 2004 13:44:16 +0530 did not reach the following recipient(s): [EMAIL PROTECTED] on Sun, 8 Feb 2004 13:46:28 +0530 The recipient name is not recognized The MTS-ID of the original message is: c=us;a=

[OS-webwork] Undeliverable: hello

2004-02-08 Thread System Administrator
Your message To: [EMAIL PROTECTED] Subject: hello Sent:Sun, 8 Feb 2004 15:52:10 +0100 did not reach the following recipient(s): [EMAIL PROTECTED] on Sun, 8 Feb 2004 15:52:01 +0100 The recipient name is not recognized The MTS-ID of the original message is: c=be;a=

[OS-webwork] Mail delivery failed: returning message to sender

2004-02-08 Thread Mail Delivery System
|- Failed addresses follow: -| [EMAIL PROTECTED] unknown user / Teilnehmer existiert nicht |--- Message text follows: (body too large, truncated) --| Received: from lists.sourceforge.net ([68.167.86.91]) by mailin06.sul.t-online.de

RE: [OS-webwork] Jakarta Common Validator vs XWork Validator

2004-02-08 Thread Jason Carreira
You should be able to, except I don't know how the error messages are added... You'll need to bridge that into the error messages on your Action. -Original Message- From: Frans Thamura [mailto:[EMAIL PROTECTED] Sent: Sunday, February 08, 2004 12:07 AM To: [EMAIL PROTECTED] Subject:

RE: [OS-webwork] TurbineScreen implementation with WW

2004-02-08 Thread Jason Carreira
Can you describe what it does? -Original Message- From: Frans Thamura [mailto:[EMAIL PROTECTED] Sent: Sunday, February 08, 2004 12:10 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] TurbineScreen implementation with WW Hi I want to implement Turbine Screen with WW, as a

[OS-webwork] WebWork 2.0 Released

2004-02-08 Thread Patrick Lightbody
I'm pleased to announce the release of WebWork 2.0. You can download it at: https://webwork.dev.java.net/files/documents/693/2886/webwork-2.0.zip XWork 1.0 has also been released and is available at: https://xwork.dev.java.net/files/documents/709/2885/xwork-1.0.zip Thank you to everyone who

Re: [OS-webwork] WebWork 2.0 Released

2004-02-08 Thread Michael Blake Day
I'm dreaming, right? - Original Message - From: Patrick Lightbody To: WebWork Sent: Sunday, February 08, 2004 10:52 PM Subject: [OS-webwork] WebWork 2.0 Released I'm pleased to announce the release of WebWork 2.0. You can download

Re: [OS-webwork] WebWork 2.0 Released

2004-02-08 Thread Anoop Ranganath
Congratulations on the release! I appreciate all the work you guys have put into WebWork/XWork, and I look forward to what's coming next. Anoop On Feb 8, 2004, at 10:52 PM, Patrick Lightbody wrote: I'm pleased to announce the release of WebWork 2.0. You can download it at:

[OS-webwork] Intended roadmap for webwork project?

2004-02-08 Thread Wayland Chan
Hello, I'd like to ask the core team what their intentions are for the webwork platform. It confuses me greatly that we have two distinctly different frameworks, maintained by two completely differently teams, using essentially the same name, and basically doing the same thing. Do you guys

Re: [OS-webwork] Intended roadmap for webwork project?

2004-02-08 Thread Hani Suleiman
No merge will happen. There's a demand for 1.x to keep being maintained. A not insignificant number of people use this in production environments and work with it on a daily basis (I suspect more than ww2 currently). Many of these people are reluctant to migrate to ww2 (for now at least).

RE: [OS-webwork] WebWork 2.0 Released

2004-02-08 Thread Jason Carreira
Blogged, added news on dev.java.net, and added news on opensymphony.com... It's real! -Original Message- From: Patrick Lightbody [mailto:[EMAIL PROTECTED] Sent: Sunday, February 08, 2004 10:53 PM To: WebWork Subject: [OS-webwork] WebWork 2.0 Released I'm pleased to announce the

RE: [OS-webwork] Intended roadmap for webwork project?

2004-02-08 Thread Jason Carreira
WebWork 2.0 is a rewrite of the framework, but provides backward compatibility with WebWork 1.x applications via a compatibility jar. As Hani points out, many people continue to use WW1.x for production applications, and supporting them is important. We aim to make migrating to WW2 as painless as