Hi, There are several areas where Axis C++ does not (yet) completely support the SOAP/XSD specs, and XML attributes is one of those.
I raised Jira AXISCPP-716 ( http://issues.apache.org/jira/browse/AXISCPP-716 ) for the specific issue you've highlighted of required and optional. Regretably, other priorities have prevented me from fixing this problem, and it looks unlikely I'll have an opportunity any time soon. Of course, there's no reason why someone else couldn't take it on. As for how to fix this. I believe most (possibly all) the logic for this needs to be in the WSDL2Ws generate code. I would suggest required attributes should be by-value while optional attributes should be by-pointer, similar to nillable and optional elements. Regards, Adrian _______________________________________ Adrian Dick ([EMAIL PROTECTED]) Franz Fehringer <[EMAIL PROTECTED]> wrote on 21/06/2006 10:21:51: > Hello, > > Today i had a closer look at the handling of xml attributes in Axis > generated C++ code (i work with latest SVN and consider for the moment > only the deserializing/response handling part). > First it seems that no difference between optional and required > attributes is made. > When it comes to deserializing, it is (equal in both cases) checked if > the attribute is present and only in this case the appropriate setter is > called. > The problem is now, that the C++ struct members representing the > attributes are values and not pointers and that there is no else branch > in the test for presence of the attribut. > The net effect is, that for nonpresent attributes the correspondent > struct members end up uninitialized (int value 4207536 for example) ant > there is no way to detect the case of missing optional attributes. > A simple (hopefully not too simple minded) fix would be to represent all > attributes as pointers and setting them to NULL in the (to be created) > else branch. > Thoughts (and btw ist there already a JIRA for this)? > > Greetings > > Franz > > > [attachment "feh.vcf" deleted by Adrian Dick/UK/IBM] > --------------------------------------------------------------------- > 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]
