If I understand you correctly, you refer to something similar to what the
J2EEDeployer is currently and what the "ApplicationDeployer" (discussed on
this list for a while now without actually coming to a decision, mostly
because of different opinions about the related classloading issue) should
be in the future ...
A generic (re-)deployment service that other deployers (such as the
Tomcat-war deployer, the EJB jar deployer, etc.) register at and to which
the actual (re-)deployment tasks are delegated after some preprocessing
(downloading remote jars, resolving dependencies, setting up classloaders,
...).
I sent some code to demonstrate how such a thing could be combined with a
radically different classloading model (non-hierarchical, dynamic,
beam-search-driven) to Marc and Rickard a while ago.
Since then, there has been unfortunately death silence and I do not know
whether we have reached some consensus there ... Maybe we should just start
coding?
Grüße aus Karlsruhe ;-)
Dr. Christoph G. Jung
Software Engineer
infor: business solutions AG
http://www.infor.de/
mailto:[EMAIL PROTECTED]
-----Ursprüngliche Nachricht-----
Von: Stefan Siprell [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 8. Februar 2001 14:01
An: '[EMAIL PROTECTED]'
Betreff: [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
>>>>>>>>>>>>>>>>>>>>>>>>>>>
