[jira] Commented: (COCOON-1794) [PATCH] Propagation of namespaces to a repeaters child bindings and implementation of a move-node binding

[ https://issues.apache.org/jira/browse/COCOON-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598943#action_12598943 ] Suzan Foster commented on COCOON-1794: -- Yes, I believe that is correct. Along with co

[jira] Commented: (COCOON-1692) [PATCH] Tree widget not handling on-selection-change events correctly.

[ http://issues.apache.org/jira/browse/COCOON-1692?page=comments#action_12441162 ] Suzan Foster commented on COCOON-1692: -- Yes, correct. > [PATCH] Tree widget not handling on-selection-change events correctly. > ---

[jira] Commented: (COCOON-1794) [PATCH] Propagation of namespaces to a repeaters child bindings and implementation of a move-node binding

[ http://issues.apache.org/jira/browse/COCOON-1794?page=comments#action_12369623 ] Suzan Foster commented on COCOON-1794: -- OK, i think i can see where the miscommunication is here. I take it you mean that if i do not use an identity binding in my repe

[jira] Commented: (COCOON-1794) [PATCH] Propagation of namespaces to a repeaters child bindings and implementation of a move-node binding

[ http://issues.apache.org/jira/browse/COCOON-1794?page=comments#action_12369500 ] Suzan Foster commented on COCOON-1794: -- In which release has this been fixed. I have checked with 2.1.8 and it does not change the order of the nodes and subsequently s

[jira] Commented: (COCOON-1794) [PATCH] Propagation of namespaces to a repeaters child bindings and implementation of a move-node binding

[ http://issues.apache.org/jira/browse/COCOON-1794?page=comments#action_12369450 ] Suzan Foster commented on COCOON-1794: -- The MoveNodeJXPathBinding doesn't move all rows up to the top of their enclosing element. It first checks if the current node is

[jira] Commented: (COCOON-1794) [PATCH] Propagation of namespaces to a repeaters child bindings and implementation of a move-node binding

[ http://issues.apache.org/jira/browse/COCOON-1794?page=comments#action_12369449 ] Suzan Foster commented on COCOON-1794: -- pre-condition: ... ... ... ... ... ... after load: row index (1) identity (a_ab) row

[jira] Commented: (COCOON-1794) [PATCH] Propagation of namespaces to a repeaters child bindings and implementation of a move-node binding

[ http://issues.apache.org/jira/browse/COCOON-1794?page=comments#action_12369438 ] Suzan Foster commented on COCOON-1794: -- In my own case an InsertAfterNodeJXPathBinding isn't sufficient as i need to have positioning capability without the insertion c

[jira] Commented: (COCOON-1794) [PATCH] Propagation of namespaces to a repeaters child bindings and implementation of a move-node binding

[ http://issues.apache.org/jira/browse/COCOON-1794?page=comments#action_12369437 ] Suzan Foster commented on COCOON-1794: -- I see your point regarding the mixed nodes. Couldn't you solve this by using a javascript binding to implement the positioning?

[jira] Commented: (COCOON-1794) [PATCH] Propagation of namespaces to a repeaters child bindings and implementation of a move-node binding

[ http://issues.apache.org/jira/browse/COCOON-1794?page=comments#action_12369431 ] Suzan Foster commented on COCOON-1794: -- You can't do this in a single iteration. You don't know which nodes are marked for deletion untill you have done your first pass

[jira] Commented: (COCOON-1794) [PATCH] Propagation of namespaces to a repeaters child bindings and implementation of a move-node binding

[ http://issues.apache.org/jira/browse/COCOON-1794?page=comments#action_12369295 ] Suzan Foster commented on COCOON-1794: -- I don't think the InsertNodeJXPathBinding is the correct place to implement positioning. Positioning doesn't imply insertion as

[jira] Created: (COCOON-1794) [PATCH] Propagation of namespaces to a repeaters child bindings and implementation of a move-node binding

[PATCH] Propagation of namespaces to a repeaters child bindings and implementation of a move-node binding - Key: COCOON-1794 URL: http://issues.apache.org/jira/browse/COCOON-1

[jira] Created: (COCOON-1692) [PATCH] Tree widget not handling on-selection-change events correctly.

[PATCH] Tree widget not handling on-selection-change events correctly. -- Key: COCOON-1692 URL: http://issues.apache.org/jira/browse/COCOON-1692 Project: Cocoon Type: Bug Components: Blocks: Forms

[jira] Commented: (COCOON-1686) [PATCH] COCOON-1671 Form not binding when prefix in binding definition is unequal to that in the instance data for the same namespace.

[ http://issues.apache.org/jira/browse/COCOON-1686?page=comments#action_12358152 ] Suzan Foster commented on COCOON-1686: -- The JXPathContext's derived from the parent-path attribute on the multi-value and repeater bindings are used without applying JX

[jira] Commented: (COCOON-1686) [PATCH] COCOON-1671 Form not binding when prefix in binding definition is unequal to that in the instance data for the same namespace.

[ http://issues.apache.org/jira/browse/COCOON-1686?page=comments#action_12358145 ] Suzan Foster commented on COCOON-1686: -- The patch only partially solves the bug entry COCOON-1671. It is still not binding to the multi-value with id 'drinks', or to th

[jira] Updated: (COCOON-1671) Form not binding when prefix in binding definition is unequal to that in the instance data for the same namespace.

[ http://issues.apache.org/jira/browse/COCOON-1671?page=all ] Suzan Foster updated COCOON-1671: - Attachment: JXPathTest.java Test code to verify that JXPath can handle this issue correctly. Tested with commons-jxpath 1.2. > Form not binding when prefix

[jira] Updated: (COCOON-1671) Form not binding when prefix in binding definition is unequal to that in the instance data for the same namespace.

[ http://issues.apache.org/jira/browse/COCOON-1671?page=all ] Suzan Foster updated COCOON-1671: - Attachment: form2_bind_xml2.xml Forms binding using xmlns:foo="http://example.com/bar/";, binds successfully whilst it shouldn't. > Form not binding when p

[jira] Created: (COCOON-1671) Form not binding when prefix in binding definition is unequal to that in the instance data for the same namespace.

Form not binding when prefix in binding definition is unequal to that in the instance data for the same namespace. -- Key: COCOON-1671 URL: http://issues.apache.org/ji

[jira] Updated: (COCOON-1671) Form not binding when prefix in binding definition is unequal to that in the instance data for the same namespace.

[ http://issues.apache.org/jira/browse/COCOON-1671?page=all ] Suzan Foster updated COCOON-1671: - Attachment: form2_bind_xml1.xml Forms binding using xmlns:foo="http://example.com/foo/";. Binding succeeds. > Form not binding when prefix in binding defini

[jira] Updated: (COCOON-1671) Form not binding when prefix in binding definition is unequal to that in the instance data for the same namespace.

[ http://issues.apache.org/jira/browse/COCOON-1671?page=all ] Suzan Foster updated COCOON-1671: - Attachment: form2_bind_xml3.xml Form binding with xmlns:bar="http://example.com/foo/";, fails whilst it should be successful. > Form not binding when prefi

[jira] Updated: (COCOON-1671) Form not binding when prefix in binding definition is unequal to that in the instance data for the same namespace.

[ http://issues.apache.org/jira/browse/COCOON-1671?page=all ] Suzan Foster updated COCOON-1671: - Attachment: form2_data.xml Instance data for the xml binding example namespaced with xmlns:foo="http://example.com/foo/";. > Form not binding when prefix i

[jira] Commented: (COCOON-1671) Form not binding when prefix in binding definition is unequal to that in the instance data for the same namespace.

[ http://issues.apache.org/jira/browse/COCOON-1671?page=comments#action_12356409 ] Suzan Foster commented on COCOON-1671: -- The problem is being caused by org.apache.cocoon.forms.util.DomHelper. In DomHelper.addLocalNSDeclarations() expects elm.getAttr