Answers to: XMLStreamException while calling a SOAP webservice

Comment by Daniel Oechslin on Björn's question

Daniel Oechslin — Fri, 13 Dec 2013 07:28:30 -0500

sent you an E-Mail

Comment by Björn on Daniel Oechslin's answer

Björn — Thu, 12 Dec 2013 16:49:15 -0500

Hi Reguel. Thank you very much for your offer to help. But as it is now too late for the students to implement a solution, I told them that they should ignore for now. But in the long-term I would like to get a solution to this. May I contact you in January 2014 for a netviewer session, so we can investigate this directly on my computer?

Comment by Reguel Wermelinger on Daniel Oechslin's answer

Reguel Wermelinger — Thu, 12 Dec 2013 15:13:32 -0500

can you share a soap UI project with the mocked service and sample answer as well? else I'm not able to reproduce this issue - as the schema is not available from my network.

Comment by Björn on Daniel Oechslin's answer

Björn — Wed, 11 Dec 2013 10:28:59 -0500

Thanks for your comment. I tried what you said, but it don't work. One of the students groups was able to at least partially test the webservice call, so I looked, what they are doing else than me. It seems, that the input string is the problem. I made another very short video to explain my findings until now (see link at the end of the initial question).

Comment by Daniel Oechslin on Daniel Oechslin's answer

Daniel Oechslin — Wed, 11 Dec 2013 10:09:00 -0500

it looks like you simply need to map the return value in the result tab of your webservice. There is an empty testwebserviceresponse. This missing xml could trigger the not found exception because there is no valid XML in an empty response.

Comment by Björn on Daniel Oechslin's answer

Björn — Wed, 11 Dec 2013 09:32:04 -0500

Thank you very much for your 2nd answer. I'm still not able to solve the problem, but I believe coming closer to the problem. I recorded a short screencast, where I show the structure of the webservice in Inubit and my attempt to use the service in Xpert.ivy (screencast is in german only, sorry). Also I exported the Xpert.ivy project shown in the screencast to an IAR-file for further investigation. The links to the screencast and iar-file are at the end of my initial question.

Answer by Daniel Oechslin

Daniel Oechslin — Tue, 10 Dec 2013 16:56:13 -0500

I found the error on your soap request. But I can't show you the solution in Xpert-Ivy. Your error is due to a missing START_ELEMENT means: the SOAP-request is missing the name of your webservice.

What you send:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:bet="https://venus.zhaw.ch:8443/ibis/ws/1383213506125/Betreibungsregisterauszug_ws_Listener">
   <soapenv:Header/>
   <soapenv:Body>
      <bet:BetreibungsregisterauszugErhalten>CH450234</bet:BetreibungsregisterauszugErhalten>      
</soapenv:Body>

and what it should be:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:bet="https://venus.zhaw.ch:8443/ibis/ws/1383213506125/Betreibungsregisterauszug_ws_Listener">
   <soapenv:Header/>
   <soapenv:Body>
<unk:betreibungsregisterauszugerhalten>
      <bet:BetreibungsregisterauszugErhalten>CH450234</bet:BetreibungsregisterauszugErhalten>      
</unk:betreibungsregisterauszugerhalten>
 </soapenv:Body>

The difference is the unk:betreibungsregisterauszugerhalten-tag in the SOAP-request. The tag specifies the name of the webservice which should handle your request. It is nescessary to know the name of the webservice, because there can be several webservices where your request may fit.

Where the first part: unk stays for the package name. unk= unknown in this case. The second part: betreibungsregisterauszugerhalten is the method name, defined in your top-level-interface. Like betreibungsregisterauszugerhalten().

If this doesn't help you, please provide a full code example.

Comment by Björn on Daniel Oechslin's answer

Björn — Tue, 10 Dec 2013 15:55:47 -0500

It would be nice, if I get further support, since I don't know how to implement the answer (see my comment of 06.12 at 14:43). The answer makes no sense to me.

Comment by Björn on Björn's question

Björn — Fri, 06 Dec 2013 16:15:46 -0500

Off topic: May I ask, where you work?

Comment by Björn on Björn's question

Björn — Fri, 06 Dec 2013 15:08:20 -0500

Probably your firewall is blocking venus.zhaw.ch, because it has not a valid SSL certificate. But when you check venus.zhaw.ch with port 8000 outside of the Soreco Network, it is open: see ping.eu/port-chk

Comment by Björn on Daniel Oechslin's answer

Björn — Fri, 06 Dec 2013 14:53:48 -0500

I've added the raw XML request at the end of my question.

Comment by Daniel Oechslin on Björn's question

Daniel Oechslin — Fri, 06 Dec 2013 14:53:30 -0500

because we can't see venus.zhaw.ch:8000 outside the zhaw Network.

http://s30.postimg.org/5hfvjzo3h/cmd.jpg

Comment by Daniel Oechslin on Daniel Oechslin's answer

Daniel Oechslin — Fri, 06 Dec 2013 14:47:52 -0500

Could you add a picture of a SoapUI generated XML-request?

Comment by Björn on Björn's question

Björn — Fri, 06 Dec 2013 14:46:58 -0500

I'm using the service now outside the ZHAW Network and it works in soapUI. Why do you mean, it isn't valid?

Comment by Björn on Daniel Oechslin's answer

Björn — Fri, 06 Dec 2013 14:43:48 -0500

Wow, this is definitely not straight forward. I hoped, that Xpert.ivy does the String-To-XMLparsing job for me, as I am used to from using Inubit.

I need more information to get your answer to work for me. Where to put your code - in a script step or somewhere else? And what do you mean with "field of choice" - is this the name of an data class attribute of the type ch.ivyteam.ivy.scripting.objects.Xml?

Comment by Daniel Oechslin on Björn's question

Daniel Oechslin — Fri, 06 Dec 2013 14:38:42 -0500

PS: Your WSDL is not valid to ppl outside the ZHAW Network.

Answer by Daniel Oechslin

Daniel Oechslin — Fri, 06 Dec 2013 14:28:18 -0500

You sent a single string instead of a valid xml. You need to send a valid XML-object.

 @XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "contentType", propOrder = {
    "senderPerson"   
})


public class ContentType{
        @XmlElement(required = true)
        protected String senderPerson;

        /**
         * Returns the senderPerson.
         * @return the senderPerson
         */
        public String getSenderPerson() {
            return senderPerson;
        }

        /**
         * Sets the sender person.
         * @param senderPerson the senderPerson to set
         */
        public void setSenderPerson(String senderPerson) {
            this.senderPerson = senderPerson;
        }

With this you create a valid response. Change the senderPerson to your field of choice and your fine.

First you need to specify how your request looks. So Ivy understands the incoming request and can validate the fields. You can create such specification in creating a plain java class inserting the code above. The first line defines the name of the request in this case contentType. Followed by properties. You add them in correct order separated by comma. I added a single field called senderPerson.

The Java class itself maps the xmltype field to Java fields and provides getter and Setters.

You can use this class now as Parameter type in your webservice call.