So here goes my scenario: I have both standalone (swt) and web (struts) clients and they need a common core. Now from your answer part 1 : - "Fortress is a lighter-weight container, more suitable in a "Request/Response" , i guessed fortress'd be more suitable for the webcontext", but on the other hand: - "Merlin kick-ass for more rigid application, either embedded into a bigger "container ...</snip> does confuse me a bit...
So, what would me more "j2ee" compatible, merlin or fortress? And in terms of future releases, will there always be merlin AND fortress or is fortress "doomed" to take the same place as phoenix? Does either of the containers, or the framework itself support cluster functionality? How could i deploy comonents in a distributed environment and how would they communicate? Altrmi, rmi/iiop, jms, axis? Again, merlin or fortress? Loads of questions for the weekend, huh? Cheers, simon -----Original Message----- From: davout [mailto:[EMAIL PROTECTED] Sent: Freitag, 14. November 2003 08:06 To: Avalon framework users Subject: RE: Apache avalon on j2ee server I read somewhere that either Merlin or Fortress has... * Support for distributed deployment; and * Will work with JBoss Is either statement true? -----Original Message----- From: Niclas Hedhman [mailto:[EMAIL PROTECTED] Sent: 14 November 2003 03:32 To: Avalon framework users Subject: Re: Apache avalon on j2ee server On Friday 14 November 2003 02:09, Stephen McConnell wrote: > [EMAIL PROTECTED] wrote: > >Why should i use merlin instead of fortress? > > * auto assembly > * muli-layer configuration management > * advanced context management > * composite component management > * packaged deployment scenarios > * local and remote repository integration > * integral jar extension management > * Maven plugin support for meta-info generation and simulated > deployment > * product packaging and install services > * based on Avalon component meta model > * support for legacy migration That was the technocrat answer ;o) The "human" answer is more like; Fortress is a lighter-weight container, more suitable in a "Request/Response" setup, for instance Cocoon is migrating to Fortress. Merlin kick-ass for more rigid application, either embedded into a bigger container or stand-alone server. Niclas --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
