[ http://issues.apache.org/jira/browse/COCOON-550?page=all ]
Helma van der Linden closed COCOON-550:
---------------------------------------
Resolution: Fixed
> xsp:attribute handled incorrectly
> ---------------------------------
>
> Key: COCOON-550
> URL: http://issues.apache.org/jira/browse/COCOON-550
> Project: Cocoon
> Type: Bug
> Components: * Cocoon Core
> Versions: 2.0.4
> Environment: Operating System: other
> Platform: Other
> Reporter: John R. Daily
> Assignee: Cocoon Developers Team
>
> This was originally posted to cocoon-users. Since the only response there
> was a
> general "Yeah, I've seen something like this too", I'm submitting it here.
> --
> I have some xsp:attribute values that are being added to the
> wrong XML element.
> With much stripping, my flow looks like:
> <xsp:page>
> <my_root_tag>
> <xsp:attribute name="foo">bar</xsp:attribute>
> <esql:connection>
> <esql:row-results>
> <xsp:attribute name="name">
> <esql:get-string column="description"/>
> </xsp:attribute>
> </esql:row-results>
> </esql:connection>
> <esql:connection>
> <esql:row-results>
> <my_nested_tag>
> ...
> </esql:row-results>
> </esql:connection>
> </my_root_tag>
> </xsp:page>
> Unfortunately, the output looks like:
> <my_root_tag foo="bar">
> <my_nested_tag name="some_description" />
> <my_nested_tag />
> ...etc...
> So the name attribute is being assigned to the first nested tag
> _after_ the xsp:attribute invocation.
> Because I'm adding attributes to my root tag, I can't use
> <xsp:element> to declare it.
> This worked fine with AxKit, so either the XSP spec isn't nailed
> down, or there's a bug with Cocoon, or I'm just showing my
> ignorance again.
> Software:
> Cocoon 2.0.4
> Tomcat 4.1.18
> Java 1.4.1 (beta)
--
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
