OK, so I found a blog post about wrapping the WAR with an EAR and
putting various excludes in the Weblogic DD. That got my app
deploying. However, when I try to invoke a service at runtime, I get
this:
...
Caused by: javax.xml.soap.SOAPException: Unable to create message
factory for SOAP: weblogic.webservice.core.soap.MessageFactoryImpl
at javax.xml.soap.MessageFactory.newInstance(Unknown Source)
at
org.apache.cxf.binding.soap.saaj.SAAJOutInterceptor.handleMessage(SAAJOutInterceptor.java:80)
... 29 more
It looks like even if I force the app to use the latest spec JARs and
things, the WebLogic SOAP implementation is being used as default
instead of whatever CXF would prefer. Any idea how I can avoid this?
Putting in a prefer package line for javax.xml.soap.* wasn't enough.
Thanks,
Aaron
On Thu, Dec 4, 2008 at 2:42 PM, Nepali, Sonam (GE Healthcare,
consultant) <[EMAIL PROTECTED]> wrote:
> In Weblogic you may need to add the information about packages that need
> to be used from your project versus out of the weblogic library jars.
> It is done by adding the info in the application deplyoment descriptor
> file. I think weblogic jars are perhaps being used instead of your cxf
> jars.
>
> thanks
>
> Sonam Nepali
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron
> Mulder
> Sent: Thursday, December 04, 2008 12:35 PM
> To: [email protected]
> Subject: JAX-WS services in WebLogic 10
>
> So I have a Spring-and-CXF app that works fine in Jetty. The Web
> Services in the app are done using a <jaxws:endpoint> element in the
> Spring config file.
>
> When I deploy this in WebLogic 10, it blows up. Apparently WebLogic
> finds the beans with the JAX-WS annotations, and tries to deploy them as
> Web Services itself -- before CXF is ever involved. This blows up
> because it uses the Sun RI that expects some generated code that CXF
> does not require.
>
> Has anyone seen this before? Any ideas for how I can convince WebLogic
> to ignore the JAX-WS services so that CXF will be the only thing that
> handles them?
>
> Thanks,
> Aaron
>
