[JBossWS] - Raw Style webservices [Design question]
by viniciuscarvalho
Hello there! I'm developing a Topdown webservice, and defining my own WSDL, and using @WebserviceProvider annotations.
The service is running, I can access it using webservice explorer or SOAPUI. When I generate the client using JBoss WS, I'm getting some errors on the response. I know it's something related to my WSDL, and SOAP response. So I was hopping someone could assist me:
WSDL
| <?xml version="1.0" encoding="UTF-8" standalone="no"?>
| <wsdl:definitions
| xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
| xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
| xmlns:xsd="http://www.w3.org/2001/XMLSchema"
|
| xmlns:sys="http://www.acme.com/schemas/sys"
| targetNamespace="http://www.acme.com/sys/definitions"
| xmlns:tns="http://www.acme.com/sys/definitions">
| <wsdl:types>
| <xsd:schema>
| <xsd:import namespace="http://www.acme.com/schemas/sys" schemaLocation="Command.xsd" id="sys"/>
| </xsd:schema>
|
| </wsdl:types>
|
| <wsdl:message name="CommandRequest">
| <wsdl:part name="parameters" element="sys:anyCommand"></wsdl:part>
| </wsdl:message>
| <wsdl:message name="CommandResponse">
| <wsdl:part name="return" element="sys:CommandResponse"></wsdl:part>
| </wsdl:message>
|
| <wsdl:portType name="CommandProcessorPortType">
| <wsdl:operation name="process">
| <wsdl:input message="tns:CommandRequest" name="CommandRequestInput"></wsdl:input>
| <wsdl:output message="tns:CommandResponse" name="CommandResponseOutput"></wsdl:output>
| </wsdl:operation>
| </wsdl:portType>
|
| <wsdl:binding name="CommandProcessorBinding" type="tns:CommandProcessorPortType">
| <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
| <wsdl:operation name="process">
| <soap:operation soapAction="http://www.acme.com/sys/CommandRequest"/>
| <wsdl:input>
| <soap:body use="literal"/>
| </wsdl:input>
| <wsdl:output>
| <soap:body use="literal"/>
| </wsdl:output>
| </wsdl:operation>
| </wsdl:binding>
|
| <wsdl:service name="CommandProcessorService">
| <wsdl:port name="CommandProcessorPort" binding="tns:CommandProcessorBinding">
| <soap:address location="http://localhost:8080/CommandProcessorService"/>
| </wsdl:port>
| </wsdl:service>
| </wsdl:definitions>
|
|
Command.xsd
| <?xml version="1.0" encoding="UTF-8"?>
| <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
| targetNamespace="http://www.acme.com/schemas/sys"
| xmlns:sys="http://www.acme.com/schemas/sys"
| elementFormDefault="qualified">
|
| <xsd:element name="anyCommand">
| <xsd:complexType>
| <xsd:sequence>
| <xsd:any minOccurs="1"></xsd:any>
| </xsd:sequence>
| </xsd:complexType>
| </xsd:element>
|
| <xsd:element name="CommandResponse">
| <xsd:complexType>
| <xsd:sequence>
| <xsd:element name="return" type="sys:ResponseCommandType"></xsd:element>
| </xsd:sequence>
| </xsd:complexType>
| </xsd:element>
|
|
|
| <xsd:complexType name="ResponseCommandType">
| <xsd:sequence>
| <xsd:element name="id" type="xsd:long"></xsd:element>
| <xsd:element name="message" type="xsd:string"></xsd:element>
| </xsd:sequence>
| </xsd:complexType>
| </xsd:schema>
|
My Provider
|
| @Local
| @Stateless
| @WebServiceProvider(wsdlLocation="META-INF/wsdl/CommandProcessor.wsdl",
| targetNamespace="http://www.acme.com/sys/definitions",
| serviceName="CommandProcessorService",
| portName="CommandProcessorPort")
| @ServiceMode(value=Service.Mode.PAYLOAD)
| public class CommandProcessor implements Provider<Source> {
| Source returnMessage;
| public Source invoke(Source messge) {
|
| DOMSource domSource = null;
|
| try {
| Transformer transformer = TransformerFactory.newInstance().newTransformer();
| transformer.setOutputProperty(OutputKeys.OMIT_XML_DECLARATION, "yes");
| transformer.setOutputProperty(OutputKeys.METHOD, "xml");
| OutputStream out = new ByteArrayOutputStream();
| StreamResult streamResult = new StreamResult();
| streamResult.setOutputStream(out);
| transformer.transform(messge, streamResult);
| String xmlReq = streamResult.getOutputStream().toString();
| System.out.println(xmlReq);
| domSource = new DOMSource(createResponseContent());
| transformer.transform(domSource, streamResult);
| xmlReq = streamResult.getOutputStream().toString();
| System.out.println(xmlReq);
| } catch (Exception e) {
| // TODO Auto-generated catch block
| e.printStackTrace();
| }
| return domSource;
| }
|
| private Document createResponseContent() throws Exception{
| DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
| dbf.setNamespaceAware(true);
| DocumentBuilder db = dbf.newDocumentBuilder();
| Document doc = db.newDocument();
| Element responseCommand = doc.createElementNS("http://www.acme.com/sys/definitions", "sys:CommandResponse");
| Element ret = doc.createElement("return");
| Element id = doc.createElement("id");
| id.appendChild(doc.createTextNode("1"));
| Element message = doc.createElement("message");
| message.appendChild(doc.createTextNode("comando recebido"));
| ret.appendChild(id);
| ret.appendChild(message);
| responseCommand.appendChild(ret);
| doc.appendChild(responseCommand);
| return doc;
| }
|
| }
|
Well, first, when I run ws-provide it throws a lot of warnings on the console, but it seems that all artifacts are created (Port,Service,Bindings,ObjectFactory).
Ok, running using soap ui:
| Request:
|
| <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sys="http://www.acme.com/schemas/sys">
| <soapenv:Header/>
| <soapenv:Body>
| <csm:anyCommand>
| <asteriskCommand>
| <voip>true</voip>
| </asteriskCommand>
| </csm:anyCommand>
| </soapenv:Body>
| </soapenv:Envelope>
|
| Response:
|
| <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
| <env:Header/>
| <env:Body>
| <sys:CommandResponse xmlns:sys="null">
| <return>
| <id>1</id>
| <message>comando recebido</message>
| </return>
| </csm:CommandResponse>
| </env:Body>
| </env:Envelope>
|
Now, the odd thing, is that the xmlns:sys is null, when I print it on the serverside it displays that the xmlns:sys is pointing to the namespace.
So I run this test with the generated client proxy, and I get an error:
Caused by: org.jboss.ws.WSException: Cannot find child element: {http://www.acme.com/schemas/sys}CommandResponse
I really don't know if this is caused because the xmlns is being returned null, and if so, why? Or did I messed the whole doc/literal wrapped/bare style? I was thinking that I was using bare style :)
Any help would be great :)
Regards
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091226#4091226
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091226
18 years
[JBossWS] - Re: wsdl based web-service (like a paypal simulator)?
by rocken7
Ok still confused, the docs just don't help.
Again from the top with some changes.
The ejb3 stateless bean as a webservice:
@WebService(name = "PayPalAPIAAInterface", portName = "PayPalAPIAA", serviceName = "PayPalAPIInterfaceService", targetNamespace = "urn:ebay:api:PayPalAPI", wsdlLocation="META-INF/wsdl/PayPalSvc.wsdl")
| @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
| @WebContext(contextRoot = "/report")
| @Remote
| @Stateless
| public class PaypalSoapSimulator implements PayPalAPIAAInterface { .. }
|
Here is the PayPalAPIAAInterface:
@WebService(name = "PayPalAPIAAInterface", targetNamespace = "urn:ebay:api:PayPalAPI")
| @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
| public interface PayPalAPIAAInterface { ... }
|
And here is a snippet from the wsdl:
<wsdl:service name="PayPalAPIInterfaceService">
| <wsdl:port name="PayPalAPI" binding="ns:PayPalAPISoapBinding">
| <wsdlsoap:address location="https://api-3t.sandbox.paypal.com/2.0/"/>
| </wsdl:port>
| <wsdl:port name="PayPalAPIAA" binding="ns:PayPalAPIAASoapBinding">
| <wsdlsoap:address location="https://api-aa-3t.sandbox.paypal.com/2.0/"/>
| </wsdl:port>
| </wsdl:service>
|
Now the PayPalSvc.wsdl imports valid official *.xsd files which are in the same folder and are straight from paypal (validated).
Jboss-4.0.5.GA no longer hangs, it just blows with a java.lang.OutOfMemoryError.
I have the heap space turned way up ( -Xmx1024m ) and it still blows?
Here is the server log, and there are tons of the xmlschema import lines before the crash.
2007-10-03 19:06:18,335 DEBUG [org.jboss.wsf.stack.jbws.WSDLFilePublisher] XMLSchema import published to: file:/C:/jboss-4.0.5.GA/server/default/data/wsdl/txs.ear/txs.jar/CoreComponentTypes.xsd
| 2007-10-03 19:06:18,350 DEBUG [org.jboss.wsf.stack.jbws.WSDLFilePublisher] XMLSchema import published to: file:/C:/jboss-4.0.5.GA/server/default/data/wsdl/txs.ear/txs.jar/eBLBaseComponents.xsd
| 2007-10-03 19:06:21,444 DEBUG [org.jboss.wsf.stack.jbws.WSDLFilePublisher] XMLSchema import published to: file:/C:/jboss-4.0.5.GA/server/default/data/wsdl/txs.ear/txs.jar/CoreComponentTypes.xsd
| 2007-10-03 19:06:21,460 DEBUG [org.jboss.wsf.stack.jbws.WSDLFilePublisher] XMLSchema import published to: file:/C:/jboss-4.0.5.GA/server/default/data/wsdl/txs.ear/txs.jar/eBLBaseComponents.xsd
| 2007-10-03 19:06:21,506 DEBUG [org.jboss.wsf.stack.jbws.WSDLFilePublisher] XMLSchema import published to: file:/C:/jboss-4.0.5.GA/server/default/data/wsdl/txs.ear/txs.jar/CoreComponentTypes.xsd
| 2007-10-03 19:06:21,538 DEBUG [org.jboss.wsf.stack.jbws.WSDLFilePublisher] XMLSchema import published to: file:/C:/jboss-4.0.5.GA/server/default/data/wsdl/txs.ear/txs.jar/eBLBaseComponents.xsd
| 2007-10-03 19:06:21,585 DEBUG [org.jboss.wsf.stack.jbws.WSDLFilePublisher] XMLSchema import published to: file:/C:/jboss-4.0.5.GA/server/default/data/wsdl/txs.ear/txs.jar/CoreComponentTypes.xsd
| 20 07-10-03 19:06:21,600 DEBUG [org.jboss.wsf.stack.jbws.WSDLFilePublisher] XMLSchema import published to: file:/C:/jboss-4.0.5.GA/server/default/data/wsdl/txs.ear/txs.jar/eBLBaseComponents.xsd
| 2007-10-03 19:07:17,102 ERROR [STDERR] Exception in thread "main-FastReceiver"
| 2007-10-03 19:07:17,102 ERROR [STDERR] java.lang.OutOfMemoryError: Java heap space
|
Any ideas what is going on?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091213#4091213
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091213
18 years
[JBossWS] - Unmarshalling Exception with Web Service Array Input
by sumitsu
Hi,
I am currently attempting to deploy a web service to JBoss 4.2.1 (using Java 6.0 and JBossWS 2.0.1) where the single input is a custom object which contains (among other fields) an array of other custom objects. Deployment seems to work correctly, but I get this error when I try to invoke the service:
| 14:16:44,997 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
| org.jboss.ws.WSException: org.jboss.ws.core.binding.BindingException: org.jboss.ws.core.jaxrpc.binding.jbossxb.UnmarshalException:
| Failed to parse source:
| Failed to resolve class name for customFields:
| No ClassLoaders found for: com.liaison.InboundWebService.messageProcessing.Array
| at org.jboss.ws.core.soap.XMLContent.unmarshallObjectContents(XMLContent.java:250)
| at org.jboss.ws.core.soap.XMLContent.transitionTo(XMLContent.java:97)
| at org.jboss.ws.core.soap.DOMContent.transitionTo(DOMContent.java:77)
| at org.jboss.ws.core.soap.SOAPContentElement.transitionTo(SOAPContentElement.java:140)
| at org.jboss.ws.core.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:171)
| at org.jboss.ws.core.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:263)
| at org.jboss.ws.core.EndpointInvocation.getRequestParamValue(EndpointInvocation.java:115)
| at org.jboss.ws.core.EndpointInvocation.getRequestPayload(EndpointInvocation.java:135)
| at org.jboss.ws.core.server.DelegatingInvocation.getArgs(DelegatingInvocation.java:82)
| at org.jboss.wsf.container.jboss42.InvocationHandlerEJB21.getMBeanInvocation(InvocationHandlerEJB21.java:169)
| at org.jboss.wsf.container.jboss42.InvocationHandlerEJB21.invoke(InvocationHandlerEJB21.java:144)
| at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:408)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
| at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Thread.java:619)
| Caused by:
| org.jboss.ws.core.binding.BindingException:
| org.jboss.ws.core.jaxrpc.binding.jbossxb.UnmarshalException:
| Failed to parse source:
| Failed to resolve class name for customFields:
| No ClassLoaders found for: com.liaison.InboundWebService.messageProcessing.Array
| at org.jboss.ws.core.jaxrpc.binding.JBossXBDeserializer.deserialize(JBossXBDeserializer.java:111)
| at org.jboss.ws.core.jaxrpc.binding.JBossXBDeserializer.deserialize(JBossXBDeserializer.java:62)
| at org.jboss.ws.core.binding.DeserializerSupport.deserialize(DeserializerSupport.java:60)
| at org.jboss.ws.core.soap.XMLContent.unmarshallObjectContents(XMLContent.java:180)
| ... 35 more
| Caused by: org.jboss.ws.core.jaxrpc.binding.jbossxb.UnmarshalException:
| Failed to parse source:
| Failed to resolve class name for customFields:
| No ClassLoaders found for: com.liaison.InboundWebService.messageProcessing.Array
| at org.jboss.ws.core.jaxrpc.binding.jbossxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshallerImpl.java:65)
| at org.jboss.ws.core.jaxrpc.binding.JBossXBDeserializer.deserialize(JBossXBDeserializer.java:103)
| ... 38 more
| Caused by:
| org.jboss.xb.binding.JBossXBException:
| Failed to parse source:
| Failed to resolve class name for customFields:
| No ClassLoaders found for: com.liaison.InboundWebService.messageProcessing.Array
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:178)
| at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:126)
| at org.jboss.ws.core.jaxrpc.binding.jbossxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshallerImpl.java:61)
| ... 39 more
| Caused by:
| org.jboss.xb.binding.JBossXBRuntimeException:
| Failed to resolve class name for customFields:
| No ClassLoaders found for: com.liaison.InboundWebService.messageProcessing.Array
| at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtElementHandler.loadClassForTerm(RtElementHandler.java:1038)
| at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtElementHandler.classForNonArrayItem(RtElementHandler.java:1367)
| at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtElementHandler.startElement(RtElementHandler.java:693)
| at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtElementHandler.startParticle(RtElementHandler.java:89)
| at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:504)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:323)
| at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
| at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
| at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
| at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
| at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:174)
| ... 41 more
|
I've tried this with JVMs 1.4.2, 5.0, 6.0, as well as with JBoss version 4.0.2 and 4.2.1 and with both WS4EE and JBossWS 1.2.1 and 2.0.1, and I get the same error every time. (The error from JBoss 4.0.2 + WS4EE is a bit different, but the gist of it is the same, that it can't deserialize the input for the array.)
My WSDL, generated by wscompile, is as follows. I've removed a few sections which do not seem relevant to the issue:
| <?xml version="1.0" encoding="UTF-8" ?>
| <definitions name="LiaisonB2BWebServiceInterface"
| targetNamespace="InboundWebService"
| xmlns:tns="InboundWebService"
| xmlns="http://schemas.xmlsoap.org/wsdl/"
| xmlns:xsd="http://www.w3.org/2001/XMLSchema"
| xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
| <types>
| <schema targetNamespace="InboundWebService"
| xmlns="http://www.w3.org/2001/XMLSchema"
| xmlns:tns="InboundWebService"
| xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
| <complexType name="CustomField">
| <sequence>
| <element name="name" type="string" nillable="true" />
| <element name="value" type="string" nillable="true" />
| </sequence>
| </complexType>
| <complexType name="ServiceRequest">
| <sequence>
| <element name="customFields" type="tns:CustomField" nillable="true" minOccurs="0" maxOccurs="unbounded" />
| </sequence>
| </complexType>
| <complexType name="ServiceStatus">
| <sequence>
| <element name="code" type="string" nillable="true" />
| <element name="subject" type="string" nillable="true" />
| </sequence>
| </complexType>
| </schema>
| </types>
| <message name="MessageEndPoint_processMessage">
| <part name="ServiceRequest" type="tns:ServiceRequest" />
| </message>
| <message name="MessageEndPoint_processMessageResponse">
| <part name="result" type="tns:ServiceStatus" />
| </message>
| <portType name="MessageEndPoint">
| <operation name="processMessage" parameterOrder="ServiceRequest">
| <input message="tns:MessageEndPoint_processMessage" />
| <output message="tns:MessageEndPoint_processMessageResponse" />
| </operation>
| </portType>
| <binding name="MessageEndPointBinding" type="tns:MessageEndPoint">
| <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc" />
| <operation name="processMessage">
| <soap:operation soapAction="" />
| <input>
| <soap:body use="literal" namespace="InboundWebService" />
| </input>
| <output>
| <soap:body use="literal" namespace="InboundWebService" />
| </output>
| </operation>
| </binding>
| <service name="WebServiceInterface">
| <port name="MessageEndPointPort" binding="tns:MessageEndPointBinding">
| <soap:address location="REPLACE_WITH_ACTUAL_URL" />
| </port>
| </service>
| </definitions>
|
Has anyone else experienced this problem? I have not been able to find many references to the Exception I'm getting. Please let me know if so; thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091198#4091198
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091198
18 years
[JBossWS] - ver1_1.Message1_1Impl cannot be cast to MessageImpl AND Cann
by DeanoUK
On trying to run a SOAP client I get:
| Exception in thread "main" java.lang.ClassCastException: com.sun.xml.internal.messaging.saaj.soap.ver1_1.Message1_1Impl cannot be cast to com.sun.xml.messaging.saaj.soap.MessageImpl
| at com.sun.xml.rpc.client.dii.CallInvokerImpl._postSendingHook(CallInvokerImpl.java:305)
| at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:324)
| at com.sun.xml.rpc.client.dii.CallInvokerImpl.doInvoke(CallInvokerImpl.java:103)
| at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:486)
| at com.sun.xml.rpc.client.dii.CallInvocationHandler.doCall(CallInvocationHandler.java:121)
| at com.sun.xml.rpc.client.dii.CallInvocationHandler.invoke(CallInvocationHandler.java:85)
| at $Proxy0.uploadNewRegistrations(Unknown Source)
|
On JBoss I receive:
| [03 Oct 2007 17:30:25] ERROR org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS - SOA
| P request exception
| org.jboss.ws.WSException: Cannot find child element: arg0
| at org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOA
| PBinding.java:891)
| at org.jboss.ws.core.CommonSOAPBinding.unbindRequestMessage(CommonSOAPBi
| nding.java:343)
|
I'm using JBoss4.2.1GA with JBossWS-2.0.1
The first exception seems related to the fact I'm using JDK 6...but jboss-saaj.jar is indeed in libs/endorsed which I believe should resolve that problem.
Any ideas on how to fix this?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091149#4091149
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091149
18 years