[ http://issues.apache.org/jira/browse/COCOON-1671?page=comments#action_12357724 ]
Michael Schlotfeldt commented on COCOON-1671: --------------------------------------------- I have not looked into this a lot. But it actually apears that the issue is that the namespaces are being registered on the JXPathContext against the instance data's namespace instead of the namespaces that are declared in the binding file. It should be defining the namespaces on the JXPathContext as defined in the binding file so that the paths you say to bind, use the prefixes defined in that file and not in the file you are binding too. As I said, I only looked quickly but that seems to be the issue. Should be really simple to fix if I'm correct. > 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/jira/browse/COCOON-1671 > Project: Cocoon > Type: Bug > Components: Blocks: Forms > Versions: 2.1.8-dev (Current SVN) > Reporter: Suzan Foster > Assignee: Cocoon Developers Team > Attachments: JXPathTest.java, form2_bind_xml1.xml, form2_bind_xml2.xml, > form2_bind_xml3.xml, form2_data.xml > > In the situation where the binding definition and the instance data share the > same namespace uri but have different namespace prefixes the binding will > fail. However, when the binding definition and the instance data share the > same namespace prefix but not the same namespace uri the binding will be > successful. This is incorrect as it shound match on the namespace uri's and > not on the prefixes. -- 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
