[JBoss-user] [JBossWS] - Unsupported number of service elements in wsdl document
Hi everyone, i am trying to deploy webservice in jboss4.0.1RC1. It is everything fine if i am using single service in wsdl file, if i am trying to use more than one services in wsdl file i am getting the following error when i am deploying my ear file. Is this is the problem of xdoclet because i am using xdoclet to generate webservice.xml file. And i am getting this service.wsdl(wsdl file) from this webservice.xml. Any one can help me how over come thing problem. thankyou.madan. my wsdl file contains: -- ?xml version=1.0 encoding=UTF-8? wsdl:definitions targetNamespace=http://WSSipikatManager; xmlns:impl=http://WSSipikatManager; xmlns:intf=http://WSSipikatManager; xmlns:apachesoap=http://xml.apache.org/xml-soap; xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns=http://schemas.xmlsoap.org/wsdl/; wsdl:message name=updateTRStatusResponse wsdl:part name=updateTRStatusReturn type=xsd:short/ /wsdl:message wsdl:message name=updateTestResultsResponse wsdl:part name=updateTestResultsReturn type=xsd:short/ /wsdl:message wsdl:message name=updateNotificationStatusResponse wsdl:part name=updateNotificationStatusReturn type=xsd:short/ /wsdl:message wsdl:message name=updateTRStatusRequest wsdl:part name=in0 type=xsd:string/ wsdl:part name=in1 type=xsd:string/ wsdl:part name=in2 type=xsd:string/ wsdl:part name=in3 type=xsd:string/ wsdl:part name=in4 type=xsd:string/ wsdl:part name=in5 type=xsd:string/ wsdl:part name=in6 type=xsd:string/ wsdl:part name=in7 type=xsd:string/ wsdl:part name=in8 type=xsd:string/ wsdl:part name=in9 type=xsd:string/ wsdl:part name=in10 type=xsd:string/ wsdl:part name=in11 type=xsd:string/ wsdl:part name=in12 type=xsd:string/ wsdl:part name=in13 type=xsd:string/ /wsdl:message wsdl:message name=updateNotificationStatusRequest wsdl:part name=in0 type=xsd:string/ wsdl:part name=in1 type=xsd:string/ wsdl:part name=in2 type=xsd:string/ wsdl:part name=in3 type=xsd:string/ wsdl:part name=in4 type=xsd:string/ wsdl:part name=in5 type=xsd:string/ /wsdl:message wsdl:message name=updateTestResultsRequest wsdl:part name=in0 type=xsd:string/ wsdl:part name=in1 type=xsd:string/ wsdl:part name=in2 type=xsd:string/ wsdl:part name=in3 type=xsd:string/ wsdl:part name=in4 type=xsd:string/ wsdl:part name=in5 type=xsd:string/ wsdl:part name=in6 type=xsd:string/ wsdl:part name=in7 type=xsd:string/ wsdl:part name=in8 type=xsd:string/ wsdl:part name=in9 type=xsd:string/ wsdl:part name=in10 type=xsd:string/ wsdl:part name=in11 type=xsd:string/ wsdl:part name=in12 type=xsd:string/ wsdl:part name=in13 type=xsd:string/ wsdl:part name=in14 type=xsd:string/ wsdl:part name=in15 type=xsd:string/ wsdl:part name=in16 type=xsd:string/ wsdl:part name=in17 type=xsd:string/ wsdl:part name=in18 type=xsd:string/ wsdl:part name=in19 type=xsd:string/ wsdl:part name=in20 type=xsd:string/ /wsdl:message wsdl:portType name=WSSipikatManager wsdl:operation name=updateTRStatus parameterOrder=in0 in1 in2 in3 in4 in5 in6 in7 in8 in9 in10 in11 in12 in13 wsdl:input name=updateTRStatusRequest message=impl:updateTRStatusRequest/ wsdl:output name=updateTRStatusResponse message=impl:updateTRStatusResponse/ /wsdl:operation wsdl:operation name=updateNotificationStatus parameterOrder=in0 in1 in2 in3 in4 in5 wsdl:input name=updateNotificationStatusRequest message=impl:updateNotificationStatusRequest/ wsdl:output name=updateNotificationStatusResponse message=impl:updateNotificationStatusResponse/ /wsdl:operation /wsdl:portType wsdl:portType name=WSAlertManager wsdl:operation name=updateTestResults parameterOrder=in0 in1 in2 in3 in4 in5 in6 in7 in8 in9 in10 in11 in12 in13 in14 in15 in16 in17 in18 in19 in20 wsdl:input name=updateTestResultsRequest message=impl:updateTestResultsRequest/ wsdl:output name=updateTestResultsResponse message=impl:updateTestResultsResponse/ /wsdl:operation /wsdl:portType wsdl:binding name=WSSipikatManagerSoapBinding type=impl:WSSipikatManager wsdlsoap:binding style=rpc transport=http://schemas.xmlsoap.org/soap/http/ wsdl:operation name=updateTRStatus wsdlsoap:operation soapAction=/ wsdl:input name=updateTRStatusRequest wsdlsoap:body use=encoded encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; namespace=http://WSSipikatManager/
[JBoss-user] [JBossWS] - Unsupported number of service elements in wsdl document
Environment: JBoss_4_0_0 on Redhat 9 with JDK 1.4.2 I tried to deploy a EJB WebServices application that contains multiple porttypes in a single wsdl file. So my wsdl looks like wsdl:definitions .. | |wsdl:service name=CEEBeanEndPointService | | wsdl:port name=CEEBeanPort binding=impl:CEEBeanPortSoapBinding | | wsdlsoap:address location=http://localhost:8080/ws4ee/services/CEEBean/ | | /wsdl:port | |/wsdl:service | |wsdl:service name=TestBeanEndPointService | | wsdl:port name=TestBeanPort binding=impl:TestBeanPortSoapBinding | | wsdlsoap:address location=http://localhost:8080/ws4ee/services/TestBean/ | | /wsdl:port | |/wsdl:service | | When this gets deployed, jboss is trying to rename the Endpoint where it gets deployed but since it uses the webservice-description-name for the endpoint, we get into a conflict where 2 services get mapped to a single name. Is this not supported in JBoss? I used the axis java2wsdl to generate the wsdl as described above. but it fails during deployment with the following stacktrace. java.lang.IllegalArgumentException: Unsupported number of service elements in wsdl document at org.jboss.webservice.metadata.WebserviceDescriptionMetaData.replaceAddressLocations(WebserviceDescriptionMetaData.java:241) at org.jboss.webservice.metadata.WebserviceDescriptionMetaData.updateServiceAddress(WebserviceDescriptionMetaData.java:229) at org.jboss.webservice.ServiceDeployer.startWebservice(ServiceDeployer.java:181) at org.jboss.webservice.ServiceDeployer.handleNotification(ServiceDeployer.java:113) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:138) at $Proxy20.handleNotification(Unknown Source) at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:104) at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:87) at org.jboss.deployment.SubDeployerSupport.start(SubDeployerSupport.java:178) at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:620) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:935) Thanks Raja View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3861556#3861556 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3861556 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
