|
From: Rod J. <rod...@in...> - 2003-08-29 17:53:45
|
> This raises a ***primary question*** of whether Spring is to be J2EE > centric or if it is to have a broader scope. Our website and sourceforge > project both emphasize its J2EE nature. If it is the latter, we should > probably provide a convenient set of jars for non-J2EE developers. This > would emphasize to developers (both Spring and users) that Spring is not > just about J2EE. I realize that it may not be good to try to be too many > things to too large an audience. Personally, I don't see why it needs to > be limited to J2EE. I haven't given up on Java for desktop applications. > What are your thoughts on this ??? Ken, This is a good point. Spring is more than just a J2EE framework. Parts of it are focused around J2EE APIs (web framework, EJB access and implementation) but the basic concept is applicable to *all* Java applications. This is one of the differentiators from Struts and co, and thank you for reminding me: I'll say that in my forthcoming TSS article. I've used Spring in non-J2EE server-side applications: effectively services without a container. Of course users can simply ignore the J2EE dependencies in unused classes in Spring Jars. Btw, last week someone asked me whether there were any plans for a .NET port. While I have no plans for this, I think the basic architectural approach would cross over nicely. Regards, Rod |