Win a copy of Functional Design and Architecture this week in the Functional programming forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

WAS v3.5 or v4.0

Ranch Hand
Posts: 65
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have a general practice question regarding WAS. We currently have an NON-EJB application deployed on WAS v3.5.6 on a Win2K server and it is working just fine.
Now, is it very necessary to go to WASv4.0? I do realize that the support for v3.5 will be stopped in Summer2003, but I have to admit, I am not too sure it would be worth our while to migrate as from what I have read about v4.0 most of the new features & advantages have to do with EJBs. Here is why I think v3.5 is fine and I'd appreciate it if someone could play the devil's advocate and give me good reasons as to why we should migrate.
1. We are just using Servlets v2.2 and JSPs v1.0 and it will be rather tedious to upgrade all our JSPs(about 120 or so) to v1.1
2. We are also using CCF connectors provided by VAJ3.5 to connect to back end legacy programs and I read that the CCF connectors are no longer used in WAS v4.0, so we might have to potentially migrate our application to use J2C connectors and that will be a major effort. And I haven't come across anyone that has successfully made an application using CCF connectors work on WAS v4.0
3. using the AAT seems more complicated that just installing the app on WAS v3.5 . I tried installing our application with just a web-module without any EJBs and am running in to roadblocks.
4. We don't anticipate too many changes to our application any time soon, to what would be the harm in staying with v3.5.6 indefinitely???
As u can see I am leaning towards sticking with WAS v3.5.6, but I would really like to know why&if I am wrong in thinking this. Any advice and options are most welcome--
Thanks & Regards,
Ranch Hand
Posts: 133
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
performance could be the only reason here for updatin considering no ejb
how many user is the system experiencing now & whts the forecast ...
Posts: 13459
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm surprised that you seem to have managed 18 posts without being told of the JavaRanch naming policy.
The details can be found here:
We require that your display name be your first name, a space, then your last name. People who refuse get their accounts locked. (this isn't a threat, just a warning that others might assume that you've been warned already)
A tiny monkey bit me and I got tiny ads:
Thread Boost feature
    Bookmark Topic Watch Topic
  • New Topic