The Magnolia instance I run is at home and I can put it on whatever JVM I want, but were I to introduce it at work, we would be hard-pressed to move to 1.5. Just this year we're migrating off WebSphere 5.0 (1.3 API) to 6.0 (1.4). We won't standardize on an app server that supports the 1.5 JDK for probably another year or so.
As an enterprise architect, I am trying to influence some varying tiers of service, and one I'm pushing is for apps that don't need an EJB container. I would like to see us put up a Tomcat infrastructure to support those apps. In that case I would push 5.5 on Linux on commodity hardware (we're moving our WebSphere there also), at which point we could run 1.5 apps pretty easily. Moving our existing apps on WebSphere versions is a huge undertaking though, so we will always be lagging there. The point of all this is that I think if you want to make inroads into large companies, you will have to maintain support for the older Java API, or be prepared to convince companies to build out an infrastructure that diverges from their standard to support your app. There's my $.02 :-) Mick Smothers Minneapolis, MN ----- Sameer Charles <[email protected]> wrote: > I am not sure if its best to stick with JDK 1.4 or start moving to > 1.5, do you guys have experience especially on websphere and weblogic > > application servers? > > I am worried that many people are still using 1.4 compatible app > servers, simply because every time you upgrade commercial software > you need to pay. > > please let us know your opinion, If we decide to stick with 1.4 for > the time being we should quickly adopt for the release. I noticed > some places where 1.5 API is used. > > Regards, > - Sameer > > ---------------------------------------------------------------- > for list details see > http://www.magnolia.info/en/magnolia/developer.html > ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
