Re: [Springframework-developer] Spring/Geronimo

[<jas...@ma...>]

On 9 Jul 2004, at 14:58, j=FCrgen h=F6ller [werk3AT] wrote:
> First of all, great to see the interest from the Geronimo side, and=20
> particularly your efforts on this, James!
>
> Regarding deployment units, I see 2 use cases:
> - a deployment unit that exposes remote beans, for example via RMI

Or maybe an alternative to MDBs or web services too.

> - a deployment unit that exposes a local bunch of components, to be=20
> accessed from multiple WARs in the same server

Agreed - or things which become available for reuse by other=20
deployments via JNDI etc.


> A single standard WAR that uses Spring within doesn't need special=20
> treatment: =46rom my point of view, that should still be deployed as=20=

> WAR, as there is no real benefit in deploying it as a special unit. So=20=

> basically, I envisage something similar to an EJB JAR, rather than a=20=

> WAR replacement.

Agreed - however it'd be nice to maybe expose Spring created POJOs to=20
the Geronimo management stack if a standard WAR were used. Maybe=20
Geronimo & Spring could detect each other somehow (e.g. Geronimo could=20=

look for a magic Spring file) and so expose the Spring stuff to=20
Geronimo's management stack. I guess the other option is to allow folks=20=

to use Spring-JMX inside the WAR.


> An EAR-like deployment unit that contains both standard WARs and=20
> Spring JARs is a different matter, I guess: There's no strong need for=20=

> it, as WARs and Spring JARs can easily be deployed separately to the=20=

> same server, at least for a start. Let's concentrate on an=20
> EJB-JAR-style deployment unit first!
>
> Questions are: How are remote beans able to interoperate with the=20
> server's central RMI infrastructure, and how are local components able=20=

> to expose themselves in some subtree of the server's central JNDI=20
> registry? Very similar to the needs of an EJB container, actually :-)

We need to figure out what the various connectors are (JNDI, JCA, JMS,=20=

RMI, WS etc) and then hopefully the geronimo-spring deployer would take=20=

care of wiring things up; though we need to figure out how to expose=20
this stuff neatly.


> Regarding the name: EJB JARs don't have a special name,

They're called EARs.

> as far as I know, but "Spring JAR" sounds a bit too generic. SPAR is=20=

> nice, although it's the name of a food chain ;-)

:) I'm easy really, call 'em anything you like.

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