You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by ja...@mac.com on 2004/06/29 20:57:41 UTC

Integrating Spring into Geronimo

Dion let the cat out of the bag...

http://www.almaer.com/blog/archives/000246.html

so I thought I'd best actually commit the code. Warning though I've not 
tested it yet  - we need an integration test to make sure this works & 
we handle all the lifecycle methods properly :)

Basically we've a GBean for Geronimo so that any existing spring XML 
config file can be slurped up & turned into beans and managed in a JSR 
77/88 way & hot deployed - so Geronimo can hot deploy arbitrary Spring 
containers within the core J2EE container - all managed in the same 
stack as web apps, web containers, EJB containers etc. We should also 
be able to JMX-ifiy all the beans as they are created into the JSR 
77/88 management stack.

At JavaOne we've discussed maybe having a special naming convention, 
say putting spring.xml inside META-INF/ or something, so that you can 
put your code in a regular jar with the XML deployment descriptor then 
drop it in a directory or whatnot and Geronimo could auo-detect it & 
use the SpringGBean to deploy it.

Its still early days but hopefully once this is sorted out & working, 
developers can spend their time in development mode just using Spring 
by itself, then at any point in time drop their jar into Geronimo (or 
build a deployment binary of Geronimo) and hey presto their apps 
running inside a J2EE container.

Going forward we should be able to further increase the functionality 
of the SpringGBean to closer integrate the two projects so that the 
Spring POJOs can take better, more efficient & easier use of the J2EE 
services in Geronimo (transactions, security, remoting, pooling, 
clustering etc).

Enjoy!

James
-------
http://radio.weblogs.com/0112098/


Re: Integrating Spring into Geronimo

Posted by Jeremy Boynes <je...@coredevelopers.net>.
There is also an initial version of Hibernate integration - currently 
this makes the SessionFactory available as a GBean or from JNDI. Work is 
in progress for integrating with the transaction manager and deployer.

http://www.codehaus.org/~jboynes/germinate-1.0-SNAPSHOT.jar
http://www.codehaus.org/~jboynes/germinate-src.jar

--
Jeremy

jastrachan@mac.com wrote:
> Dion let the cat out of the bag...
> 
> http://www.almaer.com/blog/archives/000246.html
> 
> so I thought I'd best actually commit the code. Warning though I've not 
> tested it yet  - we need an integration test to make sure this works & 
> we handle all the lifecycle methods properly :)
> 
> Basically we've a GBean for Geronimo so that any existing spring XML 
> config file can be slurped up & turned into beans and managed in a JSR 
> 77/88 way & hot deployed - so Geronimo can hot deploy arbitrary Spring 
> containers within the core J2EE container - all managed in the same 
> stack as web apps, web containers, EJB containers etc. We should also be 
> able to JMX-ifiy all the beans as they are created into the JSR 77/88 
> management stack.
> 
> At JavaOne we've discussed maybe having a special naming convention, say 
> putting spring.xml inside META-INF/ or something, so that you can put 
> your code in a regular jar with the XML deployment descriptor then drop 
> it in a directory or whatnot and Geronimo could auo-detect it & use the 
> SpringGBean to deploy it.
> 
> Its still early days but hopefully once this is sorted out & working, 
> developers can spend their time in development mode just using Spring by 
> itself, then at any point in time drop their jar into Geronimo (or build 
> a deployment binary of Geronimo) and hey presto their apps running 
> inside a J2EE container.
> 
> Going forward we should be able to further increase the functionality of 
> the SpringGBean to closer integrate the two projects so that the Spring 
> POJOs can take better, more efficient & easier use of the J2EE services 
> in Geronimo (transactions, security, remoting, pooling, clustering etc).
> 
> Enjoy!
> 
> James
> -------
> http://radio.weblogs.com/0112098/

Re: Integrating Spring into Geronimo

Posted by ja...@mac.com.
On 29 Jun 2004, at 22:58, Alex Karasulu wrote:
>>> Going forward we should be able to further increase the functionality
>>> of the SpringGBean to closer integrate the two projects so that the
>>> Spring POJOs can take better, more efficient & easier use of the J2EE
>>> services in Geronimo (transactions, security, remoting, pooling,
>>> clustering etc).
>
> That would really be worth while because then these components need not
> roll their own redundant utilities like thread pools etcetera.  If 
> these
> and other services that are already part of Geronimo's scaffolding 
> could
> be accessible to the spring components then that would be most
> wonderful.

Agreed.

> Just as a feeler how far off is all this from being mature and
> available?

We just need an integration test to check its working & that the 
lifecycle methods hook up - and to wire in the GBeanMBean method and 
we're done. Then the deployer may wish to auto-recognise spring.xml 
inside META-INF/ or whatever - which would be cool.

James
-------
http://radio.weblogs.com/0112098/


Re: Integrating Spring into Geronimo

Posted by Alex Karasulu <ao...@bellsouth.net>.
On Tue, 2004-06-29 at 15:09, Colin Sampaleanu wrote:
> This is seriously cool!

Oh yeah!

> jastrachan@mac.com wrote:
> 
> > Dion let the cat out of the bag...
> >
> > http://www.almaer.com/blog/archives/000246.html
> >
> > Basically we've a GBean for Geronimo so that any existing spring XML 
> > config file can be slurped up & turned into beans and managed in a JSR 
> > 77/88 way & hot deployed - so Geronimo can hot deploy arbitrary Spring 
> > containers within the core J2EE container - all managed in the same 
> > stack as web apps, web containers, EJB containers etc. We should also 
> > be able to JMX-ifiy all the beans as they are created into the JSR 
> > 77/88 management stack.

<snip/>

> > Going forward we should be able to further increase the functionality 
> > of the SpringGBean to closer integrate the two projects so that the 
> > Spring POJOs can take better, more efficient & easier use of the J2EE 
> > services in Geronimo (transactions, security, remoting, pooling, 
> > clustering etc).

That would really be worth while because then these components need not
roll their own redundant utilities like thread pools etcetera.  If these
and other services that are already part of Geronimo's scaffolding could
be accessible to the spring components then that would be most
wonderful.  

Just as a feeler how far off is all this from being mature and
available?

Alex






Re: Integrating Spring into Geronimo

Posted by Colin Sampaleanu <co...@exis.com>.
This is seriously cool!

jastrachan@mac.com wrote:

> Dion let the cat out of the bag...
>
> http://www.almaer.com/blog/archives/000246.html
>
> so I thought I'd best actually commit the code. Warning though I've 
> not tested it yet  - we need an integration test to make sure this 
> works & we handle all the lifecycle methods properly :)
>
> Basically we've a GBean for Geronimo so that any existing spring XML 
> config file can be slurped up & turned into beans and managed in a JSR 
> 77/88 way & hot deployed - so Geronimo can hot deploy arbitrary Spring 
> containers within the core J2EE container - all managed in the same 
> stack as web apps, web containers, EJB containers etc. We should also 
> be able to JMX-ifiy all the beans as they are created into the JSR 
> 77/88 management stack.
>
> At JavaOne we've discussed maybe having a special naming convention, 
> say putting spring.xml inside META-INF/ or something, so that you can 
> put your code in a regular jar with the XML deployment descriptor then 
> drop it in a directory or whatnot and Geronimo could auo-detect it & 
> use the SpringGBean to deploy it.
>
> Its still early days but hopefully once this is sorted out & working, 
> developers can spend their time in development mode just using Spring 
> by itself, then at any point in time drop their jar into Geronimo (or 
> build a deployment binary of Geronimo) and hey presto their apps 
> running inside a J2EE container.
>
> Going forward we should be able to further increase the functionality 
> of the SpringGBean to closer integrate the two projects so that the 
> Spring POJOs can take better, more efficient & easier use of the J2EE 
> services in Geronimo (transactions, security, remoting, pooling, 
> clustering etc).
>
> Enjoy!
>
> James
> -------
> http://radio.weblogs.com/0112098/
>