You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Jean-Baptiste Quenot (JIRA)" <ji...@apache.org> on 2006/02/06 12:37:09 UTC
[jira] Closed: (COCOON-1238) Improvements for CustomJXPathBinding
[ http://issues.apache.org/jira/browse/COCOON-1238?page=all ]
Jean-Baptiste Quenot closed COCOON-1238:
----------------------------------------
Fix Version: 2.2-dev (Current SVN)
2.1.9-dev (current SVN)
Resolution: Fixed
Committed, thanks!
See http://svn.apache.org/viewcvs.cgi?view=rev&rev=375253
> 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
> Fix For: 2.2-dev (Current SVN), 2.1.9-dev (current SVN)
> 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