Archie Cobbs wrote: > > > I have a somewhat contrarian view, but IMHO this is a good example of why > XSD documents are basically useless. Invariably XML documents require > programmatic, runtime validation beyond what XSD provides. As I understand > things SOAP requires them; for me, that's a good reason to avoid SOAP (not > to mention most other products of Microsoft). > > The pattern I end up following is: start with Java classes with JSR 303 > annotations (including custom validators as necessary), create the > corresponding JiBX bindings, and validate at runtime simply by (a) > processing through JiBX and (b) running the result through the validator. > If > it passes (a) and (b), you've got something that will work. Moreover, > there's no validation that can't be verified by some combination of (a) > and > (b). > > -Archie >
Very important points. Even if JiBX could generate the JSR-303 annotations from the XSD, they would still most often be incomplete. I think your approach is a very good one given the state of the specifications and available components. -- View this message in context: http://old.nabble.com/Anyone-have-a-solution-for-JSR-303-validation--tp30564412p30700982.html Sent from the jibx-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ jibx-users mailing list jibx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-users
