|
Hi Oleg,
If you look at your WSDD file the web service you deployed is of document literal type. And for document literal type of services the request does not contain the element with the method name as the immediate child of the body. In turn the firsy child is the message->part->element.
<service name="sequencer" provider="java:RPC" style="document" use="literal">
Hope this helps.
Best regards, Shrikant… HPP/eProfile QA Lead. HP
For those who are interested in Web Services testing: ----------------------------------------------------- I found that WebServiceTester from Optimyz software is a very good tool for testing any types of web services, and I'm great fan of this tool. It supports all types of web services, and all simple and complex types and it very usable than any other tool in the market I ever used/evaluated. It automatically generates the SOAP requests and invokes the intended web services. It can perform functional, regression and load testing of web services. Result analysis and status reporting is just wonderful. I'll highly recommend this tool for testing web services, saves lots of time and efforts in testing web services. For more information visit http://www.optimyz.com.
DISCLAIMER ================================================================ THESE ARE MY PERSONAL VIEWS/OPINIONS AND DOES NOT REPRESENT HP, AND THE INFORMATION PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE I/HP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS INFORMATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. =================================================================
-----Original Message-----
Hi all.
I just recently started using axis, so my question may seem trivial for some of you, but please bare with me :) I've created a Java interface with 3 different methods and an implementation class. I also configured ant build.xml file to run java2wsdl, wsdl2java, and axis-admin tasks. So, my service gets deployed on Tomcat, which runs under that lates JBoss.
The problem is that according to SOAP monitor applet, all my SOAP requests are missing the names of the invoked methods. So, the same method is always invoked on the server side independent of the method executed by the client. See SOAP requests and responses in the attachment. (Unfortunately SOAP Monitor does not allow me to copy anything from the applet, so I had to attach it as an image.)
I checked the SoapBindingStubImpl class and the method names are set to all the operations created there, and they are also used in deploy.wsdd file. However, for some reason they are missing from my soap requests.
I attached an image of the SOAP Monitor applet and my deploy.wsdd file.
Thanks.
Oleg
************************************* This e-mail may contain privileged or confidential
material intended for the named recipient only. ************************************* |
Title: Message
