Gonzalo,
>I am VERY new to Avalon, so please bear with me. > >We are defining the architecture for a pretty big set of >projects that will have to work together to an extent. >Some of the projects in the set are already implemented >and make heavy use of EJBs; others are yet to be defined, >including some form of common architecture that should >bind everything in place. It is NOT a requirement that >everything uses EJBs, but again, EJBs ARE part of the mix. > There is no EJB container that is compatible with Phoenix (if that is what you were asking). >Does Avalon have anything to say in such a scenario? Could >I use the concepts and patterns present in Avalon to define >an architecture that will also allow the interaction with >EJBs? > Yes you could, framework methods are faily cool (referring to the jakarta-avalon classes). The interaction between say JBoss and an Avalon-Phoenix hosted component would have to be home grown over RMI or AltRMI or JMX. 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. >Some of the new projects will surely have to implement new >EJBs. Can Avalon be used to help in this? Can I use the >Avalon components to simplify or improve the construction >of new EJB components? > Not really, due to the lack of overlap between EJB containers and Avalon. >Besides what can be found at the Jakarta site (including the >PDF doc), are there any further documents or resources about >Avalon? About Avalon and EJBs? > No... because we have no bean server that is phoenix compatible. >If Avalon is not a good fit for an EJB/nonEJB environment, >anybody has suggestions for alternative frameworks? > 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. >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? 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. - Paul -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
