-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
Just a bump since I didn't get any responses other than a question from
Chuck.
Mark? Filip? Bill? Tim? I'd even go for a flame from Remy. ;)
Thanks,
- -chris
On 2/5/2009 4:49 PM, Christopher Schultz wrote:
All,
Back in July, I asked about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
Back in July, I asked about RealmBase requiring a Container object in
order to function properly. This has to do with using securityfilter
with Tomcat's built-in Realms.
Here is a reference to the original thread:
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject: RealmBase's 'Container' requirement (revisited)
Should I continue down this road of trying to prop-up a
Tomcat skeleton server inside the webapp's space
I'm confused (seems to be happening a lot lately): Tomcat already
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
Caldarale, Charles R wrote:
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject: RealmBase's 'Container' requirement (revisited)
Should I continue down this road of trying to prop-up a
Tomcat skeleton server inside
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill,
Bill Barker wrote:
| Unless you pre-registester the Realm with JMX, the dummy needs to extend
| ContainerBase. But otherwise, it just needs to implement getLogger() and
| getContainerSuffix() (not needed if you JMX register yourself) to have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
Securityfilter includes a feature that allows users to wrap Tomcat Realm
classes (Such as DataSourceRealm, JAASRealm, etc.) so they don't have to
implement their own. The adapter that provides the plumbing between the
sf code and the tc code is
Christopher Schultz [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
Securityfilter includes a feature that allows users to wrap Tomcat Realm
classes (Such as DataSourceRealm, JAASRealm, etc.) so they don't have to
implement
