• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

xsi:type ommited in the request xml - axis2 - adb binding - websphere

Hemanth Avs
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am consuming a web service and Generated the Client code using Axis Framework with ADB Binding. I Observed the request xml generated is containing the xsi:type in case I run my code in stand alone ( J2SE ) way. When I am executing the same code from Web Sphere server , I observed the instead of xsi:type only type is coming. because of which I am getting Validation problem from Service provider. They require xsi:type in request xml inoder to pass validation and process the request.

xsi:type may not required when WS-I compliance. But I would like to know how to ensure the xml generated by executing the code in server ( J2EE ) contains xsi:type. I cannot approach service provided to change their code not to validate, since the their service are being used by multiple systems for the past many years.

Is it some thing related to Jars? I mean jars used in the stand alone are differnet from axis jars used during the runtime in websphere.
I see this Websphere provided default axis engine. how can i solve this issue?

Can you please help in this aspect

Hemanth AVS
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic