You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by "Somas, Arun" <AS...@sr.csg.com> on 2001/04/19 23:05:14 UTC

RE: apache 2.0 Response parameters

Would it be possible for you to post the BeanInfo class please?

-----Original Message-----
From: Ext-Shaun.OHagan@nokia.com [mailto:Ext-Shaun.OHagan@nokia.com]
Sent: Thursday, February 22, 2001 4:55 AM
To: soap-dev@xml.apache.org
Subject: RE: apache 2.0 Response parameters


Hi Everyone,

I've fixed my own problem.  I created my own beaninfo class with the
appropriate upper case char attributes and it now passes thru.  Now I'm
trying to make sense of the result ;-)

Sorry to have bothered you and thanks to those whom have helped me so far.

Shaun

-----Original Message-----
From: ext Ext-Shaun.OHagan@nokia.com [mailto:Ext-Shaun.OHagan@nokia.com]
Sent: Thursday, February 22, 2001 10:19 AM
To: soap-dev@xml.apache.org
Subject: RE: apache 2.0 Response parameters


Hi,

I've been trying to get a beanserializer to demarshall some data out of an
SOAP message.  I'm finding the following problem.  

Consider the following code -

In BeanSerializer.unmarshall() line 156

      Bean paramBean = xjmr.unmarshall(inScopeEncStyle,
                                       RPCConstants.Q_ELEM_PARAMETER,
                                       tempEl);
      Parameter param = (Parameter)paramBean.value;
      Method propWriteMethod = getWriteMethod(param.getName(),
                                              properties,
                                              javaType);

Using a soap.jar built with debug=on I've walked down into xjmr.unmarshall
and into ParameterSerializer.unmarshall().  On line 111    String name =
paramEl.getTagName(); gives me my first AttributeList XML element as
LastName which is correct and expected.

When I then walk into BeanSerializer.getWriteMethod seen above the code
simply loops thru my AttributeList bean objects PropertyDescriptors looking
for a match on LastName.  My AttributeList bean does have the correct
attribute but it is lastName so the if
(propertyName.equals(pds[i].getName())) will never match !

Changing the SOAP XML to say lastName may fix it but thats not what I want
to do. 

Any pointers gratefully accepted

Regards,

Shaun O'Hagan