That is already the case. You load whatever you want in the JMX spine.
In fact we load the ContainerFactory in there but it could be anything. We
load the deployer etc... the administration is taken care of by the JMX
MBeanServer you provide the MBean.
Other than that if your bean needs a container that is close to EJB then you
can simply add the "interceptor" to the interceptor chain. I believe the
interceptors were XML externalized very recently, I don't know that it is
fully documented yet.
You will have to be more precise if you want more information
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Stefan Siprell
|Sent: Thursday, February 08, 2001 5:01 AM
|To: '[EMAIL PROTECTED]'
|Subject: [jBoss-Dev] Container for Generic Components
|
|
| Hi,
| I admit, that I'm absolute newbie, but after talking with all the local
|tech-heads, I was advised to post this question on this maillist. Currently
|my company is using the bea weblogic application server, but we have
|developed the need, to have a special kind of container, to host a kind of
|pluggable adapters. Instead of building such a container from scrap, I
|would like create a generic container, which:
| -deploys Components in the J2EE-usual way
| -creates an enviroment for the running Components
| -creates an administration interface for the Enviroment and its components
|
| The Enviroment itself should not be implemented in the
|"Container-Framework". Yet there should be a set of Abstract Classes, that
|allow an Enviroment to be plugged into the Container as desired. The
|"Enviroment-Plugin" then processes the deployment XML-documents on a rel.
|high level of logic (all the lowlevel stuff should be managed by the
|"Container-Framework").
| The administration interface could be implemented in a similar way.
| Such a configurable Container System could replace the current core
|EJB-Container, and allow JBoss to host just about any kind of Component out
|there (even the ones to come).Further I would think a
|EJB-Interface could be
|designed to allow the hosting of several containers on one system (which
|even would not have to be a JBoss Application Server).
| Being able to use well working Core Elements of the JBoss-Project as
|peripherial Elements on current professional systems, would allow new and
|more conservative developers to "snoop in" JBoss, with out the risk of a
|complete failure, and probably convince them to use more of the
|projects, or
|even completly swapping the core in favour of you -us?- .
|
| My questions:
| -would it be reasonable to modify the current container?
| -is such a modificication desired by the community?
|
|
| Thanx a lot for your open ear (-or eyes ;^)).
| I'm looking forward to your feedback.
|
|
|Stefan Siprell
|Software-Development
|
|<<<<<<<<<<<<<<<<<<<<<<<<<<<
|<sitewaerts> GmbH
|Hebelstr. 15
|76133 Karlsruhe
|Germany
|
|Tel.: +49 (721) 920 918 22
|Fax: +49 (721) 920 918 29
|
|mailto:[EMAIL PROTECTED]
|http://www.sitewaerts.de
|>>>>>>>>>>>>>>>>>>>>>>>>>>>
|
|
