-
Key: I2JAV11-28
-
Legacy Issue Number: 4059
-
Status: closed
-
Source: Borland Software Corporation ( Vishy Kasar)
-
Summary:
Java language mapping gives the user ability to set the delegate on a
servant through:abstract public class Servant {
{ _delegate = delegate; }
public void _set_delegate(org.omg.PortableServer.portable.Delegate
delegate)}
POA implementation must also set this delegate in many instances where
user provides POA with a servant. activate_object, set_servant etc. In
normal cases user does not set any delegate of his own. In special cases
user may set his delegate on a servant before passing the servant to
POA.There are also cases where user written servant manager may return the
same servant over and over again.It is unclear from the language spec if POA is supposed to honor the
already set delegate or set its own Delegate no matter what. It seems
beneficial to me to look at the existing servant to see if this already
has a Delegate and set it only if it has none. Comments? If that is a
good idea shall we change the language spec to state that explicitly? If
we do not state this explicitly, user code may behave differently when
moved from one ORB implementation to the other. -
Reported: I2JAV 1.0 — Fri, 17 Nov 2000 05:00 GMT
-
Disposition: Resolved — I2JAV 1.1
-
Disposition Summary:
see above
-
Updated: Fri, 6 Mar 2015 20:58 GMT
I2JAV11 — When to honor the servant delegate in POA?
- Key: I2JAV11-28
- OMG Task Force: IDL to Java December 2000 RTF