Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <153525772.1130110202899.JavaMail.jira@ajax.apache.org>
Date: Mon, 24 Oct 2005 01:30:02 +0200 (CEST)
From: "Pier Fumagalli (JIRA)" <jira@apache.org>
To: dev@cocoon.apache.org
Subject: [jira] Moved: (COCOON-1659) xslt extension functions with bsf broken
 due to xalan-2.6 / bsf-2.3 conflict
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/COCOON-1659?page=all ]

Pier Fumagalli moved CTEMP-1175 to COCOON-1659:
-----------------------------------------------

      Project: Cocoon  (was: Cocoon 2)
          Key: COCOON-1659  (was: CTEMP-1175)
     Workflow: Cocoon Workflow  (was: jira)
    Component: * Cocoon Core
                   (was: core)
      Version: 2.1.5
                   (was: 2.1.5)

> xslt extension functions with bsf broken due to xalan-2.6 / bsf-2.3 conflict
> ----------------------------------------------------------------------------
>
>          Key: COCOON-1659
>          URL: http://issues.apache.org/jira/browse/COCOON-1659
>      Project: Cocoon
>         Type: Bug
>   Components: * Cocoon Core
>     Versions: 2.1.5
>  Environment: Operating System: All
> Platform: All
>     Reporter: Bruce Robertson
>     Assignee: Cocoon Developers Team

>
> xsl comprising extension functions implemented through BSF will throw an error
> indicating that the required com.ibm.bsf class cannot be found. In fact, the
> namespace of bsf has changed from com.ibm.bsf to org.apache.bsf in the switch
> from bsf-2.2.jar, which was in cocoon-2.1.4 and bsf-2.3.jar, which is provided
> in the bsf block of cocoon-2.1.5 It seems that xalan-2.6, a core component of
> cocoon-2.1.5, was compiled against the com.ibm.bsf version, and this causes the
> error. 
> Temporary solution is to add a bsf-2.2.jar file to build/webapp/WEBINF/lib. In
> the future, perhaps testing should be done for extension functions in xslt.

-- 
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