--
Jody Garnett

On 15 February 2016 at 16:40, Devon Tucker <[email protected]> wrote:

> I tried implementing a similar approach for the ResourceStore, but it's
> complicated by the fact that GeoServerResourceLoader is itself an
> implementation of ResourceStore and already define in the main
> applicationContext.xml. I also looked at monkeying around with things using
> the Spring Primary/Autowire functionality, but this is hampered by the XML
> config API being slightly different than the annotations based config and I
> didn't get very far.
>

Sorry about that, made it implement the interface to make migrating client
code easier.

Anyone have any thoughts? Is there something more basic I'm missing?
>

The auto migration from file to jdbc makes this more complicated then
strictly necessary. If not for this feature we could make a war that only
had the JDBCResourceStore implementation.

Does spring have a priority we could use to control extensions? Or we could
bust out a -D command line option (to tell the proxy what to use? - with
the default being the file based implementation).
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to