cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Heinicke (JIRA) <>
Subject [jira] Closed: (COCOON-1196) [XSP] logicsheet-util.xsl failes with duplicate namespace declarations
Date Tue, 03 Oct 2006 13:34:23 GMT
     [ ]

Jörg Heinicke closed COCOON-1196.

    Fix Version/s: 2.2-dev (Current SVN)
                   2.1.10-dev (current SVN)
       Resolution: Fixed

Matching/Selecting is now done using namespace-uri instead of namespace-prefix found in an
"obscure" way. The old way would not have been only failed with duplicate namespace declarations,
but also for redeclared namespaces.

> [XSP] logicsheet-util.xsl failes with duplicate namespace declarations
> ----------------------------------------------------------------------
>                 Key: COCOON-1196
>                 URL:
>             Project: Cocoon
>          Issue Type: Bug
>          Components: Blocks: XSP
>    Affects Versions: 2.1.8
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Andreas Hartmann
>         Assigned To: Jörg Heinicke
>            Priority: Minor
>             Fix For: 2.2-dev (Current SVN), 2.1.10-dev (current SVN)
> If an input module namespace is declared twice, e.g.
>   xmlns:xsp-input=""
>   xmlns:input=""
> and <input:param> is used for a required parameter:
>   <input:get-attribute>
>     <input:param name="name">foo</input:param>
>     <input:param name="module">list</input:param>
>   </input:get-attribute>
> a ProcessingException is thrown, because the template
> "get-namespace-prefix" in logicsheet-util.xsl is matching
> the first namespace declaration and does not find any
> parameter tags for this namespace prefix.
> I think it is not a good practise to rely on namespace
> prefixes. Wouldn't it be possible to use just the
> namespace URIs to resolve the parameter?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message