I would flip this around the other way.
The fact that there is time between spec revisions alows for stabilization
of the
EJB vendor industry. Historically Java initiatives have churned to fast for
the
user community to really adopt them.
Just because Entity Beans are optional until after Moscone doesn't mean they
aren't well supported. Most EJB vendors are supporting Entity Beans.
-Chris.
----------------------------------------------------------------------
Chris Raber, Systems Engineer, GemStone Systems Inc.
100 West Big Beaver, Suite 200, Troy, MI 48084
phone: (248)-680-6691, fax: (248)-680-6689,
email: [EMAIL PROTECTED]
web: http://www.gemstone.com/
----------------------------------------------------------------------
> -----Original Message-----
> From: Erik Ertzeid [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, February 22, 1999 6:59 AM
> To: [EMAIL PROTECTED]
> Subject: Re: future releases of its Enterprise JavaBeans (EJB)
>
> Sven-Uwe Meyer wrote:
> >
> > Hi,
> >
> > ich just had a look at
> >
> > http://www.javaworld.com/jw-02-1999/jw-02-iw-ejb.html?020899txt
> >
> > and i was very surprised that we have to wait a long time until the next
> > EJB specification will come up - here is an extract of the timeline:
> >
> > Q2 1999 - Moscone : next EJB specification (use XML for DD)
> >
> > end of 1999 - Moscone reference implementation
> >
> > Q1 2000 - Javits : connecting to legacy data such as ERP-systems
> > ?? ???? - Milano : entity beans
> >
> > entity beans more than one year ! I'm afraid that many users and vendors
> > don't want to wait that long and will deliver/use proprietary solution
> > which will mess up all the plattform independence.
> > Does that mean that EJB if of no (real) use for another 2 years ?
> >
> > thanks for any comments, sven
> >
>
> Ref. Sven-Uwe Meyer's questions - I have seen no comments so far.
> Is everyone in shock ?
> Is EJB / Java now uninteresting for non-academic purposes ?
> Should companies now look to other solutions ?
> If not, what should an "EJB-based" application developement /
> maintenance strategy now look like ?
>
> Erik
>
> ==========================================================================
> =
> 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".
