Eric Pugh wrote:

Hi all,

I started looking at what Stephen did with the crypto service, and it is
very interesting.  The Turbine dev team knows we need to come up with
something better then ECM, however we just haven't gotton around to writing
either a good FortressComponentService or MerlinComponentService.  However,
if someone has something that they could contribute, that would go a long
way towards getting the ball moving on getting the various services in the
Fulcrum project moved towards Merlin.


There are some recent additions to Merlin related to the AbstractMerlinTestCase (which itself was written to handle Turbine test requirements). These additions include a new class called MerlinLoader that simplifies the overhead of embedded containment. There are also a bunch of discussions going on over in Avalon land about the embedding subject with input from the Eve project (ldapd incubator inative), OpenIM, and others - taking into account requirements from the OpenORB project, JBoss, etc.


I've been going over the Fulcrum code base and based on everything I've seen so far it looks like everything could be supported in Merlin under the current formal release (3.0). The testcase and plugins related to Avalon meta-info generation are all in place and working nicely relative to 3.2 dev (which is runtime compatible with 3.0). I expect to see some interesting development on the embedded services and the abstract test case code over the comming days.


Before Turbine 2.4 release, which is focusing on integrating all the services moved to Fulcrum, we need to basically pick our container to run with.. We don't want to go with Fortresss/ECM, and then in 2.5 start swapping to Merlin which could require config changes, so it is definitly on the list to get the MerlinComponentService written.


What is the projected release date for 2.4?


My guess is that it would not take much time to bring Fulcrum up-to-date with respect to the Avalon Meta package and provide fine-grain component test integration (along the lines of the crypto package example). I can continue to transform a few more of the Fulcrum packages along the lines of the crypto transformation if that is of interest.

Stephen.


Eric Pugh




-----Original Message-----
From: Stephen McConnell [mailto:[EMAIL PROTECTED]
Sent: Monday, October 20, 2003 10:05 AM
To: Avalon Developers List
Cc: [EMAIL PROTECTED]
Subject: Re: [RT] My Merlin Wish List



[reposting with correct turbine-dev address]


J Aaron Farr wrote:




Embeddable Merlin containers
 servlets




you mean tomcat/jerry running as a merlin service OR merlin


running as a


tomcat/jetty war? ;)




Both of course! :)

Actually, there's a couple things that would be cool here:
- Tomcat/Jetty running as merlin service
- An Avalon light weight servlet container (which adds avalon
lifecycle support to servlets)
- Easy way to access Avalon services from within service,


action, etc.


(this can be done via AltRMI or JNDI, but we need to put


together docs


and examples)

I'm not very familiar with Turbine, but it would be nice to


see Turbine


services running in Fortress and Merlin without too much trouble.



Hi Aaron:

Confession - I'm not familiar with Turbine either.

I have played around with Turbine Fulcrum a bit - did some
treaking of the
crypto package and things are working fine (using crypto
component).  I've
got a local copy running against Merlin 3.2 using the new test case as
part of own my own test-and-validation-release-suite.

I'm interested in the Avalon/Turbine connection because I
would like to
play with the potential of Turbine as a smart web-service
system that we
plugin on the container facilites side of merlin.  I'm also a
interested
in potential applications of Turbine on the server side (just
a hunch).

Cheers, Steve.

--

Stephen J. McConnell
mailto:[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]





--


Stephen J. McConnell
mailto:[EMAIL PROTECTED]




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to