[jira] Commented: (AXISCPP-716) Support for the attribute construct 'use'

["Franz Fehringer (JIRA)" <ax...@ws.apache.org>]

    [ http://issues.apache.org/jira/browse/AXISCPP-716?page=comments#action_12428078 ] 
            
Franz Fehringer commented on AXISCPP-716:
-----------------------------------------

Mail (response) by Adrian Dick
-------------------------

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 (adrian.dick@uk.ibm.com)


Franz Fehringer <fe...@isogmbh.de> 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
> >
> >
> > 



> Support for the attribute construct 'use'
> -----------------------------------------
>
>                 Key: AXISCPP-716
>                 URL: http://issues.apache.org/jira/browse/AXISCPP-716
>             Project: Axis-C++
>          Issue Type: Improvement
>          Components: Client - Deserialization, Serialization, Server - Deserialization, SOAP, WSDL processing - Doc, WSDL processing - RPC
>    Affects Versions: current (nightly)
>            Reporter: Adrian Dick
>
> Currently, there is no support for the 'use' construct on attributes defined in a WSDL file.
> The values this can take are:
> - required
> - optional
> - prohibited
> The current default behaviour we provide matches to 'required', although WSDL2Ws does not validate this is definitely the case.
> To support optional we would need to do something similar to the behaviour for nillable on elements.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org