> The configuration is completely orthogonal to the org.geoserver.catalog > classes, much as templates and permissions are. Decoration layouts are > defined in XML files, which can be referenced by name in a format option > as described in both the GSIP and the wiki page.
Noted; so is it the users problem if they specify one of these format options while configuring their geowebcache? > These layouts are global; at present there is no association between layouts > and any other > configuration entity. Okay; last comment comes by way of the magic "format=png-decorated" - can this be removed as the GSIP is accepted? That is can we apply these layouts to any encoding format? > Disabling the feature is as simple as neglecting to define any layout files. >> Can this be used to package up the "watermark" functionaltiy in a cleaner >> form. > > The existing watermark configuration is already interpreted as an extra > 'static image' decoration which is appended to each layout. And my question goes to the idea of not providing duplicate functionality through different mechanisms. Jody ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
