You are not logged in.
Announcement
Unanswered posts
|
Pages: 1

Hello --
I am working with a web service that uses parameters as a complex type. I have tried sending them in the basic settings in the tWebServiceInput but it does not look like that is supported. I have read in a few forums that you need to create stub code in the advanced settings and create the parameter settings in a routine. I am not familiar with routines and stub code but cannote get started as I get an IO exception when I try to generate the code:
java.io.FileNotFoundException
When I look at the .log file here is the exception:
!ENTRY org.talend.platform.logging 4 0 2012-07-12 17:35:03.729
!MESSAGE 2012-07-12 17:35:03,728 ERROR org.talend.commons.exception.CommonExceptionHandler - C:\Program Files\Talend\TOS_DI-Win32-r84309-V5.1.1\ontext.Service_WSD (The system cannot find the file specified)
!STACK 0
java.io.FileNotFoundException: C:\Program Files\Talend\TOS_DI-Win32-r84309-V5.1.1\ontext.Service_WSD (The system cannot find the file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(Unknown Source)
at java.io.FileInputStream.<init>(Unknown Source)
at sun.net.www.protocol.file.FileURLConnection.connect(Unknown Source)
at sun.net.www.protocol.file.FileURLConnection.getInputStream(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:369)
at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:420)
at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:482)
at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
at java.lang.Thread.run(Unknown Source)Any help that you all can provide to send the parameters properly please let me know. In case it matters below is the method information from the WSDL:
<s:element name="GetCourseBookings"> <s:complexType> <s:sequence> <s:element minOccurs="0" maxOccurs="1" name="UserName" type="s:string"/> <s:element minOccurs="0" maxOccurs="1" name="Password" type="s:string"/> <s:element minOccurs="1" maxOccurs="1" name="StartDate" type="s:dateTime"/> <s:element minOccurs="1" maxOccurs="1" name="EndDate" type="s:dateTime"/> <s:element minOccurs="0" maxOccurs="1" name="Buildings" type="tns:ArrayOfInt"/> <s:element minOccurs="0" maxOccurs="1" name="Statuses" type="tns:ArrayOfInt"/> <s:element minOccurs="0" maxOccurs="1" name="EventTypes" type="tns:ArrayOfInt"/> <s:element minOccurs="1" maxOccurs="1" name="ViewComboRoomComponents" type="s:boolean"/></s:sequence> </s:complexType> </s:element>
Offline

Hi
Are you sure that there is a file called ontext.Service_WSD under C:\Program Files\Talend\TOS_DI-Win32-r84309-V5.1.1\?
In Talend, you can't install TOS under a path with a space in it(e.g. C:\Program Files is forbidden) which may cause unexpexted errors. Please reinstall it in the path like this C:\tos\.
Regards,
Pedro
Offline

Hi Pedro --
As always thanks for the prompt reply. I have moved the installation back to a root directory with no spaces and I have the same result. Any other suggestions?
Wes
Offline

Sorry, no the file did not exist in that path so I created an empty file called "ontext.Service_WSD" and received a different error:
org.xml.sax.SAXException
Last edited by webarnes99 (2012-07-17 05:58:48)
Offline

Hi Pedro --
I have taken several screenshots of the component setup for your review. I hope that this helps.
Offline

Hi Pedro --
Just checking to see if you have any additional ideas to help me with this?
Thanks,
Wes
Offline

I have resolved this problem although I am not sure why TOS was behaving this way. I have changed the basic settings to set the WSDL URL from a context parameter to the actual context address. I believe that TOS is trying to find a file with the context parameter name which in my case was called context.Service_WSDL and TOS wanted that file in the root of the installation path. I would still like to use the context parameter as I am trying to make this a template for other integration jobs I am working on.
Thanks,
Wes
Offline

Hi Wes
I have created a job using context variable in twebserviceInput.
And it works fine.
See these images.
I think i must miss some details.
Or you didn't set it correctly.
Regards,
Pedro
Offline
Pages: 1