XML document has two forms: well-formed and valid. For a well-formed XML
document, you just need to follow the XML syntax. To have a valid XML document,
you need a DTD. So my point is this: in order for your suggestion to work, you
will need a new DTD which declares the custom elements and attributes for the
validation to work. Even with DTD, I worry about interoperability of EJB between
vendors. It seems to me with your approach I would end up having to add the
customised elements whenever I switch EJB container or need to support multiple
EJB containers. The deployment descriptor will become a bloat! Why do we use
Java? To be platform neutral! Why do we use JDBC? To be database vendor neutral!
I know in reality both are not 100% true and we need to make some compromises.
But we should still strive to be EJB container neutral, especailly in this early
stage of EJB specs.
Rickard �berg wrote:
> This format will allow deployment info from several servers to happily
> coexist in the same EJB-JAR XML descriptor.
>
===========================================================================
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".
