let's say i take the merlin tutorial hello example, and i call it from a struts action. How would i be obtaining a reference to the hello component? I have absolutly no idea!
Please help! -----Original Message----- From: Niclas Hedhman [mailto:[EMAIL PROTECTED] Sent: Freitag, 14. November 2003 09:26 To: Avalon framework users Subject: Re: Apache avalon on j2ee server On Friday 14 November 2003 15:57, [EMAIL PROTECTED] wrote: > 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? I think you should stop thinking "container" for a second, and start thinking "components". This is exactly the beauty of multiple container implementations of the same specification. With a little bit of caution, the components yu design will work in all Avalon containers (perhaps ECM excempted). Going back to the container issue. You can mix and match. Fortress as component manager inside Jetty, which is running as a component inside Merlin? Sounds good? Merlin hosting the SWT application? I can't see why not. Or do you use an GUI Platform, such as Eclipse, you can either embed Merlin or Fortress. Back to the component issue, which container is depending more on memory consumption vs features. > And in terms of future releases, will there always be merlin AND > fortress or is fortress "doomed" to take the same place as phoenix? ALL software is doomed, just like any species (humans included) are doomed. It is only a matter of how soon, and if it will evolve into something else or just sudden death. I think a "light weight" container will "always" exist. But maybe in a few years Merlin is de-composed into "building blocks" and you choose the features you need and get "weight" accordingly. And in such scenario Fortress' purpose cease to exist. Who knows? > Does either of the containers, or the framework itself support cluster > functionality? See separate mail. > How could i deploy comonents in a distributed environment and how would > they communicate? Altrmi, rmi/iiop, jms, axis? Yes ;o) Merlin is not there yet. There are many intricate decisions to make about this issue on the container level. However, Components can also provide these kind of services, but not as transparently. Avalon is a horizontal framework and it doesn't provide you with the kitchen-sink, sorry to say. We try to solve the lowest-level problems and we try to do it well. Before the component repository grows, our users will have the same problems, and ask the same questions about applicability. We are trying to address the component shortage as well, and I personally think that this is the most important issue to our users, not whether the container is Merlin or Fortress, or to create Avalon Framework 5. I hope you don't get discouraged by my inability to answer you questions. 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]
