[tao-bugs] Cannot demarshal valuetypes that indirectly support abstract interfaces

Tadeu Martins tmartins at tecgraf.puc-rio.br
Wed Sep 16 09:10:50 CDT 2015

On 2015-09-09 15:38, Johnny Willemsen wrote:
> Hi,
> Thanks for using the PRF form. This is a very special case, maybe
> somewhere a small bug in the code generation. Could you rework your
> example into a TAO unit test, see https://github.com/DOCGroup/ATCD/ for
> the main repository, see TAO/tests/OBV and TAO/tests/Abstract_Interface
> for some tests in this area. Make it a fully automated test as the
> others so that we can easily build it and run it. Maybe you can see if
> you can find the bug, probably in the code generation by TAO_IDL.
> Best regards,


After some more investigation, I found that implementing
`create_for_unmarshal_abstract()` in my own factories suffices to work
around the problem. However, I could not find any documentation
---either in CORBA specs or in TAO docs--- on its purpose and proper
usage. Could you give me some light on that?

I have also noticed that the workaround mentioned in the first mail
covered a failure of the code generator to implement such member
function at the ADerivedValueType_init class.

I will adapt the tests. Thanks for the attention.

Best regards,

-- Tadeu Martins

More information about the tao-bugs mailing list