[JBoss-dev] [JBossWS] - Re: Deserializing parameter error
Hi, Sure!. It is: ?xml version=1.0 encoding=UTF-8? | java-wsdl-mapping xmlns=http://java.sun.com/xml/ns/j2ee; version=1.1 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd; | package-mapping | package-typehelloservice3Web/package-type | namespaceURIurn:Foo/namespaceURI | /package-mapping | package-mapping | package-typehelloservice3Web/package-type | namespaceURIhttp://DefaultNamespace/namespaceURI | /package-mapping | | java-xml-type-mapping | java-typehelloservice3Web.HelloIF_sayHello_RequestStruct/java- type | root-type-qname xmlns:typeNS=urn:FootypeNS:sayHello/root-type-qname | qname-scopecomplexType/qname-scope | variable-mapping | java-variable-nameString_1/java-variable-name | xml-element-nameString_1/xml-element-name | /variable-mapping | /java-xml-type-mapping | | java-xml-type-mapping | java-typehelloservice3Web.HelloIF_sayHello_ResponseStruct/java-type | root-type-qname xmlns:typeNS=urn:FootypeNS:sayHelloResponse/root-type-qname | qname-scopecomplexType/qname-scope | variable-mapping | java-variable-nameresult/java-variable-name | xml-element-nameresult/xml-element-name | /variable-mapping | /java-xml-type-mapping | | service-interface-mapping | service-interfacehelloservice3Web.MyHelloService/service-interface | wsdl-service-name xmlns:serviceNS=http://DefaultNamespace;serviceNS:MyHelloService/wsdl-service-name | port-mapping | port-nameHelloIFPort/port-name | java-port-nameHelloIFPort/java-port-name | /port-mapping | | /service-interface-mapping | service-endpoint-interface-mapping | service-endpoint-interfacehelloservice3Web.HelloIF/service-endpoint-interface | wsdl-port-type xmlns:portTypeNS=http://DefaultNamespace;portTypeNS:HelloIF/wsdl-port-type | wsdl-binding xmlns:bindingNS=http://DefaultNamespace;bindingNS:HelloIFBinding/wsdl-binding | | service-endpoint-method-mapping | java-method-namesayHello/java-method-name | wsdl-operationsayHello/wsdl-operation | wrapped-element/ | method-param-parts-mapping | param-position0/param-position | param-typejava.lang.String/param-type | wsdl-message-mapping | wsdl-message xmlns:wsdlMsgNS=http://DefaultNamespace;wsdlMsgNS:HelloIF_sayHello/wsdl-message | wsdl-message-part-nameString_1/wsdl-message-part-name | parameter-modeIN/parameter-mode | /wsdl-message-mapping | /method-param-parts-mapping | wsdl-return-value-mapping | method-return-valuejava.lang.String/method-return-value | wsdl-message xmlns:wsdlMsgNS=http://DefaultNamespace;wsdlMsgNS:HelloIF_sayHelloResponse/wsdl-message | wsdl-message-part-nameresult/wsdl-message-part-name | /wsdl-return-value-mapping | | /service-endpoint-method-mapping | | /service-endpoint-interface-mapping | | /java-wsdl-mapping | Thanks. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3859428#3859428 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3859428 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossWS] - Deserializing parameter error
Hello,
I have a deployed web service but when the client tries to use it, a server
deserializing parameter error is shown:
| 11:47:10,715 ERROR [RPCInvocation] org.xml.sax.SAXException: Deserializing
parameter 'sayHello': could not find deserializer for type {urn:Foo}sayHello
| org.xml.sax.SAXException: Deserializing parameter 'sayHello': could not
find deserializer for type {urn:Foo}sayHello
| at
org.apache.axis.message.RPCHandler.onStartChild(RPCHandler.java:329)
| at
org.apache.axis.encoding.DeserializationContextImpl.startElement(DeserializationContextImpl.java:1186)
| at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:244)
| at
org.apache.axis.message.SOAPElementAxisImpl.publishToHandler(SOAPElementAxisImpl.java:1406)
| at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:262)
| at org.apache.axis.message.RPCElement.getParams(RPCElement.java:396)
| (...)
|
My wsdl file is (the piece involved in the operation sayHello):
| ?xml version=1.0 encoding=UTF-8?
| definitions name=MyHelloService
targetNamespace=http://DefaultNamespace; xmlns:tns=http://DefaultNamespace;
xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:ns2=urn:Foo
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns=http://schemas.xmlsoap.org/wsdl/;
| types
| schema targetNamespace=urn:Foo
xmlns=http://www.w3.org/2001/XMLSchema;
xmlns:soap11-enc=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:tns=urn:Foo xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
| complexType name=sayHello
| sequence
| element name=String_1 nillable=true
type=string//sequence/complexType
| complexType name=sayHelloResponse
| sequence
| element name=result nillable=true
type=string//sequence/complexType
| element name=sayHello type=tns:sayHello/
| element name=sayHelloResponse type=tns:sayHelloResponse/
| /schema
| /types
| message name=HelloIF_sayHello
| part name=parameters element=ns2:sayHello/
| /message
| message name=HelloIF_sayHelloResponse
| part name=result element=ns2:sayHelloResponse/
| /message
| portType name=HelloIF
| operation name=sayHello
| input message=tns:HelloIF_sayHello/
| output message=tns:HelloIF_sayHelloResponse/
| /operation
| /portType
| binding name=HelloIFBinding type=tns:HelloIF
| soap:binding style=document
transport=http://schemas.xmlsoap.org/soap/http/
| operation name=sayHello
| soap:operation soapAction=/
| input
| soap:body use=literal/
| /input
| output
| soap:body use=literal/
| /output
| /operation
| /binding
| service name=MyHelloService
| port name=HelloIFPort binding=tns:HelloIFBinding
| soap:address
location=http://localhost:8080/HelloService/JoseluService/
| /port
| /service
| /definitions
|
I am using document literal encoding (wscompile tool).
The input output parameters are String type. Why cannot it be deserialized
using the default deserializer?
Please, I would also known which (de)serializer could the the most suitable.
Thanks in advance
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858683#3858683
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3858683
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossWS] - Document-literal encoding with JBoss 4.0.1
Hi, I have deployed a web service using rpc-literal as encoding to generate wsdl jaxrpc-mapping files with wscompile tool. However, I cannot deployed using document-literal encoding (many class synchonization errors). This one is needed to run Microsoft InfoPath as a Client. Is there any constraint about the using of document-literal encoding with JBoss 4.0.1? Thanks in advance. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3857349#3857349 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3857349 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossWS] - Re: Class not found error when deploying with JBoss401
Thanks for the reply, Thomas. Yes, you are right, I am using wscompile. I dont mind the existing warnings but I am not sure they affect to my Web Service because, in a few seconds, the following error is also shown: 16:11:20,626 INFO [EARDeployer] Started J2EE application: file:/C:/NM/JBoss/jboss-4.0.1RC1/jboss-4.0.1RC1/server/default/deploy/HelloService4.ear 16:11:57,639 FATAL [InternalException] Exception: java.lang.Exception: The OperationDesc for getSubsInfo was not synchronized to a method of helloservice3Web.HelloIF. at org.apache.axis.InternalException.(InternalException.java:106) at org.apache.axis.description.ServiceDesc.syncOperationToClass(ServiceDesc.java:869) at org.apache.axis.description.ServiceDesc.getSyncedOperationsForName(ServiceDesc.java:1216) at org.apache.axis.description.ServiceDesc.loadServiceDescByIntrospectionRecursive(ServiceDesc.java:1062) at org.apache.axis.description.ServiceDesc.loadServiceDescByIntrospection(ServiceDesc.java:983) at org.apache.axis.providers.java.JavaProvider.initServiceDesc(JavaProvider.java:730) at org.jboss.webservice.server.InvokerProvider.initServiceDesc(InvokerProvider.java:102) at org.apache.axis.handlers.soap.SOAPService.getInitializedServiceDesc(SOAPService.java:388) at org.apache.axis.deployment.wsdd.WSDDService.makeNewInstance(WSDDService.java:560) at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:322) at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:307) at org.apache.axis.deployment.wsdd.WSDDDeployment.getService(WSDDDeployment.java:526) at org.apache.axis.configuration.FileProvider.getService(FileProvider.java:288) at org.apache.axis.AxisEngine.getService(AxisEngine.java:300) at org.jboss.webservice.server.ServiceEndpointServlet.doGet(ServiceEndpointServlet.java:72) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:370) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:66) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:153) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:54) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at
[JBoss-dev] [JBossWS] - Class not found error when deploying with JBoss401
Hi, I am trying to deploy an application (JBoss401RC1) based on servlet+ejb but it shows the following errors (Class not found): 16:36:54,972 INFO [EARDeployer] Init J2EE application: file:/C:/NM/JBoss/jboss-4.0.1RC1/jboss-4.0.1RC1/server/default/deploy/HelloService4.ear 16:36:55,914 INFO [TomcatDeployer] deploy, ctxPath=/HelloService, warUrl=file:/C:/NM/JBoss/jboss-4.0.1RC1/jboss-4.0.1RC1/server/default/tmp/deploy/tmp13496HelloService4. ts/helloService4-exp.war/ 16:36:56,434 INFO [WSDLFilePublisher] WSDL published to: file:/C:/NM/JBoss/jboss-4.0.1RC1/jboss-4.0.1RC1/server/default/data/wsdl/helloService4.war/MyHelloService.wsdl 16:36:56,845 WARN [TypeMappingDescription] Class not found: helloservice3Web.HelloIF_createSubscriber_RequestStruct 16:36:56,855 WARN [TypeMappingDescription] Class not found: helloservice3Web.HelloIF_createSubscriber_ResponseStruct 16:36:56,855 WARN [TypeMappingDescription] Class not found: helloservice3Web.HelloIF_deleteSubscriber_RequestStruct (...) 16:36:56,975 INFO [AxisService] WSDD published to: C:\NM\JBoss\jboss-4.0.1RC1\jboss-4.0.1RC1\server\default\data\wsdl\helloService4.war\MyHelloService.wsdd 16:36:56,995 INFO [AxisService] Web Service deployed: http://localhost:8080/HelloService/JoseluService 16:36:57,065 INFO [EARDeployer] Started J2EE application: file:/C:/NM/JBoss/jboss-4.0.1RC1/jboss-4.0.1RC1/server/default/deploy/HelloService4.ear Any hint about how to solve it? Thanks in advance View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3857062#3857062 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3857062 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
