You are not logged in.
Announcement
Unanswered posts
|
- Index
- » Usage, Operation
- » tWebServiceInput component with JAX-WS (document style) service
Post a reply
Topic review (newest first)
- Matt
- 2010-02-01 18:24:45
Same here; using a Microsoft WSSF WCF reference (basicHttp binding) and can't get this to work.
Please can anyone at Talend answer this thread ASAP?
- halthern
- 2010-02-01 11:30:05
Encountering similar problems (trying to use tWebServiceInput component as client for our own JAX-WS service) we prepared our prototype. Could someone please look into archive (short instructions, sources for JAX-WS service, screenshots from TOS, stack trace with error raised) and help us to resolve the issue?
http://rapidshare.de/files/49085806/ws- … d.zip.html
- mikefinnx
- 2009-05-29 14:23:41
I ended up getting a sample XML doc imported, but not sure that is safe, as opposed to importing the XSD. Is there a way to import an XSD to use as the basis of a Talend schema?
If that can work, the original question still stands - does Talend work with JAX-WS document style services? If so, is there a cookbook, tutorial or anything that tells how it can be done?
Thanks,
Mike
- mikefinnx
- 2009-05-27 23:03:09
I have been trying to determine the capabilities of Talend consuming a JAX-WS service, with a document style service, where the input and output messages are fairly complex (containing several complex types, many levels of depth). I have read through forums and the component docs, but it seems like the component is intended for RPC-style services.
Is such a case supported?
Is there a sample use-case or cookbook somewhere?
Some specific questions:
- What type to use for the argument?
- How to create and reference the schema, based on the messages defined by the XSDs referenced in the service WSDL? I tried creating schema from XML document, but the importer chokes on namespace prefixes. Is is namespace-aware?
- Will it always require hand-coding, a la wsdl2java-and-modify?
We are looking at replacing several data interfaces, but many are doc-style web services and anything built here forward is JAX-WS, so it's a key need for us.
Any help appreciated!
Mike