What Hani is saying is that the purpose of external validation metadata
in the form of XML files is to separate the validations applied from the
code itself... Combining the two into one source file reduces the
advantages of this. 

I have several cases where we use different validations, but it's down
in model classes. We have different validations for data entry vs. batch
loading, for instance. 

> -----Original Message-----
> From: Robert Nicholson [mailto:[EMAIL PROTECTED] 
> Sent: Monday, December 01, 2003 2:10 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [OS-webwork] XDoclet and XWork validators
> 
> 
> Validators are tied to their action when defined in 
> ActionName-Validation.xml files right?
> 
> So, why not generate these files from javadoc comments in the code?
> 
> I'm only familiar with them as they are defined/explained in the JOSP 
> book.
> 
> If I'm not mistake XDoclet already supports struts validators which I 
> assume work the same way as webwork?
> 
> I haven't see any cases were you'd define multiple validators for the 
> same property of the same action and use each in a different context.
> 
> On Nov 30, 2003, at 6:46 PM, Hani Suleiman wrote:
> 
> > I'm missing something here....
> >
> > so you want external validators, specified in an external xml
> > configuration file...and you want to generate this file by adding 
> > javadoc comments to the source file that needs the validation, thus 
> > putting in validation code right alongside the code that needs it, 
> > without the benefits of type safety and suchlike?
> >
> > On Nov 30, 2003, at 7:41 PM, Robert Nicholson wrote:
> >
> >> Can XDoclet currently generate these from javadoc comments in your
> >> action?
> >>
> >> I don't see any references to doing this in the JOSP book.
> >>
> >>
> >>
> >> -------------------------------------------------------
> >> This SF.net email is sponsored by: SF.net Giveback Program. Does 
> >> SourceForge.net help you be more productive?  Does it help 
> you create 
> >> better code?  SHARE THE LOVE, and help us help YOU!  Click Here: 
> >> http://sourceforge.net/donate/ 
> >> _______________________________________________
> >> Opensymphony-webwork mailing list 
> >> [EMAIL PROTECTED]
> >> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
> >>
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: SF.net Giveback Program. Does 
> > SourceForge.net help you be more productive?  Does it help 
> you create 
> > better code?  SHARE THE LOVE, and help us help YOU!  Click Here: 
> > http://sourceforge.net/donate/ 
> > _______________________________________________
> > Opensymphony-webwork mailing list 
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program. 
> Does SourceForge.net help you be more productive?  Does it 
> help you create better code?  SHARE THE LOVE, and help us 
> help YOU!  Click Here: http://sourceforge.net/donate/ 
> _______________________________________________
> Opensymphony-webwork mailing list 
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
> 


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to