>
> > However, I truly believe that
> > those who will have experimented with the EJB 2.0 preview
> will have a big
> > headstart when their company decides to switch over to EJB
> 2.0 after the
> > specification has been finalized.
>
> I would like to see some end customers comment on how useful this is
> compared with the pain of rewriting code that they expected would
> only require 'minor' changes.
>
>
We moved to the EJB 2.0 implementation in WebLogic 5.1 (and now 6.0) but not
for the API, we had problems with pessimistic locking that the 2.0 preview
solved.
In all, the changes from the 5.1 EJB 2.0 implementation to the 6.0 EJB 2.0
implementation were minor (compared to the other aspects of the upgrade).
The 1.1 -> 2.0 upgrade is admittedly difficult, but must be taken in any
case. Some hacking with perl automated most of it.
The WebLogic EJB implementation is *not* an area where I have complaints
(but I would like to see finders-load-bean and CMR integrated!)
- Avi
--
And now for something completely different.
===========================================================================
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".
