Aaron Mulder wrote:
>
> This will probably eventually work much like an EJB JAR. You'll
> get an Oracle .RAR with an Oracle deployment descriptor, use EJX to create
> a JBoss-specific deployment descriptor describing all the pools you want
> to set up and the connection and security parameters for each, and dump
> the .RAR into dist/deploy and voila! your pools will be started. That
> part isn't implemented yet, so currently you have to put all the JBoss
> configuration in jboss.jcml and then use the JMX web interface (or
> whatever) to tell the "RARDeployer" service to deploy the .RAR at a URL
> you provide. I think Toby's working on the further automation and
> deployment support.
Well, "planning" might be more accurate :-)
I really dislike the idea of defining connection pools etc, i.e.
configuring a connection factory, in the RAR itself. I also dislike
doing this with EJB JARs. The idea of having extra deployment
descriptors separate from the component archive but included in the EAR
makes a lot more sense to me. I think that the J2EE spec has some
support for this with alternative deployment descriptors or some such.
Anyway, yes, I am thinking about this. The first step is to get the
RARDeployer in the loop so that RARs can be autodeployed by putting them
in dist/deploy or including them in an EAR. My first instinct when I
contemplate J2eeDeployer is "Refactor!! Quick!!!", so I 've been putting
this off until some sort of decision is made regarding the desired
deployment/classloading architecture.
Toby.
P.S. That was an exceptionally clear explanation. I wish I could explain
things that well.
