It depends on what do you need. Spring gives you a lot of flexibility. The question is, how much flexibility you need? Spring is little difficult to grasp at first.
But I'd certainly not label spring as overkill. You can use only the parts you need. In web application it really doesn't matter if you have one additional 1.5 megs jar or not. Quite often you start using spring for basic stuff (IOC, some simple AOP) and then you need something more, and you find out that the support is already there. We integrated spring in one project and at some point, we needed to publish a service as WebService (but not necessarily SOAP). So I put couple of lines to the spring configuration file and the service was exported. It haven't taken more than 30 minutes to get it working. -Matej Vincent Jenks wrote: > Right, right, I understand all of that...but the configuration looks > similar...it seems like a good candidate for this portal project for > externalizing resources. In other words - Spring might be overkill if > it can be done more easily w/ Obix if I were to use EJB3. > > I guess I was thinking aloud....heh. > > On 6/14/06, Matej Knopp <[EMAIL PROTECTED]> wrote: >> IOC + AOP + Remoting + Lot of other stuff. >> Spring is a swiss army knife of web development :) >> >> -Matej >> >> Igor Vaynberg wrote: >>> i dont think so. spring is an ioc container at the very least. obix is >>> just a lib to make it easy to read in config files. >>> >>> -Igor >>> >>> >>> On 6/14/06, *Vincent Jenks * <[EMAIL PROTECTED] >>> <mailto:[EMAIL PROTECTED]>> wrote: >>> >>> Coincidentally, I came across this article the other day: >>> >>> http://www.javaworld.com/javaworld/jw-06-2006/jw-0605-obix.html >>> >>> It seems like Obix has a lot of overlap w/ Spring, no? >>> >>> On 6/14/06, Igor Vaynberg <[EMAIL PROTECTED] >>> <mailto:[EMAIL PROTECTED]>> wrote: >>> > they have made some improvements yes. but as i said, if you know >>> what you >>> > are doing xml is minimal even in 1.2.6 >>> > >>> > -Igor >>> > >>> > >>> > >>> > On 6/14/06, Vincent Jenks <[EMAIL PROTECTED] >>> <mailto:[EMAIL PROTECTED]>> wrote: >>> > > >>> > Perhaps it'd be worth developing a container and non-container >>> based >>> > version of the project...or something in between. I suppose I'll >>> need >>> > to do my homework first! >>> > >>> > Is Spring 2.x moving away from XML? I just downloaded the M5 >>> > reference, I'll flip through it for a bit. >>> > >>> > On 6/14/06, Igor Vaynberg <[EMAIL PROTECTED] >>> <mailto:[EMAIL PROTECTED]>> wrote: >>> > > spring has simple transaction demarcation, see @Transactional >>> annotation. >>> > > and as far as persistence if using spring 1.x you can use >>> hibernate with >>> > > ejb3 annotations, or if using spring 2.x you can use hibernate's >>> > > entitymanager which is basically ejb3 and they have jpa (or wtf >>> that >>> > acronym >>> > > is) support as well >>> > > >>> > > -Igor >>> > > >>> > > >>> > > >>> > > On 6/14/06, Vincent Jenks <[EMAIL PROTECTED] >>> <mailto:[EMAIL PROTECTED]>> wrote: >>> > > > >>> > > >and for a portal this xml you /will/ want to have >>> > > > configurable at deployment time in order to configure what >>> > > portlets/services >>> > > > are available to the portal - so even with ejb3 this kind of >>> stuff still >>> > > has >>> > > > to be in some external config. >>> > > >>> > > I was actually thinking about that the other day...you're >>> absolutely >>> > > right on that point, it has to be externalized somehow. >>> > > >>> > > I don't see how Spring couldn't be used to compliment EJB 3.0 >>> in the >>> > > regard. Spring could be used to externalize modular resources, >>> i.e. >>> > > portlets whereas EJB3 could do what it does best...persistence and >>> > > simple transaction demarcation. >>> > > >>> > > >>> > > _______________________________________________ >>> > > Wicket-user mailing list >>> > > Wicket-user@lists.sourceforge.net >>> <mailto:Wicket-user@lists.sourceforge.net> >>> > > https://lists.sourceforge.net/lists/listinfo/wicket-user >>> > > >>> > > >>> > > >>> > > >>> > > _______________________________________________ >>> > > Wicket-user mailing list >>> > > Wicket-user@lists.sourceforge.net >>> <mailto:Wicket-user@lists.sourceforge.net> >>> > > https://lists.sourceforge.net/lists/listinfo/wicket-user >>> > > >>> > > >>> > > >>> > >>> > >>> > _______________________________________________ >>> > >>> > Wicket-user mailing list >>> > Wicket-user@lists.sourceforge.net >>> <mailto:Wicket-user@lists.sourceforge.net> >>> > https://lists.sourceforge.net/lists/listinfo/wicket-user >>> > >>> > >>> > >>> > >>> > _______________________________________________ >>> > Wicket-user mailing list >>> > Wicket-user@lists.sourceforge.net >>> <mailto:Wicket-user@lists.sourceforge.net> >>> > https://lists.sourceforge.net/lists/listinfo/wicket-user >>> > >>> > >>> > >>> >>> >>> _______________________________________________ >>> Wicket-user mailing list >>> Wicket-user@lists.sourceforge.net >>> <mailto:Wicket-user@lists.sourceforge.net> >>> https://lists.sourceforge.net/lists/listinfo/wicket-user >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Wicket-user mailing list >>> Wicket-user@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wicket-user >> >> >> _______________________________________________ >> Wicket-user mailing list >> Wicket-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wicket-user >> > > > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
