Just for a clear historical perspective, the EJB 1.0 spec required the use
of PRO.narrow(). Note that this requirement was not in place in < EJB 0.95.
The overwhelming preponderance of code out there that does not use
PRO.narrow() is due to WebLogic's examples that didn't conform to the 1.0
standard. Unfortunately, this practice was picked up by the two EJB authors
(you know who you are) ;-), who's examples were written to run in the
WebLogic server.
I am not trying to throw stones here. Weblogic was on the scene first (by
far), and had/has a killer collection of documentation, developer support,
and a freely downloadable trial version of their product. They proved that
this technology was more than just a theoretical framework. They opened the
door for me and, I suspect, the majority of people on this list.
jim
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED]
> I believe the issues currently being raised about PRO.narrow are
> really EJB
> 1.0 issues where the EJB 1.0 spec recommended but didn't entirely enforce
> PRO.narrow and in fact many vendors implemented a simple java
> cast as their
> first cut at EJB.
===========================================================================
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".
