Please report new issues athttps://github.com/DOCGroup
In the course of the corba_env_clean overhaul, we deprecated the method env() in the CORBA::Request interface (see $TAO_ROOT/tao/DynamicInterface/Request.h) However, when using the DII, the env() method may still be required. Thus it would be helpful to either bring the env() method back to life for DII users, or to give a recipe on how DII users can circumvent its lack.
Assigning the bug to me. Oliver, I am not yet clear on the motivation why this is needed by the application. If you can provide me a use case scenraio on why this is needed, it would be awesome. Thanks
Bala, The question arose when I attempted to port CorbaScript (http://corbaweb.lifl.fr/CorbaScript/index.html) to newer versions of TAO. For more detail, see http://groups.google.com/groups?q=env+%2B+corbascript+group:comp.soft- sys.ace&hl=en&lr=&ie=UTF-8&group=comp.soft- sys.ace&safe=off&selm=3F18033C.8855C9E%40sysde.eads.net&rnum=2 It seems that all other CorbaScript supported ORBs support the CORBA::Request::env() operation. Thanks for looking into this.
Oliver- I took a look at the spec and looks like the env () is required. Time to fix this. !
Bala, > I took a look at the spec and looks like the env () is required. Yes. One interesting thing is, CORBA 3.0 actually _does_ deprecate the operation. (At least I found no mention of env() in the CORBA 3.0.1 PIDL file for CORBA::Request.) Now I'm not sure which CORBA version TAO is targeting, but I think it would be friendly to CORBA 2.x users to support it.
Oliver- The latest C++ mapping spec requires it anyway. We have to go by that. Please see http://www.omg.org/docs/formal/03-06-03.pdf sections 1.30, specifically 1.30.2 on pages 1.119 and 1.120 HTH
Accepting this
This should be less than a day's worth of work. We need to pass the environment pointer and use that while making requests. Should be easy to fix it as soon as we can get to it.
Hi Bala, You wrote: > [...] We need to pass the environment pointer and use that > while making requests. I gave this a shot but I was not sure where the environment pointer comes from in native exception builds (the ACE_ENV_ macros resolve to thin air in this case?) Thanks.
to pool