tapestry-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "D&J Gredler" <djgred...@gmail.com>
Subject Re: I'm trying to get the marvelous BeanForm component working with tap 4.1
Date Sun, 03 Sep 2006 13:31:02 GMT
You didn't feel bad for breaking my BeanForm?!? Shame on you! ;-)

On 9/3/06, Jesse Kuhnert <jkuhnert@gmail.com> wrote:
>
> Horrible weekend so far...I've spent it working on anything but what I
> want.
> (which is tapestry obviously)..First client project, then fixing old
> wounds
> in maven2...Then happily upgraded to edgy eft (sweet!) .
>
> I think Daniel mentioned I broke his beanform at some point, but I don't
> remember how I did it...I do remember not feeling very bad about it after
> finding out why but that's as much of the details as I remember. I assumed
> it was working again when I didn't hear anything back from him.
>
> On 9/3/06, Josh Long <starbuxman@gmail.com> wrote:
> >
> > Hello all,
> >
> > I'm trying to get the marvelous tapestry 4.1 component working with
> > tapestry 4.1.
> >
> > It seems to sucessfully create the form, but when I submit the form it
> > errors out, saying:
> >
> > ...
> >
> > [ +/- ] Exception: Unable to read OGNL expression '<parsed OGNL
> > expression>' of $BeanFormRows_727@15d1298[search/Test/$BeanForm.rows]:
> > properties
> > org.apache.tapestry.BindingException
> > Unable to read OGNL expression '<parsed OGNL expression>' of
> > $BeanFormRows_727@15d1298[search/Test/$BeanForm.rows]: properties
> > binding:        ExpressionBinding[search/Test/$BeanForm.rows properties]
> > location:       classpath:/net/sf/beanform/BeanFormRows.jwc, line 33,
> > column 52
> > 28      </description>
> > 29
> > 30      <parameter name="element" default-value="literal:tr"/>
> > 31
> > 32      <component id="rows" type="For">
> > 33      <binding name="source" value="properties"/>
> > 34      <binding name="value" value="property"/>
> > 35      <binding name="index" value="index"/>
> > 36      </component>
> > 37
> > 38      <component id="informal" type="Any"
> > inherit-informal-parameters="yes">
> >
> > :: ahem:: anyway, before I attempt to get in there and figure this out
> > myself, has anyone cleared this path yet? Is there a reasonable/simple
> > update that just needs to be applied or, is it possible tapestry has
> > so changed from 4.0 (on which the samples are based) to 4.1 that the
> > component could have broke?
> >
> > Thanks in advance for any help, and i hope your weekend is going well.
> >
> > Josh
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo/(and a dash of TestNG), team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message