Doron,
        You are right about not using distributed transactions and security. There were
not many vendors who supported distributed transactions at the time we started working
on the components. Also, some of the vendors were moving to Java 2 security model, so
that's the reason we opted not to test security.
As Tom Daly pointed out our initial goal was to get a single set of EJB's working
portably, by using features like transactions, bean to bean calls, etc. We were just
trying to demonstrate portability, and not "COMPLIANCE" or PERFORMANCE" testing.
We are definitely working on making these components available on JDC over the next few
weeks.

Also, this was the first of many exercises planned. We will definitely consider using
distributed transactions, and security in future.


Thanks,
Uday

MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Date: Mon, 28 Jun 1999 15:18:24 -0700
From: Doron Somer <[EMAIL PROTECTED]>
Subject: Re: EJB Deployathon Results?
To: [EMAIL PROTECTED]

Actually I had the same doubts and by talking with one of the leading
vendors they were confirmed. The beans are really quite simple, and I don't
believe distributed transactions or security were involved.

One thing that was successfully implemented according to that vendor was
container managed persistence. All vendors used the same relational database
and mapped it to the beans persistent state.

I like the idea of challenging Sun to provide the source code.

In any case, even if the beans were not very sophisticated, I think that
it's quite impressive to see the exact same application deployed on 14
different products w/o any source changes.

Doron

> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Brian Maso
> Sent: Monday, June 28, 1999 2:38 PM
> To: [EMAIL PROTECTED]
> Subject: Re: EJB Deployathon Results?
>
>
> 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".

Reply via email to