[ http://issues.apache.org/jira/browse/COCOON-1725?page=comments#action_12363580 ]
Grzegorz Kossakowski (aka g[R]eK) commented on COCOON-1725: ----------------------------------------------------------- Yes, it is still a problem. There is no suggested patch because I'm not sure what is preferred way of resolving this issue (see comments above). Some more experienced developers should take a look at this problem. > Unexpected attempt to read values of JavaBean while saving form > --------------------------------------------------------------- > > Key: COCOON-1725 > URL: http://issues.apache.org/jira/browse/COCOON-1725 > Project: Cocoon > Type: Bug > Components: Blocks: Forms > Versions: 2.1.8 > Reporter: Grzegorz Kossakowski (aka 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
