You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cocoon.apache.org by bu...@apache.org on 2004/08/16 12:33:46 UTC

DO NOT REPLY [Bug 30693] New: - Improvements for CustomJXPathBinding

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30693>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30693

Improvements for CustomJXPathBinding

           Summary: Improvements for CustomJXPathBinding
           Product: Cocoon 2
           Version: 2.1.5
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: CocoonForms
        AssignedTo: dev@cocoon.apache.org
        ReportedBy: b.molenkamp@bizzdesign.nl


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.