UNCLASSIFIED////
I have 2.0-incubator working fine in Weblogic 9.2 using a JAX-WS frontend. It's probably overkill but I have even more in my prefer-application-packages. Here's my weblogic-application.xml contents : <?xml version="1.0" encoding="UTF-8"?> <weblogic-application xmlns="http://www.bea.com/ns/weblogic/90"> <application-param> <param-name>webapp.encoding.default</param-name> <param-value>UTF-8</param-value> </application-param> <prefer-application-packages> <package-name>javax.jws.*</package-name> <package-name>org.apache.xerces.*</package-name> <package-name>com.ctc.wstx.*</package-name> <package-name>org.springframework.*</package-name> </prefer-application-packages> </weblogic-application> I would have guessed 10.0 would be easier with builtin JAX-WS support. -- Jamie -----Original Message----- From: Tchang, Jeffrey (Genworth) [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 15, 2007 5:24 PM To: [email protected] Subject: RE: Deploying CXF to Weblogic 10.0 > > 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). I have not tried in Tomcat yet but it works locally without an application server. The more general question I had was if anyone had managed to get CXF working out of the box in a BEA Weblogic environment. > > 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.get > ConnectionFactory(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. Sounds like a good idea. I will double check how to enable classloader logging in BEA. Thanks. -Jeff UNCLASSIFIED////
