I also tried to send requests using aoapUI. I got similar response. See below.
Mark Heron wrote:Here you go. I have to modify additionType.xsd to additionTypes.xsd(extra "s" in name) to locate XSD correctly. I assume it is typo in study guide.(Version: July 12, 2010)
Indeed! Thank you for pointing this out!
I pasted the WSDL and the XML schema into my version of the web service and it does look like there are no problems with those two files, since the web service works as expected.
I did generate the JAXB bean classes etc using the Ant-script.
I tried with soapUI and received this response:
If you want me to look further into this, please compress the entire web service project in an archive file and put it somewhere where I can download it.
Thanks for looking into this. I appreciate your help.
Can you please provide me corresponding HTTP(NOT SOAP) request? Also, Please let me know Glassfish and soapUI version you are using.
I noticed one thing, I can successfully test my webservice using Glassfish test tool. However, it uses diffrent SOAP request than what soapUI and standalone client is using. Moreover, when I compare WSDL within my webservice project with Glassfish version of WSDL they are diffrent in Action and operation name. I guess Glassfish generates WSDL out of implementation class and it doesn't care what mapping is defined within WSDL inside WEB-INF/wsdl folder. I wish Glassfish can validate class and WSDL at deploy time and flag error if something is not matching rather than silently generating own version of wsdl and use it.
posted 8 years ago
If GlassFish generates a WSDL instead of using the existing one, then make sure that the endpoint implementation class is properly annotated:
I'll get back later with more information and sample request.
Sorry about the delay.
First of all, I use GlassFish 3.0.1 but originally when developing the sample, I used GlassFish 2.1.
For testing, I have used soapUI 3.5.
I can only supply the request generated by soapUI, which looks like this:
Finally, it worked. I was using GlassFishV3 application server. When I moved same code to GlassFish 3.0.1, it worked like charm. Funny Right? The core idea of Webservice is interoperability but it doesn't seem to be portable between two versions of same server.
Anyways, Thanks a lot for your quick followup.
posted 8 years ago
Good to hear that the matter is resolved.
Did you use v3 or v3 prelude before switching to v3.0.1?