> Emmanuel Pirsch wrote:
> > You may gain a little for a little more consistence but you loose a lot
> in error
> > report. You do not use the capability of XML DTD to validate an XML
> file.
>
> Which becomes a non-issue if editors are used (mine is just finished and
> will be released in a couple of days).
>
>
> > That way at least you will gain a little in validation. But again you
> loose on
> > effeciency because the resulting DOM tree will be a lot bigger.
>
> My view is that validation can be done much better and with higher
> control in Java-based editors, instead of trying to create messy XML
> rules (is it even possible?).
>
not (yet) an expert in this area but it appears that you're
interpreting "validation" to include design thru deployment time. what about
runtime, when your system receives "something" from somewhere and wants to
validate/route/etc before execution? would your definition of "Java-based
editors" cover this? and what if the receiving system can't/won't execute
such an editor? seems that this is part of the reason for xml to exist in
the first place.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
