This is quite confusing for me. How does the J2EE container distinguish between an Avalon component and an EJB component(Session or entity beans). How do call back methods (eg: ejbCreate, ejbRemove etc) co-exist with the life cycle methods available in Avalon. Or to put it in another way, can an EJB component(any bean) be a Avalon component?
Regards. Jeevan Maben. -----Original Message----- From: Berin Loritsch [mailto:[EMAIL PROTECTED] Sent: Friday, July 11, 2003 5:46 PM To: Avalon framework users Subject: Is Framework Limiting? (was Re: [Phoenix] Reconfigurable) jeevan wrote: > Basically, I would like to use Avalon from the code maintainability's > perspective. We would be using weblogic and would like to implement the > other J2EE patterns. Will the use of Avalon restrict me in any way from > using weblogic as my container, or restrict me from using other design > patterns? > > Generally I would be more interested in using the Framework project in > Avalon. > > Thanks for the reply. Avalon is the framework for Cocoon which lives quite comfortably in a J2EE server. Avalon does not restrict you from working with 3rd party containers. In fact we are looking at ways of making it even easier. We all have to live with them for the time being. -- "They that give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
