[ http://issues.apache.org/jira/browse/COCOON-1934?page=comments#action_12442846 ] Alexander Klimetschek commented on COCOON-1934: -----------------------------------------------
Even better would be to have the cocoon-deployer-plugin auto-create the above mentioned properties file when the org.apache.cocoon.mode=dev is set (which enables reloading on runtime). Then it is possible to simply call "mvn -Dorg.apache.cocoon.mode=dev cocoon:deploy jetty:run". The only question left is how the deployer finds out the original directory of a maven module jar? > [Patch] Allow file system URLs for blockContextURL in BlockServlets > ------------------------------------------------------------------- > > Key: COCOON-1934 > URL: http://issues.apache.org/jira/browse/COCOON-1934 > Project: Cocoon > Issue Type: Improvement > Components: - Blocks Framework > Affects Versions: 2.2-dev (Current SVN) > Reporter: Alexander Klimetschek > Attachments: cocoon-blocks-fw-filesystem-for-blockContextURL.patch > > > When configuring a BlockServlet, you have to specify a blockContextURL which > is used to find the resources for a block (eg. the sitemap when using a > SitemapServlet inside). Currently it does not accept file:/ URLs, which are > useful if you want the development resource reloading feature and have that > URL directly point to the src/main/resources/COB-INF folder. > This patch allows file:// URLs by explicitly checking for them and directly > creating the corresponding URL object. In all other cases, the normal URL > handling of the servlet context is used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
