Hi!
Emmanuel Pirsch wrote:
> It it not a non-issue because an validating editor will not always be used to
>produce the
> XML descriptor. The more validation we can put on the root (DTD)) the better the
>spec will
> be.
The EJB server that loads the XML should always use the verifier
(EJB1.1, page 245) to check the input, and the bean
developer/application assembler/deployer person should always use it to
verify the correctness of his output by the same method.
> > But both Description and Reentrant are logical attributes of Entity,
> > hence it becomes confusing if different rules apply to them.
>
> Reentrant is a lofical attribute, Description is something that get added to the
>descriptor
> without any effect regarding it's content. So Reentrant is really an attribute to the
> Entity (and modify it's meaning) and Description is just something that get attached
>to it
> to provide infromation about it (and it does not affect it's meaning).
I disagree. Both are attributes IMO.
> XML provide us with a lot of functionnality to describe the content of a document,
>why not
> use it to it's full extent?
Because XML will not be able to cover 100% of the rules. A Java verifier
will. Why make something that is harder to use (which the DTD would be
IMO) and verifiable, instead of easy to use (as it is now) and
verifiable? Doesn't make sense to me.
/Rickard
ps. BTW, the whole XML/DTD chapter in the EJB1.1 spec is terribly buggy.
I've currently reported 9 errors/major typos, so if something seems
confusing it's probably wrong... the XML example isn't even parseable..
ah well... ds.
--
Rickard �berg
Computer Science student@LiTH
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
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".
