Jody Garnett a écrit :
> - Adaptor is a wrapper that supports a different interface than the
> origional - this focus is on changing interface rather than adding on
> functionality.
Yes, this is why my old names like "AuthorityFactoryAdapter" were incorrect, and
why I'm trying to figure out a better scheme.
>> "Decorator" may be more accurate, but I'm not a big fan of this name
>> because it seems to have historical root in GUI Windows (adding title
>> or scrollbars to an existing Window, etc.).
> That is just the example in the book; adding security checks to a web
> service is also commonly done with a decorator. Indeed spring AOP almost
> entirly is focused as generating these decorators on the fly using the
> java dynamic proxy facilities.
Yes the design pattern is widely accepted; it is just the name "Decorator"
applied to non-visual stuff that make me inconfortable. Being disturbed by this
details may be yet an other exageration of mine...
Looking at the spring API, I found a few classes ending with "Decorator", for
example this "CachingMapDecorator" wrapping java.util.Map - looks like similar
spirit than CachedAuthorityDecorator. I found only 4 "Decorator" suffix however.
Maybe the decorator pattern is widely applied in an anonymous way like java.io,
I don't know.
Thanks for all your hints,
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
