> There is no EJB container that is compatible with Phoenix (if that is > what you were asking).
Hhmmm... Not exactly, although I see this as an interesting possibility. But I'm thinking more of the Avalon Framework, not Phoenix. > If you are asking if you can make beans in, say, JBoss that use > framework interfaces, buit are *entirely* contained in JBoss, then the > answer is likely no. > Reason? Following instantiation a sereries of interffaces are check for > present via instanceof and invoked against the bean. Lastlu initiaize() > and start() are called (if present) to indicate the eban can go about > its business. JBoss knows nothing about avalon framework methods and > can;t invoke them in a lifecycle concept. Contrast this with the other response I got in this thread; not everyone is talking about the same thing? > The question is not "avalon is not a good fit for an EJB env". > Avalon-Phoenix is the base that a vendor (or OSS team) might choose to > write an EJB container on top of. None have so far. In a year the > answer may be different. Aha, as I said, this could be interesting to me. > >Completely outside Avalon, does anybody know any framework > >whose target is the EJB world? I mean, a framework with > >concepts, patterns and practices that will help with the > >development of portable, scalable, nice, hip, beautiful > >and fashionable EJBs? Hopefully open source? > > > See http://sourceforge.net/projects/webwork/ > > Lastly. Is your product not going live for about six months?, > care to be on a bleeding edge? Is there any other way? ;-) > If yes, see http://sourceforge.net/projects/eob/ > > It is a bean server that is not EJB compliant and does use Avalon > framework classes. It is just not ready for prime time yet. Thanks for the links. > - Paul -- Gonzalo A. Diethelm [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>