-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi gang
I've had discussions with Felix (which is sitting next to me) about the issue that the mount path in each block is carved in stone in the SitemapServlet bean definition (I suppose it is not overwritable by Springs PropertyOverwrite mechanism we use as it is an attribute of our own servlet Spring extension thingy). Consider you have a third party block that can display stuff by itself and states to be mounted on path "this-is-IBMs-best-ever". Would you like to have such a part in your URLs? To me it seems we need a way to have a deployer person be able to overwrite such URL path parts. Next comes, while Felix is converting the samples to use servlet-services, that outside a request to the DisplatcherServlet (outside a block context) there is no such information available to where a block is mounted to. After having a look into the DispatcherServlet I would propose to refactor the logic in the createMountableServletsMap method into a Spring bean so that for example the cocoon-webapp can access it and produce a listing page of all samples it has found in the work/blocks directory with the correct links to them. WDYT? - -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (GNU/Linux) iD8DBQFGStkyLNdJvZjjVZARAudxAJ9RBVeQjgerhfQzFsp5I6aVj91DggCgmKCP r1nK/LJmt5rgd+oSK7a0PSE= =Qdhe -----END PGP SIGNATURE-----
