Re: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.

2008-01-29 Thread axisnewbee

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.

2008-01-29 Thread Martin Gainty
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.

2007-12-04 Thread Srinivas Gupta
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.

2007-12-03 Thread Martin Gainty
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.

2007-12-03 Thread Peter
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.

2007-12-03 Thread Martin Gainty
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.