Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (nike.apache.org: domain of joerg.heinicke@gmx.de
 designates 213.165.64.20 as permitted sender)
Message-ID: <4772AE12.2080701@gmx.de>
Date: Wed, 26 Dec 2007 20:40:02 +0100
From: Joerg Heinicke <joerg.heinicke@gmx.de>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US;
 rv:1.8.1.11) Gecko/20071128 SeaMonkey/1.1.7
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: svn commit: r597535 - in
 /cocoon/trunk/blocks/cocoon-forms/cocoon-forms-impl/src:
 main/java/org/apache/cocoon/forms/datatype/FlowJXPathSelectionList.java
 test/java/org/apache/cocoon/forms/datatype/FlowJXPathSelectionListTestCase.java
References: <20071123034959.E83151A983A@eris.apache.org>
 <47464EF1.7030208@gmx.de> <4772A6DC.6020104@tuffmail.com>
In-Reply-To: <4772A6DC.6020104@tuffmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 26.12.2007 20:09 Uhr, Grzegorz Kossakowski wrote:

>>> URL: http://svn.apache.org/viewvc?rev=597535&view=rev
>>> Log:
>>> Fix FlowJXPathSelectionList test-case in a different way:
>>> Since it was the test case that's broken, not our code, fix the issue
>>> in the test case.
>>>
>>> Modified:
>>>    
>>> cocoon/trunk/blocks/cocoon-forms/cocoon-forms-impl/src/main/java/org/apache/cocoon/forms/datatype/FlowJXPathSelectionList.java
>>> cocoon/trunk/blocks/cocoon-forms/cocoon-forms-impl/src/test/java/org/apache/cocoon/forms/datatype/FlowJXPathSelectionListTestCase.java
>>>
>>> +        // FIXME: Why is the namespace declaration available as
>>> attribute on the expected document?
>>> +        //        That's the reason why we have to add it to
>>> destDocument as well.
>>> +        destDocument.getDocumentElement().setAttribute("xmlns:" +
>>> FormsConstants.INSTANCE_PREFIX, FormsConstants.INSTANCE_NS);
>> Does anybody have an idea why the namespace declaration is available as
>> attribute on the expected document only after springifing CForms? Is it
>> a classpath issue with an old or inappropriate parser version?
> 
> I was hit another time by this issue. Are there any news on this? Or do you have any clue what may
> have caused the change of how documents are parsed and why it seems to be only a problem for test cases?

I can imagine two possible reasons:
1. Different class path settings so that a different parser library is 
used, maybe endorsed libs stuff.
2. Options on the DocumentBuilderFactory or the SAXParserFactory.

Joerg