-----Original Message-----
From: Stephen McConnell [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 8:13 PM
To: Avalon framework users
Subject: Re: Webapp example
Nicolai:
Are you also tracking [EMAIL PROTECTED] Thre are some recent posts on the HTTP subject which are more than relevant to this subject.
Steve.
Steve,
I am subscribing to the [EMAIL PROTECTED] as well, have not had time to read it for
a few weeks though. Just took a brief look, the HTTP stuff looks
interesting.
The primary driver for a design decision to use Avalon and Merlin as I see it is being able to build re-usable components that can be used in the different Java environments that exist; Web Containers (and J2EE...), Standalone server applications and even client applications unmodified aswell as version managed component repository.
Exactly - setup the profile and deliver the content.
The HTTP stuff is really interesting for standalone server applications.
The standalone question is relative to the embedder.
The demo demonstrates running merlin as a web application host from the command line. However - the scenario can be replicated in any embedded merlin environment - i.e. jelly, sevelet, cli, jmx, etc.
For embeeding I see a need to be able to be able to call services from servlets and JSP-pages (for building web user interfaces that use components), and keeping the strengths of the version management component repository that Avalon/Merlin provides.
Some points here - personally I believe that the only reason to deliver a servlet is to be compliant with respect to a deployment constraints. Once you have the web-app up and running what matters is how is the system responds to HTTP requests.
Consider the following:
(a) we can package a web-app that embeds merlin
(b) the web-app declares the public interface (via context path mapping)
(c) the solution is handled via components (and implementation strategy)
(d) components are easier and simpler than servlets - they have
- ability to declare dependencies
- ability to publish services
- and all of the other cool IOC stuff
(e) which leads massive simplification of the web-app model
(f) which leads major reductions in costs
(g) and lead time on deliveryI am downloading the snapshoot now, to take a look at the servlet to component code.
Main things to focus on is the TestCompoent (really simple) and the test.block - where it all happens. But the value proposition is in the fact that this is deployable remotely. I.e. your clients can run the same command and it will work the same way.
Maybe we should move this thread to the dev-list?
Shame we don't have a [EMAIL PROTECTED]
Cheers, Steve.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
