On Tue, Oct 30, 2012 at 2:25 PM, Justin Deoliveira <[email protected]> wrote:
> I kind of like David's suggestion of just having template support merged
> into the main set of catalog resources and basically ensure that templates
> is a reserved word.
Hum, I like this path, seems cleaner, but I have a concern.
Later down the road I'd like to request the PSC that this change to be
backported
to the 2.2.x series.
I did not foresee any particular trouble since this was meant to be purely
additive functionality, but adding a constraint on valid workspace name may
increase the likeliness of a negative vote.
> Also can we get around this by in the mapping file hardcoding the ".ftl"
> suffix? So the mappings would look like:
>
> /workspaces/templates.ftl
> /workspaces/{workspace}/datastores/templates.ftl
>
> Or does that still lead to a conflict?
Would lead to a convention breakage, when we ask for templates.ftl we
are supposed
to get back a xml or json file.
Besides, can workspaces have dots in the name? I think so, in this
case templates.ftl is less likely
to generate a conflict than templates, but still possible
Cheers
Andrea
--
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
