geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: Adding new deployable module types
Date Sat, 10 Jun 2006 21:34:46 GMT

On Jun 10, 2006, at 2:25 PM, Aaron Mulder wrote:

> On 6/10/06, Stefan Arentz <> wrote:
>> I'm not interested in wrapping every Spring bean in a GBean actually.
>> I would simply add a GBean for each spring context that is created,
>> nothing more.
> OK, that should be pretty straightforward.
>> What I would like to do is deploy resources are part of an
>> application. Like adding a myapp-service.xml in a JBoss  
>> application to
>> define for example queues or connection pools.
> You can do that.  You can create JMS resource groups (connection
> factories and destinations), JDBC pools, and security realms in the
> console.  But instead of actually deploying from the console, use the
> other ("show plan") link on each screen to generate a deployment plan.
> Then, you can include that deployment plan in an EAR, so database
> pools, JMS resources, and security realms can be deployed as part of
> the application.  Each of the "show plan" screens should have some
> tips about how you can do this.
> You can also package the resource and application as plugins, so they
> could be separate but anyone who installed the application plugin
> would automatically get the realm and pool and so on.

I think the missing piece is making the stuff deployed this way  
accessible through spring.  I think the way to to is is with spring  
beans that look up the gbeans: then you can use spring injection to  
get the e.g. datasource into your spring bean.

david jencks

> Thanks,
>     Aaron

View raw message