We're using Avalon in an EJB environment with great success. Please look here for some tips: http://marc.theaimsgroup.com/?t=100541560200002&r=1&w=2
This reminds me that Vincent Massol and I have promised to provide a chapter on that topic for "Developing with Avalon". Hmm, still looking for time to do this... On 15.03.2002 17:16:39 Gonzalo A. Diethelm wrote: > 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. > > 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? > > 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? > > 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? > > If Avalon is not a good fit for an EJB/nonEJB environment, > anybody has suggestions for alternative frameworks? > > 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? Cheers, Jeremias M�rki mailto:[EMAIL PROTECTED] OUTLINE AG Postfach 3954 - Rhynauerstr. 15 - 6002 Luzern Fon +41 (0)41 317 2020 - Fax +41 (0)41 317 2029 Internet http://www.outline.ch -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
