cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Portier <>
Subject Re: [CForms] Change proposal in Custom bindings
Date Mon, 06 Sep 2004 15:21:00 GMT
I had a quick scan through your problem and patches (and sorry for not 
doing that earlier)

AFAICS you would get the same effect by just ommitting the xpath from 
the binding and adding it as a nested config

ie not
   <fb:custom id="x" path="something"
              factorymethod="createBinding" />

but rather
   <fb:custom id="config"
              factorymethod="createBinding" >
       <fb:config propspath="some" />

that way the path="." will be assumed on the wrapper and the 
parent-context will be passed down so your custom binding can narrow 
down with the local config 'propspath' (potentially checking for null's 


if you need more control then this, I suggest skipping the 
custom-binding alltogether and go straight for the own builder and 
binding + declaring the builder in the xconf file. (you're not that far off)


above seems to indicate that what you need can be done already, pls 
comment if that is not the case


Bart Molenkamp wrote:
> Hi all,
> A few weeks ago I made a request for a small change in
> CustomJXPathBinding. It can be found here [1]. I already implemented the
> change, made a patch, and placed it in bugzilla [2]. But noone was gave
> me some response to this change (maybe due to vacations?) So I was
> wondering; are there people interested in this change, or do I need to
> maintain this change in the source tree of my project?
> Bart.
> [1]
> [2]

Marc Portier                  
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at                          

View raw message