Can you also attach any schemas that the WSDL references?

Essentially, yes, it's the blank line that's the problem. The first line must contain that start tag, <?xml>, or not at all, for it to be recognized as correct XML. The response's content type is declared as:

"text/xml; charset=ISO-8859-1"

So, the parser expects XML and will correctly parse it if the first line is declared correctly, or if it is omitted altogether. But, because that tag is declared on the second line, the parser is basically seeing this:

1: <?xml version="1.0" encoding="ISO-8859-1"?>
2: <?xml version="1.0" encoding="UTF-8"?>
...

To note, a client like Advanced REST Client, or something similar, will likely treat the response as having the content type "text/plain", which means it simply presents the response as text. This is excellent for testing because it means you will always see the response, regardless. The behavior you are seeing is simply the way the web service framework we use operates. I'll do some research to see if there is a way around this so you can at least make a request/response.

You're likely going to need to write some Java to get at the values. I don't know what the object hierarchy looks like, but I imagine there is an array of Item objects, and within each there is the key/value pair, which you can extract.

Your application appears setup correctly. I tried out the URL you have in Chrome, as a standard URL, and I get a similar error:

This page contains the following errors:

error on line 2 at column 6: XML declaration allowed only at the start of the document

Same error, different wording. The issue is that this is the return data:

<?xml version="1.0" encoding="UTF-8"?>

<Root>

<Output>

<ReturnCode>-1</ReturnCode>

<numLocations>0</numLocations>

<locationList>

<location>

<name />

<address1 />

<address2 />

<address3 />

<address4 />

<city />

<state /> 

<zipCode />

<phone />

<distance />

</location>

</locationList>

</Output>

</Root>

That looks fine, but all of that is wrapped in another <?xml> block. Having the second <?xml> makes this invalid XML. I'm not sure what REST client you're using from Chrome, but I'm guessing it doesn't do any parsing of the return data the way that OD needs to do. It simply gives you back the XML as text. Either way, the web service shouldn't be returning data in this fashion.

Yes, it would appear that the web service is returning XML within the XML return. It's a bit like this:

<OuterTag>
<?xml version="1.0" encoding="UTF-8"?>
<MoreXML>
....
</MoreXML>
</OuterTag

There's an XML document within the XML document, which is going to throw that error because it is invalid. Do you own the web service? Or do you have a way to modify it?

That's a little tough to answer, as any releases before 6.0 aren't officially supported anymore, and 7.0 changes many things. Plus, there are extra instructions for deployment of 7.0 apps for each application server.

Your best bet is probably to start using the 6.0 release, with 6.0 release approved runtime environments, and then go from there.

If all you want to do is set the endpoint URL dynamically, you can do so by opening the Java source file associated with the WSOP. These are found in:

WEB-INF/src/connectivity.ws.operations

The name of the source file should be the same as that given to the WSOP. In the file, you can scroll down to where the following line is written:

        //}}END:CLASS:CONSTRUCTOR

Below that line, you can set the endpoint just by assigning the value to the variable:

        //}}END:CLASS:CONSTRUCTOR



		// Set directly

		endPoint = "http://www.URL.com";



		// Set from an OD variable

		endPoint = mySession.getVariable(IProjectVariables.UNTITLED).getSimpleVariable().getStringValue();

The above method will work for Axis, Axis2, or REST web services.

It looks like the service is supposed to send back a calendar object, but is instead returning something else. The trace shows that there are question marks, '?', for each of the return values, which is probably why you're seeing the error. If you're using some sort of web service testing application, SoapUI, I'd suggest having it send back a properly formatted date/time value. Something like this:

2015-05-18T15:56:54.925Z

You might need to play with it, though, as I've read it can be temperamental with the format it expects.

Is this the same issue as that posted in this thread?

http://www.devconnectprogram.com/forums/posts/list/18435.page

I am posting a reply there, and if the two are the same, please refer there for follow-up. Thanks.

OD 7 does not officially support Java 8 or Tomcat 8, so you should install Java/Tomcat 7 and point the environment to those installations first before proceeding further. Especially since the issues you are seeing are build and/or runtime related.

No, you can use all 3 connectors in the same application if you wish.

Can you also try one more thing? Put default values in each field in the complex variable that you are using. You can use anything, the letter A, or an empty string.

Neither I nor a colleague can reproduce the error or find anything wrong with your code, unfortunately. Can you confirm that line 124 is actually where the append() problem happens?

at flow.subflow.Services_Module.WS_OutBal_Last5.servletImplementation(WS_OutBal_Last5.java:124)

Is there any other custom code in the file? Perhaps you can send the file to me, either attach to your post or email me:

srkowshik@avaya.com

Try adding in this line before you call the web service:

_stub.getServiceClient().getOptions().setProperty(org.apache.axis2.transport.http.HTTPConstants.CHUNKED, Boolean.FALSE);

Basically, that happens when you try and use a complex variable like a field or a simple variable. For example, if you have a complex variable named "Return" and it has a bunch of fields, and you write this line to access it:

IVariableField returnVar = mySession.getVariableField(IProjectVariables.RETURN);

You will get that error because the variable Return is not a field or simple. To properly access it, you would have to write:

IVariable returnVar = mySession.getVariable(IProjectVariables.RETURN);

You can then access the fields with something like this:

IVariableField field = returnVar.getComplexVariable().getField("FieldNameHere");

There are also methods which let you list out the field names, or get an array of all the fields, etc. The above isn't the only way to access a complex variable field in code, though, but if you get a complex var object you can do other things too, like creating a collection.

Hopefully that clears it up!