Closed glassfishrobot closed 17 years ago
Reported by binod@java.net
binod@java.net said: Created an attachment (id=19) WSDL file
vivekp@java.net said: Cause known. It will be fixed in jaxws 2.1 RI.
vivekp@java.net said:
vivekp@java.net said: I have added this functionality where you would use -extension switch to generate code for non-soap binding. The code will be generated from the abstract portType.
Try the nightly build of jaxws 2.1.
gmpatil@java.net said: Created an attachment (id=41) Sample WSDL from Yahoo news feeder
File: OutputFileService.wsdl Attached By: binod@java.net
File: yahoonews.wsdl Attached By: gmpatil@java.net
Was assigned to vivekp@java.net
This issue was imported from java.net JIRA JAX_WS-34
Marked as fixed on Monday, November 20th 2006, 11:00:28 am
Doing wsImport on the attached WSDL (which doesnt have a SOAP binding) fails.
<<< e-mail discussion >>> Hi Binod,
I see you're using wsomcpile, that means jaxrpc. wscompile only worked with the wsdl with SOAPBinding. It didn't support any other binding.
I tried with jaxws, wsimport tool. At present wsimport also only supports SOAPBinding. We can try to add a feature where such wsdls can be supported. Can you file an issue at jax-ws http://jax-ws.dev.java.net/servlets/ProjectIssues and we can try to add this feature in wsimport in the upcoming version of jaxws.
If you can use jaxws, as a work around, you can work with Dispatch and Provider endpoint?
-vivek.
Binod wrote: