Thinking about switching from Oracle Applicationserver to Glassfish
Hi,
I'm responsible for developing a huge, innovative javaee application. Currently the application is running on the latest Oracle Application Server 10.x. I'm seriously thinking about switching to Glassfish.
The reason is that Glassfish seems to offer the best support for the latest standards and open source frameworks such as EJB3, JSF 1.2, JAX-WS, Hibernate and Spring.
The next days I will try to talk a little bit about the problems about switching to the latest Glassfish V2.
posted by Klaus Stake at
8:12 AM
5 Comments:
Good decision!
11/22/2006 11:31 PM
Hello,
Can you give more details about the exact reason you want to switch?
Will not post as anonymous user, and I am probably biased since I am Product Manager for OC4J ;-)
However, here some comments:
- EJB 3.0 support: as you may know, the Reference Implementation of EJB3 is based on Toplink Essentials. So it is not "better" support in Glassfish since the source is Oracle.
- Hibernate: OC4J supports hibernate, you just need to apply a specific configuration of the class loader as documented here
- Spring: Oracle has made lot of work to support Spring as you can see here: http://www.oracle.com/technology/tech/java/spring.html
- For JAX-WS: do you have specific requirements that are not satisfied by JAX-RPC and the JSR181. It is really interesting to me to understand that
- On JSF, it is true that Oracle does not support 1.2 Yet, however we do provide using ADF Faces or MyFaces-Trinidad. After all the runtime is really important for JSF, but I also think that the rich set of components you can use is also really important
11/27/2006 1:40 AM
Just to add, when I am talking about EJB3 and toplink essential I am talking about the JPA implementation
11/27/2006 1:43 AM
Hi,
I run into compatibility problems using JAX-WS RI in OC4J, saaj.jar to be specific.
The specific requirements in JAX-WS RI is the generation of Java code from a WSDL. The WSDL my client provides contains complex types that are unbounded choice elements. See example:
..s:complexType name="GenericRequest"
....s:sequence
......s:choice minOccurs="0" maxOccurs="unbounded"
........s:element minOccurs="0" maxOccurs="1" name="OperationA" type="xyz:OperationA"
........s:element minOccurs="0" maxOccurs="1" name="OperationC" type="xyz:OperationB"
etc (real example many more elements)
JAX-WS conveniently generates Java beans with method List getOperationAorOperationB(), so I can provided arbitrary combinations of operationA and operationB elements.
Alternatives using Axis, JAX-RPC do not generate this code, they generate getOperationA and getOperationB so no list.
Regards Marcel
2/05/2007 5:54 AM
I'm pursuing a dual track policy so there is a viable alternative. OAS licensing is $5K per CPU which on a series of large web site
/services deployments as we are planning, is expensive (though I work for an Oracle partner so the real cost could be less). I've developed Java-first web services and the main effort was getting the deployment descriptors right. Also, the released OC4J (10.3.1.1) is not as strict as the forthcoming OC4J and current Glassfish re annotations (see my post on http://forums.java.net/jive/thread.jspa?
messageID=238474) which caused some pain. However, about a week of work has brought me to the point where my web services work on both.
10/09/2007 3:54 AM
Post a Comment
<< Home