Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <1083954454.1138207089998.JavaMail.jira@ajax.apache.org>
Date: Wed, 25 Jan 2006 17:38:09 +0100 (CET)
From: "Jean-Baptiste Quenot (JIRA)" <jira@apache.org>
To: dev@cocoon.apache.org
Subject: [jira] Commented: (COCOON-1609) form binding  ambiguity creating
 new paths
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

    [ http://issues.apache.org/jira/browse/COCOON-1609?page=3Dcomments#acti=
on_12363974 ]=20

Jean-Baptiste Quenot commented on COCOON-1609:
----------------------------------------------

You say: =C2=AB The ValueJXPathBinding class calls createPathAndSetValue() =
while others expect that the given path does already exist calling getRelat=
iveContext() directly. =C2=BB

This is a bug, and should be fixed.  Could you provide a patch for that?

> form binding  ambiguity creating new paths
> ------------------------------------------
>
>          Key: COCOON-1609
>          URL: http://issues.apache.org/jira/browse/COCOON-1609
>      Project: Cocoon
>         Type: Bug
>   Components: Blocks: Forms
>     Versions: 2.2-dev (Current SVN)
>  Environment: Operating System: other
> Platform: Other
>     Reporter: Stefan Podkowinski
>     Assignee: Jean-Baptiste Quenot

>
> The current way cform binding is handled is a bit confusing regarding the
> creation of new (jx)path elements.
> While fb:value works (to me) as expected, other bindings behave quite dif=
ferent.
> E.g. the following binding would create the given path if non-existing.=
=20
> <fb:value id=3D"form.test" path=3D"/test/hello" />
> Others, such as fb:set-attribute or fb:custom would not and throw an exce=
ption
> given the path above. This must be due the fact that the doSave() method =
of each
> binding class is implemented differently. The ValueJXPathBinding class ca=
lls
> createPathAndSetValue() while others expect that the given path does alre=
ady
> exist calling getRelativeContext() directly. This behaviour is especially
> annoying for fb:custom bindings in my case.
> See also:
> http://issues.apache.org/bugzilla/show_bug.cgi?id=3D30693
> http://www.mail-archive.com/dev@cocoon.apache.org/msg20645.html
> fb:custom exception:
> org.apache.commons.jxpath.JXPathException: Cannot create a relative conte=
xt for
> a non-existent node: /form/test
> =09at
> org.apache.commons.jxpath.ri.JXPathContextReferenceImpl.getRelativeContex=
t(JXPathContextReferenceImpl.java:581)
> =09at
> org.apache.cocoon.forms.binding.CustomJXPathBinding.doSave(CustomJXPathBi=
nding.java:83)
> =09at
> org.apache.cocoon.forms.binding.JXPathBindingBase.saveFormToModel(JXPathB=
indingBase.java:192)

--=20
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