-
1. Re: could not find deserializer for type
thomas.diesler Jul 5, 2005 9:42 AM (in response to thomas.diesler)In future versions we might auto-discover jaxrpc-mapping.xml
http://jira.jboss.org/jira/browse/JBWS-314
IMHO, this is a flaw in the jaxrpc API that forces a provider to generate static stubs. The wsdl/java mapping is however defined in JSR-109 and should be usable with jaxrpc -
2. Re: could not find deserializer for type
kvreddy74 Jul 5, 2005 10:27 AM (in response to thomas.diesler)Hi Thomas,
[Code:
ServiceFactoryImpl factory = (ServiceFactoryImpl )ServiceFactory.newInstance();
Service service = factory.createService(wsdlURL, qname, mappingURL, portName); ]
Thanks for your reply.I will try this.what is the mappingUrl ? -
3. Re: could not find deserializer for type
anil.saldhana Jul 5, 2005 10:43 AM (in response to thomas.diesler)Location of your jaxrpc-mapping.xml file.
-
4. Re: could not find deserializer for type
kvreddy74 Jul 5, 2005 2:33 PM (in response to thomas.diesler)Hi All,
Thanks to you all for your support.Finally this problem is resolved.But I have a situtaion.I was porting this webservice on another jboss server,but that server didn't start the webservice at all.It din't show the wsdl file at all.It doesn't throw any exception also.What could be the problem.I am using same jboss versions. -
5. Re: could not find deserializer for type
bsheward Jul 5, 2005 3:44 PM (in response to thomas.diesler)Thomas,
Re:ServiceFactoryImpl factory = (ServiceFactoryImpl )ServiceFactory.newInstance(); Service service = factory.createService(wsdlURL, qname, mappingURL, portName);
I can't see anything in javax.xml.rpc.ServiceFactory which resembles the createService() method shown above. What implementation of ServiceFactory are you talking about? Is this JBoss specific code?
Finally, can this technique be used with non-DII implementations? My code is something like:URL url = new URL( urlstr ); QName qname = new QName( SESSION_URN, serviceName ); ServiceFactory factory = ServiceFactory.newInstance(); Service service = factory.createService(url, qname); WebServicesTest svc = (WebServicesTest) service.getPort(WebServicesTest.class); System.out.println( "output:" + svc.getStringArray() );
-
6. Re: could not find deserializer for type
thomas.diesler Jul 6, 2005 8:16 AM (in response to thomas.diesler)The key issue is that with this type of WS client the web service engine has to come up with some sort of wsdl/java mapping. Reflection on the SEI is the natural coice, but is nothing more than guess work.
What is needed are explicit mapping directives like we have with JSR-181 annotations (jboss-5.x) or the JSR-109 jaxrpc-mapping.xml file (jboss-4.x). -
7. Re: could not find deserializer for type
bsheward Jul 12, 2005 3:08 PM (in response to thomas.diesler)Thomas,
You wrote:"thomas.diesler@jboss.com" wrote:
Your client is aware of the wsdl, which defines the abstract contract, but is unaware of the java/wsdl mapping information.
Use the WS4EE client deployment model, i.e. a JNDI lookup of a preconfigured stub or useServiceFactoryImpl factory = (ServiceFactoryImpl )ServiceFactory.newInstance(); Service service = factory.createService(wsdlURL, qname, mappingURL, portName);
I couldn't find that method, but instead found:
createService(java.net.URL wsdlLocation, java.net.URL mappingLocation, java.net.URL ws4eeMetaData, QName serviceName, java.lang.String portName)
JavaDoc is at: http://docs.jboss.com/jbossas/javadoc/4.0.2/org/jboss/webservice/client/ServiceFactoryImpl.html#createService(java.net.URL,%20java.net.URL,%20java.net.URL,%20javax.xml.namespace.QName,%20java.lang.String)
My question is, which file is the ws4eeMetaData file? It obviously is NOT the jaxrpc-mapping.xml or the wsdl files, so I guess it could be the wscompile-config.xml file, webservices.xml file or the ws4ee-deployment.xml file.
Any help would be appreciated!
Thanks and Regards,
Barry -
8. Re: could not find deserializer for type
fpitschi Jul 13, 2005 3:40 AM (in response to thomas.diesler)I think it's the ws4ee-deployment.xml file (you can declare additional type mappings there, looks like they're translated into the wsdd at runtime, together with wsdl informations about the elements of the types...)
-
9. Re: could not find deserializer for type
thomas.diesler Jul 22, 2005 1:53 PM (in response to thomas.diesler)You could read the wiki on DII clients.
http://wiki.jboss.org/wiki/Wiki.jsp?page=WSClientDII -
10. Re: could not find deserializer for type
jtsoong Jul 27, 2005 10:30 PM (in response to thomas.diesler)Hi Thomas, you wrote:
Your client is aware of the wsdl, which defines the abstract contract, but is unaware of the java/wsdl mapping information.
Use the WS4EE client deployment model, i.e. a JNDI lookup of a preconfigured stub or use
Code:ServiceFactoryImpl factory = (ServiceFactoryImpl )ServiceFactory.newInstance(); Service service = factory.createService(wsdlURL, qname, mappingURL, portName);
I have been looking for this method, but can't find it anywhere (createService() with the 4 input parameters). I am compiling with axis-ws4ee.jar as the first thing in my classpath, but still can't find it.
Any ideas on where it might be, it seems a number of people can't find it either.
Cheers
J -
11. Re: could not find deserializer for type
mwaschkowski Jul 28, 2005 10:42 AM (in response to thomas.diesler)jtsoong - just read the wiki, as suggested on DII clients. You will see example of 5 parameter method that works.
Regards,
Mark -
12. Re: could not find deserializer for type
raygeeknyc Aug 1, 2005 12:43 PM (in response to thomas.diesler)"thomas.diesler@jboss.com" wrote:
You could read the wiki on DII clients.
http://wiki.jboss.org/wiki/Wiki.jsp?page=WSClientDII
Thomas
I am struggling with this same issue; I think that full source of the classes that are excerpted in the Wiki page would go a long way to helping. (to provide example values for the parameters and such)
Thanks
---Raymond