Never mind -- my build script wasn't properly rebuilding the client stub.
Thanks.
On 3/1/08, Michael Nelson <[EMAIL PROTECTED]> wrote:
>
> I am using CXF 2.0.4 on both client and server. I have a simple server
> interface derived from one of the samples (see below). When
For non-trivial methods, WSDL2Java forces me to deal with request/response
wrapper classes in the client code it generates (see the 1st method as
compared to the 2nd method). Is there a way to prevent this?
Thanks,
-mike
Examples:
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE
I am using CXF 2.0.4 on both client and server. I have a simple server
interface derived from one of the samples (see below). When I try to call
the "deleteCustomer" function using the CXF 2.0.4 wsdl2java client, the
first element of the paramArray passed into
org.apache.cxf.jaxws.JAXWSMethodInvoke
// parameter though.
> sf.getServiceFactory().setWrapped(false);
>
>sf.create();
>}
>
> Willem.
>
> Michael Nelson wrote:
> > I am trying to figure out how to get access to WebServiceContext in the
> > restful_http_binding sample that comes with CX
I am trying to figure out how to get access to WebServiceContext in the
restful_http_binding sample that comes with CXF. In CustomerServiceImpl.java,
I've added:
@Resource
private WebServiceContext wsContext;
to the CustomerServiceImpl class.
But wsContext isn't set when methods are invo
I am trying to figure out how to get access to WebServiceContext in the
restful_http_binding sample that comes with CXF 2.0.3. In
CustomerServiceImpl.java, I've added:
@Resource
private WebServiceContext wsContext;
to the CustomerServiceImpl class.
But wsContext isn't set when methods ar
