cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Heinicke (JIRA) <j...@apache.org>
Subject [jira] Closed: (COCOON-1813) <fb:identity> doesn't work with nested repeaters
Date Sat, 06 Jan 2007 21:11:27 GMT

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

Jörg Heinicke closed COCOON-1813.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.10

Assuming it's fixed. Please reopen if that's not the case. A test case would be helpful then
:) Thanks.

> <fb:identity> doesn't work with nested repeaters
> ------------------------------------------------
>
>                 Key: COCOON-1813
>                 URL: https://issues.apache.org/jira/browse/COCOON-1813
>             Project: Cocoon
>          Issue Type: Bug
>          Components: Blocks: Forms
>    Affects Versions: 2.1.8
>            Reporter: Eric Meyer
>             Fix For: 2.1.10
>
>
> I have a repeater where each row contains a different repeater (concretely a repeater
of "tabs" where each row contains a repeater of "modules"). I used the tasktree example (http://cocoon.zones.apache.org/demos/21branch/samples/blocks/forms/do-taskTree.flow)
for a sample structure to get me started.
> I can see that the fb:identity bindings for both the outer and inner repeaters are being
loaded successfully. However reordering inner or outer repeater elements does not result in
any of the collection items being reordered in the underlying object model.
> If i remove my fb:identity bindings, then new objects are successfully created each time
the form is saved (and the old ones are discarded). This is not ideal, as the objects are
persistent (mapped using Hibernate). I have a work-around, but it's not pretty.
> The use of repeaters inside repeaters is pretty rare, so I think I just stumbled into
a dusty corner. I'd be happy to collaborate on a fix.
> Regards,
> Eric

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message