Den 10/09/10 16.38, Murali Rao skrev:
We use Tomcat for windows server for servlet req/res, and WAS implementation on i.

What is the actual reason for us to move to Glassfish if we have tomcat for windows& WAS for i? Are there any real benefits?
In my opinion, if you don't see any reason to upgrade, I would not bother. WAS is supported by IBM on the i and supports Java EE 5, and Tomcat does very well as a stand-alone web container under Windows.

There is, however, so much new and very interesting technologies in Java EE 6 that it is a good idea to at least _consider_ it if you are doing new development these days.

Some examples:

* CDI - a technology to glue components together without them knowing of one another (through the "new" keyword). This allows for a library list approach to Java components which we are investigating in.
* JavaServer Faces - a technology to create very complex web pages as simple XHTML-pages. The 2.0 version in EE 6 is much, much nicer to work with than earlier versions.
* Web Services - the Java 6 approach is well embedded in Java EE 6, and just requires a few annotations on the method you want to expose, plus a few hints to let the rest be done by the system.

Plenty more: http://www.oracle.com/technetwork/java/javaee/tech/index.html

Glassfish also has the very nice autodeploy folder, where you just drop in WAR and EAR files and they automatically deploy, and when you delete them, they undeploy. I do not know if WAS can do that.

But again, WAS is well supported by IBM. Unless you really have the need to go with unsupported software (at least until we figure out the magic words to make it work) then stay with WAS


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.