Hey
Anthony Eden wrote:
> Has anyone come across a situation where an EJB could also be a JavaBean. By
> this, I am suggesting that the JavaBean can be customized in a JavaBeans
> compliant builder and then be distributed to an EJB compliant container and
> executed as an EJB?
This *could* work if EJB-containers used Beans.instantiate instead of
Class.newInstance to create new bean instances. But since this is not a
requirement by EJB1.0 you cannot rely on this, although I don't think it
would be wrong if an EJB container would do this.
> Is this totally out there? Are there unresolvable conflicts between the two
> design patterns? Have I forgotten my medicine?
Seems like good thinking to me. But one could question if its the best
way to configure beans. My Top 3 EJB Configure list is as follows (or
would be if JavaBeans conf. worked):
1. Use Properties files + Class.getResource (gives app. wide settings
easily, editable through text editor. preferrably loaded in setXContext
of bean!!)
2. Deployment descriptor environments (per bean settings only. needs
deployment tool to change. not possible to use generic tool, server
specific one must be used(!!))
3. JavaBean Customizer (again single bean only, but requires BeanBox or
similar to change)
So even if it worked I don't think I'd use it 'cause the other ways are
better. IMHO of course.
/Rickard
--
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".
