[ http://issues.apache.org/jira/browse/COCOON-1238?page=comments#action_12364985 ]
Stefan Podkowinski commented on COCOON-1238: -------------------------------------------- Your latest version will work much better by leaving the decision to the custom binding impl how to handle paths. It will of course break backward compatibility though, because you pass an entirly different path to the binding impl, but I dont see any way around this. IMO its better to make the custom bindings actually useful instead of just keeping compatibility. > Improvements for CustomJXPathBinding > ------------------------------------ > > Key: COCOON-1238 > URL: http://issues.apache.org/jira/browse/COCOON-1238 > Project: Cocoon > Type: Improvement > Components: Blocks: Forms > Versions: 2.1.5 > Environment: Operating System: All > Platform: All > Reporter: Bart Molenkamp > Assignee: Jean-Baptiste Quenot > Priority: Minor > Attachments: 20060201-cocoon-forms-1238, AbstractCustomBinding.java.patch, > CustomJXPathBinding.java.patch, CustomJXPathBindingBuilder.java, > CustomJXPathBindingBuilder.java.patch > > 2 improvements: > 1. Custom bindings get a service manager when they implement Serviceable. > 2. Relative JXPath context is not created. Instead, the current context, and > the > xpath query are passed to the custom binding. This allows bindings to set > values > for objects that are null (whereas a getRelativeContext() will throw an > exception). Custom bindings now can do a > context.createPathAndSetValue(getXpath(), ...) to set a value that was null > before setting it. -- 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
