cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Lundquist (JIRA)" <>
Subject [jira] Commented: (COCOON-1725) Unexpected attempt to read values of JavaBean while saving form
Date Mon, 26 Dec 2005 21:17:32 GMT
    [ ] 

Mark Lundquist commented on COCOON-1725:

But it's not just for debugging... the current and previous values are compared to decide
whether a model update is required.  So you would have to come up with some other way to make
that determination... either that, or say that @direction="save" entails unconditional updates.
 I don't know enough to say whether that would be feasible...?

> Unexpected attempt to read values of JavaBean while saving form
> ---------------------------------------------------------------
>          Key: COCOON-1725
>          URL:
>      Project: Cocoon
>         Type: Bug
>   Components: Blocks: Forms
>     Versions: 2.1.8
>     Reporter: g[R]eK
>     Priority: Minor

> Problem lays in org.apache.cocoon.forms.binding.ValueJXPathBinding.doSave at line 123:
>         Object oldValue = jxpc.getValue(this.xpath); //line 123
>         if (getLogger().isDebugEnabled()) {
>             getLogger().debug("value= " + value + "-- oldvalue=" + oldValue);
>         }
> This is for debugging purpose and it's quite handy but if there is no get method in bean
exception org.apache.commons.jxpath.JXPathException: No read method will be thrown and binding
will be interrupted. It will try to read value even @direction="save" is set.
> I think it is not valid to require read method while it is excplicitly stressed the direction
of binding.

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