> This is VERY slow, and in some tests its 100's of times slower than
implementing a connection pool. For the original sender (and Conrad if you
are not aware of this), there are two methods I would choose over the others
above. The first is connection pooling. Servlets in the same web app
maintain a Servlet Context that is a good place to store "global" objects.
This way seems like a good idea because it should be portable across J2EE
compliant application servers right?
> Option 2 is better when you are dealing with application servers,
especialy
with Orion. Orion has a very easy built-in connection pooling capability.
When you suggest this method, I assume you are talking about an Orion
specific mechanism correct? This is convenient if Orion is the only server
you're using. If you ever want to migrate your app to a new server, you have
to use that server's method or resort to the custom connection pool class
above.
Have I grasped the situation, or is there a J2EE-based "standard" mechanism
for connection pooling that is portable across application servers?
Thanks,
Kit Cragin
VP of Product Development
Mongoose Technology, Inc.
www.mongoosetech.com
