This week's book giveaway is in the Agile and other Processes forum. We're giving away four copies of The Mikado Method and have Ola Ellnestam and Daniel Brolund on-line! See this thread for details.
Originally posted by Maris Orbidans: It's Axis 1.4
On both sides? i.e. client and the server side? Remember that the RPC/encoded messaging mode (with SOAP encoding) is an interoperability nightmare which is why most of the current generation SOAP web service stacks don't even support it.
faultString: transactionId is not a valid xsi:int
This could simply suggest that the server is "unable" to follow the href to the multiRef element to obtain the value. i.e. it is expecting:
It's c++ on server but it works with java client and axis which I am using. And it fails before request is sent to server.
I changed envelope format:
Now error is different:
AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client faultSubcode: faultString: Invalid element faultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}stackTrace:Invalid element
Maris Orbidans
Ranch Hand
Joined: Mar 08, 2004
Posts: 149
posted
0
no, it comes from server
<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Client</faultcode><faultstring>transactionId is not a valid xsi:int</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
Peer Reynders
Bartender
Joined: Aug 19, 2005
Posts: 2906
posted
0
Originally posted by Maris Orbidans: It's c++ on server but it works with java client and axis which I am using.