Hi, Dan. Sorry it took me so long to get back on this.
> -----Original Message-----
> From: Dan OConnor [mailto:[EMAIL PROTECTED]]
> Sent: Monday, October 16, 2000 3:15 PM
> To: jBoss Developer
> Subject: RE: [jBoss-Dev] Tomcat Security and JNDI Integration
>
[...]
> However, I recognize that a separate project has some problems,
> which I think motivated your concern. Maybe a better approach is
> just to have a more configurable ant build. It could look for a
> "TOMCAT" environment variable, similar to the startup files. If
> Tomcat exists, it could build the interceptors; if not, it could skip
> them.
I think this sounds good. Even a secondary target would work. The
build.sh/bat could look for TOMCAT_HOME, and, if found, add the Tomcat
target to the target list. Or maybe this is exactly what you were
saying. ;-)
Did you see my mail from a few minutes ago? My thought is that, as long
as we just "use" Tomcat code (and not modify it, etc), we don't get
infected, and we can use the GPL. It's possible that APL clause 5 may
mess us up, though. These licensing issues are a bummer.
Anyway, I think at least our JNDI code is clean at this point.
I think one of our security adapters does what yours does, but it
requires the Tomcat SimpleRealm to be ahead of it in the stack. I also
think it would work with the Tomcat JDBCRealm by just placing it after
that realm on the stack. I just thought of that. Kinda nice if it
works.
I'm rambling. What do you think? I would really like to get this stuff
in.
Thanks.
-Kevin
