Re: Does jBoss work on iSeries? -- JAVA400-L

    Hi Ivan,

    There's a basic confusion here that should be straightened out.  EJB
stands for Enterprise JavaBeans.  There are three varieties of EJBs.  These
are:

    Session Beans - Stateful and stateless

    Message-Driven Beans

    Entity Beans - using CMP ( Container Managed Persistence ) and BMP (
Bean Managed Persistence )

    *Entity Beans*, which are used for database interaction, rather than
EJBs as a whole, are what the downsides of J2EE, so far in this discussion,
have been about.

    If you take a look at "The J2EE Platform" at

www.conceptgo.com/gsejb/ov01.html

you'll see the services available to ALL EJBs under J2EE 1.3.  That includes
thread manaagement, usually connection pooling and the other things you were
getting at.  J2EE 1.4 adds Web Services.  In applications where you need
these features, J2EE and the proper EJBs usually wins hands down over trying
to do it yourself.  Notice I said "proper"; there are many aspects of Entity
Beans one should be aware of to make an informed decision.  As always, we
need to be clear as to what we are discussing, especially since many reader
may take comments on this list at face value.

    As to performance, bang for the buck, resource usage and so on, I agree
with Dieter:  use the AS/400 for what it does best.  To me that is security
and database.


                                                         Joe Sam

Joe Sam Shirah -        http://www.conceptgo.com
conceptGO         -        Consulting/Development/Outsourcing
Java Filter Forum:       http://www.ibm.com/developerworks/java/
Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
Going International?    http://www.jguru.com/faq/I18N
Que Java400?             http://www.jguru.com/faq/Java400


----- Original Message -----
From: "Ivan Hurtado" <iva030@xxxxxxxxx>
To: "Java Programming on and around the iSeries / AS400"
<java400-l@xxxxxxxxxxxx>
Sent: Monday, March 08, 2004 11:04 AM
Subject: RE: Does jBoss work on iSeries?


> Joe,
>
> I am in the infancy stage with this design, so I can
> go in any direction. Using EJB is the major decision I
> am still grapling with. I understand what you are
> saying about using JDO for data access, however, what
> about all the other system level functionality that an
> EJB server/container provides... i.e. the connection
> pooling, thread mgmt, session/state mgmt, etc? I'd
> rather not code any of that.
>
> --- Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> wrote:
> > > From: Ivan Hurtado
> > >
> > > I am interested in using jBoss 3.2.3 server on an
> > > iSeries, however, I recently read in Don
> > Denoncourt's
> > > "Java at Work" book that the opensource J2EE/EJB
> > > servers (jBoss and jONas) don't work on iSeries
> > JVM's.
> > >  Is this still true?
> >
> > Ivan, I don't know how far you've gone with your
> > design, but for the
> > last several years the industry has been moving away
> > from EJB.  Even Don
> > Denoncourt, one of the early adopters of the EJB
> > architecture, will tell
> > you that the EJB architecture simply adds too much
> > overhead for all but
> > the simplest applications.  You really should
> > consider another form of
> > ORM.  JDO is a relatively lightweight model, and
> > there are also a number
> > of Open Source persistence packages.  Hibernate is
> > one of the more
> > popular options today.
> >
> > Joe
> >