• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Axis rejects int parameter

 
Maris Orbidans
Ranch Hand
Posts: 149
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Anything wrong with my code ?



SOAP envelope:



AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
faultSubcode:
faultString: transactionId is not a valid xsi:int



It's Axis 1.4
[ November 25, 2008: Message edited by: Ulf Dittmer ]
 
Peer Reynders
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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:




So try to configure the client with


or

 
Maris Orbidans
Ranch Hand
Posts: 149
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Posts: 149
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Posts: 2968
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Maris Orbidans:
It's c++ on server but it works with java client and axis which I am using.


If you have a client that works, intercept it's request envelope with Apache TCPMon (Tutorial) or java.net tcpmon for comparison purposes.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic