| Summary: | Object::get_orb is missing | ||
|---|---|---|---|
| Product: | TAO | Reporter: | Johnny Willemsen <jwillemsen> |
| Component: | ORB | Assignee: | Johnny Willemsen <jwillemsen> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | Ulrich.Becker |
| Priority: | P3 | ||
| Version: | 1.4.3 | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | |||
| Bug Blocks: | 2136, 1278 | ||
added blocks In TAO, CORBA::Object is also missing this operation (also from CORBA 3.0.3): 4.3.1.2 repository_id repository_id returns the repository ID of an object (see Section 10.6, "Component Interface Repository Interfaces" on page 10-50 for details of repository IDs). The implementation of this operation must contact the ORB that implements the target object. For LocalObject, it should raise NO_IMPLEMENT. (Note that in some places in the spec, repository_id is misspelled "respository_id".) accept I will add these operations soon. accepted From the draft 3.1 spec. With chapter it refers to the PortableInterceptor chapter: All local objects specified in this chapter except for Interceptor and local interfaces derived from it, PolicyFactory and ORBInitializer override the default behavior of the Object::get_orb operation and return the ORB that the portable interceptor facility is associated with. Added blocks I have _get_orb () ready in my local workspace for CORBA::Object and CORBA::LocalObject. Only the special behaviour for some local objects must be added. We should then also look if the TAO specific _orb_core is still needed as public method. _get_orb() is now there in object and localobject. Only have to override it for the specific local objects that should return the orb associated with. accept For the repository id I made a separate entry, much easier to handle. The draft 3.1 spec restricts repository-id to GIOP 1.4. The only part that has to be done is implement _get_orb for the local objects that need to return the orb instead of throwing an exception * tao/PortableServer/Root_POA.{h,cpp}:
* tao/PortableServer/POAManager.{h,cpp}:
Overruled _get_orb as required by the CORBA spec
Tue Jul 26 09:57:12 UTC 2005 Johnny Willemsen <jwillemsen@remedy.nl> * tao/PICurrent.{h,cpp}: * tao/PICurrent_Loader.cpp: Overruled _get_orb and store an ORB_Core reference instead of a pointer this is in tao |
Added a placeholder bug for the report below from the mailing list. The get_orb () is missing and needs to be added. This is not just simple adding one operation, local objects have different behaviour (see below) The Report: Hello, if I understand the CORBA spec (Version 3.0.3) correctly, CORBA::Object should provide a get_orb() operation that returns the ORB that is responsible for this reference. This doesn't seem to be implemented in TAO. Is this correct, and if so, are there plans to implement it or is there a workaround to get the ORB that is responsible for an object? See the PRF below for our configuration. Best regards, Ulrich TAO VERSION: 1.4.2 ACE VERSION: 5.4.2 HOST MACHINE and OPERATING SYSTEM: Dual processor Xeon, Linux 2.4.26 / 2.6.7 TARGET MACHINE and OPERATING SYSTEM, if different from HOST: COMPILER NAME AND VERSION (AND PATCHLEVEL): gcc-3.3.3 AREA/CLASS/EXAMPLE AFFECTED: CORBA::Object interface DOES THE PROBLEM AFFECT: COMPILATION? No LINKING? No EXECUTION? No OTHER (please specify)? SYNOPSIS: CORBA::Object is missing the get_orb() operation DESCRIPTION: REPEAT BY: SAMPLE FIX/WORKAROUND: -- _ Ulrich Becker ASCII ribbon campaign ( ) - against HTML email X http://www4.cs.fau.de/~ub/ & vCards / \ From the spec 4.3.13 Getting the ORB 4.3.13.1 get_orb ORB get_orb(); March 2004 CORBA, v3.0.3: ORB Interface Chapter 4-23 4 This operation returns the local ORB that is handling this particular Object Reference. 4.3.14 LocalObject Operations Local interfaces are implemented by using CORBA::LocalObject, which derives from CORBA::Object and provides implementations of Object pseudo operations and any other ORB specific support mechanisms that are appropriate for such objects. Object implementation techniques are inherently language mapping specific. Therefore, the LocalObject type is not defined in IDL, but is specified by each language mapping. • The LocalObject type provides implementations of the following Object pseudooperations that raise the NO_IMPLEMENT system exception with standard minor code 8: • get_interface • get_domain_managers • get_policy • get_client_policy • set_policy_overrides • get_policy_overrides • validate_connection • get_component • respository_id • The LocalObject type provides implementations of the following pseudooperations: • non_existent - always returns false. • hash - returns a hash value that is consistent for the lifetime of the object. • is_equivalent - returns true if the references refer to the same LocalObject implementation. • is_a - returns TRUE if the LocalObject derives from or is itself the type specified by the logical_type_id argument. • get_orb - The default behavior of this operation when invoked on a reference to a local object is to return the system exception NO_IMPLEMENT with standard minor code 8. Certain local objects that have close association with an ORB, like POAs, Current objects and certain portable interceptors related local objects override the default behavior and return a reference to the ORB that they are associated with. These are documented in the sections where these local objects are specified See the spec for more info