On 5/17/07, Dave <[EMAIL PROTECTED]> wrote:
On 5/16/07, Sean Gilligan <[EMAIL PROTECTED]> wrote:
> Lately, I've been using JNDI and Tomcat's context.xml for configuring
> webapps (in turn I use Spring to do JNDI lookups and inject config
> parameters, so components don't have dependencies on JNDI). By doing it
> this way it is possible to produce an immutable WAR that doesn't need
> any changes for deployment. All deployment-specific configuration
> options go in context.xml (for Tomcat)
Making it possible to set up the DB connection and mail-session via
connection properties or JNDI names is the easy part and, for the DB,
we've already got code in place.
> Pros:
> 1) WAR file is "immutable" artifact and compatible with all Servlet
> containers
Yes, I'd definitely like to see an immutable WAR. We've got that now,
thanks to roller-custom.properties unless you want to configure Acegi
for LDAP or SSO. Personally, I'd like to solve that problem by
dropping Acegi entirely and going back to Servlet Authentication so we
can take advantage of the authentication that's built into the app
servers now -- that's what IBM did with Lotus Connections to support
WebSphere and that's what I may have to do in my builds to fully
support Glassfish. But I'm not proposing that (yet).
The problem with ditching Acegi is we have to add back in our own
custom Remember Me and SSL Switching logic. Also, you'd have to
document how to create a JDBC Realm for each application server.
Why do you like CMA better than Acegi? Because IBM is using it?
Matt
> I haven't looked at recent Roller releases, but I get the impression
> that making things 100% Apache license compatible has complicated
> installation. So perhaps the WAR file version could be in the Roller
> Support Java.net project and include all the software with
> verboten-licenses.
Once we switch over to OpenJPA, we will no longer have any dependency
on LGPL code, so the user will not have to do a separate download of
Hibernate.
- Dave
--
http://raibledesigns.com
