Ronald Pieterse wrote: > > However this uses classes from the server since I have no client code > generated here. You don't want to have your clients do this, right? >
You can split out the JAX-WS artifacts into a separate JAR, usable by both client and service provider, using Maven's assembly plugin: http://www.jroller.com/gmazza/date/20080417#WFstep2 Ronald Pieterse wrote: > > My service is MTOM enabled through the WebService annotation like so: > @BindingType(value = SOAPBinding.SOAP11HTTP_MTOM_BINDING) > > My questions: > 1. Why does using SOAP12HTTP_MTOM_BINDING throw the following exception > for me: > Have no idea. Hopefully someone else can help here, or just say with SOAP11 if you can. Here's my MTOM sample of last year, maybe it has something you can snarf: http://www.jroller.com/gmazza/date/20071102 Ronald Pieterse wrote: > > 2. My Axis 1.4 client code does not work when I try to invoke the call. > Could this be due to incompatibility between CXF 2.1.1 and Axis 1.4? > It was generated just fine but invocation of the getFile method throws the > following exception: > > Axis 1.4 is not a JAX-WS implementation, and I'm unsure if MTOM existed when Axis 1.x was implemented--regardless, I would ask on the Axis user's list for this. Or Google your exception stack. Ronald Pieterse wrote: > > 3. How do I generate client code with CXF 2.1.1? I can't seem to find the > WSDL2Java file anymore. I have the JAX-WS frontend stuff in my classpath > (I use maven so it came in with CXF) > The link I gave you at the top shows an Ant and Maven way of running wsdl2java. HTH, Glen -- View this message in context: http://www.nabble.com/Problem-client-code-MTOM-enabled-service-%28CXF-2.1.1%29-tp18961332p18972873.html Sent from the cxf-user mailing list archive at Nabble.com.
