incubator-yoko-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darren Middleman (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (YOKO-357) Binding does not handle CORBA nil object references
Date Wed, 25 Apr 2007 13:18:15 GMT

     [ https://issues.apache.org/jira/browse/YOKO-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Darren Middleman resolved YOKO-357.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: v1.0-incubating-M2

Resolved with revision 532348

> Binding does not handle CORBA nil object references
> ---------------------------------------------------
>
>                 Key: YOKO-357
>                 URL: https://issues.apache.org/jira/browse/YOKO-357
>             Project: Yoko - CORBA Server
>          Issue Type: Bug
>          Components: CorbaBinding
>    Affects Versions: v1.0-incubating-M2
>            Reporter: Darren Middleman
>         Assigned To: Darren Middleman
>             Fix For: v1.0-incubating-M2
>
>
> It is possible for a nil value to be returned or passed as a parameter value for a CORBA
object reference.  Currently, the binding does not map this nil value correctly for the creation
of EndpointReferenceTypes in CXF.
> The proposed solution allows for EndpointReferenceTypes to be defined as nillable in
the WSDL schema.  The binding would then detect a null EndpointReferenceType and write the
corresponding nil CORBA object reference.  Similarly, reading a nil object reference would
result in the binding generating the appropriate STAX output so that a null EPR could be created.
> Note that this change will also require some modifications to the IDLToWSDL tool in order
to indicate that object references can be nillable.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message