Hi there !
A couple of questions about Merlin :
- talking about JMX, is there anything in Merlin's roadmap regarding
a pluggable JMX administration that could provided to the embedded
components ? If so, any hint about how this could be achieved (lifecycle
extensions, specific interfaces, ...) ?
- you're talking about several management policies of component
instances, such as pooled, one per thread, singleton or transient. What
about stateful components storing conversational state for a specific
client, such as Stateful EJBs ?
- I guess it is not possible at this point to provide my own
management policy (by providing a specific classname in the appliance
descriptor, for example) for a given composant. Am I wrong ? This could
help providing enhanced features such as the management of stateful
components.
- Regarding the URL protocol to access components deployed in Merlin,
what about providing a naming context to locate them ? I agree a URL
protocol is lighter and can easily run in a standalone application. Do you
think adding naming features would be worth the (small ?) effort ?
I don't know if those questions should be posted on the users list... but
I'm investigating Merlin and am really fond of all those concepts !
Laurent (really impressed by the Merlin stuff !)
"Schaible, J�rg"
<Joerg.Schaible@g To: "Avalon framework users"
<[EMAIL PROTECTED]>
ft.com> cc:
Subject: RE: [Newbie] Merlin demo as
webapp ... what next?
02/18/2003 01:56
PM
Please respond to
"Avalon framework
users"
Hello Ulrich,
> Fair enough, but be aware that this way you are making the servlet
> engine the top container and embed an application server(*).
Yes, but ... when do expect Merlin to be a full-featured AppServer <g>?
> Since an application server can not only run servlets, but
> also generic
> server applications, it is IMHO more sensible to make it the top
> container. Servlets are just specialized server applications.
Yes again, but when I speak of integrating into a J2EE compiant servlet
engine, this implies even WebLogic or WebShpere or other less known systems
we have partner contracts ... these are the ones that we meet mainly in the
real world. So basically, I have already full-blown appserver
functionality, if I need it.
> Also, from application servers one can expect operational support to
> manage lifecycle etc. of the applications via a management
> console. This
> is something which servlet engines rarely provide and, I
> believe, never
> in a standardized way (JMX).
Something like this is currently out of scope - at least in this form.
Regards,
J�rg
---------------------------------------------------------------------
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]
