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]
