();
String response = service.sayHi(Client);
Console.Out.WriteLine(response= + response);
flat-out
--
View this message in context:
http://www.nabble.com/WSDL-not-recognized-by-vs-net-tf4599448.html#a13641274
Sent from the cxf-user mailing list archive at Nabble.com.
result to parameters
vs net recognized the WSDL, and string hello.sayHi(string) is
finally available.
Anyone could tell me why?
William Leung wrote:
I am testing CXF and sadlly found that our method parameters and
returns are not recognized in vs net.
VS NET recongnized the sayHi function
in context:
http://www.nabble.com/WSDL-not-recognized-by-vs-net-tf4599448.html#a13132033
Sent from the cxf-user mailing list archive at Nabble.com.
will be very appreciated
--
View this message in context:
http://www.nabble.com/WSDL-not-recognized-by-vs-net-tf4599448.html#a13133442
Sent from the cxf-user mailing list archive at Nabble.com.
The WSDL that you got from from CXF is Document/Literal Wrapped.
If you want to set it to the Document/Literal model , you need to set
the JaxWsServiceFactory's wrapped attribute to be false.
Willem.
William Leung wrote:
I am testing CXF and sadlly found that our method parameters and
from result to parameters
vs net recognized the WSDL, and string hello.sayHi(string) is finally
available.
Anyone could tell me why?
William Leung wrote:
I am testing CXF and sadlly found that our method parameters and returns
are not recognized in vs net.
VS NET recongnized the sayHi
, October 10, 2007 6:48 AM
To: cxf-user@incubator.apache.org
Subject: Re: WSDL not recognized by vs net
Sorry for the newbie question.
Is vs only support not wrapped?
Willem2 wrote:
The WSDL that you got from from CXF is Document/Literal Wrapped.
If you want to set
, October 10, 2007 10:18 AM
To: cxf-user@incubator.apache.org
Subject: RE: WSDL not recognized by vs net
Yes, I am testing on VS 2005.
Unwrapped DOC/LIT - worked but required me to annonate all method with
SOAP
Actions.
Wrapped DOC/LIT - worked but
The default WSDL (CXF 2.0.2) has
