Connecting to the Axis2 EchoService example

<p>I am using BIRT 4.5.0 and Eclipse/Mars, and attempting a very simple ODA connection to the Axis2 EchoService example using the following configurations:</p>
<ul><li>WSDL v1.1 and SOAP v1.1</li>
<li>WSDL v1.1 and SOAP v1.2</li>
</ul><p>Both scenarios work with SoapUI, result in successful pings from the ODA Data Source dialog, and fetch available operations and input parameters from within the ODA Data Set dialogs. The issue comes up when trying to obtain a SOAP response and configure Row Mappings within the ODA Data Set dialogs. ODA gives different errors for each of these two configurations.</p>
<p> </p>
<p>Note I've selected the Axis2 Echo example service to get the mechanics figured out for integrating BIRT to Axis2 SOAP services.... just trying to get the most simplistic scenario working before moving on to more complex situations. Below is the result of this unsuccessful exercise.</p>
<p> </p>
<p>Some questions:</p>
<ul><li>Are both WSDLv1.1/SOAPv1.1 and WSDLv1.1/SOAPv1.2 officially supported by BIRT/ODA?</li>
<li>Is WSDL v1.2 officially supported by BIRT/ODA?</li>
<li>Are there any known issues connecting BIRT/ODA with web services hosted by Axis2?</li>
<li>Are there any tricks in the hand-coded WSDL's given below which I need to be aware of?</li>
<li>Other possible issues which are preventing these simple scenarios from working with BIRT/ODA?</li>
</ul><p> </p>
<p><u><strong>WSDL v1.1 and SOAP v1.1</strong></u></p>
<p>I have set up a Web service data source using the following url:</p>
<pre class="_prettyXprint">
http://localhost:9763/services/EchoService?wsdl</pre>
<p>The "Test Connection" within the Data Source configuration dialog is successful. I then attempt to create a Data Set. For this, I can successfully select available operations and select input parameters. When constructing a SOAP response, I choose the following two options:</p>
<p> </p>
<ol><li>Select SOAP Response Schema, for which I chose 'Use operation response..."</li>
<li>Select Sample SOAP response message, for which I left blank</li>
</ol><p>These are the default options which are advised within Actuate tutorials. When hitting the button to navigate from the SOAP Response Page to the Row Mapping Page, I get the following error.</p>
<pre class="_prettyXprint">
XML data source cannot be retrieved. XML data source file is invalid or the file doesn't exist.</pre>
<p>The WSDL for this configuration is given as follows:</p>
<pre class="_prettyXprint">
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://com/xyz/foundation/service/echo/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="EchoService" targetNamespace="http://com/xyz/foundation/service/echo/">
<wsdl:types>
<xsd:schema targetNamespace="http://com/xyz/foundation/service/echo/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="echoStringResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="echoResponse" type="xsd:string" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>

<xsd:element name="echoStringInput">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="echoInput" type="xsd:string" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>

<wsdl:message name="echoOperationRequest">
<wsdl:part element="tns:echoStringInput" name="parameter" />
</wsdl:message>
<wsdl:message name="echoOperationResponse">
<wsdl:part element="tns:echoStringResponse" name="parameter" />
</wsdl:message>

<wsdl:portType name="EchoServicePortType">
<wsdl:operation name="echoOperation">
<wsdl:input message="tns:echoOperationRequest" />
<wsdl:output message="tns:echoOperationResponse" />
</wsdl:operation>
</wsdl:portType>

<wsdl:binding name="EchoSOAP" type="tns:EchoServicePortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
<wsdl:operation name="echoOperation">
<soap:operation soapAction="echoOperation" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>

<wsdl:service name="EchoService">
<wsdl:port binding="tns:EchoSOAP" name="EchoServicePort">
<soap:address location="http://localhost:8080/jaxws-samples/services/EchoService" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

</pre>
<p>The full stack trace for this error is as follows:</p>
<div>
<pre class="_prettyXprint">
org.eclipse.datatools.connectivity.oda.OdaException: XML data source cannot be retrieved. XML data source file is invalid or the file doesn't exist.
at org.eclipse.datatools.enablement.oda.xml.ui.wizards.XPathChoosePage.populateXMLTree(XPathChoosePage.java:482)
at org.eclipse.datatools.enablement.oda.xml.ui.wizards.XPathChoosePage.refreshControls(XPathChoosePage.java:207)
at org.eclipse.datatools.enablement.oda.xml.ui.wizards.XPathChoosePage.refresh(XPathChoosePage.java:201)
at org.eclipse.datatools.enablement.oda.ws.ui.wizards.XMLTableMappingPage.refresh(XMLTableMappingPage.java:105)
at org.eclipse.datatools.enablement.oda.ws.ui.wizards.SOAPResponsePage.getNextPage(SOAPResponsePage.java:644)
at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:878)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:425)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
at org.eclipse.jface.window.Window.open(Window.java:803)
at org.eclipse.birt.report.designer.data.ui.actions.NewDataSetAction.createNewDataSet(NewDataSetAction.java:194)
at org.eclipse.birt.report.designer.data.ui.actions.NewDataSetAction.run(NewDataSetAction.java:182)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
</pre>
</div>
<p> </p>
<p> </p>
<p><u><strong>WSDL v1.1 and SOAP v1.2</strong></u></p>
<p>I have been equally unsuccessful setting up a data set for the configuration leveraging WSDL v1.1 and SOAP v1.2. The same exact steps were taken as described for the WSDLv1.1/SOAPv1.1 configuration, only I get the following error message:</p>
<pre class="_prettyXprint">
SOAP response can't be retrieved, please verify the network or SOAP Response setting.</pre>
<p>The WSDL for this configuration is as follows:</p>
<pre class="_prettyXprint">
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:tns="http://com/xyz/foundation/service/echo/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="EchoService12" targetNamespace="http://com/xyz/foundation/service/echo/">
<wsdl:types>
<xsd:schema targetNamespace="http://com/xyz/foundation/service/echo/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="echoStringInput">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="echoInput" type="xsd:string" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="echoStringResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="echoResponse" type="xsd:string" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>

<wsdl:message name="echoOperationRequest">
<wsdl:part element="tns:echoStringInput" name="parameter" />
</wsdl:message>
<wsdl:message name="echoOperationResponse">
<wsdl:part element="tns:echoStringResponse" name="parameter" />
</wsdl:message>

<wsdl:portType name="EchoService12PortType">
<wsdl:operation name="echoOperation">
<wsdl:input message="tns:echoOperationRequest" />
<wsdl:output message="tns:echoOperationResponse" />
</wsdl:operation>
</wsdl:portType>

<wsdl:binding name="EchoSOAP12" type="tns:EchoService12PortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
<wsdl:operation name="echoOperation">
<soap:operation soapAction="echoOperation" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>

<wsdl:service name="EchoService12">
<wsdl:port binding="tns:EchoSOAP12" name="EchoService12Port">
<soap:address location="http://localhost:8080/jaxws-samples/services/EchoService12" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
</pre>
<p>There is no stack trace for the specified error for this configuration.</p>
<p> </p>
<p class=""> </p>
<p> </p>
<p> </p>

Find more posts tagged with

Comments

randalleleonard

<p>For what it's worth, I've attempted connecting to the weather service, as documented in Actuate documentation, and get the following error from <u>SoapUI</u>:</p>
<div>
<pre class="_prettyXprint">
<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><soap:Fault><soap:Code><soap:Value>soap:Receiver</soap:Value></soap:Code><soap:Reason><soap:Text xml:lang="en">System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Net.WebException: The request failed with the error message:
--
mÃNÃƒ0DÃ¯Ã¹
;ÃžnhÂ±M #Ã zÃ›Âd'kÃ½{Ã¤ÃŠqfÃžjgÃ°ÂªÃšmÃ´GWgÃ6Â¢{{lÂ¶Q^lkÃ½PÃ©jInÃ¤
~)UÂ¼SÃˆdlÃ©Â©Ã›Ã•ZÂ´ÃƒHVtÂ½Ã©Â©OÃ®Â°Ã‚Ã£Ã—`/Ã“Ã½ZÃ½ÃƒfÂ·Ã€ 4Â°ÃƒÃ¾Ã›g[Â°9?Â£hG:ÃœRÂ¸8FÃ¸Â´7NÃ¾ILQ~Â½Ã—ÃCÃ·yÂ¦8RÃžÃ¬{Ã›,JÂ¥ÃŠ(!%Ã‚Ã”lÃ®Â¿O?xY
--.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at WeatherService.www.nws.noaa.gov.ndfdXML.NDFDgen(Decimal latitude, Decimal longitude, productType product, DateTime startTime, DateTime endTime, weatherParametersType weatherParameters)
at WeatherService.WeatherForecast.getData(Double latitude, Double longtitude)
at WeatherService.WeatherForecast.GetWeatherByZipCode(String ZipCode)
--- End of inner exception stack trace ---</soap:Text></soap:Reason><soap:Detail /></soap:Fault></soap:Body></soap:Envelope>
</pre>
</div>
<div>Proceeding with testing Birt/ODA with Actuate documentation is therefore not possible as the weather service is not operational. So I've created a simple Axis2 service using the EchoService examples, as described above. I am getting the same errors described in the earlier post with the Kepler, Luna, and Mars versions of Eclipse with varying iterations of Birt/ODA.</div>
<div> </div>
<div>This should be simple, but it just seems quite challenging to get the most basic examples working.</div>
<div> </div>
<div>It would be very nice to see at least one WSDL for which I could run wsdl2java to generate code and deploy in Axis2, then connect via Birt/ODA. If someone has such a wsdl, could you please upload?</div>

jfranken

<p>Greetings,</p>
<p> </p>
<p>This is not my area of expertise. One thing that was suggested to me is that the BIRT/ODA does not support the following namespace notation:</p>
<p> </p>
<p><span><wsdl:types></span></p>
<p> </p>
<p>try this instead:</p>
<p> </p>
<p><wsdl></p>
<p> <types></p>
<p> </p>
<p>I hope this is helpful.</p>

Clement Wong

<p>The Web Service ODA can support SOAP 1.1 and SOAP 1.2.</p>
<p> </p>
<p>Attached is working sample design pulling data from a public weather web service, and the default Axis2 Version web service ( @ <a data-ipb='nomediaparse' href='http://localhost:8080/axis2/services/Version?wsdl'>http://localhost:8080/axis2/services/Version?wsdl</a>). It was tested in commercial BIRT iHub 3.1 and in OS BIRT 4.5. For reference, my Tomcat version is 8.0.30 and Axis2 is 1.6.3. </p>
<p> </p>
<p>Here are steps that I followed when using the Axis2 Version web service in BIRT:</p>
<p> </p>
<p>1. Defined Web Services Data Source</p>
<p style="margin-left:40px;">a. Entered WSDL URL under WSDL Descriptor (<a data-ipb='nomediaparse' href='http://localhost:8080/axis2/services/Version?wsdl'>http://localhost:8080/axis2/services/Version?wsdl</a>) </p>
<p style="margin-left:40px;">b. Entered SOAP End Point (<a data-ipb='nomediaparse' href='http://localhost:8080/axis2/services/Version.VersionHttpSoap12Endpoint/'>http://localhost:8080/axis2/services/Version.VersionHttpSoap12Endpoint/</a>) </p>
<p> </p>
<p>2. Defined New Data Set using Data Source from Step 1</p>
<p style="margin-left:40px;">a. Expand and select "getVersion" under <em>Version > VersionHttpSoap12Endpoint</em></p>
<p style="margin-left:40px;">b. No parameters for this request, so click Next</p>
<p style="margin-left:40px;">c. Click Next again in the SOAP Request (no parameters)</p>
<p style="margin-left:40px;">d. Select the second option "Use schema from response." under Select SOAP Response Schema.</p>
<p style="margin-left:40px;"> (Note: Query Web Service at SOAP end point should be selected and "<a data-ipb='nomediaparse' href='http://localhost:8080/axis2/services/Version.VersionHttpSoap12Endpoint/'>http://localhost:8080/axis2/services/Version.VersionHttpSoap12Endpoint/" </a>filled in.) Click on Next </p>
<p style="margin-left:40px;">e. For Row Mapping, expand until ns:getVersionResponse and click on > button</p>
<p style="margin-left:80px;"> i. The first option should be selected. Click OK</p>
<p style="margin-left:80px;"> ii. The XPath should be "/soapenv:Envelope/soapenv:Body/ns:getVersionResponse"</p>
<p style="margin-left:80px;"> iii. Click on Next</p>
<p style="margin-left:40px;">f. For Column Mapping, "ns:getVersionResponse" should be highlighted.</p>
<p style="margin-left:80px;"> i. Click on >> button</p>
<p style="margin-left:80px;"> ii. "ns:return" with XPath of /ns:return should be populated</p>
<p style="margin-left:80px;"> iii. Click on "Show Sample Data" to test</p>
<p style="margin-left:80px;"> iv. Click on Finish</p>
<p style="margin-left:40px;">g. Select "Preview Results" in the bottom left of the Edit Data Set dialog</p>
<p> </p>
<p>You should see that ns:return is similar to "Hi - the Axis2 version is 1.6.3". <br>
</p>
<p> </p>
<p> </p>
<p> </p>

randalleleonard

<p>Clement:</p>
<p> </p>
<p>Thank you for your detailed response. This seems straightforward, but I am still having problems.</p>
<p> </p>
<p>My configuration is as follows:</p>
<ul><li>Birt Designer v4.5.0 and v4.5.1</li>
<li>Axis v1.6.2</li>
</ul><p> </p>
<p>Attached are screen shots for both my Version data source and data set. </p>
<ul><li>I think you will agree I've configured this exactly (?) as you had specified in your prior response</li>
<li>Note the BIRT Data Source successfully connects using "Test Connection"</li>
<li>But I am unable to create a Data Set; the error is identical to that provided in my original response. (see attached)</li>
</ul><p>I have also noted Eclipse is detecting a runtime error with BIRT tools, and requesting I submit the attached error report.</p>
<p> </p>
<p>Perhaps I should try older versions of BIRT? Curious if you have feedback.</p>
<p> </p>
<p>Thanks,<br>
Randy</p>

Clement Wong

<p>There are slight differences between your environment and mine, but it should <strong>not </strong>make a difference that you're running on a Mac and I'm on a Windows. I will test on a Mac later today. Also, to simulate your environment, what version of Tomcat are you running so that I can attempt to replicate? I'm using Java (java version "1.7.0_45") and you're using 1.7.0_60-ea-b15.</p>
<p> </p>
<p>Were you able to run my report?</p>
<p> </p>
<p>In a new Web Service Data Source/Data Set, are you able to create one based on my sample for the weather (<a data-ipb='nomediaparse' href='http://wsf.cdyne.com/WeatherWS/Weather.asmx?wsdl'>http://wsf.cdyne.com/WeatherWS/Weather.asmx?wsdl</a> with <a data-ipb='nomediaparse' href='http://wsf.cdyne.com/WeatherWS/Weather.asmx'>http://wsf.cdyne.com/WeatherWS/Weather.asmx</a> endpoint). </p>
<p> </p>
<p>When does the error in the "VersionDataSet" screenshot occur? After you pressed "Connect Now" or "Next"?</p>
<p> </p>
<p>Did you try the SOAP1.2 endpoint? I just tried using the SOAP1.1 endpoint, and that also works for me.</p>

Clement Wong

<p>I was able to test with both OS BIRT 4.5and commercial BIRT iHub 3.1.1 Designer on a Mac, and I <strong>do </strong>see the error you encountered. At this time, I do not know why this is occurring on the Mac only.</p>
<p> </p>
<p>I did sniff the network traffic to capture the TCP stream response returned by the Version web service:</p>
<pre class="_prettyXprint">
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><ns:getVersionResponse xmlns:ns="http://axisversion.sample"><ns:return>Hi - the Axis2 version is 1.6.2</ns:return></ns:getVersionResponse></soapenv:Body></soapenv:Envelope></pre>
<p>If you test using an online XML/XPath tester, we'll see an error:</p>
<p>ERROR - Failed to evaluate XPath expression: org.apache.xpath.domapi.XPathStylesheetDOM3Exception: Prefix must resolve to a namespace: ns</p>
<p> </p>
<p>Here is the saved XPath test link @ <a data-ipb='nomediaparse' href='http://www.xpathtester.com/xpath/b9c2eb1154603daddf9ae09f946cd122'>http://www.xpathtester.com/xpath/b9c2eb1154603daddf9ae09f946cd122</a></p>
<p> </p>
<p>Now, if we just moved the ns definition to the soapenv:Envelope:</p>
<pre class="_prettyXprint">
<?xml version="1.0" encoding="UTF-8"?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://axisversion.sample">
<soapenv:Body>
    <ns:getVersionResponse>
      <ns:return>Hi - the Axis2 version is 1.6.2</ns:return>
    </ns:getVersionResponse>
</soapenv:Body>
</soapenv:Envelope></pre>
<p>And ran the same XPath query, we'll see an expected result. Here is the save XPath Test link @ <a data-ipb='nomediaparse' href='http://www.xpathtester.com/xpath/adc4ce1e55aef40fba36bee9b04afe40'>http://www.xpathtester.com/xpath/adc4ce1e55aef40fba36bee9b04afe40</a></p>
<p> </p>
<p> </p>
<p> </p>
<p>The only workaround I found (but might not yield the results) in other non-Mac environments is:</p>
<p>In Step 2d for SOAP Response, select the third option "Use external XML schema file:". Point that to <a data-ipb='nomediaparse' href='http://localhost:8080/axis2/services/Version?xsd'>http://localhost:8080/axis2/services/Version?xsd</a></p>
<p> </p>
<p>For 2e Row Mapping, use "//ns:getVersionResponse".</p>
<p> </p>
<p>For 2f Column Mapping, use "/ns:return". Don't click on "Show Sample Data".</p>
<p> </p>
<p>Click Finish.</p>
<p> </p>
<p>Now, click on Preview Results.</p>
<p> </p>
<p>I was able to see the expected results.</p>

randalleleonard

<p><span style="color:rgb(40,40,40);font-family:'Source Sans Pro', sans-serif;">> what version of Tomcat are you running so that I can attempt to replicate? </span></p>
<p style="color:rgb(40,40,40);font-family:'Source Sans Pro', sans-serif;">Running Axis2 in standalone mode. But note I get the same error when hitting the weather service. So this is not related to Axis or Tomcat, but instead my local BIRT tooling?</p>
<p style="color:rgb(40,40,40);font-family:'Source Sans Pro', sans-serif;"> </p>
<p style="color:rgb(40,40,40);font-family:'Source Sans Pro', sans-serif;">> When does the error in the "VersionDataSet" screenshot occur? After you pressed "Connect Now" or "Next"?</p>
<div>When clicking "Next" on the Soap Response page for creating a new data set</div>
<div> </div>
<div>Note I am getting the following error my Eclipse Error Log when doing so...</div>
<p> </p>
<div>eclipse.buildId=4.5.1.M20150904-0015</div>
<div>java.version=1.7.0_60-ea</div>
<div>java.vendor=Oracle Corporation</div>
<div>BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US</div>
<div>Framework arguments: -product org.eclipse.epp.package.reporting.product -keyring /Users/randy/.eclipse_keyring -showlocation</div>
<div>Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.reporting.product -keyring /Users/randy/.eclipse_keyring -showlocation</div>
<div> </div>
<div>org.eclipse.birt.report.data.oda.jdbc.dbprofile.sampledb</div>
<div>Error</div>
<div>Thu Dec 10 21:00:50 EST 2015</div>
<div>/Users/randy/Loop/workspaces/portal-reports/.metadata/.plugins/org.eclipse.birt.report.data.oda.jdbc.dbprofile.sampledb/db/META-INF/MANIFEST.MF (No such file or directory)</div>
<div> </div>
<div>java.io.FileNotFoundException: /Users/randy/Loop/workspaces/portal-reports/.metadata/.plugins/org.eclipse.birt.report.data.oda.jdbc.dbprofile.sampledb/db/META-INF/MANIFEST.MF (No such file or directory)</div>
<div>at java.io.FileOutputStream.open(Native Method)</div>
<div>at java.io.FileOutputStream.<init>(FileOutputStream.java:221)</div>
<div>at java.io.FileOutputStream.<init>(FileOutputStream.java:171)</div>
<div>at org.eclipse.birt.report.data.oda.jdbc.dbprofile.sampledb.internal.impl.SampleDbFactory.initSampleDb(SampleDbFactory.java:187)</div>
<div>at org.eclipse.birt.report.data.oda.jdbc.dbprofile.sampledb.internal.impl.SampleDbFactory.setInitializationData(SampleDbFactory.java:88)</div>
<div>at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:251)</div>
<div>at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)</div>
<div>at org.eclipse.datatools.connectivity.internal.InternalProfileManager.initializeLocalDatabase(InternalProfileManager.java:1380)</div>
<div>at org.eclipse.datatools.connectivity.internal.InternalProfileManager.loadLocalRegisteredDatabases(InternalProfileManager.java:1360)</div>
<div>at org.eclipse.datatools.connectivity.internal.InternalProfileManager.loadProfiles(InternalProfileManager.java:1070)</div>
<div>at org.eclipse.datatools.connectivity.internal.InternalProfileManager.getProfiles(InternalProfileManager.java:150)</div>
<div>at org.eclipse.datatools.connectivity.internal.InternalProfileManager.getProfilesByCategory(InternalProfileManager.java:200)</div>
<div>at org.eclipse.datatools.connectivity.ProfileManager.getProfilesByCategory(ProfileManager.java:88)</div>
<div>at org.eclipse.datatools.connectivity.ui.wizards.NewConnectionProfileWizardPage.createControl(NewConnectionProfileWizardPage.java:158)</div>
<div>at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:175)</div>
<div>at org.eclipse.datatools.connectivity.ui.wizards.NewConnectionProfileWizard.createPageControls(NewConnectionProfileWizard.java:309)</div>
<div>at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:705)</div>
<div>at org.eclipse.jface.wizard.WizardDialog.setWizard(WizardDialog.java:1153)</div>
<div>at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1211)</div>
<div>at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1208)</div>
<div>at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1197)</div>
<div>at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)</div>
<div>at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1194)</div>
<div>at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:885)</div>
<div>at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:425)</div>
<div>at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)</div>
<div>at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)</div>
<div>at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)</div>
<div>at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)</div>
<div>at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)</div>
<div>at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)</div>
<div>at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)</div>
<div>at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)</div>
<div>at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)</div>
<div>at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)</div>
<div>at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)</div>
<div>at org.eclipse.jface.window.Window.open(Window.java:803)</div>
<div>at org.eclipse.birt.report.designer.data.ui.actions.NewDataSourceAction.run(NewDataSourceAction.java:127)</div>
<div>at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)</div>
<div>at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)</div>
<div>at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)</div>
<div>at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)</div>
<div>at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)</div>
<div>at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)</div>
<div>at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)</div>
<div>at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)</div>
<div>at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)</div>
<div>at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)</div>
<div>at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)</div>
<div>at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)</div>
<div>at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)</div>
<div>at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)</div>
<div>at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)</div>
<div>at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)</div>
<div>at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)</div>
<div>at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)</div>
<div>at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)</div>
<div>at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)</div>
<div>at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)</div>
<div>at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)</div>
<div>at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)</div>
<div>at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)</div>
<div>at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)</div>
<div>at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)</div>
<div>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)</div>
<div>at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)</div>
<div>at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)</div>
<div>at java.lang.reflect.Method.invoke(Method.java:606)</div>
<div>at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)</div>
<div>at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)</div>
<div>at org.eclipse.equinox.launcher.Main.run(Main.java:1515)</div>

Clement Wong

<p>My latest replied was around the time when you replied on <a data-ipb='nomediaparse' href='http://developer.actuate.com/community/forum/index.php?/topic/37700-connecting-to-the-axis2-echoservice-example/?p=140514'>post #7</a> so you may not have seen my reply with additional comments.</p>
<p> </p>
<p>Were you able to try the workaround?</p>
<p> </p>
<p>I will need to log a defect -- Unable to use Web Service Data Set via Web Service Data Source ODA on a Mac.</p>

randalleleonard

<p>Clement:</p>
<p> </p>
<p>Thanks for post #7, your workaround was valid for the Version and EchoService services for native Axis2 on my Mac.</p>
<p> </p>
<p>I doubt this will work for my scenario of importing multiple xsd documents into a single wsdl. So I look forward to a BIRT patch which resolves this issue. Could you please provide a link to the defect you are logging for this, so I may track progress?</p>
<p> </p>
<p>Thanks,</p>
<p>Randy</p>

Clement Wong

<p>I logged a defect BIRT 1554 in our tracking system.</p>