Which part? The validation configuration is currently defined in xml files. The localized messages are built using the getText() method from ActionSupport (also defined in an Interface now, if you don't want to have to subclass ActionSupport), so they use properties files for the ResourceBundle, like the messages from Webwork 1.x did, and Xwork 1.0 and WW 2.0 are (currently).
> -----Original Message----- > From: Hani Suleiman [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 13, 2003 10:47 PM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] Webwork 2.0 > > > Can it be made to work with properties files (again, for those of us > with huge internationalised apps), or does everything have to > be moved > to xml files? > > On Thursday, February 13, 2003, at 10:41 PM, Jason Carreira wrote: > > > I started building one. The consensus at the design meeting > last week > > was that creating a dependency on another validation > framework was a > > Bad Thing, so, since it only took a few hours to put in > localized and > > parameterized messages, we're sticking with our own. > > > >> -----Original Message----- > >> From: Francisco Hernandez [mailto:[EMAIL PROTECTED]] > >> Sent: Thursday, February 13, 2003 4:37 PM > >> To: [EMAIL PROTECTED] > >> Subject: Re: [OS-webwork] Webwork 2.0 > >> > >> > >> i havent kept up with all the emails but will you guys be building > >> your own validator? or will an existing one be used? > >> > >> ----- Original Message ----- > >> From: "Jason Carreira" <[EMAIL PROTECTED]> > >> To: <[EMAIL PROTECTED]> > >> Sent: Thursday, February 13, 2003 12:01 PM > >> Subject: RE: [OS-webwork] Webwork 2.0 > >> > >> > >> Ok, what do we want to see for docs? Should we go back > into the stuff > >> from 1.x and re-do that, or just document the new / > different stuff > >> for now? > >> > >> > >> Here's a quick outline: > >> > >> Xwork > >> 1)Introduction > >> a) What is Xwork > >> Xwork is a generic command pattern framework... > >> b) How does Xwork relate to Webwork? > >> Webwork 2.0 is built on top of Xwork... > >> 2) The basics > >> a) Actions > >> Actions are the basic unit of execution... > >> 1) The Action Interface > >> 2) ActionSupport > >> 3) Lifecycle > >> b) No FormBeans? > >> Xwork / Webwork does not require the use of FormBeans > >> like Struts... > >> 3) Configuration - Xwork.xml > >> > >> 4) Ognl > >> Ognl is used as both the expresion language and bean population > >> utility for Xwork... > >> > >> 5) Interceptors > >> a) Utility Interceptors > >> The TimerInterceptor and LoggingInterceptor ... > >> b) Parameter Interceptors - populating your Action > >> The StaticParameterInterceptor and ParameterInterceptor > populate your > >> Action fields... > >> c) ResultInterceptor > >> > >> 6) Validation Framework (optional) > >> a) The ValidationInterceptor > >> b) Defining validation rules in a validation.xml > >> c) Building a FieldValidator > >> d) Localized and Parameterized messages > >> > >> > >> I'll take 3, 5, and 6. Patrick, you take (at least) 4, and > Joe, since > >> you brought it up, you get 1 and 2 :-) > >> > >> What else do we need in there? > >> > >> Jason > >> > >> > >>> -----Original Message----- > >>> From: Patrick Lightbody [mailto:[EMAIL PROTECTED]] > >>> Sent: Thursday, February 13, 2003 1:18 PM > >>> To: [EMAIL PROTECTED] > >>> Subject: Re: [OS-webwork] Webwork 2.0 > >>> > >>> > >>> Actually, I think Joe may be right for once in his life. We > >> should get > >>> cracking on the documentation soon. Maybe you can work on a > >> skeleton > >>> documentation effort while you're on the plane? > >>> > >>> -Pat > >>> > >>> ----- Original Message ----- > >>> From: "Jason Carreira" <[EMAIL PROTECTED]> > >>> To: <[EMAIL PROTECTED]> > >>> Sent: Thursday, February 13, 2003 7:25 AM > >>> Subject: RE: [OS-webwork] Webwork 2.0 > >>> > >>> > >>>> I guess that depends on how much help we get :-) It would > >>> be good if > >>>> someone besides Patrick and I were to work on things (hint hint). > >>>> > >>>> Patrick and I were talking about releasing a first Alpha > >> of XW1.0 / > >>>> WW2.0. What features from WW1.x need to be ported over to > >> WW2? This > >>>> isn't an academic question... I'm flying home tonight (probably > >>>> leaving the office for the airport at about 4-4:30 Central > >>> time) and I > >>>> asked this question to Patrick last night: What's the next most > >>>> pressing need in WW2.0? Give me something to do on my flight. > >>>> > >>>> Jason > >>>> > >>>>> -----Original Message----- > >>>>> From: Heng Sin Low [mailto:[EMAIL PROTECTED]] > >>>>> Sent: Thursday, February 13, 2003 1:16 AM > >>>>> To: OS-Webwork > >>>>> Subject: [OS-webwork] Webwork 2.0 > >>>>> > >>>>> > >>>>> All, > >>>>> > >>>>> We are currently evaluting the framework to use for our new CRM > >>>>> product. I'm bias towards webwork and really like many of the > >>>>> features plan for webwork 2.0 ( I've been using webwork > >>> and are not > >>>>> entirely happy with the current version ). > >>>>> > >>>>> So, my concern now is the schedule of webwork 2.0 and > >> whether it > >>>>> would be inline with our development schedule ( We are > >> looking at > >>>>> releasing the first version by September 2003 ). I do > >> not mind to > >>>>> live with the rough edges of the initial beta release but > >>> would like > >>>>> to know the estimated schedule of webwork 2.0 ( For > >> e.g, when it > >>>>> will be promoted from sandbox, what is the estimated first beta > >>>>> release date, etc ). > >>>>> > >>>>> Also, We are looking at using webwork, velocity, hibernate and > >>>>> sitemesh together, maybe someone here can share his/her > >>> experience > >>>>> with us ? > >>>>> > >>>>> thanks. > >>>>> > >>>>> Regards, > >>>>> Low > >>>>> > >>>>> > >>>>> > >>>>> __________________________________________________ > >>>>> Do you Yahoo!? > >>>>> Yahoo! Shopping - Send Flowers for Valentine's Day > >>>> http://shopping.yahoo.com > >>>> > >>>> > >>>> ------------------------------------------------------- > >>>> This sf.net email is sponsored by:ThinkGeek > >>>> Welcome to geek heaven. > >>>> http://thinkgeek.com/sf > >>>> _______________________________________________ > >>>> Opensymphony-webwork mailing list > >>>> [EMAIL PROTECTED] > >>>> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > >>>> > >>>> > >>>> ------------------------------------------------------- > >>>> This SF.NET email is sponsored by: FREE SSL Guide from > >>> Thawte are you > >>>> planning your Web Server Security? Click here to get a FREE > >>> Thawte SSL > >>>> guide and find the answers to all your SSL security issues. > >>>> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en > >>>> _______________________________________________ > >>>> Opensymphony-webwork mailing list > >>>> [EMAIL PROTECTED] > >>>> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > >>> > >>> > >>> > >>> ------------------------------------------------------- > >>> This SF.NET email is sponsored by: FREE SSL Guide from > >> Thawte are you > >>> planning your Web Server Security? Click here to get a FREE > >> Thawte SSL > >>> guide and find the answers to all your SSL security issues. > >>> http://ads.sourceforge.net/cgi-> bin/redirect.pl?thaw0026en > >>> > >>> > >>> _______________________________________________ > >>> Opensymphony-webwork mailing list > >>> [EMAIL PROTECTED] > >>> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > >>> > >> > >> > >> ------------------------------------------------------- > >> This SF.NET email is sponsored by: FREE SSL Guide from Thawte are > >> you planning your Web Server Security? Click here to get a FREE > >> Thawte SSL guide and find the answers to all your SSL security > >> issues. http://ads.sourceforge.net/cgi-> bin/redirect.pl?thaw0026en > >> > >> > >> _______________________________________________ > >> Opensymphony-webwork mailing list > >> [EMAIL PROTECTED] > >> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > >> > >> > >> > >> ------------------------------------------------------- > >> This SF.NET email is sponsored by: FREE SSL Guide from Thawte are > >> you planning your Web Server Security? Click here to get a FREE > >> Thawte SSL guide and find the answers to all your SSL security > >> issues. http://ads.sourceforge.net/cgi-> bin/redirect.pl?thaw0026en > >> > >> > >> _______________________________________________ > >> Opensymphony-webwork mailing list > >> [EMAIL PROTECTED] > >> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > >> > > > > > > ------------------------------------------------------- > > This SF.NET email is sponsored by: FREE SSL Guide from > Thawte are you > > planning your Web Server Security? Click here to get a FREE > Thawte SSL > > guide and find the answers to all your SSL security issues. > > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en > > _______________________________________________ > > Opensymphony-webwork mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: FREE SSL Guide from > Thawte are you planning your Web Server Security? Click here > to get a FREE Thawte SSL guide and find the answers to all > your SSL security issues. > http://ads.sourceforge.net/cgi-> bin/redirect.pl?thaw0026en > > > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
