> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Sacha Labourey
> Furthermore, on this particular issue (10 different bean "types" but the
> same remote/home/bean), I do not see why the CLR would add simplicity?
Sorry, brain shortcut.
What I meant is that the CLR supports meta attributes at the bytecode level, so
you can specify metadata directly in your source file. Even better, you can
query your own metadata and it is available in the language your are using. If
we had that, we could probably get rid of all XML deployment descriptors
altogether and specify everything in the source file (a la EJBGen).
Of course, this approach doesn't work if you intend to deploy the same Java
classes as different EJB's, but you could simply consider having these
attributes in a separate Java file anyway. You could still access all your
metadata directly in Java at runtime (as opposed to the current state of affair
wher you have to either parse an XML file or parse your own source file, looking
for Javadoc tags).
--
Cedric
===========================================================================
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".
