|Subject:||RE: XmlBeans behaving different in service|
|From:||Cezar Andrei (cez...@bea.com)|
|Date:||Oct 18, 2007 1:06:39 pm|
You have to make sure that the marshaller has access to the xbean jar you generated from the schema.
In other words, the marshaller finds the required schema type in the contextTypeLoader, see org.apache.xmlbeans.XmlBeans.getContextTypeLoader().
I do not use Axis in my project. (And I do not have access to the server side) 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 there ) 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 payload? 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 .
:firstName> <user:lastName>Nambiar</user:lastName> </entry>
XML generated when deployed as a service
<entry xmlns:user="http://www.abc.com/schemas/user "> <user:firstName>Beena</user:firstName> <user:lastName>Nambiar</user:lastName> </entry>
My pom file has these dependencies currently listed
org.apache.xmlbeans xmlbeans xmlbeans-qname xmlbeans-xpath xmlbeans-xmlpublic
Any idea why the behavior is different in standalone environment and container ? Any other dependencies I need to add to make this work in a service environment. ? Thanx
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated entities, that
may be confidential, proprietary, copyrighted and/or legally privileged, and is
intended solely for the use of the individual or entity named in this message.
If you are not the intended recipient, and have received this message in error,
please immediately return this by email and then delete it.