Please report new issues athttps://github.com/DOCGroup
In TAO we have: Object create_reference_with_id (in ObjectId oid, in CORBA::RepositoryId intf) raises (WrongPolicy); The corba spec doesn't define the raises clause. Also in the Current local interface the spec defines the following methods not in TAO. Object get_reference() raises(NoContext); Servant get_servant() raises(NoContext);
Another mismatch is the ExceptionHolder, which is part of the Messaging module. According to the spec it should be: // IDL module Messaging { // ... all the other stuff native UserExceptionBase; valuetype ExceptionHolder { void raise_exception() raises (UserExceptionBase); void raise_exception_with_list( in CORBA::ExceptionList exc_list) raises (UserExceptionBase); private boolean is_system_exception; private boolean byte_order; private sequence<octet> marshaled_exception; };
Accept for tao-support
The set_servant_manager behaviour is also not according to the spec, TAO allows to change the servant manager after set, this is not allowed according the spec. Also the exception thrown when a nil or invalid object reference is set is not correct.
The method get_servant in Current will be added as part of my POArefactoring work.
The change for create_reference_with_id is done in the POArefactor2 branch.
The create_reference_with_id and get_servant are now both in the main cvs repo.
It seems that the exception holder interface has an impact on AMI. I found in OMG issue 2929 also the following. There doesn't seem to be a need for a special exception holder. This will change the way the reply handlers is generated by the users. See 22.11 of the corba spec. 4. On page 62, the section 6.5.2: changes: void <operName>_excep( in AMI_<ifaceName>ExceptionHolder excep_holder); .... void get_<attrName>_excep( in AMI_<ifaceName>ExceptionHolder excep_holder); .... void set_<attrName>_excep( in AMI_<ifaceName>ExceptionHolder excep_holder); to: void <operName>_excep( in Messaging::ExceptionHolder excep_holder); .... void get_<attrName>_excep( in Messaging::ExceptionHolder excep_holder); .... void set_<attrName>_excep( in Messaging::ExceptionHolder excep_holder);
Some input from Jeff on the ExceptionHolder. It seems that fixing this will have more impact that initially expected. Johnny is right, getting this up to date will involve changes to the Messaging library, IDL compiler, and about half a dozen tests and examples. Perhaps the biggest headache will be the breakage of stuff for any of our users who employ AMI (I have no clue how many that might be). If there would not be too much screaming in this last category. maybe it's something we should think about for 1.5. It will reduce the size of AMI-related generated code slightly ;-).
the ExceptionHolder update is ready and in cvs. End users can get the old mapping if they define TAO_HAS_DEPRECATED_EXCEPTION_HOLDER in their config.h file before building TAO and the IDL compiler.
The Object get_reference() raises(NoContext) is as operation in cvs, only implementation will be added soon, last item from this bugzilla entry
the get_reference is now also in CVS and this bug is now fully fixed.