Re: WSDL not recognized by vs net
Hi.
This way might be another way to get doc/literal bare WSDL.
We just need to add annotation @SOAPBinding.
import javax.jws.soap.SOAPBinding;
import javax.jws.WebService;
import javax.jws.WebParam;
@SOAPBinding(style=SOAPBinding.Style.DOCUMENT,
use=SOAPBinding.Use.LITERAL,
parameterStyle=SOAPBinding.ParameterStyle.BARE)
@WebService
public interface HelloWorld {
String sayHi(@WebParam(name="text") String text);
}
So we can write client-side code like this:
//doc/lit wrapped
HelloWorldImplService service = new HelloWorldImplService();
CXFSpring.sayHi hi = new CXFSpring.sayHi();
hi.text = "Client";
CXFSpring.sayHiResponse response = service.sayHi( hi);
Console.Out.WriteLine("response=" + [EMAIL PROTECTED]);
//doc/lit bare
HelloWorldImplService service = new HelloWorldImplService();
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.
RE: WSDL not recognized by vs net
Sadly, I still don't know why my wsdl, even with parts named 'parameters', still misfires. As soon as I find out I'll let you know. > -Original Message- > From: Daniel Kulp [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 11, 2007 5:43 PM > To: cxf-user@incubator.apache.org > Cc: William Leung > Subject: Re: WSDL not recognized by vs net > > > This is committed and a new 2.0.3 SNAPSHOT is being deployed now. > Another 20 minutes or so. I'd really appreciate it if you could give > it a try and see if it works with .NET a bit better. > > Dan > > > On Thursday 11 October 2007, Daniel Kulp wrote: > > Spent a bunch of time playing with the JWS and JAXWS TCK's last night > > and digging though specs to figure out what can be done here. > > > > 1) For the simple frontend, I can definitely make the > > default "parameters" for all cases. > > > > 2) For jaxws, I can make the default parameters for MOST cases. > > There are one or two cases where I cannot, but they are edge cases. > > (Example: all the OUT parts are header="true". The resulting wrapper > > type is an empty complex type.) > > > > Anyway, I'm going to work on getting this committed today. > > > > Dan > > > > On Wednesday 10 October 2007, William Leung wrote: > > > Very annoyance :((( > > > > > > After quite a few trys, I finally make HelloWorld worked with vs net > > > (2005). > > > > > > just change these line in WDSL: ( wrapped DOC/LIT ) > > > > > > > > > > > > > > > > > > > > > after change the name 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 function as > > > > --- sayHi ( sayHi As sayHi ) As sayHiResponse > > > > it should be > > > > --- sayHi ( arg0 As string) as string > > > > > > > > > > > > When I change the wsdl manually from > > > > > > > > > > > > > > > > > > > >> > > type="xsd:string"/> > > > > > > > > > > > > to > > > > > > > > > > > > > > > > > > > > > > > type="xsd:string"/> > > > > > > > > > > > > > > > > It worked, but I have no idea how could I make this changes > > > > without switch to "wsdl first" (I dont want to, I have just too > > > > many methods to export) > > > > > > > > Any help will be very appreciated > > > > -- > J. Daniel Kulp > Principal Engineer > IONA > P: 781-902-8727C: 508-380-7194 > [EMAIL PROTECTED] > http://www.dankulp.com/blog
Re: WSDL not recognized by vs net
This is committed and a new 2.0.3 SNAPSHOT is being deployed now. Another 20 minutes or so. I'd really appreciate it if you could give it a try and see if it works with .NET a bit better. Dan On Thursday 11 October 2007, Daniel Kulp wrote: > Spent a bunch of time playing with the JWS and JAXWS TCK's last night > and digging though specs to figure out what can be done here. > > 1) For the simple frontend, I can definitely make the > default "parameters" for all cases. > > 2) For jaxws, I can make the default parameters for MOST cases. > There are one or two cases where I cannot, but they are edge cases. > (Example: all the OUT parts are header="true". The resulting wrapper > type is an empty complex type.) > > Anyway, I'm going to work on getting this committed today. > > Dan > > On Wednesday 10 October 2007, William Leung wrote: > > Very annoyance :((( > > > > After quite a few trys, I finally make HelloWorld worked with vs net > > (2005). > > > > just change these line in WDSL: ( wrapped DOC/LIT ) > > > > > > > > > > > > > > after change the name 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 function as > > > --- sayHi ( sayHi As sayHi ) As sayHiResponse > > > it should be > > > --- sayHi ( arg0 As string) as string > > > > > > > > > When I change the wsdl manually from > > > > > > > > > > > > > > >> > type="xsd:string"/> > > > > > > > > > to > > > > > > > > > > > > > > > > > type="xsd:string"/> > > > > > > > > > > > > It worked, but I have no idea how could I make this changes > > > without switch to "wsdl first" (I dont want to, I have just too > > > many methods to export) > > > > > > Any help will be very appreciated -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
Re: WSDL not recognized by vs net
Spent a bunch of time playing with the JWS and JAXWS TCK's last night and digging though specs to figure out what can be done here. 1) For the simple frontend, I can definitely make the default "parameters" for all cases. 2) For jaxws, I can make the default parameters for MOST cases. There are one or two cases where I cannot, but they are edge cases. (Example: all the OUT parts are header="true". The resulting wrapper type is an empty complex type.) Anyway, I'm going to work on getting this committed today. Dan On Wednesday 10 October 2007, William Leung wrote: > Very annoyance :((( > > After quite a few trys, I finally make HelloWorld worked with vs net > (2005). > > just change these line in WDSL: ( wrapped DOC/LIT ) > > > > > > > after change the name 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 function as > > --- sayHi ( sayHi As sayHi ) As sayHiResponse > > it should be > > --- sayHi ( arg0 As string) as string > > > > > > When I change the wsdl manually from > > > > > > > > > > > > > > > > > > to > > > > > > > > > > > type="xsd:string"/> > > > > > > > > It worked, but I have no idea how could I make this changes without > > switch to "wsdl first" (I dont want to, I have just too many methods > > to export) > > > > Any help will be very appreciated -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
RE: WSDL not recognized by vs net
AFICT, this is a Microsoft 'feature'. It is creating 'wrapped' structures, not 'cracking' the param list. I am thinking of opening a support request at Microsoft; there used to be a way to avoid this. > -Original Message- > From: William Leung [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 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 this problem, this method is not > available > in the generated stub: > >string sayHi(string) > > > To call sayHi, I have to write urgly codes: > >localhost.HelloWorld client = new localhost.HelloWorld(); >localhost.localhost.sayHiRequest request = new localhost.sayHiRequest(); >localhost.sayHiResponse response; > >request.arg0 = "World"; >response = client.sayHi(request); > >String result = response.return; // "Hello World" > > > until I change the WSDL's Response's part name from "result" to > "parameters". > > > > bmargulies wrote: > > > > What version of Visual Studio? With 2005, I don't see a difference based > > on part names. There is a web page out there that claims that wsdl.exe > > does different things depending on the part name, but 2005 works just > > the same (wrapping parameters in an object) either way. > > > >> -Original Message- > >> From: William Leung [mailto:[EMAIL PROTECTED] > >> Sent: Wednesday, October 10, 2007 8:01 AM > >> To: cxf-user@incubator.apache.org > >> Subject: Re: WSDL not recognized by vs net > >> > >> > >> Very annoyance :((( > >> > >> After quite a few trys, I finally make HelloWorld worked with vs net > >> (2005). > >> > >> just change these line in WDSL: ( wrapped DOC/LIT ) > >> > >> > >> > >> > >> > >> > >> after change the name 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 function as > >> > --- sayHi ( sayHi As sayHi ) As sayHiResponse > >> > it should be > >> > --- sayHi ( arg0 As string) as string > >> > > >> > > >> > When I change the wsdl manually from > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > to > >> > > >> > > >> > > >> > > >> > > type="xsd:string"/> > >> > > >> > > >> > > >> > > >> > It worked, but I have no idea how could I make this changes without > >> switch > >> > to "wsdl first" (I dont want to, I have just too many methods to > > export) > >> > > >> > Any help will be very appreciated > >> > > >> > >> -- > >> View this message in context: > > http://www.nabble.com/WSDL-not-recognized- > >> by-vs-net-tf4599448.html#a13134355 > >> Sent from the cxf-user mailing list archive at Nabble.com. > > > > > > > > -- > View this message in context: http://www.nabble.com/WSDL-not-recognized- > by-vs-net-tf4599448.html#a13136844 > Sent from the cxf-user mailing list archive at Nabble.com.
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 this problem, this method is not available in the generated stub: string sayHi(string) To call sayHi, I have to write urgly codes: localhost.HelloWorld client = new localhost.HelloWorld(); localhost.localhost.sayHiRequest request = new localhost.sayHiRequest(); localhost.sayHiResponse response; request.arg0 = "World"; response = client.sayHi(request); String result = response.return; // "Hello World" until I change the WSDL's Response's part name from "result" to "parameters". bmargulies wrote: > > What version of Visual Studio? With 2005, I don't see a difference based > on part names. There is a web page out there that claims that wsdl.exe > does different things depending on the part name, but 2005 works just > the same (wrapping parameters in an object) either way. > >> -Original Message- >> From: William Leung [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, October 10, 2007 8:01 AM >> To: cxf-user@incubator.apache.org >> Subject: Re: WSDL not recognized by vs net >> >> >> Very annoyance :((( >> >> After quite a few trys, I finally make HelloWorld worked with vs net >> (2005). >> >> just change these line in WDSL: ( wrapped DOC/LIT ) >> >> >> >> >> >> >> after change the name 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 function as >> > --- sayHi ( sayHi As sayHi ) As sayHiResponse >> > it should be >> > --- sayHi ( arg0 As string) as string >> > >> > >> > When I change the wsdl manually from >> > >> > >> > >> > >> > >> > >> > >> > >> > to >> > >> > >> > >> > >> > type="xsd:string"/> >> > >> > >> > >> > >> > It worked, but I have no idea how could I make this changes without >> switch >> > to "wsdl first" (I dont want to, I have just too many methods to > export) >> > >> > Any help will be very appreciated >> > >> >> -- >> View this message in context: > http://www.nabble.com/WSDL-not-recognized- >> by-vs-net-tf4599448.html#a13134355 >> Sent from the cxf-user mailing list archive at Nabble.com. > > > -- View this message in context: http://www.nabble.com/WSDL-not-recognized-by-vs-net-tf4599448.html#a13136844 Sent from the cxf-user mailing list archive at Nabble.com.
RE: WSDL not recognized by vs net
In my experience, the VS2005 wsdl.exe doesn't like bare, at least when CXF 2.0.2 and Aegis+JAX-WS are at work. It complains bitterly of name conflicts. If this is supposed to work, I'll concoct a JIRA. > -Original Message- > From: William Leung [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 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 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 > returns > >> are > >> not recognized in vs net. > >> > >> VS NET recongnized the sayHi function as > >> --- sayHi ( sayHi As sayHi ) As sayHiResponse > >> it should be > >> --- sayHi ( arg0 As string) as string > >> > >> > >> When I change the wsdl manually from > >> > >> > >> > >> > >> > >> > >> > >> > >> to > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> It worked, but I have no idea how could I make this changes without > >> switch > >> to "wsdl first" (I dont want to, I have just too many methods to export) > >> > >> Any help 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.
RE: WSDL not recognized by vs net
What version of Visual Studio? With 2005, I don't see a difference based on part names. There is a web page out there that claims that wsdl.exe does different things depending on the part name, but 2005 works just the same (wrapping parameters in an object) either way. > -Original Message- > From: William Leung [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 10, 2007 8:01 AM > To: cxf-user@incubator.apache.org > Subject: Re: WSDL not recognized by vs net > > > Very annoyance :((( > > After quite a few trys, I finally make HelloWorld worked with vs net > (2005). > > just change these line in WDSL: ( wrapped DOC/LIT ) > > > > > > > after change the name 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 function as > > --- sayHi ( sayHi As sayHi ) As sayHiResponse > > it should be > > --- sayHi ( arg0 As string) as string > > > > > > When I change the wsdl manually from > > > > > > > > > > > > > > > > > > to > > > > > > > > > > > > > > > > > > > > It worked, but I have no idea how could I make this changes without > switch > > to "wsdl first" (I dont want to, I have just too many methods to export) > > > > Any help will be very appreciated > > > > -- > View this message in context: http://www.nabble.com/WSDL-not-recognized- > by-vs-net-tf4599448.html#a13134355 > Sent from the cxf-user mailing list archive at Nabble.com.
Re: WSDL not recognized by vs net
Very annoyance :((( After quite a few trys, I finally make HelloWorld worked with vs net (2005). just change these line in WDSL: ( wrapped DOC/LIT ) after change the name 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 function as > --- sayHi ( sayHi As sayHi ) As sayHiResponse > it should be > --- sayHi ( arg0 As string) as string > > > When I change the wsdl manually from > > > > > > > > > to > > > > > > > > > > It worked, but I have no idea how could I make this changes without switch > to "wsdl first" (I dont want to, I have just too many methods to export) > > Any help will be very appreciated > -- View this message in context: http://www.nabble.com/WSDL-not-recognized-by-vs-net-tf4599448.html#a13134355 Sent from the cxf-user mailing list archive at Nabble.com.
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 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 returns >> are >> not recognized in vs net. >> >> VS NET recongnized the sayHi function as >> --- sayHi ( sayHi As sayHi ) As sayHiResponse >> it should be >> --- sayHi ( arg0 As string) as string >> >> >> When I change the wsdl manually from >> >> >> >> >> >> >> >> >> to >> >> >> >> >> >> >> >> >> >> It worked, but I have no idea how could I make this changes without >> switch >> to "wsdl first" (I dont want to, I have just too many methods to export) >> >> Any help 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.
Re: WSDL not recognized by vs net
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 returns are not recognized in vs net. VS NET recongnized the sayHi function as --- sayHi ( sayHi As sayHi ) As sayHiResponse it should be --- sayHi ( arg0 As string) as string When I change the wsdl manually from to It worked, but I have no idea how could I make this changes without switch to "wsdl first" (I dont want to, I have just too many methods to export) Any help will be very appreciated
WSDL not recognized by vs net
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 as --- sayHi ( sayHi As sayHi ) As sayHiResponse it should be --- sayHi ( arg0 As string) as string When I change the wsdl manually from to It worked, but I have no idea how could I make this changes without switch to "wsdl first" (I dont want to, I have just too many methods to export) Any help will be very appreciated -- View this message 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.
