axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dimuthu Chathuranga" <>
Subject Re: [axis2c] generated code doesn't respect parameterOrder attribute
Date Wed, 27 Dec 2006 14:00:24 GMT

IIRC the generated parse_om function does not check the order in the
current template. Only the build_om function check the order. This is
a bug in the current templates as you mentioned.

Parse_om just build the xml from the schema objects that is built
using the associated build_om function or built manually.
(  build_om  converts  xml(axiom) --> schema type objects
   parse_om  converts schema type objects-> xml(axiom)

I think manual build of schema objects may caused your problem.

Anyway if it is not the case you may able to edit the xslt file in
atleast for your specific requirement.

If the schema elements are defined within <sequence> tag, the xml
comes with '@ordered' set to true. You may use that.


On 12/21/06, Nicholas Hart <> wrote:
> I'm encountering another problem with client stub code generated with
> wsdl2java.  It looks like it isn't respecting the "parameterOrder"
> attribute specified in the operations in my WSDL file, which results in
> a failure when the SOAP request is made.  If I manually change the order
> in the generated axis2_myFunction_parse_om() function then the SOAP call
> succeeds.
> Is there a wsdl2java argument or some other setting that will fix this?
>   I really don't want to have to manually change potentially hundreds of
> functions...  or failing that, can someone point me to where the code
> that generates the axis2_*_parse_om() functions so I can look into
> possibly adding this feature?
> thanks!
> PS: I'm using axis2 (java) I built from the trunk about a week ago...
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message