Thanks, Karl. All very good points.
My application has a lot of interdependant entity beans and I have found EJB 1.1
somewhat limiting and a just a bit frustrating in this reguard, so I was hopeing to
find
an escape route from that. I suppose that was wishfull thinking. I realize the draft
will probably be changing, possibly radically or possible just slightly. Still, I am
willing to code to the public draft and make the needed changes as they occur until the
spec is final.
But your right. I understand the RIs purpose is to provide a definitive testbed for
compliance. Again, there was more wishfull thinking.
Thanks for the heads up on Orian. You guys are doing a fine job with that product. Can
you give us a hint as to whether "soon" is a few weeks or a few months?
Thanks,
Jim
Karl Avedal wrote:
> Hello Jim,
>
> I can not know for sure how the J2EE RI team is thinking, but the most important
> reason that the RI exists is probably to help ensure compatibility between
> application servers in the sense that the RI is a true implementation of the
> specification and vendors can compare to that version to find portability issues.
>
> If you see that as the main reason, it doesn't really make sense to build a
> Reference Implementation for a draft. The draft will never be anything but a draft
> and compatibility between different implementations of the draft is unimportant
> since the draft will not be compatible with the final EJB 2.0 standard.
>
> Another important thing is that the J2EE RI version with support for EJB 2.0 will be
> the RI for J2EE 1.3. The J2EE 1.3 specification is not available in public draft yet
> and neither are some of its sub-specifications like JSP 1.2 and Servlet 2.3. If the
> J2EE RI team is supposed to update the RI to all the latest drafts of different J2EE
> technologies they will not be able to finish it until a new set of drafts are out.
>
> I haven't used the Weblogic EJB 2.0 beta implementation of the draft so I can not
> say how complete it is, but I can say one thing for sure. If you decide on
> developing for EJB 2.0 now, you will most likely have to modify your application,
> possibly quite a lot, as the specification evolves into the final version. The
> problem of getting tied to Weblogic is probably a much smaller one than the problem
> of getting tied to a draft that will soon be obsolete.
>
> Of course this doesn't mean that you should not be playing with EJB 2.0 already, you
> just have to be aware of the fact that it is just a draft and will change and is not
> a good choice for an application that you want to deploy anytime soon.
>
> <vendor>
> The Orion Application Server will also soon be available in an EJB 2.0 technology
> preview version, intended for those who wants to experiment with EJB 2.0 already.
> However, note that this will in no way be an EJB 2.0 implementation, since EJB 2.0
> simply does not exist yet. It is only based on the public draft.
> </vendor>
>
> Regards,
> Karl Avedal
> The Orion team (http://www.orionserver.com)
>
> Jim Archer wrote:
>
> > Hi All...
> >
> > Sorry if this went out twice... I sent it yesterday but it didn't seem to make
> > the list.
> >
> > I was wondering what Sun's police on J2EE RI is reguarding which spec it
> > implements. I'm wondering if we have to wait for EJB 2.0 to be final before RI
> > implements it, or if we might see it sooner.
> >
> > If we won't see RI for 2.0 soon, does anyone know how we might be able to write
> > code and test it for 2.0? I realize Weblogic has a 2.0 beta, but I don't want to
> > commit to Weblogic, since I won't really be able to afford it (and I doubt my
> > customers will be either) when I'm ready to deploy.
> >
>
> ===========================================================================
> 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".
