You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cocoon.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2012/12/03 12:19:58 UTC

[jira] [Closed] (COCOON3-107) With latest cocoon-block-deployment and cocoon-service-impl SNAPSHOTs, integration tests fail

     [ https://issues.apache.org/jira/browse/COCOON3-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francesco Chicchiriccò closed COCOON3-107.
------------------------------------------

    Resolution: Invalid

This issue is generated by an incorrect fix for COCOON3-105 that I am about to revert.
                
> With latest cocoon-block-deployment and cocoon-service-impl SNAPSHOTs, integration tests fail
> ---------------------------------------------------------------------------------------------
>
>                 Key: COCOON3-107
>                 URL: https://issues.apache.org/jira/browse/COCOON3-107
>             Project: Cocoon 3
>          Issue Type: Bug
>          Components: cocoon-sample-webapp, cocoon-servlet, cocoon-sitemap
>    Affects Versions: 3.0.0-beta-1
>            Reporter: Francesco Chicchiriccò
>            Priority: Critical
>             Fix For: 3.0.0-beta-1
>
>         Attachments: BlockcontextInterpreter.java, BlockcontextInterpreter.java
>
>
> This is happening as a consequence of COCOON3-105, by upgrading cocoon-servlet-service-impl to 1.3.2-SNAPSHOT and cocoon-block-deployment to 1.2.2-SNAPSHOT
> Basically, since there is no more an installed URLStreamHandlerFactory, every "new URL()" should include an instance of BlockContextURLStreamHandler.
> This makes every other URL loading (including XSLT sheets in a separate block, like happening for cocoon-sample-webapp) unaware of "blockcontext://" URLs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira