cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc Portier (JIRA)" <>
Subject [jira] Commented: (COCOON-1687) [PATCH] JXPATHBinding : when saving the form, remove xml elements if the value of the widget is null
Date Thu, 10 Aug 2006 13:41:17 GMT
    [ ] 
Marc Portier commented on COCOON-1687:

Reverted this patch:

This patch was shipped with the 2.1.9 release of cocoon. 
Because of that, people on that version seeing unwanted removal of elements during bind-save
will need to resort to some sort of workaround.

A typical sample is to replace an ordinary

<fb:value id="whatever" path="whatever" />


<fb:value id="whatever" path="whatever" direction="load"/>
<fb:javascript id="whatever" path="whatever" direction="save">
      if (widget.getValue() != null)

> [PATCH] JXPATHBinding : when saving the form, remove xml elements if the value of the
widget is null
> ----------------------------------------------------------------------------------------------------
>                 Key: COCOON-1687
>                 URL:
>             Project: Cocoon
>          Issue Type: Bug
>          Components: Blocks: Forms
>    Affects Versions: 2.1.8, 2.2-dev (Current SVN), 2.1.7
>            Reporter: Philippe Gassmann
>         Attachments:
> When a form is saved using a JXPathBinding, the xml elements that correspond to null
widget values must be removed.
> Here is our problem : we have a form containing a "date widget" that is not mandatory,
> 1. the user wants to set a value to this widget ex 2005/05/09
> 2. the user save this form
> 3. the user does not want the date to be set anymore (why ? why not !)
> 4. the user edit the value removing its content (ie the value of the widget will be null)
> 5. the user save the form
> 6. when the user wants to view what's happened, he see : the element containing the value
of the date is present, if he loads the form again he found : 1970-01-01 in the date field
(the org.w3c.util.DateParser return this value if empty string its given).
> In general, it has no sense for kind of data (integer, float, date...) to have three
"state" : empty, null and filled with a value !
> So here is a patch to correct this : 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message