RE: Non persistent connection

["Shengaout, Misha (MARC)" <MShengaout@MARCLife.com>]

If you decided to go EJB route, RMI-IIOP is THE way to go, so any talk about
"lightweight" connection with J2EE is a nonsense. But I would really like to
know why is it that you are using J2EE server for Swing client? Do you have
a web client to support as well? Are you having a very complex transactions
spanning multiple databases? Because if the answers are no and you are using
J2EE just as an object-to-relational layer, the whole EJB approach is
"heavyweight". In such case the lightweight approach would be using some
sort of the object-to-relational data layer, like open source Objectstyle
Cayenne or Castor, or a similar commercial product.

Misha

-----Original Message-----
From: mingfei shi [mailto:mingfeis@hotmail.com]
Sent: Wednesday, July 24, 2002 10:21 AM
To: ajug-members@www.ajug.org
Subject: Non persistent connection



Hi,

We are currently prototyping a J2ee project by using RMI-IIOP to connect the

rich client (Swing) to j2ee server.  But our higher level management had an 
outsider consultant review the prototyping architecture, saying RMI-IIOP 
connection is too heavyweight and it should be replaced with lightweight and

non-persistent couterpart (unfortunately he didn't elaborate more than 
that).  My understanding is non-persistent connection is only used between 
browser and web-server.  Is anyone familiar with this "lightweight and 
non-persistent connection" between Java Swing client and ejb server?  Any 
info would be deeply appreciated.

Many thanks,

Mingfei


_________________________________________________________________
Join the world's largest e-mail service with MSN Hotmail. 
http://www.hotmail.com