Am Mittwoch, den 15.08.2007, 14:41 -0400 schrieb Tchang, Jeffrey (Genworth):
> So I've been trying to get CXF to deploy to a BEA Weblogic 10.0 application > server. However, I am running into a number of issues. Most of them have to > do > with the numerous JARs that come with CXF and conflicts with BEA (surprise > surprise). I've opened up support tickets with BEA anyway to see if they can > help. > Pardon the non-answer, but what you're trying to do, could you get it working on Tomcat, or are you using EJB's? I would say normally BEA comes in when you can get it working on Tomcat but not on Weblogic. Whether or not you can get it to work on Tomcat helps to separate the problem as being BEA-specific (if you can) or CXF-specific (if you can't). > The most successful I have been with deploying CXF is using the following > options in weblogic-application.xml: > > <prefer-application-packages> > <package-name>javax.jws.*</package-name> > <package-name>javax.xml.ws.*</package-name> > <package-name>javax.net.ssl.*</package-name> > </prefer-application-packages> > > However, these settings throw a > > java.lang.NoClassDefFoundError: javax/net/ssl/HostnameVerifier at > org.apache.cxf.transport.http.AbstractHTTPTransportFactory.getConnectionFactory(AbstractHTTPTransportFactory.java:244). I would check to see if you can enable classloader logging somewhere in BEA--Oracle App server at least has that option. It may tell you if it can't find certain required JARs. You may find out that you are missing a JAR file not containing the class above, but which has a class that HostnameVerifier can't load without. I had a Spring MVC web application once that worked perfectly on Tomcat but fell apart on OAS. Apparently I had missed one library that Tomcat had by default but OAS didn't--but only OAS classloader logging pointed out the error to me. HTH, Glen
