Re: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.
Hi,
Thank u so much for responding.. I am attaching the files u have asked for.
Hope this will help u.. I am using axis 1.4 ..
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.6.5
Created-By: 1.4.2_08-b03 (Sun Microsystems Inc.)
Name: org/apache/axis
Implementation-Title: Apache Axis
Implementation-Version: 1.4 1855 April 22 2006
Implementation-Vendor: Apache Web Services
Thanks,
mgainty wrote:
>
> can you post the code ClientDeployConfiguration.java
> and also post the code for AdminServiceV001ServiceLocator.java
> please display client_deploy_xyz.wsdd
>
> which version axis are you working with ..presumably 1.3 or 1.4?
>
> which version axis.jar are you working with (display contents of
> manifest.mf
> as contained within axis.jar..)
>
> M-
> - Original Message -
> From: "axisnewbee" <[EMAIL PROTECTED]>
> To:
> Sent: Tuesday, January 29, 2008 9:32 AM
> Subject: org.xml.sax.SAXException: SimpleDeserializer encountered a child
> element, which is NOT expected, in something it was trying to deserialize.
>
>
>>
>> Hi Experts,
>>
>> Can i now why i am getting this error.
>>
>> Below is the scenario:
>>
>>
>> I am using a functionality which is using two wsdl's.. These wsdls are
>> generated by WebSPhere WebServices.
>>
>> I am using one client_deploy.wsdd for our security purposes and creating
>> a
>> engine configuration for that
>>
>>
>> public static EngineConfiguration xyz_config = new
>> FileProvider("client_deploy_xyz.wsdd");
>>
>> I am passing this engine Configurator for the serviceLocator of the
>> client
>> code of both wsdls.
>>
>> service1 = new
>> AdminServiceV001ServiceLocator(ClientDeployConfiguration.xyz_CONFIG);
>> service2 = new
>> PricingServiceV001ServiceLocator(ClientDeployConfiguration.xyz_config);
>>
>> I my application when i try to use both services interchagably i am
> getting
>> this error..
>>
>> Sequece ..
>> first used service1
>> next used service2
>> third again used serice1
>>
>> i get a
>>
>>
>> org.xml.sax.SAXException: SimpleDeserializer encountered a child element,
>> which is NOT expected, in something it was trying to deserialize.
>>
>> at
>>
> org.apache.axis.encoding.ser.SimpleDeserializer.onStartChild(SimpleDeseriali
> zer.java:145)
>>
>> at
>>
> org.apache.axis.encoding.DeserializationContext.startElement(Deserialization
> Context.java:1035)
>>
>> at
>>
> org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
>>
>> at
>>
> org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:
> 1141)
>>
>> at
> org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
>>
>> at
>> org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
>>
>> at org.apache.axis.client.Call.invoke(Call.java:2467)
>>
>> at org.apache.axis.client.Call.invoke(Call.java:2366)
>>
>> at org.apache.axis.client.Call.invoke(Call.java:1812)
>>
>>
>> Can anyone tell me what is the problem ..
>> Do let me know if you have any clarifications ..
>>
>> Note:
>>
>> if i use different EngineConfigators i dont get this error
>>
>>
>> public static EngineConfiguration admin_config = new
>> FileProvider("client_deploy_xyz.wsdd");
>> public static EngineConfiguration pricing_config = new
>> FileProvider("client_deploy_xyz.wsdd");
>>
>> but we have quick a lot of servies to be used in our applications.. and i
> am
>> not sure if this the correct solution.
>>
>>
>>
>>
>> Thanks,
>>
>>
>>
>>
>>
>> --
>> View this message in context:
> http://www.nabble.com/org.xml.sax.SAXException%3A-SimpleDeserializer-encount
> ered-a-child-element%2C-which-is-NOT-expected%2C-in-something-it-was-trying-
> to-deserialize.-tp15160285p15160285.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
http://www.nabble.com/file/p15168037/client_deploy_poe.wsdd
client_deploy_poe.wsdd
http://www.nabble.com/file/p15168037/ClientDeployConfiguration.java
ClientDeployConfiguration.java
http://www.nabble.com/file/p15168037/STSAdminServiceV001ServiceLocator.java
STSAdminServiceV001ServiceLocator.java
--
View this message in context:
http://www.nabble.com/org.xml.sax.SAXException%3A-SimpleDeserializer-encountered-a-child-element%2C-which-is-NOT-expected%2C-in-something-it-was-trying-to-deserialize.-tp15160285p15168037.html
Sent from the Axis - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.
can you post the code ClientDeployConfiguration.java
and also post the code for AdminServiceV001ServiceLocator.java
please display client_deploy_xyz.wsdd
which version axis are you working with ..presumably 1.3 or 1.4?
which version axis.jar are you working with (display contents of manifest.mf
as contained within axis.jar..)
M-
- Original Message -
From: "axisnewbee" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, January 29, 2008 9:32 AM
Subject: org.xml.sax.SAXException: SimpleDeserializer encountered a child
element, which is NOT expected, in something it was trying to deserialize.
>
> Hi Experts,
>
> Can i now why i am getting this error.
>
> Below is the scenario:
>
>
> I am using a functionality which is using two wsdl's.. These wsdls are
> generated by WebSPhere WebServices.
>
> I am using one client_deploy.wsdd for our security purposes and creating a
> engine configuration for that
>
>
> public static EngineConfiguration xyz_config = new
> FileProvider("client_deploy_xyz.wsdd");
>
> I am passing this engine Configurator for the serviceLocator of the client
> code of both wsdls.
>
> service1 = new
> AdminServiceV001ServiceLocator(ClientDeployConfiguration.xyz_CONFIG);
> service2 = new
> PricingServiceV001ServiceLocator(ClientDeployConfiguration.xyz_config);
>
> I my application when i try to use both services interchagably i am
getting
> this error..
>
> Sequece ..
> first used service1
> next used service2
> third again used serice1
>
> i get a
>
>
> org.xml.sax.SAXException: SimpleDeserializer encountered a child element,
> which is NOT expected, in something it was trying to deserialize.
>
> at
>
org.apache.axis.encoding.ser.SimpleDeserializer.onStartChild(SimpleDeseriali
zer.java:145)
>
> at
>
org.apache.axis.encoding.DeserializationContext.startElement(Deserialization
Context.java:1035)
>
> at
>
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
>
> at
>
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:
1141)
>
> at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
>
> at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
>
> at org.apache.axis.client.Call.invoke(Call.java:2467)
>
> at org.apache.axis.client.Call.invoke(Call.java:2366)
>
> at org.apache.axis.client.Call.invoke(Call.java:1812)
>
>
> Can anyone tell me what is the problem ..
> Do let me know if you have any clarifications ..
>
> Note:
>
> if i use different EngineConfigators i dont get this error
>
>
> public static EngineConfiguration admin_config = new
> FileProvider("client_deploy_xyz.wsdd");
> public static EngineConfiguration pricing_config = new
> FileProvider("client_deploy_xyz.wsdd");
>
> but we have quick a lot of servies to be used in our applications.. and i
am
> not sure if this the correct solution.
>
>
>
>
> Thanks,
>
>
>
>
>
> --
> View this message in context:
http://www.nabble.com/org.xml.sax.SAXException%3A-SimpleDeserializer-encount
ered-a-child-element%2C-which-is-NOT-expected%2C-in-something-it-was-trying-
to-deserialize.-tp15160285p15160285.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.
I'm not too familiar with Rampart, but the security handlers we're using are
mandated by our customer. So, we have to use them, as well as Axis 1.2.1.
I can't seem to find a consistent resolution on this list, so right now I'm
trying to tweak the server-config.wsdd.
- Original Message
From: Martin Gainty <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Monday, December 3, 2007 9:06:45 PM
Subject: Re: org.xml.sax.SAXException: SimpleDeserializer encountered a child
element, which is NOT expected, in something it was trying to deserialize.
do these security handlers have any advantages over
rampart ?
M-
- Original Message -
From:
Peter
To: axis-user@ws.apache.org
Sent: Monday, December 03, 2007 7:56
PM
Subject: Re: org.xml.sax.SAXException:
SimpleDeserializer encountered a child element, which is NOT expected, in
something it was trying to deserialize.
We're using 3rd party security handlers that only work in Axis
1.2.1.
Srinivas Gupta
Martin Gainty <[EMAIL PROTECTED]> wrote:
DIV {
MARGIN:0px;}
Synivas-
why not
upgrade?
M--
-
Original Message -
From:
Srinivas
Gupta
To:
axis-user@ws.apache.org
Sent:
Monday, December 03, 2007 5:22 PM
Subject:
org.xml.sax.SAXException: SimpleDeserializer encountered a child element,
which is NOT expected, in something it was trying to deserialize.
Hello,
I have a test client whose classes were generated by
Axis 1.2.1 wsdl2java, and I use this to hit services also generated by
wsdl2java. The services comprise what we call a "data
provider". I have used this test client against many data providers
without any problems. But now I'm getting the following exception
when I try to hit a new data provider:
org.xml.sax.SAXException:
SimpleDeserializer encountered a child element, which is NOT expected, in
something it was trying to deserialize
This data provider is using
the same WSDL as all of the other data providers. The only thing
that might be different with this data provider is its
server-config.wsdd. I've tried tweaking the server-config.wsdd, but
to no avail. For example, I tried changing style="document" to
style="rpc". I wish that I could upgrade to Axis 1.4 or Axis 2.0,
but we are constrained to Axis 1.2.1 because of project
requirements...
Does anyone have any suggestions?
Thank
you.
Srinivas Gupta
Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See
how.
Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See
how.
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
Re: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.
do these security handlers have any advantages over rampart ? M- - Original Message - From: Peter To: axis-user@ws.apache.org Sent: Monday, December 03, 2007 7:56 PM Subject: Re: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize. We're using 3rd party security handlers that only work in Axis 1.2.1. Srinivas Gupta Martin Gainty <[EMAIL PROTECTED]> wrote: Synivas- why not upgrade? M-- - Original Message - From: Srinivas Gupta To: axis-user@ws.apache.org Sent: Monday, December 03, 2007 5:22 PM Subject: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize. Hello, I have a test client whose classes were generated by Axis 1.2.1 wsdl2java, and I use this to hit services also generated by wsdl2java. The services comprise what we call a "data provider". I have used this test client against many data providers without any problems. But now I'm getting the following exception when I try to hit a new data provider: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize This data provider is using the same WSDL as all of the other data providers. The only thing that might be different with this data provider is its server-config.wsdd. I've tried tweaking the server-config.wsdd, but to no avail. For example, I tried changing style="document" to style="rpc". I wish that I could upgrade to Axis 1.4 or Axis 2.0, but we are constrained to Axis 1.2.1 because of project requirements... Does anyone have any suggestions? Thank you. Srinivas Gupta -- Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how. -- Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how.
Re: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.
We're using 3rd party security handlers that only work in Axis 1.2.1.
Srinivas Gupta
Martin Gainty <[EMAIL PROTECTED]> wrote:DIV { MARGIN: 0px }Synivas-
why not upgrade?
M--
- Original Message -
From:SrinivasGupta
To: axis-user@ws.apache.org
Sent: Monday, December 03, 2007 5:22PM
Subject: org.xml.sax.SAXException:SimpleDeserializer encountered a child
element, which is NOT expected, insomething it was trying to deserialize.
Hello,
I have a test client whose classes were generated by Axis1.2.1 wsdl2java,
and I use this to hit services also generated bywsdl2java. The services
comprise what we call a "data provider". Ihave used this test client
against many data providers without anyproblems. But now I'm getting the
following exception when I try to hita new data provider:
org.xml.sax.SAXException: SimpleDeserializerencountered a child element,
which is NOT expected, in something it was tryingto deserialize
This data provider is using the same WSDL as all of theother data
providers. The only thing that might be different with thisdata provider
is its server-config.wsdd. I've tried tweaking theserver-config.wsdd, but
to no avail. For example, I tried changingstyle="document" to style="rpc".
I wish that I could upgrade to Axis 1.4or Axis 2.0, but we are constrained
to Axis 1.2.1 because of projectrequirements...
Does anyone have any suggestions?
Thankyou.
Srinivas Gupta
-
Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See
how.
-
Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how.
Re: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.
Synivas- why not upgrade? M-- - Original Message - From: Srinivas Gupta To: axis-user@ws.apache.org Sent: Monday, December 03, 2007 5:22 PM Subject: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize. Hello, I have a test client whose classes were generated by Axis 1.2.1 wsdl2java, and I use this to hit services also generated by wsdl2java. The services comprise what we call a "data provider". I have used this test client against many data providers without any problems. But now I'm getting the following exception when I try to hit a new data provider: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize This data provider is using the same WSDL as all of the other data providers. The only thing that might be different with this data provider is its server-config.wsdd. I've tried tweaking the server-config.wsdd, but to no avail. For example, I tried changing style="document" to style="rpc". I wish that I could upgrade to Axis 1.4 or Axis 2.0, but we are constrained to Axis 1.2.1 because of project requirements... Does anyone have any suggestions? Thank you. Srinivas Gupta -- Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how.
Re: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected
Hello, as I've read in other posts there resson can be a false wsdd file which does not match to the gotten soap xml. I've generated the wsdl with the axis Admin client with the following wsdd file http://xml.apache.org/axis/wsdd/"; xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";> use="literal"> using the command line java -classpath $AXISCLASSPATH org.apache.axis.client.AdminClient -l http://127.0.0.1:8080/axis/servlet/AxisServlet deploy_service.wsdd That generates the following wsdl: targetNamespace="http://localhost:8080/axis/services/HelloWorldXmlEnc";> − − − http://aa";> − targetNamespace="http://localhost:8080/axis/services/HelloWorldXmlEnc";> − − − − − transport="http://schemas.xmlsoap.org/soap/http"/> − − − − − name="HelloWorldXmlEnc"> location="http://localhost:8080/axis/services/HelloWorldXmlEnc"/> Please, if anybody as an idea where to look respond . Regards Mathias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: org.xml.sax.SAXException: SimpleDeserializer encountered a child element...
The xs:schema in your section is missing a targetNamespace. Presuming that you mean this namespace to be targetNamespace="http://localhost:8080/poc-axis-server/services/MessageServi ce" then you should add the xmls:impl=http://localhost:8080/poc-axis-server/services/MessageService"; attribute in the appropriate place. Then the soap body you transmit should contain ... Jeff - Original Message - From: "Dino Chiesa" <[EMAIL PROTECTED]> To: Sent: Tuesday, March 15, 2005 3:56 PM Subject: RE: org.xml.sax.SAXException: SimpleDeserializer encountered a child element... Ps: you originally said you were using AXIS 1.2RC3, But that WSDL doc (which I still cannot parse) says it was generated by AXIS 1.2RC2. ?? Seems like in your WSDD you are specifying a static WSDL? Is that right? Then there is nothing guaranteeing that the static WSDL you are serving actually conforms to what your code is expecting. The static WSDL file could have a picture of tweety bird in it, but that doesn't mean your MessageService actually implements the tweety bird contract. -Dino -Original Message- From: BALDWIN, ALAN J [AG-Contractor/1000] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 15, 2005 5:40 PM To: 'axis-user@ws.apache.org' Subject: RE: org.xml.sax.SAXException: SimpleDeserializer encountered a child element... Actually, that WSDL validated in the eclipse plugin... I was including an external wsdl into the wsdd file so that axis would not generate one for me. I have determined that is not the problem. Here is what is happening now (I've been dealing with this issue for a while): I have a "PurchaseOrder" java bean with a "description" field on it. Again, I'm using document/literal. If the soap message looks like this, it works: test... This does NOT work: test... When I put the PurchaseOrder node in, it breaks. This is just a proof of concept service, but when we implement, I will need the root node in there to validate against an industry standard schema. In this case, I'm just using PurchaseOrder. Any ideas? Thanks for the reply. Here is the WSDL: (copied from the running service, auto-generated from axis) http://localhost:8080/poc-axis-server/services/MessageS ervice"> http://localhost:8080/poc-axis-server/services/MessageS ervice"> http://server.web.services.farmsource.com";> http://localhost:8080/poc-axis-server/services/MessageService "/> http://schemas.xmlsoap.org/soap/http"/> http://localhost:8080/poc-axis-server/services/MessageService"; /> -Original Message- From: Dino Chiesa [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 15, 2005 4:24 PM To: axis-user@ws.apache.org Subject: RE: org.xml.sax.SAXException: SimpleDeserializer encountered a child element... It looks like a disagreement in XML namespace. The echoMessage in the wsdl appears to be in a particular namespace, whereas the VB6 client is sending a message in no namespace at all. string The WSDL you sent isn't a real wsdl. It is missing a bunch of stuff? So it is hard to say whether what I wrote above is right. -Original Message- From: BALDWIN, ALAN J [AG-Contractor/1000] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 15, 2005 5:03 PM To: 'axis-user@ws.apache.org' Subject: RE: org.xml.sax.SAXException: SimpleDeserializer encountered a child element... Here is the response I'm getting, if this helps. I've seen several people having this problem on the web, but nobody seems to have posted any fixes. http://schemas.xmlsoap.org/soap/envelope/";> soapenv:Server.userException org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize. http://xml.apache.org/axis/";>LCEVER Thanks, -Alan Baldwin- -Original Message- From: BALDWIN, ALAN J [AG-Contractor/1000] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 15, 2005 2:56 PM To: 'axis-user@ws.apache.org' Subject: org.xml.sax.SAXException: SimpleDeserializer encountered a child element... Hi all, I'm having an issue with Apache Axis 1.2 RC3. It is running on Tomcat 5.0.28. The error I'm getting is "org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize". I've tried tweaking the schema and wsdl but to no avail. Nothing I do seems to get rid of this error. I'm using a document/literal approach, as you will note below. Is this a schema validation problem? I have downloaded the axis source, but I haven't dug *too* deeply into it. Can anyone help me? Thanks a lot, Alan Baldwin Stack trace: Caused by: org.xml.sax.SAXExcept
RE: org.xml.sax.SAXException: SimpleDeserializer encountered a child element...
Ps: you originally said you were using AXIS 1.2RC3, But that WSDL doc (which I still cannot parse) says it was generated by AXIS 1.2RC2. ?? Seems like in your WSDD you are specifying a static WSDL? Is that right? Then there is nothing guaranteeing that the static WSDL you are serving actually conforms to what your code is expecting. The static WSDL file could have a picture of tweety bird in it, but that doesn't mean your MessageService actually implements the tweety bird contract. -Dino -Original Message- From: BALDWIN, ALAN J [AG-Contractor/1000] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 15, 2005 5:40 PM To: 'axis-user@ws.apache.org' Subject: RE: org.xml.sax.SAXException: SimpleDeserializer encountered a child element... Actually, that WSDL validated in the eclipse plugin... I was including an external wsdl into the wsdd file so that axis would not generate one for me. I have determined that is not the problem. Here is what is happening now (I've been dealing with this issue for a while): I have a "PurchaseOrder" java bean with a "description" field on it. Again, I'm using document/literal. If the soap message looks like this, it works: test... This does NOT work: test... When I put the PurchaseOrder node in, it breaks. This is just a proof of concept service, but when we implement, I will need the root node in there to validate against an industry standard schema. In this case, I'm just using PurchaseOrder. Any ideas? Thanks for the reply. Here is the WSDL: (copied from the running service, auto-generated from axis) http://localhost:8080/poc-axis-server/services/MessageS ervice"> http://localhost:8080/poc-axis-server/services/MessageS ervice"> http://server.web.services.farmsource.com";> http://localhost:8080/poc-axis-server/services/MessageService "/> http://schemas.xmlsoap.org/soap/http"/> http://localhost:8080/poc-axis-server/services/MessageService"; /> -Original Message- From: Dino Chiesa [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 15, 2005 4:24 PM To: axis-user@ws.apache.org Subject: RE: org.xml.sax.SAXException: SimpleDeserializer encountered a child element... It looks like a disagreement in XML namespace. The echoMessage in the wsdl appears to be in a particular namespace, whereas the VB6 client is sending a message in no namespace at all. string The WSDL you sent isn't a real wsdl. It is missing a bunch of stuff? So it is hard to say whether what I wrote above is right. -Original Message- From: BALDWIN, ALAN J [AG-Contractor/1000] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 15, 2005 5:03 PM To: 'axis-user@ws.apache.org' Subject: RE: org.xml.sax.SAXException: SimpleDeserializer encountered a child element... Here is the response I'm getting, if this helps. I've seen several people having this problem on the web, but nobody seems to have posted any fixes. http://schemas.xmlsoap.org/soap/envelope/";> soapenv:Server.userException org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize. http://xml.apache.org/axis/";>LCEVER Thanks, -Alan Baldwin- -Original Message- From: BALDWIN, ALAN J [AG-Contractor/1000] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 15, 2005 2:56 PM To: 'axis-user@ws.apache.org' Subject: org.xml.sax.SAXException: SimpleDeserializer encountered a child element... Hi all, I'm having an issue with Apache Axis 1.2 RC3. It is running on Tomcat 5.0.28. The error I'm getting is "org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize". I've tried tweaking the schema and wsdl but to no avail. Nothing I do seems to get rid of this error. I'm using a document/literal approach, as you will note below. Is this a schema validation problem? I have downloaded the axis source, but I haven't dug *too* deeply into it. Can anyone help me? Thanks a lot, Alan Baldwin Stack trace: Caused by: org.xml.sax.SAXException: SimpleDeserializer encountered a child ele
RE: org.xml.sax.SAXException: SimpleDeserializer encountered a child element...
The reason I say the WSDL isn't valid is, for example, the wsdl: prefix is not defined: http://localhost:8080/poc-axis-server/services/MessageS ervice"> What is the meaning of the wsdl: prefix in the above ? There are a bunch of other missing prefixes: xsd, impl, etc. -Original Message- From: BALDWIN, ALAN J [AG-Contractor/1000] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 15, 2005 5:40 PM To: 'axis-user@ws.apache.org' Subject: RE: org.xml.sax.SAXException: SimpleDeserializer encountered a child element... Actually, that WSDL validated in the eclipse plugin... I was including an external wsdl into the wsdd file so that axis would not generate one for me. I have determined that is not the problem. Here is what is happening now (I've been dealing with this issue for a while): I have a "PurchaseOrder" java bean with a "description" field on it. Again, I'm using document/literal. If the soap message looks like this, it works: test... This does NOT work: test... When I put the PurchaseOrder node in, it breaks. This is just a proof of concept service, but when we implement, I will need the root node in there to validate against an industry standard schema. In this case, I'm just using PurchaseOrder. Any ideas? Thanks for the reply. Here is the WSDL: (copied from the running service, auto-generated from axis) http://localhost:8080/poc-axis-server/services/MessageS ervice"> http://localhost:8080/poc-axis-server/services/MessageS ervice"> http://server.web.services.farmsource.com";> http://localhost:8080/poc-axis-server/services/MessageService "/> http://schemas.xmlsoap.org/soap/http"/> http://localhost:8080/poc-axis-server/services/MessageService"; /> -Original Message- From: Dino Chiesa [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 15, 2005 4:24 PM To: axis-user@ws.apache.org Subject: RE: org.xml.sax.SAXException: SimpleDeserializer encountered a child element... It looks like a disagreement in XML namespace. The echoMessage in the wsdl appears to be in a particular namespace, whereas the VB6 client is sending a message in no namespace at all. string The WSDL you sent isn't a real wsdl. It is missing a bunch of stuff? So it is hard to say whether what I wrote above is right. -Original Message- From: BALDWIN, ALAN J [AG-Contractor/1000] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 15, 2005 5:03 PM To: 'axis-user@ws.apache.org' Subject: RE: org.xml.sax.SAXException: SimpleDeserializer encountered a child element... Here is the response I'm getting, if this helps. I've seen several people having this problem on the web, but nobody seems to have posted any fixes. http://schemas.xmlsoap.org/soap/envelope/";> soapenv:Server.userException org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize. http://xml.apache.org/axis/";>LCEVER Thanks, -Alan Baldwin- -Original Message- From: BALDWIN, ALAN J [AG-Contractor/1000] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 15, 2005 2:56 PM To: 'axis-user@ws.apache.org' Subject: org.xml.sax.SAXException: SimpleDeserializer encountered a child element... Hi all, I'm having an issue with Apache Axis 1.2 RC3. It is running on Tomcat 5.0.28. The error I'm getting is "org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize". I've tried tweaking the schema and wsdl but to no avail. Nothing I do seems to get rid of this error. I'm using a document/literal approach, as you will note below. Is this a schema validation problem? I have downloaded the axis source, but I haven't dug *too* deeply into it. Can anyone help me? Thanks a lot, Alan Baldwin Stack trace: Caused by: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize. at org.apache.axis.encoding.ser.SimpleDeserializer.onStartChild(SimpleDeser ializer.java:143) at org.apache.axis.encoding.DeserializationContext.startElement(Deserializa tio
RE: org.xml.sax.SAXException: SimpleDeserializer encountered a child element...
It looks like a disagreement in XML namespace.
The echoMessage in the wsdl appears to be in a particular namespace,
whereas the VB6 client is sending a message in no namespace at all.
string
The WSDL you sent isn't a real wsdl. It is missing a bunch of stuff?
So it is hard to say whether what I wrote above is right.
-Original Message-
From: BALDWIN, ALAN J [AG-Contractor/1000]
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 15, 2005 5:03 PM
To: 'axis-user@ws.apache.org'
Subject: RE: org.xml.sax.SAXException: SimpleDeserializer encountered a
child element...
Here is the response I'm getting, if this helps. I've seen several
people having this problem on the web, but nobody seems to have posted
any fixes.
http://schemas.xmlsoap.org/soap/envelope/";>
soapenv:Server.userException
org.xml.sax.SAXException: SimpleDeserializer
encountered a child element, which is NOT expected, in something it was
trying to deserialize.
http://xml.apache.org/axis/";>LCEVER
Thanks,
-Alan Baldwin-
-Original Message-
From: BALDWIN, ALAN J [AG-Contractor/1000]
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 15, 2005 2:56 PM
To: 'axis-user@ws.apache.org'
Subject: org.xml.sax.SAXException: SimpleDeserializer encountered a
child element...
Hi all, I'm having an issue with Apache Axis 1.2 RC3. It is running on
Tomcat 5.0.28. The error I'm getting is "org.xml.sax.SAXException:
SimpleDeserializer encountered a child element, which is NOT expected,
in something it was trying to deserialize". I've tried tweaking the
schema and wsdl but to no avail. Nothing I do seems to get rid of this
error. I'm using a document/literal approach, as you will note below.
Is this a schema validation problem? I have downloaded the axis source,
but I haven't dug *too* deeply into it.
Can anyone help me?
Thanks a lot,
Alan Baldwin
Stack trace:
Caused by: org.xml.sax.SAXException: SimpleDeserializer encountered a
child element, which is NOT expected, in something it was trying to
deserialize.
at
org.apache.axis.encoding.ser.SimpleDeserializer.onStartChild(SimpleDeser
ializer.java:143)
at
org.apache.axis.encoding.DeserializationContext.startElement(Deserializa
tionContext.java:1031)
at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:
165)
at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.j
ava:1140)
at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:238)
at
org.apache.axis.message.RPCElement.getParams(RPCElement.java:386)
at
org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.ja
va:148)
at
org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:319
)
Here is my soap message (vb6 client):
http://www.w3.org/2001/XMLSchema";
xmlns:SOAPSDK2="http://www.w3.org/2001/XMLSchema-instance";
xmlns:SOAPSDK3="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";>
test
Here is my wsdl:
http://localhost:8080/poc-axis-server/services/MessageS
ervice">
http://schemas.xmlsoap.org/soap/http"/>
http://localhost:8080/poc-axis-server/services/MessageService";
/>
Here is my WSDD:
...snip...
PurchaseOrder.wsdl
../snip
Here is my Java code:
public class JaxRpcMessageService extends ServletEndpointSupport
implements
RemoteMessageService, MessageService {
protected final Log logger = LogFactory.getLog(getClass());
private MessageService messageService;
//this is from a spring context. this is working fine.
protected void onInit() throws ServiceException {
messageService = (MessageService)
getWebApplicationContext().getBean(
"messageService");
logger.info("Service implementation (from application context):"
+ messageService.getClass());
}
public String echoMessage(SOAPElement po) {
logger.info("Retrieving broadcast message from local service");
return messageService.echoMessage(po);
}
}
