Re: Does jBoss work on iSeries?

    Hi Ivan,

    As a followup, while no one can give really meaningful advice without
understanding your application, it begins to sound as if Tomcat or Jetty
with/without an HTTP server might meet your needs.  You still should
consider future usage; if you see a need in the future for the integrated
services I pointed out in my previous message, you might still opt for J2EE.

    Incidentally, most JDBC drivers now include a connection pooling
facility.  You are not going to get away from thread safety issues in
webapps whether under J2EE or not.  If your transaction management
requirements are purely for database operations, JDBC has it.  If your
transactions include non-DB operations, then you will need an overall
transaction manager, which is included in J2EE.  HTH,


                                                         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 1:10 PM
Subject: Re: Does jBoss work on iSeries?


> For this project I'm designing, it will ALL reside on
> a single as400 machine. There are no other
> servers/machines involved here. That is why I am
> hesitant to jump into the EJB world for this. I want
> something simple to produce and which performs fast.
> If I avoid EJB, then I can disregard the need for
> expensive Websphere Enterprise Servers and such,
> simply using Tomcat as a standalone. Also I don't have
> to deal with the EJB complexity. However, I was
> looking for good alternatives since using EJB does
> provide much system level functionality via the
> container (i.e state mgmt, threading, transaction
> control, pooling, persistence, etc.).
>
> I have looked at google searches for EJB. I know I can
> use JDO, or even Record-Level I/O from jt400, to
> access the database instead of using CMP. But I was
> concerned about how much of that system level code I'd
> have to write myself if I did not EJB at all.
>
> To consolidate some of the responses, it sounds like I
> can use something called Proxool to handle connection
> pooling. And Hibernate (not familiar with it) to
> handle persistence (not sure if this is instead of or
> in addition to using JDO). Then that leaves state
> mgmt, threading and transaction control to be dealt
> with... any suggestions on how to best deal with those
> items without EJB?
>
> Thx!
>