Brian,

We went right into the architecture and what was and was not tested by our
comonents during the Developing portable enterprise JavaBeans BOF at JavaOne.
E.g we didn't test say "getHandle" but we DID use transactions AND bean to
bean calls AND calls out to a web server AND aggregation of components etc.

We will cover this pretty well in our documentation and I think you will see
that what we did was to try and create a realistic demo, by creating
components that you might reasonably expect to use in an e-commerce website.
You can judge the reality of this when we get the stuff posted.

By the way I would comment that simple beans are good beans, it is be design
not by accident. If this makes the beans easier to code and hence be portable
..then this is good not bad. It doesn't mean this is not a poweful way to
create distributed n-tier transactional/secure applications

I am not sure how or when we might release the source code.

HTH
Tom Daly


> Is the source code for the beans you did eventually get to work across
> different vendors available, as well as the DDs? I saw the "deployathon"
> demo, and I must admit I was quite sceptical about what EJB features were
> actually being exercised. I imiagine its quite possible to make a simple
> beans that works across all sorts of different servers, but can you make a
> non-trivial one? I'm still reserving judgement until I see the source and a
> bit more description of the beans that were used.
>
> Brian Maso
> DevelopMentor Java Curriculum Developer; http://www.develop.com
> Blumenfeld & Maso, Inc.
>
> -----Original Message-----
> From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> Date: Monday, June 28, 1999 1:27 PM
> Subject: Re: EJB Deployathon Results?
>
>
> >Jorgen,
> >
> >My name is Tom Daly and I was part of the team from within Sun that put
> "The
> >Enterprise JavaBeans Deployathon" together.  Firstly we are expecting  a
> >couple of articles to show up on  java.sun.com and/or the java developer
> >connection over the next few weeks giving more details of the exercise,
> >hopefully this will explain it well enough for those who missed the JavaOne
> >event.
> >
> >To answer your question, our initial goal for the deployathon was to get a
> >single set of EJB's working portably (i.e unchanged) across a core set of
> EJB
> >servers. Our target number of servers was 6, we achieved more than 12 !
> >
> >Our (i.e. Sun + Server Vendors) intention was to prove that EJB is real
> today
> >by creating a realistic e-commerce demonstration web site with EJB's. We
> were
> >also trying to demonstrate the huge industry support EJB has and finally
> and
> >very importantly we were trying to convincingly demostrate the portability
> of
> >EJB's.
> >
> >I believe we demostrated all these things very clearly and I believe we
> >established clearly the value in not just in the servers we demonstrated
> but
> >in the platform as a whole!
> >
> >HTH
> >Tom Daly (Market Development Engineering, Sun Microsystems)
> >
> >
> >
> > > Can anyone shed any light on the outcome of the "EJB Deployathon" held
> >> at JavaOne'99 last week?   Unfortunately, I was one of the few people on
> >> the planet that wasn't there! :-(
> >>
> >> There is a glossy write-up of the idea behind the event on Sun's web
> >> site, but absolutely no mention of any results.
> >> http://java.sun.com/features/1999/06/ejbdeploy.html
> >> last modified 18-Jun-1999 when I checked yesterday.
> >>
> >> <devils_advocate>
> >> Should I be cynical and assume that it all went horribly wrong and only
> >> proved how non-standard most of the current offering of EJB servers seem
> >> to be???
> >> </devils_advocate>
> >>
> >> Does Sun have any plans to produce a write up of the event or the
> >> results?
> >> If so, any indication of timescales?
> >> I imagine the drafts will probably have to go through several revisions
> >> to keep all the lawyers happy, so I guess this could take some time!
> >>
> >> Further, are there any plans to make the deployathon sample available
> >> for general consumption, perhaps as a general test of container
> >> compatibility?
> >> Obviously most of the Open-Source EJB developments would find this sort
> >> of sample very useful if it were readily available.
> >>
> >>
> >> For the record, I have absolutely NO connections with ANY ejb server
> >> vendor, although no doubt this message will prompt lots of <vendor>
> >> responses :-|
> >> I am merely interested to here some REAL feedback on what actually
> >> happened on the day.
> >>
> >> - Jorgen
> >>
> >> ------------------------------------------------------------
> >> | Software Technologies  -=-=:=-=-  http://www.SwTech.com/ |
> >> | ----------->  One-stop Developer Reference  <----------- |
> >> | Technical reference for professional software developers |
> >> ------------------------------------------------------------
> >>
> >>
> ===========================================================================
> >> 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".

Reply via email to