Hi all,
maybe this simple question has already been discussed on this list, if
so I apologize.
To use the same implementation of an Enterprise JavaBean in different
contexts, one would customize the bean appropriately as it is done with
the get/set methods on JavaBeans. But how would you do that with EJBs?
It seems to me that there are several techniques to do so and the spec
doesn't comment on that (does it?).
For stateful session beans I see 2 possibilities:
1. Deploy the bean for each context with a different environment (e.g.
deployment-descriptor or with the spec 1.1: different entries in the
JNDI environment)
2. Use get/set-methods on the bean like it's done with JavaBeans
What is your opinion on that? What about Entity Beans and customization?
And why is there no mechanism to introspect an Enterprise JavaBean like
the BeanInfo class on JavaBeans (javax.ejb.EJBMetaData is not the same
thing. You still need to do the "low-level" reflection on your own!) ?
Especially, I'm asking that, because customization & introspection is a
main topic when talking about component systems generally. But with EJB
this seems to be different.
Thanks,
Matthias David, University of Karlsruhe, Germany.
===========================================================================
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".
