David Winslow ha scritto:
...
>> * spring configuration seems a little verbose. Instead of
>> declaring the path in the map, can't we have the resources
>> themselves provide the path, and just declare the resources
>> in the spring context? Something like:
>> <bean name="layerGroupResource"
>> class="org.geoserver.restconfig.LayerGroupListResource">
>> <property name="WMSConfig">
>> <ref bean="wmsConfig" />
>> </property>
>> <property name="location" value="/layergroups/{group}.{type}"/>
>> </bean>
>> </property>
>> </bean>
>> This of course would be an extra, that is, it should not
>> disallow people from writing their own restlets of finders
>> (maybe the default router could scan the context for custom restlet,
>> finders and resources that do expose a location property,
>> which means, custom geoserver subclasses of the ones provided
>> by Restlet).
> The thought behind doing it this way is that you may want to have different
> paths to the same resource (for a trivial example, you might want to allow
> /foo and /foo?{query} and have them handled by the same restlet).
I can have the same by registering the same resource twice and providing
the url in the spring context... and it still seems a lot more compact
to me ;)
...
> Thanks for the comments, Andrea.
Hum, ok, so I gather that if I need a list based resource, I'll have
to roll my own restlet? In the work I'm doing I've been asked to return
arrays of json maps.
Cheers
Andrea
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
