db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Trejkaz (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-5397) Make it possible to directly set a UserAuthenticator instance on the NetworkServerControl.
Date Wed, 31 Aug 2011 01:31:09 GMT
Make it possible to directly set a UserAuthenticator instance on the NetworkServerControl.
------------------------------------------------------------------------------------------

                 Key: DERBY-5397
                 URL: https://issues.apache.org/jira/browse/DERBY-5397
             Project: Derby
          Issue Type: Improvement
          Components: Network Server
            Reporter: Trejkaz


We are using NetworkServerControl to embed the Derby server.  We would like to use our own
user authenticator for this.  Currently, this requires setting a system property and Derby
creates a brand new instance every time it needs to call it.

This wreaks havoc with our development philosophy because we would like to unit test our stuff,
but Derby is constructing an instance directly instead of letting us pass a mock authenticator.

The workaround we are using is:

* Set the real authenticator as a static field somewhere and provide register()/deregister()/lookup()
access methods
* Make a DelegatingUserAuthenticator which calls lookup() on the real thing and then delegates
the call to it



--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message