nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to see soap parameters in a dataset from webservice datasource

julienemixis · 2015-03-19T06:49:56+00:00

Hello, I'm designing a report from a webservice datasource but when i try to create a new dataset from it, i can't see soap parameters.. Is there something special to add to the wsdl definition to see soap parameters? I'm using Birt 3.7.1. wsdl url : <a…

julienemixis

Hello,
 
I'm designing a report from a webservice datasource but when i try to create a new dataset from it, i can't see soap parameters..
Is there something special to add to the wsdl definition to see soap parameters?
I'm using Birt 3.7.1.
 
wsdl url : <a data-ipb='nomediaparse' href='http://uat.aidoo-mobile.com/platform/FleetService/FleetService.wsdl'>http://uat.aidoo-mobile.com/platform/FleetService/FleetService.wsdl</a>
 
I try with this example and i works and can see them : 
 
wsdl url : <a data-ipb='nomediaparse' href='http://www.webservicex.net/uszip.asmx?WSDL'>http://www.webservicex.net/uszip.asmx?WSDL</a>
 
But i don't know what's the difference between the two wsdl..
 
Many thanks in advance,
 
Julien

Find more posts tagged with

Comments

JFreeman

I think this is going to have do with Web Service ODA having trouble fully reading your WSDL which is more complex and structured differently than the sample WSDL that is pulling in the parameters automatically.
 
If you go past the parameter selection dialogue, you can see that the SOAP request being generated doesn't include the elements that would contain your parameters which is why they are not showing up in the initial parameter dialogue.
 
What you can try doing is going past the first parameters dialogue to the SOAP request dialogue. Then modify the auto generated SOAP request with a modified version that includes your needed parameters (a utility such as SOAP UI might help with this). Then complete the column and row mapping to generate the data set.
 
After the data set is generated, with the edit data set dialogue still open, manually add the parameters to the data set through the parameter dialogue on the left.
 
This should allow you pass the needed parameters to the SOAP endpoint.

julienemixis

Thanks for your response Jesse.
 
I'd already done what you said in your response and i succeded to call the webservice and get a response but i have lots of a report to write and it's a waste of time to always go to see the wsdl definition to see how are parameters and set them manually in the soap request..
 
But thanks for your response yet.
 
Regards,
 
Julien

JFreeman

Unfortunately, I think that is going to be the option for using the out of the box Web Service ODA with your WSDL.
 
As an alternative, you could look towards customizing the existing ODA or creating a custom ODA to better handle your WSDL.
 
You may also be able to create a scripted Data Source/Set that can be used a template for all of your report designs.
 
I would also recommend filing an enhancement request through bugzilla for BIRT to request an enhancement to the Web Service ODA to handle more diverse and complex WSDLs.

julienemixis

Ok Thank you for your help, i will do that.
 
Regards,
 
Julien