[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Non persistent connection
Well, Shengaout has a good point.
However another point is that you have to consider different ways to talk to
the J2EE server. I'll try to enumerate them:
1) The Default approach is RMI/RMI-IIOP/RMI-HTTP/CORBA and all the kinds of
RMI over something. This is the heavyweight way.
2) JMS. In this way you can use asynchronous messaging to exchange
information between the client and the middle tier. Thus, you can use all
kind of messaging protocols available under you particular JMS
implementation. SOAP could be one of them. I guess this could be the
lightweight approach for you.
3) Web Services - SOAP, UDDI, WSDI and all kind of other stuff. Another
4) Servlets. The way it works is your application sends HTTP requests to the
a servlet and the servlet returns http replies (not necessary html code)
This is just four different ways off the top of my head. If you ask your
consultant he/she might invent another one.
Hope it helps,
|From: Shengaout, Misha (MARC) [mailto:MShengaout@MARCLife.com]
|Sent: Wednesday, July 24, 2002 10:41 AM
|To: 'mingfei shi'; 'email@example.com'
|Subject: RE: Non persistent connection
|If you decided to go EJB route, RMI-IIOP is THE way to go, so any
|"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
|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.
|From: mingfei shi [mailto:firstname.lastname@example.org]
|Sent: Wednesday, July 24, 2002 10:21 AM
|Subject: Non persistent connection
|We are currently prototyping a J2ee project by using RMI-IIOP to
|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
|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.
|Join the world's largest e-mail service with MSN Hotmail.