Hey Dimuthu,

You are right.  I was using the 1.3 release version, but the latest 
snapshot has resolved this issue.

Thanks!

Michael J Molé
Software Engineer
IBM Software Group - Rational
(781)676-2710



"Dimuthu Gamage" <[EMAIL PROTECTED]> 
11/01/2007 12:11 AM
Please respond to
"Apache AXIS C User List" <[email protected]>


To
"Apache AXIS C User List" <[email protected]>
cc

Subject
Re: Axis2C: WSDL2C not properly handling attributes







***********************
Warning: Your file, case2.tar.gz, contains more than 32 files after 
decompression and cannot be scanned.
***********************

Hi Michael,
This problem was there for sometime back. And I thought I fixed it. May be 
it is not for all the cases.
I m attaching the testcase I used to test attribute. 

WSDL: case2/res/Adder4.wsdl
Generated stub code: case2/stub 
Generated skel code: case2/skel

And if you find your generated code is different, please try with the 
latest snapshot. 
http://people.apache.org/dist/axis2/nightly/axis2-SNAPSHOT-bin.zip 

Thanks
Dimuthu

On 11/1/07, Michael Mole <[EMAIL PROTECTED]> wrote:

I have an xsd that defines a complex type with an attribute.  When I 
generate adb databindings using WSDL2C, the generated serialize method 
will crash when I run it.  It appears that this is because the attribute 
is added using  a call to axiom_element_add_attribute.  However, the 
element being passed to axiom_element_add_attribute is of type 
axutil_stream_t, and the element tags had already been written anyway 
using axutil_stream_write. 

I can't imagine that I'm the first one to try to use adb_bindings with an 
element that has an attribute.  Has anyone else ever run into a problem 
like this or been successful?  Should I raise a JIRA? 
        

Thanks,
Mike 

Michael J Molé
Software Engineer
IBM Software Group - Rational
(781)676-2710
[attachment "case2.tar.gz" deleted by Michael Mole/Lexington/IBM] 
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to