Re: [Springframework-developer] Creating reusable component packages with Spring

[Mike Cannon-B. <mca...@gm...>]

Please no mandatory JNDI! :)=20

Spring rocks because the bean configuration to a large extent replaces
JNDI in an enterprise application (yes, I know what JNDI is for - but
realistically in _most_ J2EE apps it's a large map to retrieve your
"stuff" from - a Spring context).

Other than that mini-rant, a Spring "component" unit would be awesome.

m

On Wed, 10 Nov 2004 08:42:36 +0000, jas...@ma...
<jas...@ma...> wrote:
> Its an interesting question. Just one immediate thought; I can see
> there being a need for a Spring deployment unit of some kind; e.g. a
> jar containing an applicationContext.xml file in APP-INF/ or something
> - maybe having any additional jars required inside the jar in
> APP-INF/lib.
>=20
> One there's a deployment unit we can add native support to Geronimo
> (and other containers could support it too) plus we could support hot
> deployment of units inside Spring natively rather than relying on the
> J2EE deployment units (WAR / EAR / RAR)
>=20
> If there was a deployment unit; the only real issue is how to handle
> cross-deployment unit references; but we could always use JNDI / JMX
> for that or use a hierarchy of BeanFactory instances.
>=20
>=20
>=20
>=20
> On 9 Nov 2004, at 22:51, James Cook wrote:
> > We have been developing a large enterprise application using Spring
> > and it
> > has proven to be a very effective framework. We use the Data access
> > abstractions heavily, along with transaction management and Hibernate
> > support.
> >
> > Now that we have most of the concepts down, some coworkers and myself
> > are
> > now considering the challenges inherent in packaging our business
> > objects,
> > service layers, spring configuration files, etc. into reusable
> > component
> > packages. We want to be able to give other developers in the company a
> > jar
> > file that contains all of this content and simply drop it into their
> > project.
> >
> > There are a lot of similarities (and differences) between what we face
> > and
> > what EJB components deal with. EJB has solutions for mapping
> > dependencies in
> > a component package to the primary application (ejb-ref, etc.) and we
> > are
> > beginning to talk about how to accomplish similar behavior using
> > Spring.
> >
> > Ultimately, there are probably many nuances to this process that we
> > won't
> > know until we actual do it, but I was wondering if the development
> > team has
> > some insight into some of the Spring features that already exist that
> > can
> > assist in some of these challenges? Perhaps also there are some
> > features
> > that are on the drawing board to assist in this matter also?
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by:
> > Sybase ASE Linux Express Edition - download now for FREE
> > LinuxWorld Reader's Choice Award Winner for best database on Linux.
> > http://ads.osdn.com/?ad_idU88&alloc_id=12065&op=3Dclick
> > _______________________________________________
> > Springframework-developer mailing list
> > Spr...@li...
> > https://lists.sourceforge.net/lists/listinfo/springframework-developer
> >
> >
>=20
> James
> -------
> http://radio.weblogs.com/0112098/
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_idU88&alloc_id=12065&opclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20


--=20
ATLASSIAN - http://www.atlassian.com