|
From: Thomas R. <tri...@tr...> - 2003-05-12 17:45:14
|
I think we also need to consider what third party jars are required as well. When I use the jdbc classes I currently need to include the following jars: spring-core, spring-jdbc, spring-xmlbean, log4j, aopalliance. Maybe we should have a few select "standalone" configurations in addition to the "full" jar. I think one of them should be the jdbc code - spring-jdbc-only (this should include all "spring" dependencies) with clearly stated third party jars and versions required to use all features. If we need to, we should also document any EJB classloader issues and what jars need to go where. Thomas > We need to review the whole distribution Jar thing. > > The AOP framework is fairly small and, I think, part of the > core. (Not so for the interceptors.) > > I'm inclining towards emphasising a single Jar--the "full" > Jar at present. Simply including this in a web app will do > the job. At a bit over 400K it's not too large, compared to > many other libraries. > > The only problem is that in EJB deployment this may produce > nasty gotchas when the EJB loader is the parent of the WAR > loader. In the release with the book I took care to package > around this issue: I think it's likely Spring in its current > form would pose more problems. > > Personally I see part of Spring's value in that it provides a > lighter-weight alternative to EJB for many things. However, > some users will need to use Spring with EJB, and we need to > support this. > > Any thoughts on this? > > Regards, > Rod > > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > -- Thomas Risberg tri...@tr... |