axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dimuthu Gamage" <>
Subject Re: "can not handle the attribute/property type axiom_attribute_t"
Date Fri, 04 Jul 2008 13:22:09 GMT
Hi Karolina,

I guess there is one schema type or some construct in your wsdl  schema,
that is not supported in WSDL2C. (most probably you should have an
"anyAttribute" element.). since wsdl2c can not parse that specific
property/attribute it fails serializing and deserializing whole message. If
you can send the the WSDL to the list, we can identify where exactly is
going wrong.


On Fri, Jul 4, 2008 at 3:39 PM, Karolina <> wrote:

> Hi List -
> I would like to know why the following comments and code appear in the
> WSDL2C generated code.  Has anyone encountered them?
> 1) In a deserialize_from_string method:
>          /* can not handle the attribute type axiom_attribute_t**/
>          status = AXIS2_FAILURE;
> 2) In a serialize_to_string method:
>         /* can not handle the property type axiom_attribute_t**/
>          text_value = NULL
> In running a client to consume a service generated using WSDL2C, the client
> invocation was failing.  In the logs, I found that NULL was being returned
> from a deserialize method causing the problem.  On examination of the WSDL2C
> generated methods for deserializing, I found the above listed comments and
> code.  As a result the method always returns NULL and causes errors.  In
> searching through the WSDL2C generated code, I found that such comments and
> code appears multiple times in serilizing and deserizlizing methods.   When
> I commented out the code, the client and server are able to successfully
> exchange messages.
> What could cause these comments/code to be generated? Could this be a
> problem with the WSDL files?
> I am new to Axis2 and using WSDL2C.  Your help is appreciated!
> -Karolina

View raw message