Hi,
is there any way to control the package name of generated exception classes
when going WSDL to Java?
I have a schema file for common exceptions that looks like this:
http://www.w3.org/2001/XMLSchema";>
The WSDL file for my webservice references thi
Hi Daniel, I've put together a little test case.
If you download the zip archive at this link:
http://dl.dropbox.com/u/24296192/JAXWSExample.zip
You will find two maven projects inside. The first one, jaxws-example-model,
contains a simple Java POJO called "Message". The project contains the
nec
I can probably rig something up over the weekend, Daniel. I'd have to trim
some of the fat as I have a full fledged application I'm trying this in; but
I can probably trim some of the fat and simplify it. Gimme a day or two and
I'll get something to you.
--
View this message in context:
http://cx
I'm using the cxf-java2ws-plugin to generate a WSDL file from JAX-WS
annotated classes. For my data objects; I'm specifying the fact that an
external schema file already exists (by adding an @XmlSchema annotation with
a location attribute to the package-info.java file). When the WSDL file gets
gene
Thanks Daniel, makes sense.
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-is-seeing-my-implementor-class-as-the-SEI-tp4914844p4919495.html
Sent from the cxf-user mailing list archive at Nabble.com.
Ahah!
I didn't notice the refs in the request schema; but now that you point them
out; I know what's causing them:
My method declaration for that method on the SEI is as follows:
@ServiceOperation(type=ServiceOperationType.QUERY)
@WebMethod(operationName="getCarrier")
@RequestWra
Hi,
I have a code-to-wsdl CXF webservice
I used the java2ws plugin to generate a WSDL file for the webservice and I
am specifying this wsdl file when I wire up the webservice in Spring; i.e.:
I then use the cxf-codegen plugin to generate the client against this WSDL.
However,it refuses to gen
Thanks Daniel, I just noticed that myself - I should not have had the
serviceName attribute on the interface.
However, I'm still seeing some strangeness
Here is my (modified) interface:
/@WebService(
name="ProvisioningOrderService",
targetNamespace="urn:ws.thinkingphones.com:provisioningord
I've been developing a code-first WebService with CXF, version 2.4.3;
following the guidelines at
http://cxf.apache.org/docs/developing-a-service.html#DevelopingaService-Writingtheinterface
My SEI interface is:
/@WebService(
name="ProvisioningOrderService",
serviceName="ProvisioningOrderService