I'll paint the target on my own back...
I was a customer that asked Inprise to include support for PRO.narrow() in
their product. Early beta releases functioned with simple casting ala
WebLogic and others. Inprise asked its beta testers if this process should
migrate to PRO.narrow and the overwhelming response was yes.
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.
jim
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Robert Patrick
> Sent: Sunday, March 19, 2000 8:47 AM
> To: [EMAIL PROTECTED]
> Subject: Re: PortableRemoteObject.narrow
>
>
> Give me a break!
>
> <vendor>
> WebLogic does not require the use of PRO but it can certainly be used with
> WebLogic -- go grab the class, stick it in your weblogic
> classpath, and use
> it (if someone wants me to send it to them, please send me email
> privately). Of course, it will be a no-op but if this makes you feel
> better about your EJB compliance then, by all means, please use
> it. PRO is
> being distributed with WebLogic 5.1 (look in the rmi-iiop11.jar or
> rmi-iiop12.jar files).
> </vendor>
>
> IAS 4.0 seems to be a reasonable product but it really makes me
> wonder when
> they start spreading lies about other vendor's products. Why not just
> focus on the features, performance, and scalability of your own product
> rather than resort to vendor bashing?
>
> Just my two cents,
> Robert
>
> At 07:08 AM 3/16/00 +0200, you wrote:
> ><vendor>
> > Take a look at the Inprise's newsgroup for a discussion on this
> >issue and what it means : www.borland.com/newsgroups
> >
> >See the thread named :
> >No portableRemoteObject narrow in weblogic from 07.03.00
> >
> ></vendor>
> >
> >
> >
> > > Hi all,
> > > I am getting as to how the PortableRemoteObject.narrow helps
> when compared
> > > to the simple cntxt.lookup!!!. The code is given below
> > > Object objref = ctx.lookup("pool.Register");
> > > RegisterHome registerhome =
> > > (RegisterHome)PortableRemoteObject.narrow(objref,
> > > connectpool.RegisterHome.class);
> > > compared to
> > > RegisterHome registerhome = (RegisterHome)
> ctx.lookup("pool.Register");
> > > Hey, to me it seems the 1st one increases the # of lines of
> code!!!! but
> > > what values does it add???
> > > Any help to clear this doubt is appreciated.
> > > TIA
> > > Anamitra
> > >
> > >
> > >
> > >
> >=================================================================
> ==========
> > > 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".
>
> ==================================================================
> =========
> 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".
