Unable to see web service operations (2.5.0)

I am using BIRT 2.5.0. I have created a web service which uses what I believe to be a valid WSDL (I would have attached it but the forum will not let me). The web service is running and can be tested via Eclipse's Web Services Explorer. I have created a data source and plugged in the URL to the WSDL (which can be viewed in a browser via the same URL). I have specified the SOAP endpoint, which can also be confirmed using a browser. I then created a data set using this source. On the WSDL operation page I see the name of the WSDL file but no operations are shown. If I hardcode the path to the WSDL into the data source I then see the operations on this page, but the web service still does not function properly (no results are returned). It seems like BIRT is having trouble fetching/parsing the WSDL file. Suggestions?

UPDATE: Right after posting this I discovered something. I plugged in various URLs of sample web services that I found, and BIRT showed the available operations as I expected. It seems that BIRT doesn't like my WSDL in particular. The WSDL was auto-generated by Eclipse ("ground-up") so I'm wondering what could be wrong with it. I'm investigating this avenue.

FURTHER UPDATE: I can use a sample web service from the internet, walk all the way through creating a data set with BIRT, and get results back. I cannot use my own service that was created and deployed by Eclipse.

Find more posts tagged with

Comments

kevinroll

PROBLEM SOLVED. VERY INSIDIOUS. After determining that other web services worked just fine I started to wonder about the WSDL file that I had as well as the web server. I took my WSDL and uploaded it to a different web server - when I pointed BIRT to that URL everything worked fine. At this point I used "wget -S" to view the HTTP headers generated when retrieving the file, and noticed that locally there was no Content-Type being returned. I added a mapping in my Tomcat instance so that the wsdl extension is mapped as "text/xml", and everything started working!

I will file a bug or two about this as it seems that things could be handled better.