Justin Deoliveira ha scritto:
>
>>>
>>> 1. Always place services under a sub context path:
>>>
>>> This would involve creating "sub contexts" for everything (similar to
>>> what we do with the ows mapping today):
>>>
>>> /geoserver/ows -> OWS style services
>>> /geoserver/rest -> REST apis
>>> /g
>>
>> 1. Always place services under a sub context path:
>>
>> This would involve creating "sub contexts" for everything (similar to
>> what we do with the ows mapping today):
>>
>> /geoserver/ows -> OWS style services
>> /geoserver/rest -> REST apis
>> /geoserver/ui -> user interface
>
> Thi wo
Andrea Aime wrote:
>
> we also have that
> italian dev group that expressed interest in redoing the GeoServer UI
> in JSF (they contacted us yesterday on IRC), I asked them to share their
> ideas on this ml, we'll see what comes up.
Which reminds me I have still to finalize my example based on C
Justin Deoliveira ha scritto:
> Hi all,
>
> I spent a few hours this evening trying relieve us of the burden of
> having to register the mapping to the spring dispatcher servlet in
> web.xml every time we add a new service. The blocker before was that the
> routing from spring to struts was not
Hi all,
I spent a few hours this evening trying relieve us of the burden of
having to register the mapping to the spring dispatcher servlet in
web.xml every time we add a new service. The blocker before was that the
routing from spring to struts was not working correctly. I managed to
fix this
