[Cosmo-dev] breaking the ui into separate webapps

[Brian Moseley]

On 11/8/06, Randy Letness <randy at osafoundation.org> wrote:

> What about dependencies like spring and hibernate?  We would have to
> package those in each webapp, which would cause snarf to double in
> size.  We could put them in tomcat/common/lib, but that becomes a
> problem when people want to deploy cosmo to an existing appserver and
> use conflicting versions of these libraries.  Or we could package cosmo
> as an .ear, but that means switching app servers.

packaging the jars in every webapp is easiest and most flexible for
the administrator, even at the cost of a larger download. eventually
we're going to distribute the webapps themselves, along with docs for
how to deploy them in non-snarf environments, and people will be able
to pick and choose what to download.

for snarf itself, i think packaging in tomcat/common/lib is totally
fine. the expectation is that people primarily use snarf to run cosmo,
and maybe some other webapps too, but those will likely package their
own hibernate and spring jars anyway, so the risk of conflict is low.

> This is something we should probably do regardless, because people are
> going to want to use some type of SSO to authenticate in cosmo.

hopefully somebody we'll turn on acegi security's sso integration and
make that configurable through cosmo.properties or a web config panel
or something. it's not a pressing requirement, but somebody will
eventually ask for it.