[opencms-dev] Questions re OpenCMS architecture

[Jonathan Woods]

Mike -

1.  OpenCms can run on Tomcat, which strictly speaking is just a web
container.  Tomcat hasn't always made it easy to organise database resources
declaratively, and even now it's a bit of a pain, so that's one possible
explanation.  And C3P0 etc weren't around (I don't think) when OpenCms came
into being, so the roll-your-own connection pooling reflects that.

2.  The OpenCms admin user doesn't need all the rights which the database
admin user has.

Jon

-----Original Message-----
From: opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org] On Behalf Of Mike W
Sent: 29 March 2006 10:49
To: opencms-dev at opencms.org
Subject: [opencms-dev] Questions re OpenCMS architecture

Hi,

I have a couple of questions regarding the architecture of OpenCMS and it's
installation process.

Firstly, why does it use its own DB pooling mechanism when it's deployed to
a J2EE container?
This means we have 2 places with connection pools defined and an inconsitent
level of control.

Secondly, why does the installation process use the supplied admin user to
then create its own (unrestricted) admin user?



_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/mailman/listinfo/opencms-dev