Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (herse.apache.org: domain of hepabolu@gmail.com designates
 66.249.92.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:reply-to:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=kywjzDLT88n+t/D3wSducLTna6dc2vQll701qGli+P7z8a2uGTRxF1OcQH73+efG7iRvPsEdR1qDie8RHwjayOc+E2x3+RrJEahZ4r8UyYPuNyxkw8K+SSBvixXoBnnnYMJqZCA/lg62l2e4bNN/juBn86/Fm6WT8pjX+BEGk1I=
Message-ID: <465592ED.1070209@gmail.com>
Date: Thu, 24 May 2007 15:28:13 +0200
From: hepabolu <hepabolu@gmail.com>
Reply-To: hepabolu@gmail.com
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: CForms binding with namespaces error - advice wanted
References: <4653073A.1020300@mi.unimaas.nl> <46535023.1050507@gmx.de>
 <46540208.1030209@gmail.com> <465410CC.6020605@apache.org>
 <465416ED.3040904@outerthought.org> <4654208B.3060403@gmail.com>
 <465481F2.7070508@gmx.de> <465495D5.10706@gmail.com>
 <4654997A.4090002@apache.org> <46553ECD.3010203@outerthought.org>
 <46555613.6090503@apache.org> <465584C8.7020307@outerthought.org>
In-Reply-To: <465584C8.7020307@outerthought.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

>> So you can't rely that you get the namespace attributes in the dom 
>> builder.

I think this is where things go wrong.

Note that both binding file and source are generated with a pipeline and 
pipelineUtil.toDOM.

I've done some debugging into pipelineUtil.toDOM and this is what I found:
- binding file has all the namespaces in pipeline. This is confirmed 
because I can save the output of the pipeline and see the namespaces in 
the root element:

<fb:context xmlns:fb="http://apache.org/cocoon/forms/1.0#binding" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:fd="http://apache.org/cocoon/forms/1.0#definition" 
xmlns:oe="openEHR/v1/Version" path="/oe:version">

- After returning from SourceUtil.toDOM (which uses the default 
DOMBuilder()), the only namespace left is 
fb="http://apache.org/cocoon/forms/1.0#binding".
Attributes of this node only holds 'path=/oe:version'.

- This is true for the source=pipeline situation as well: only the 
oe="openEHR/v1/Version" is left.

- The source=file situation has all namespaces in the attributes.

I can understand that in the situation of source=pipeline there cannot 
be any matching because the oe namespace is not known in the binding 
file. However, this is also true for the situation of source=file and 
there matching happens on various fb:context until it fails on a 
difference in datatype.

What I also don't understand is the fact that putting the 
source=pipeline through the savedocument function as I did this morning, 
gives me all the namespaces back.

I'm not sure if this helps in the discussion and I have no clue on how 
to solve this.

Anyone?

Bye, Helma