While working on GEOS-6010 I've taken a look at the XStreamServiceLoader
and ServiceFactoryExtension classes and their children.
It seems like the two overlap in their ability to create new ServiceInfo
objects.
XStreamServiceLoader and its subclasses are replacing a bunch of nulls
with default values when deserializing. If those properties should be
non-null, then it seems like they should be set to their defaults when a
new service is created as well as when being deserialized.
Am I missing something about why it's set up like this or is this just a
case of someone reinventing the wheel?
--
Kevin Smith
Junior Software Developer, OpenGeo
<[email protected]>
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
