Arron, Thanks for the hands-on. Shame really.. surely the parser provides this data.. wonder if there's another way to 'compile' that information into a method.
BTW, have you used Castor's Object-Relational mapping? The second half of the equation would be to use that to persist the populated beans from within the Action. Cheers, Jon Arron Bates wrote: > I've tried to do this with Castor generated objects. Problem is though, > is that the errors are not fine grained at all. > You validate the document by calling the validate() method on the top > node, and you get a yes or a no. > You can do this for all of the sub objects, but it's just that, you > still have to implement the field validation yourself. > > Naturally you can't play any tricks with the calling of property methods > to work around various issues as your objects are locked down to the > automation process. > > Otherwise it's quite excellent. > > Arron. > > Jon Ferguson wrote: > > >( Republished under appropriate Subject :-( ). > > > >Hey, > > > >I've been toying with the idea of Modelling my form beans using XML Schema, > >then generating the actual beans using some XML binding tool like Castor (which > >should also generate my validate function). I should also be able to use > >Castor to do RDBMS mapping as well.. (but from a session bean manipulating the > >formbeans for example). > > > >I'm thinking of utilising schema from developments such as RosettaNet, BizTalk > >Frameworks and ebXML - noting that often the info entered into forms could be > >the same message information that might be passed between businesses. (Eg. a > >Purchase Order, etc.). > > > >I'm hoping that the result would: a) help to standardize the business app. b) > >leave it wide open for making use of b-2-b developments such as webServices and > >the above efforts. c) provide automatic form validation (inherent in the > >Schema), d) obviate the hand-coading of formbeans. > > > >Any comments on this approach? Has anyone tried this? > > > >Cheers, > > > >Jon > > > > > >------------------------------------------------------------------------ > > > >-- > >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
