> -----Original Message----- > From: Stephen McConnell [mailto:[EMAIL PROTECTED] > > 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 embedded. > > 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 delivery
For any type of remote interfaces and most situations where a servlet would be used there is an advantage of using this approach. Components can replace servlets, but for Web User Interface's most of the action will not be in the servlets. It would look something like: JSP Page -> Tag Library Class -> Components (exposed as services). Struts (or other MVC) F/W Dispatcher -> Struts (or other MVC) Action -> Components (exposed as services). This way Avalon/Merlin is an effective replacement for EJB's for developing these types of applications (besides all the obvious advantages of COP, IOC and disadvantages with EJB's). Except when needing transactions though. > 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. Downloaded it just now, my Internet connection where I am now is a bit slow. Looks good! Looking forward to take a look at the source for the HTTP stuff, to see how it can be used for embedding. / Nicolai --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
