geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder" <>
Subject Re: Adding new deployable module types
Date Sat, 10 Jun 2006 19:42:32 GMT
Funny you should ask...  I'm writing a Wiki page on how to do this
with a plugin in Geronimo 1.1 as we speak.  The bottom line is that
you have to write a pretty hairy deployer class, but most of it is
relatively boilerplate code, just unpleasant boilerplate.  :)

For purposes of the example I'm working on, this would be something
deployed separately from J2EE modules (e.g. you couldn't pack one in
an EAR).  I think we're still undecided as to whether you ought to be
able to pack non-J2EE modules into EARs, or whether we ought to have
some larger ZIP/JAR format that holds an EAR along with other modules
if you want to deploy them together, or something else entirely.  What
do you think?


On 6/10/06, Stefan Arentz <> wrote:
> How difficult is it to add a new deployable module type to geronimo?
> For example, I want to deploy .foo files. Do I have to hook into the
> j2ee-builder module and add a new 'foo' Module? Or is a 'deployable
> unit' defined outside the J2EE context?
>  S.

View raw message