On Thu, 02 Sep 2004 19:06:44 -0400, Frank Zammetti <[EMAIL PROTECTED]> wrote: > Ironic as it seems to myself to be saying it, I don't think I like the idea > of Struts moving to newer spec/JDK versions just yet. > > Here at work, most of our development is now Struts-based, and much of it is > moving to IBM Portal Server. Unfortunately, because of some issues between > that product and WebSphere itself (and probably some other components), we > are currently very sensitive to versioning, more so than we might otherwise > be.
Ironically, people wanting to run Struts in a portlet (JSR-168 compatible) environment should be the ones most interested in a Struts revolution :-). The current method signatures for all the important methods are very much dependent on the servlet APIs, and the various portal server vendors have all done their own (non-interoperable) modifications to Struts to make it kind-of sort-of work. We should be doing that. We can't do that based on Servlet 2.2 / JSP 1.1. Craig > > For instance, I have a production app that is based on Struts 1.1, and I > have it running on a "rogue" Tomcat server with JDK 1.3.1 because IBM is not > yet supporting a higher JDK version, believe it or not! > > If the newest Struts has a bunch of cool features, but it requires a higher > JDK or higher servlet specs than Tomcat or Websphere (when we finally figure > out how to get the app up on it), I'm going to be in a bind with this app > because I'm sure to want to use those features (and being able to make some > good business cases for doing so even) but not be able to. If nothing else, > that's going to be depressing :) > > The flip-side of the argument of course is that eventually everyone is going > to want, and be able, to move to all the newest specs, JDK levels, etc., me > along with them. And of course the difficult decision is when to make that > move. My point in the end I think is that if you can scratch the itches > without *requiring* newer versions of anything, I think that would be ideal. > For those things that absolutely can't be done without newer versions, I'd > like to see those new features optional or swappable in some way. > I don't believe it is possible to "scratch the itches without *requiring* newer versions of anything." Choosing a newer version of servlet or JSP apis is buying in to the ability to do the fundamental architecture of Struts in a new and different way. That's not the kind of thing you do with "optional add on packages that have extra requirements." > Frank W. Zammetti > Founder and Chief Software Architect > Omnytex Technologies > www.omnytex.com > Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
