Re: problem using default Realm in new unit tests

2012-01-12 Thread markt
Brian Burch wrote: >On 10/01/12 13:21, Brian Burch wrote: >Tomcat.getEngine has not changed its overall behaviour: it creates the >Engine when it doesn't already exist. However, it now also creates and >assigns the default MemoryRealm to the new StandardEngine instance. It isn't the MemoryRea

Re: problem using default Realm in new unit tests

2012-01-12 Thread Brian Burch
On 10/01/12 13:21, Brian Burch wrote: Konstantin, Thank you for your prompt and helpful response... at least I know I haven't overlooked something simple. With your encouragement, I'm happy to keep "fighting the alligators until I can get back to draining the swamp"! I am working on this issue

Re: problem using default Realm in new unit tests

2012-01-09 Thread Brian Burch
Konstantin, Thank you for your prompt and helpful response... at least I know I haven't overlooked something simple. With your encouragement, I'm happy to keep "fighting the alligators until I can get back to draining the swamp"! On 10/01/12 02:56, Konstantin Kolinko wrote: 2012/1/9 Brian B

Re: problem using default Realm in new unit tests

2012-01-09 Thread Konstantin Kolinko
2012/1/9 Brian Burch : > On 06/01/12 11:47, Konstantin Kolinko wrote: >> >> 2012/1/6 Brian Burch: >>> >>> I am developing some new unit tests to validate SingleSignOn and >>> Authenticator logic. I have used this existing test class as my template: >>> >>> org.apache.catalina.authenticator.TestDige

Re: problem using default Realm in new unit tests

2012-01-09 Thread Brian Burch
On 06/01/12 11:47, Konstantin Kolinko wrote: 2012/1/6 Brian Burch: I am developing some new unit tests to validate SingleSignOn and Authenticator logic. I have used this existing test class as my template: org.apache.catalina.authenticator.TestDigestAuthenticator .. which extends org.apache.ca

Re: problem using default Realm in new unit tests

2012-01-05 Thread Konstantin Kolinko
2012/1/6 Brian Burch : > I am developing some new unit tests to validate SingleSignOn and > Authenticator logic. I have used this existing test class as my template: > > org.apache.catalina.authenticator.TestDigestAuthenticator > > .. which extends org.apache.catalina.startup.TomcatBaseTest. > > I

problem using default Realm in new unit tests

2012-01-05 Thread Brian Burch
I am developing some new unit tests to validate SingleSignOn and Authenticator logic. I have used this existing test class as my template: org.apache.catalina.authenticator.TestDigestAuthenticator .. which extends org.apache.catalina.startup.TomcatBaseTest. I noticed that TestDigestAuthenticat