[JBossWS] - Re: Generate WSDL (From JBoss Eclipse IDE or Command line)
by rudyfell
i have the same problem running wstools from the eclipse ide in linux. I am therefore using the comand line which is working well.
About the error you receive when using the command line
| Exception in thread "main" java.lang.NoClassDefFoundError: javax/jws/soap/SOAPBinding$ParameterStyle
| at org.jboss.ws.tools.helpers.ToolsHelper.handleJavaToWSDLGeneration(ToolsHelper.java:105)
| at org.jboss.ws.tools.WSTools.process(WSTools.java:133)
| at org.jboss.ws.tools.WSTools.generate(WSTools.java:69)
| at org.jboss.ws.tools.WSTools.generate(WSTools.java:119)
| at org.jboss.ws.tools.WSTools.main(WSTools.java:58)
|
i think its because you have not added jboss-wsclient.jar to build path since it contains the javax.jws.soap package. Therefore adding this to your project should make it work. It can be found in the com.eviware.soapui.jbosside.wstools_0.4.1/lib which is under eclipse/plugins.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062943#4062943
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062943
16 years, 12 months
[JBossWS] - Re:
by palin
"chris05atm" wrote : 22:03:04,797 WARN [PolicyMetaDataBuilder] Cannot get service '{xmlapi_1.0}FindImplService' from the given wsdl definitions! Eventual policies attached to this service won't be considered.
| |
|
This is actually a warning; it says that the policy deployer was not able to get '{xmlapi_1.0}FindImplService' from the given wsdl definition, i.e. most probably the provided wsdl file doesn't match with the service metadata obtained from the annotated classes. For this reason eventual policies (cfr. WS-PolicyAttachment specs) won't be considered. But I think you don't care this, at least at the moment, since you have no attached policies.
"chris05atm" wrote : Considering a possible bug? in the raw soap generation I moved onto using a client created from wsconsume. Same error so this is maybe a WSDL issue... but the WSDL looks correct and the files are generated from the WSDL so now I'm really confused. A possible deployment problem?
|
Do you mean the annotated server classes were generated starting from wsconsume, i.e. using a top-down development strategy http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_User_Guide#Top-Do... ? If not, I would try this...
Bye
Alessio Soldano
http://www.javalinux.it
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062855#4062855
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062855
16 years, 12 months
[JBossWS] - Re:
by chris05atm
Considering a possible bug? in the raw soap generation I moved onto using a client created from wsconsume. Same error so this is maybe a WSDL issue... but the WSDL looks correct and the files are generated from the WSDL so now I'm really confused. A possible deployment problem?
Simple client:
| package webservice;
|
| import java.net.MalformedURLException;
| import java.net.URL;
|
| import javax.xml.namespace.QName;
| import javax.xml.ws.Service;
|
| public class FindClient {
|
| public static void main(String[] args) throws MalformedURLException {
| Service service = Service.create(new URL("http://127.0.0.1:8080/xmlapi/invoke?wsdl"),
| new QName("xmlapi_1.0", "XmlApiMethods"));
|
| FindInterface find = service.getPort(FindInterface.class);
|
| find.ping();
| }
|
| }
|
The error generated:
| Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: Endpoint {xmlapi_1.0}FindInterfacePort does not contain operation meta data for: {xmlapi_1.0}ping
| at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:69)
| at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:109)
| at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:553)
| at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:371)
| at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
| at $Proxy15.ping(Unknown Source)
| at webservice.FindClient.main(FindClient.java:17)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062775#4062775
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062775
16 years, 12 months
[JBossWS] - Re:
by chris05atm
Moved to jbossws version 2.0 GA and now I get this error when I deploy the war:
| 22:03:04,567 INFO [LifecycleHandlerImpl] WebService stopped: http://127.0.0.1:8
| 080/xmlapi/invoke
| 22:03:04,567 INFO [BasicEndpointRegistry] remove: jboss.ws:context=xmlapi,endpo
| int=find
| 22:03:04,797 WARN [PolicyMetaDataBuilder] Cannot get service '{xmlapi_1.0}FindI
| mplService' from the given wsdl definitions! Eventual policies attached to this
| service won't be considered.
| 22:03:05,027 INFO [TomcatDeployer] deploy, ctxPath=/xmlapi, warUrl=.../tmp/depl
| oy/tmp27747xmlapi-exp.war/
| 22:03:05,157 INFO [WSDLFilePublisher] WSDL published to: file:/C:/cygwin/home/S
| tokeC/jboss-4.2.0.GA/server/default/data/wsdl/xmlapi.war/XmlApiMethods.wsdl
| 22:03:05,177 INFO [BasicEndpointRegistry] register: jboss.ws:context=xmlapi,end
| point=find
| 22:03:05,177 INFO [LifecycleHandlerImpl] WebService started: http://127.0.0.1:8
| 080/xmlapi/invoke
|
The find method still works, while the ping method still returns the error:
| 22:14:58,563 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
| javax.xml.rpc.soap.SOAPFaultException: Endpoint {xmlapi_1.0}FindInterfacePort do
| es not contain operation meta data for: {xmlapi_1.0}ping
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062772#4062772
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062772
16 years, 12 months