Here is a reprised version of a conversation from Scot Bellamy response to Patrick Lighbody on this topic
As for the last question, should entity beans be used, it depends on what the bean is needed to do. One valuable use of entity beans is for objects that will be cached and used by multiple sessions (users) simultaneously. This allows you to adopt a caching algorithm (supported by your container) without having to write the caching mechanism yourself. This can greatly enhance performance. For short-lived objects that will not benefit from a cache, session beans might be a better fit. This shouldn't be viewed as a hard rule but might be a good place to start when deciding between entity beans and session beans. Certainly session beans are generally faster and have less overhead.
Conclusion for DB Connections: Short lived: Session beans Long lived: Entity beans
My apologies for the WAY off topic divergence.. (Scott and everyone else on this list)
Martin Gainty
(cell) 617-852-7822
From: "THOMAS, JAI [AG-Contractor/1000]" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
Subject: RE: tomcat connection pooling
Date: Mon, 13 Dec 2004 14:13:47 -0600
MIME-Version: 1.0
Received: from mail.apache.org ([209.237.227.199]) by mc4-f40.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Mon, 13 Dec 2004 12:14:35 -0800
Received: (qmail 59518 invoked by uid 500); 13 Dec 2004 20:13:59 -0000
Received: (qmail 59469 invoked by uid 99); 13 Dec 2004 20:13:59 -0000
Received: pass (hermes.apache.org: local policy)
Received: from gateway1.monsanto.com (HELO gateway1.monsanto.com) (199.89.234.134) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 13 Dec 2004 12:13:55 -0800
Received: from agstlsmtp02.monsanto.com (agstlsmtp02.monsanto.com [10.30.64.102])by gateway1.monsanto.com (Switch-3.1.6/Switch-3.1.0) with ESMTP id iBDKDpM2028975for <[EMAIL PROTECTED]>; Mon, 13 Dec 2004 14:13:51 -0600 (CST)
Received: by agstlsmtp02.monsanto.com with Internet Mail Service (5.5.2657.72)id <XFTHZVCA>; Mon, 13 Dec 2004 14:13:51 -0600
X-Message-Info: JGTYoYF78jEJixih+PFgfXRFU98oZhwT
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
Precedence: bulk
list-help: <mailto:[EMAIL PROTECTED]>
list-unsubscribe: <mailto:[EMAIL PROTECTED]>
list-post: <mailto:[EMAIL PROTECTED]>
Delivered-To: mailing list [EMAIL PROTECTED]
X-ASF-Spam-Status: No, hits=0.0 required=10.0tests=
X-Spam-Check-By: apache.org
X-Mailer: Internet Mail Service (5.5.2657.72)
X-Virus-Checked: Checked
Return-Path: [EMAIL PROTECTED]
X-OriginalArrivalTime: 13 Dec 2004 20:14:35.0515 (UTC) FILETIME=[5D7A5CB0:01C4E150]
It doesn't matter what type of ejb it is. Your web service is only an access point to
a set of business functionalities. If your service invokes a session bean, whatever connection pooling mechanism you have in place would work in the same way it is acessed via a web interface (or anything else for that matter).
Jai
-----Original Message----- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Monday, December 13, 2004 1:03 PM To: [EMAIL PROTECTED] Subject: RE: tomcat connection pooling
Thomas
Let me rephrase the question to make myself clearer
What Im looking for is Is the Database Connection Pool you are speaking of a Session Bean? a CMP Bean a Entity Bean?
I think this may be OffTopic from SOAP so feel free to respond to my inquiry
offline.
Thank You,
Martin Gainty
(cell) 617-852-7822 (e) [EMAIL PROTECTED] (http)www.laconiadatasystems.com
>From: "THOMAS, JAI [AG-Contractor/1000]" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
>Subject: RE: tomcat connection pooling
>Date: Mon, 13 Dec 2004 10:24:09 -0600
>MIME-Version: 1.0
>Received: from mail.apache.org ([209.237.227.199]) by mc6-f22.hotmail.com
>with Microsoft SMTPSVC(5.0.2195.6713); Mon, 13 Dec 2004 08:30:36 -0800
>Received: (qmail 26710 invoked by uid 500); 13 Dec 2004 16:24:56 -0000
>Received: (qmail 26614 invoked by uid 99); 13 Dec 2004 16:24:55 -0000
>Received: pass (hermes.apache.org: local policy)
>Received: from gateway1.monsanto.com (HELO gateway1.monsanto.com)
>(199.89.234.134) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 13 Dec 2004
>08:24:51 -0800
>Received: from agstlsmtp02.monsanto.com (agstlsmtp02.monsanto.com
>[10.30.64.102])by gateway1.monsanto.com (Switch-3.1.6/Switch-3.1.0) with
>ESMTP id iBDGOC7m001079for <[EMAIL PROTECTED]>; Mon, 13 Dec 2004
>10:24:12 -0600 (CST)
>Received: by agstlsmtp02.monsanto.com with Internet Mail Service
>(5.5.2657.72)id <XFTHZKK1>; Mon, 13 Dec 2004 10:24:12 -0600
>X-Message-Info: JGTYoYF78jEHjJx36Oi8+YDSEg8qKPPD
>Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
>Precedence: bulk
>list-help: <mailto:[EMAIL PROTECTED]>
>list-unsubscribe: <mailto:[EMAIL PROTECTED]>
>list-post: <mailto:[EMAIL PROTECTED]>
>Delivered-To: mailing list [EMAIL PROTECTED]
>X-ASF-Spam-Status: No, hits=0.0 required=10.0tests=
>X-Spam-Check-By: apache.org
>X-Mailer: Internet Mail Service (5.5.2657.72)
>X-Virus-Checked: Checked
>Return-Path: [EMAIL PROTECTED]
>X-OriginalArrivalTime: 13 Dec 2004 16:30:36.0593 (UTC)
>FILETIME=[13419A10:01C4E131]
>
>Martin,
>Connection pool is an enterprise app resource. As long as the service is
>part of the app, it should be able to make use of that.
>Jai
>
>-----Original Message-----
>From: Martin Vossler [mailto:[EMAIL PROTECTED]
>Sent: Monday, December 13, 2004 9:01 AM
>To: [EMAIL PROTECTED]
>Subject: tomcat connection pooling
>
>
>Does anyone know if its possible for an Apache Soap service to leverage
>Tomcats database connection pooling features? Any point in the right
>direction for where to find such information is greatly appreciated.
