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 21:19:51 GMT
OK, I put most of the code up (including the deployer GBean, the
Quartz deployment plan schema, the Maven script that builds XMLBeans
beans for the schema, and the deployment plan for the deployer service
itself).  It'll probably be a while before I get through all the text,
but you can work off the samples there and you're welcome to ask
questions on the list.


On 6/10/06, Aaron Mulder <> wrote:
> The Wiki page I'm working on is at
> though it's
> going to be empty until I save.
> The example there is Quartz integration where you can deploy Quartz
> jobs as the new deployment unit (e.g. a JAR containing the classes
> with an XML plan that includes the schedule, etc.).
> I think we're definitely interested in improving our Spring
> integration.  Currently, it seems like it will be a little awkward to
> wrap every Spring bean in a GBean (because, if I remember right,
> Spring creates them all and then we'd have to try to find them, and it
> would get a little confusing as to who "owns" the
> configuration/injection settings and so on).  But one of the things
> we've talked about for 1.2 is to make Spring beans native citizens in
> Geronimo.
> Can you clarify your last bit about "what I really like is to be able
> to deploy resources to automatically make database pools and JMS
> queues/topics."  I'm not sure if you're saying you *can* do that in
> Geronimo, or you *wish* you could.  If the latter, can you explain
> exactly what you'd like?
> THanks,
>     Aaron
> On 6/10/06, Stefan Arentz <> wrote:
> > On 6/10/06, Aaron Mulder <> wrote:
> > > 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.  :)
> >
> > Interesting! Can you post a link to that page when it is available?
> >
> > > 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?
> >
> > Short term: simple deployable spring applications - I have a lot of
> > applications that are just a bunch of Spring beans talking to JMS or
> > Quartz for example. It would be really nice if I could just deploy
> > those to Geronimo. These apps usually don't have a web interface and
> > just turning them into a .war for bootstrapping the Spring context
> > seems a bit lame.
> >
> > Long term: What I'm interested in is building a 'Spring Application
> > Server'. For me that would be a Geronimo instance that provides a
> > certain base of functionality. For example: Spring 2.0, OpenJPA, a
> > Transaction Manager, Quartz, ActiveMQ and Derby.
> >
> > Just making life easier for myself while building applications :-) It
> > would be nice to be able to just pick the components that I like most
> > and use them to build an app server environment for my own needs.
> >
> > I'm not very interested in following 'industry' specs/apis. I'm more
> > interested in getting the job done with my favorite tools. Geronimo
> > sounds like a good platform for that.
> >
> > I would even go so far as defining a new .ear style deployment unit to
> > be able to bundle a bunch of web and spring apps. Oh and what I really
> > like is to be able to deploy resources to automatically make database
> > pools and JMS queues/topics.
> >
> >  S.
> >

View raw message