As long as they support the PRO.narrow() method call then all is well. That
wasn't my interpretation. It seemed that some were giving vendor's who
implemented the method (and those of us who want them to conform to the
spec) a black-eye.
Just trying to point out the obvious, PRO.narrow() is part of the spec,
therefore any server that claims to be EJB 1.1 compliant will have to
support the method call. If it does nothing, then so be it.
jim
----- Original Message -----
From: Rickard Öberg <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 23, 2000 3:06 AM
Subject: Re: PortableRemoteObject.narrow
Hi!
James Cook wrote:
> There was no semantic reason for doing so. I felt the server should
conform
> to the EJB 1.1 spec. The spec states that PRO.narrow is the mechanism for
> "casting/narrowing" remote object references. I want my beans to be
portable
> among as many servers as possible. Unfortunately, any servers that do not
> allow this function [no names ;-)] are not EJB 1.1 compliant. I have to
code
> around this limitation. This to me is the problem.
Not quite sure what you're referring to here. If the server handles the
conversion without PRO, then the narrow() call is a no-op. I.e. narrow()
will work with any server, it's just that some don't need it to
function.
/Rickard
--
Rickard Öberg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.dreambean.com
Question reality
===========================================================================
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".
===========================================================================
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".
