Laurent:


Wow - lots of questions in this one! I'm kind of deep in some rather heavy stuff for the next 24-48 hours but I promise to put together a detailed answer to you email and a complete roadmap of where things are going with Merlin.

Cheers, Steve.


Laurent Rieu wrote:


Hello,

Stephen, you're talking about "lots of demos available". Do you have
anything close to a kernel loader able to work in a J2EE context (Web App)
? What are the issues I have to deal with ? I am mainly worrying about
potential classloading conflicts / problems : should I put the component
jar files in the root of the EAR and declare this directory as the system
or shared directory ? By the way, could you give me some hint about what
are the context informations I should pass to the Merlin kernel when
bootstraping it (ie : home, system, shared, ...) ?

You also told me about some interesting things about how you see component
adminstration using JMX in Merlin. Basically, if I understand you well, we
have two different level of administration : Appliance and Component
instances. While it is feasible to plug a Component-level administration
using lifecycle extensions, it seems more intrusive to me to have Appliance
management. Am I right ? This brings one question to my mind : are
Appliances and other internal stuff "true" components", meaning : are such
things registered within the container as components which would
potentially enable us to provide them with lifecycle extensions ? I guess
this is not that easy as these form the core of the container. I'm talking
about all that coz I'm pretty interested in giving Merlin a try within a
J2EE webapp and providing it with JMX administration.

By the way (sorry for so many questions at the same time !), what about
component proxies (using Dynamic proxies, CGlib, ...) which would enable us
to plug interceptors and potentially provide components with security,
conversational state, ... ? Does it fit in Merlin plans ?

Oh, one last thing. Where are you at with your Service URL stuff ? How can
a client access a component deployed in the container ?

Thanks !

Laurent





Stephen McConnell <[EMAIL PROTECTED] To: Avalon framework users <[EMAIL PROTECTED]> .org> cc: Subject: Re: Phoenix and Merlin 02/25/2003 10:59 PM Please respond to "Avalon framework users"








J Aaron Farr wrote:




Hello all.

Can or will Merlin be able to load Phoenix blocks/components?

I believe this has been covered before, or at least hypothesized about,

but I'm

not sure if in reality it is the case. Anyone want to confirm?



Merlin is based on the Assembly package which is based on the Meta package. The meta package provides a legacy <blockinfo> reader that handles the construction of the Type based on the Phoneix xinfo format.


I'm starting another project at work that would be better suited for a

full

featured container like Phoenix.  Just wanted to be sure that if I go with
Phoenix now, that switching to Merlin when possible shouldn't be too

difficult.


No change is required - they will just run.


Cheers, Steve.

p.s. Lots of demos available if you need them.


jaaron

__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/

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






--


Stephen J. McConnell
mailto:[EMAIL PROTECTED]
http://www.osm.net




--------------------------------------------------------------------- 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]
http://www.osm.net




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



Reply via email to