[Esapi-user] New ESAPI Singleton Implementation
chrisisbeef at gmail.com
Tue Jun 8 00:46:23 EDT 2010
ESAPI Community -
I have just checked in a major overhaul of the ESAPI Singleton Pattern
implementation that is currently in-use and am looking to get this out into
some test environments to be sure that I have all the bugs smoked out.
The change that was made is simple and is important if you are using
customized implementations of the ESAPI Classes.
First - the ESAPI Locator is no longer responsible for maintaining instances
of classes, it is now setup to do exactly as it was intended, act as a
Service Locator. This means that the responsiblity of both establishing and
maintaining that a class should be used as a singleton falls to the class
The ObjFactory that is used by ESAPI will now check for the existence of a
method with the following signature in the implementation class it is
public static <Type> getInstance();
If there is a getInstance method on the class, AND it is publicly
accessible, AND it is static, the ObjFactory will return the result of
calling that method rather than calling newInstance on the class itself.
This change will need to be reflected in any custom implementations that you
are using in your ESAPI
If you have any questions, feel free to shoot them out on the ESAPI-Users
list and we will address your questions or concerns promptly.
The issue associated with this revision is #128 - if you find issues with
the new singleton implementation, please submit an issue in the google issue
tracker and we will be notified.
Thanks for your continued support, and we look forward to hearing about your
experiences using ESAPI!
OWASP ESAPI Developer
Check out OWASP ESAPI for Java
Yet Another Developers Blog
Bio and Resume
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Esapi-user