>
> I have added two static methods on pull request 568:
>>
>> GeoServerExtensions.mock( context );
>> GeoServerExtensions.mock("resourceLoader", resourceLoader);
>>
>
> I'm against having testing code creep into the normal API so explicitly.
>
I can change the method to be a bit less obvious, but we are kind of stuck
since GeoServerExtensions is acting a singleton (much like
GeoserverDataDirectory before it).
> Can we have a helper object that resides in testing packages that does
> that, without pulluting GeoServerExtension
> directly?
>
I am not quite sure how to make a testing only object to help out. Even if
we create one we still need to inject it into this singleton. I found a few
test cases manipulating the internal state of GeoServerExtension and I
figured methods were better for consistency.
--
Jody
------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
