Richard Monson-Haefel wrote:
>
> Where do I get information on javax.rmi.PortableRemoteObject class? Its used
> in the spec to narrow remote references

We've been asking Sun for this for at least a year now, to no avail!
But I did find it finally just the other day. It is included in the
RMI/IIOP beta, in particular you will find it in iioprt.jar (no source
though).

It is surprising to me that when the spec so clearly states that this
class must be used to portably narrow references, that it has been so
extraordinarily difficult for us to obtain an implementation! The most
recent thing we were told by one Sun representative was that we could
implement it ourselves, as apparently some other vendors have done! I
wouldn't be surprised if this violates our license. Apart from that,
probably one day some version of the JDK will include this class, so
we wanted to be sure that our EJB stub architecture would be compatible
from day one with whatever Sun intended to deliver.

We have been told that we are one of only two vendors who have requested
this class from Sun. If this is true, it shows an appaling lack of
interest from the vendors in portability of EJB client programs! I am
very interested in hearing the vendor responses to this point.

If you have an EJB runtime that allows direct casting without the
use of PortableRemoteObject.narrow, you will probably find (as I did)
that PortableRemoteObject.narrow works fine, so the addition of
PortableRemoteObject.narrow to make your client portable won't break
your existing stub archtiecture. I hope that Sun will at least commit
to this continuing to work.

If your EJB runtime doesn't allow direct casting, it looks like the
PortableRemoteObject.narrow won't work yet, since it doesn't seem to
include the "IDL:" prefix in the CORBA repository id that is passes
in _is_a calls to the server (I am sure this will be easily fixed).

Perhaps someone with some background knowledge of what is going on here
could shed some light on the situation. As far as I can tell, the first
mention of the PortableRemoteObject class was in an OMG spec, and
perhaps that spec didn't have the buy-in of the right folks within Sun.
(This is pure speculation on my part).

As you can see by my response, I am not entirely pleased with the
process by which we have finally obtained the implementation of this
class, but I am pleased that it is finally available, and I do hope for
some further discussion of this issue.

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to