I do not use Axis in my project. (And I do not have access to the server
Its RPC style payload.
And the XML gets generated in Eclipse real good.
Only in when I deploy it as a service the xsi:type=blablabla disappears in
the final xml.
My google search returns similar problem reported (but no solutions posted
by another user.
On 10/17/07, Jacob Danner <jaco...@gmail.com> wrote:
This is just a guess, but is the endpoint (server) needing an RPC/encoded
Otherwise are you using Axis in your container? If so which version? Are
you seeing: http://issues.apache.org/jira/browse/AXIS2-2578<https://issues.apache.org/jira/browse/AXIS2-2578>
On 10/17/07, Alex Rayan <alex...@gmail.com > wrote:
I'm using org.apache.xmlbeans.2.3.0.
Using Eclipse/maven2/OSGI for development/deployment.
I've generated the java classes from the xsd document.
And using those classes I generate my request XML.
This works fine when I run this within Eclipse.
But when I deploy my application as a service in a OSGI container,
the xml generated doesnt have the xsi:type in the XML.
Server is external and it rejects the xml without this xsi:type.
XML generated when run as standalone .
<entry xsi:type="userAddition" xmlns:user="http://www.abc.com/schemas/user
XML generated when deployed as a service
<entry xmlns:user="http://www.abc.com/schemas/user ">
My pom file has these dependencies currently listed
Any idea why the behavior is different in standalone environment and
Any other dependencies I need to add to make this work in a service