[ 
https://issues.apache.org/jira/browse/COCOON-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555463#action_12555463
 ] 

Jörg Heinicke commented on COCOON-2155:
---------------------------------------

> I'm don't like these superfluous declarations either but my opinion is that 
> test-cases should always reflect in every detail behaviour of components they 
> test.
> Current behaviour of tested components is to leave superfluous namespace 
> declarations and this must be reflected in tests.

My point was that it is no error if the component's behavior changes in this 
regard. But I really don't have a strong opinion on this and I am absolutely ok 
with the way you did it.

> Failing test cases due to additional attributes from namespace declarations 
> in a DOM from parser, but not from serializer
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: COCOON-2155
>                 URL: https://issues.apache.org/jira/browse/COCOON-2155
>             Project: Cocoon
>          Issue Type: Bug
>          Components: * Cocoon Core
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Grzegorz Kossakowski
>         Attachments: COCOON-2155-cocoon-core.patch, 
> COCOON-2155-cocoon-forms-impl.patch, COCOON-2155-cocoon-template-impl.patch, 
> COCOON-2155-parent-pom.patch
>
>
> Quoting Joerg:
> "Just an explanation: A namespace declaration is not an attribute (even 
> if it looks so) and that's why it should not end as such. The DOM 
> produced by Cocoon is absolutely correct, the one by parsing expected 
> document in the test case is not since it has both the namespace 
> declaration AND an attribute xmlns:fi - which broke our test."
> (http://article.gmane.org/gmane.text.xml.cocoon.devel/75975)
> Also see this: http://article.gmane.org/gmane.text.xml.cocoon.devel/75974

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to