[Cosmo-dev] breaking the ui into separate webapps

Randy Letness randy at osafoundation.org
Wed Nov 8 09:29:19 PST 2006


Brian Moseley wrote: 
> this would require us to package the service apis (and several others)
> in a cosmo-core.jar which would be included in each of the webapps.
> the webapps would  all have access to the same database through j2ee.
>

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.

> it would also require us to set up single sign-on in the snarf bundle
> so that users don't have to log into each ui webapp separately. and
> we'd have to share some components, like the login page, between the
> apps.
>
This is something we should probably do regardless, because people are 
going to want to use some type of SSO to authenticate in cosmo.

-Randy


More information about the cosmo-dev mailing list