Thanks all for your help. I decided to use empty nested complexType elements
for no-input soap reqeusts and the generated code works much better.
--
View this message in context:
http://www.nabble.com/soap-requests-with-no-attributes-or-elements-tp16715370p16744039.html
Sent from the cxf-user
Am Dienstag, den 15.04.2008, 19:52 -0700 schrieb Fazle Khan:
> I am trying to use cxf to make a soap request that has no attributes or
> elements and it seems to be generating invalid xml. I assume I'm using the
> api wrong.
>
I don't think you can do that, because it would be a degenerate case
On Wednesday 16 April 2008, Fazle Khan wrote:
> I'm using spring-ws contract-first wsdl generation so I'll see if the
> users on that form have a suggestion.
>
> btw, I did find 2 work arounds till I find a better solution
>
> 1. pass in an empty string for the Object parameter of the service.
>
t that way a typed parameter is
used in the service method and the class is generated.
--
View this message in context:
http://www.nabble.com/soap-requests-with-no-attributes-or-elements-tp16715370p16722537.html
Sent from the cxf-user mailing list archive at Nabble.com.
Hi Fazle,
Since the request has no input, how about change your wsdl a bit to make
it compatible with doc/liter/wrapped so that the generated method
timeSalesAllInstruments() has no input parameter.
I will change your wsdl inline
Regards
Freeman
Fazle Khan wrote:
I am trying to use cxf to mak
lInstrumentsRequest", name = "TimeSalesAllInstrumentsRequest")
java.lang.Object timeSalesAllInstrumentsRequest
);
TimeSalesAllInstrumentsResponse response =
client.timeSalesAllInstruments(null);
I assume I should not be passing null into the method, but what should I
pass?
-fazle
--
