1 person found this helpful
You can test web service directly from WLS server with http://host:port/wls_utc
Also you can test web service from JDeveloper (Tools->HTTP Analyzer).
It seems that jdev doesn't generate proper WS proxy in both cases so I don't think that low level messages can help(except if you can modify WS ).
Maybe you can try to invoke WS with some third party java library (for example Apache CXF).
The HTTP Analyzer is helpful. I did find that and have been able to call the service successfully in the "HTTP Content" view of the HTTP Analyzer but if I try to use the "Soap Structure" view of the HTTP Analyzer the service responds with nothing and if I flip over to HTTP Content the body is empty and the service responded with a message... "Request does not conform to TH spec: No method located in request"... which is a message provided by the service (TH is the service name).
IT sometimes help to test out the service using e.g .SoapUI which is really helpful in analyzing a web service and all the soap envelopes passed around. If the service runs in SoapUI you at least know that the problem is somewhere in the JDev generated code. To my knowledge there are some problems with the generated proxy or WebService data control with complex type.
But lest check if the service is running OK.
You mean "SoapUI"... the third party tool? I am not sure I need that to verify the service is running. See the earlier post about using "HTTP Analyzer" in JDeveloper and getting a proper response from the service. I would like to keep my debugging to within JDeveloper if possible. I want to use as much of the ADF Framework as possible and if I can fix this through JDev that would be better. I am confident I can write a POJO to call out to the service if I must but would rather not.
You don't have to use SoapUI, it's just that this tool allows more then just test a web service. It's ok if you like to do all testing in jdev, it's your choice.
My solution at this point is to create a POJO and call the web service using an HttpURLConnection. I can then deserialize the response into the proxy generated classes pretty easily and use them. I can then expose the proxy generated classes as Data Controls to the UI and as Web Service for consumption by my ADF Mobile application. I have this working. A bit disappointing I have to go this route. The web service data control would have been optimal but it seems that if it goes wrong for some reason there is not really a way to debug the problems. If I get some suggestions about debugging these I can always pull the manual call and move to a Web Service Data Control. The JDeveloper "HTTP Analyzer" suggestion was very helpful... thanks.