> http://jira.codehaus.org/browse/GEOS-3055 > is proof that at least someone is using global templates. And in > fact, our template documentation says you can put them into > the featureTypes directory to affect all types: > http://geoserver.org/display/GEOSDOC/GetFeatureInfo+templates > > So I would say that yes, we need that for backwards compatibility. > I personally don't find odd that people might want a different default > template, independent of the namespace/workspace. Ahhh... right, thanks for jogging my memory. > > For 3, what about putting the templates directly under > workspaces instead of making up a separate directory? > It follows the general idea of the other .ftl: > workspaces/<ws>/<store>/<typeName>/content.ftl (type specific) > workspaces/<ws>/content.ftl (workspace specific) > workspaces/content.ftl (totally generic) This works for me. > > (and this makes me wonder about > workspaces/<ws>/<store>/content.ftl (store specific) > too) Why not, once we agree on a scheme it should be pretty easy to handle all the levels of a feature type hierarchy. > > Another thing that makes me wonder is the resource/publishing > split. In the future I guess we'll want map and layer specific > templates, and use the resource ones only as fallbacks? Good point. The resource-pub split would mean that each map/layer would have specific templates as well. But I don't see a reason why we can't continue to support templates in the resource hierachy for backwards compability. So the lookup order would become:
maps/<map>/<layer>/content.ftl maps/<map>/content.ftl map/content.ftl workspaces/<ws>/<store>/<typeName>/content.ftl workspaces/<ws>/content.ftl workspaces/content.ftl > > Cheers > Andrea > > > Cheers > Andrea > > >> Andrea Aime wrote: >>> Justin Deoliveira ha scritto: >>>> So in the new system the specific .ftl files would be located under: >>>> >>>> workpaces/<ws>/<ds>/<ft>/*.ftl >>> >>> Makes sense. Where are the global templates going to be located? >>> In the root? >>> >>>> And yes, on the data directory import phase, all the templates and >>>> any other files in the original feature type directory is copied over. >>>> >>>> As for lookups, they will still be looking at the old directory >>>> structure, so that will need to be changes. Will open a jira for this. >>> >>> Cool >>> >>> Cheers >>> Andrea >>> >> >> > > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
