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

Posted to dev@cocoon.apache.org by "Thorsten Scherler (JIRA)" <ji...@apache.org> on 2012/10/24 02:54:13 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13482880#comment-13482880 ] 

Thorsten Scherler commented on COCOON3-107:
-------------------------------------------

add <bean name="expression-language:blockcontext" class="org.apache.cocoon.sitemap.expression.BlockcontextInterpreter" /> to your app context then use it in your sitemap as {blockcontext:raw-to-internal.xsl} where raw-to-internal.xsl would be resolved against the current blockservice file uri.
                
> 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
>
>
> 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