On Mon, Oct 29, 2012 at 6:28 PM, Andrea Aime <[email protected]> wrote: >> /templates/workspaces/<template> >> /templates/workspaces/<workspace>/<template> >> /templates/workspaces/<workspace>/datastores/<datastore>/<template> >> /templates/workspaces/<workspace>/datastores/<datastore>/featuretypes/<featuretype>/<template> >> >> Don't we have the same issue than before? What if someone names a >> template like a workspace?
Actually, the issue above is easily solved by using this hierarchy: /templates/<template> /templates/workspaces/<workspace>/<template> /templates/workspaces/<workspace>/datastores/<datastore>/<template> /templates/workspaces/<workspace>/datastores/<datastore>/featuretypes/<featuretype>/<template> (just changed the location of the main templates). This way a template can only conflict with the name 'workspaces', 'datastores', 'featuretypes' and 'coverages', which is no conflict today and unlikely to happen in the future too. 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
