RE: I'm trying to get the marvelous BeanForm component working with tap 4.1
Switch to Gentoo and have a current system. :-). -Original Message- From: Josh Long [mailto:[EMAIL PROTECTED] Sent: Sun 9/3/2006 1:44 AM To: Tapestry users Subject: Re: I'm trying to get the marvelous BeanForm component working with tap 4.1 ROFL! that's the best response ever!! I'm sorry about your awkward weekend though! So you get to upgrade linux and I'm stuck on SuSe 9.2 or 3. Seems like everyones updating without me. But I will not be jealous. It doesn't suit me. I finally uninstalled Red Hat 9 at best a year ago.. thought that was progress. OK, so I'm jealous. My coworker switched from kde to gnome of late and they've got some twisted OS X expose-style effects built in, now... I have alt+tab. OK, anyway, I will follow up with (the simialarly sainted, generous, and benevolent) Daniel and hopefully we'll resolve this. It'll be fun. I'll have ajax-ready, one-liner forms. I could provide a full-page editable form for an object with 20 properties using nothing more than div jwcid=mPojo / that works with ajax and validation if I get this working in 4.1! I can just imagine the hair that'll fall out when the web designer sees it.. Imagine it...! Thanks again, Josh On 9/3/06, Jesse Kuhnert [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED]/Test/$BeanForm.rows]: properties org.apache.tapestry.BindingException Unable to read OGNL expression 'parsed OGNL expression' of [EMAIL PROTECTED]/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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: I'm trying to get the marvelous BeanForm component working with tap 4.1
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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED]/Test/$BeanForm.rows]: properties org.apache.tapestry.BindingException Unable to read OGNL expression 'parsed OGNL expression' of [EMAIL PROTECTED]/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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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
Re: I'm trying to get the marvelous BeanForm component working with tap 4.1
ROFL! that's the best response ever!! I'm sorry about your awkward weekend though! So you get to upgrade linux and I'm stuck on SuSe 9.2 or 3. Seems like everyones updating without me. But I will not be jealous. It doesn't suit me. I finally uninstalled Red Hat 9 at best a year ago.. thought that was progress. OK, so I'm jealous. My coworker switched from kde to gnome of late and they've got some twisted OS X expose-style effects built in, now... I have alt+tab. OK, anyway, I will follow up with (the simialarly sainted, generous, and benevolent) Daniel and hopefully we'll resolve this. It'll be fun. I'll have ajax-ready, one-liner forms. I could provide a full-page editable form for an object with 20 properties using nothing more than div jwcid=mPojo / that works with ajax and validation if I get this working in 4.1! I can just imagine the hair that'll fall out when the web designer sees it.. Imagine it...! Thanks again, Josh On 9/3/06, Jesse Kuhnert [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED]/Test/$BeanForm.rows]: properties org.apache.tapestry.BindingException Unable to read OGNL expression 'parsed OGNL expression' of [EMAIL PROTECTED]/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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: I'm trying to get the marvelous BeanForm component working with tap 4.1
Ow.. that was a depressing run at nabble. Gotta stop nabbl'ing after midnight. Nothing good comes of it.. So it was an ognl issue, eh? http://www.nabble.com/BeanForm-Move-tf1921926.html#a5262830 I'm not scared of ognl... much... Josh On 9/3/06, Josh Long [EMAIL PROTECTED] wrote: ROFL! that's the best response ever!! I'm sorry about your awkward weekend though! So you get to upgrade linux and I'm stuck on SuSe 9.2 or 3. Seems like everyones updating without me. But I will not be jealous. It doesn't suit me. I finally uninstalled Red Hat 9 at best a year ago.. thought that was progress. OK, so I'm jealous. My coworker switched from kde to gnome of late and they've got some twisted OS X expose-style effects built in, now... I have alt+tab. OK, anyway, I will follow up with (the simialarly sainted, generous, and benevolent) Daniel and hopefully we'll resolve this. It'll be fun. I'll have ajax-ready, one-liner forms. I could provide a full-page editable form for an object with 20 properties using nothing more than div jwcid=mPojo / that works with ajax and validation if I get this working in 4.1! I can just imagine the hair that'll fall out when the web designer sees it.. Imagine it...! Thanks again, Josh On 9/3/06, Jesse Kuhnert [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED]/Test/$BeanForm.rows]: properties org.apache.tapestry.BindingException Unable to read OGNL expression 'parsed OGNL expression' of [EMAIL PROTECTED]/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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: I'm trying to get the marvelous BeanForm component working with tap 4.1
You didn't feel bad for breaking my BeanForm?!? Shame on you! ;-) On 9/3/06, Jesse Kuhnert [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED]/Test/$BeanForm.rows]: properties org.apache.tapestry.BindingException Unable to read OGNL expression 'parsed OGNL expression' of [EMAIL PROTECTED]/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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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
Re: I'm trying to get the marvelous BeanForm component working with tap 4.1
Hehe...I have to admit - as much as I love programming with the exceptionally good Qt toolkit - I like using the gnome desktop much more than KDE :) On 9/3/06, Josh Long [EMAIL PROTECTED] wrote: ROFL! that's the best response ever!! I'm sorry about your awkward weekend though! So you get to upgrade linux and I'm stuck on SuSe 9.2 or 3. Seems like everyones updating without me. But I will not be jealous. It doesn't suit me. I finally uninstalled Red Hat 9 at best a year ago.. thought that was progress. OK, so I'm jealous. My coworker switched from kde to gnome of late and they've got some twisted OS X expose-style effects built in, now... I have alt+tab. OK, anyway, I will follow up with (the simialarly sainted, generous, and benevolent) Daniel and hopefully we'll resolve this. It'll be fun. I'll have ajax-ready, one-liner forms. I could provide a full-page editable form for an object with 20 properties using nothing more than div jwcid=mPojo / that works with ajax and validation if I get this working in 4.1! I can just imagine the hair that'll fall out when the web designer sees it.. Imagine it...! Thanks again, Josh On 9/3/06, Jesse Kuhnert [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED]/Test/$BeanForm.rows]: properties org.apache.tapestry.BindingException Unable to read OGNL expression 'parsed OGNL expression' of [EMAIL PROTECTED]/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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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
Re: I'm trying to get the marvelous BeanForm component working with tap 4.1
Good deal.
I've seen a couple of garden gnome ads on gmail when I've been viewing
emails on this list about trolling and trolls :-)
On 9/4/06, Josh Long [EMAIL PROTECTED] wrote:
It worked like a charm, Daniel!
I would have responded earlier but I was too busy playing with my
shiny new component..
The code below is magic, nothing less. It works with ajax, exposes all
the properties to edit that I want, has validation, and supports all
the intrinsically tapestry 4.1 features like the updateComponents
param. Very, very cool. Now, to start offering to build more
update/edit pages!
In related news: google ads isn't completely sure what we're smoking,
so it's offering me 'Garden Gnomes and more' on the right of my gmail
window... right on top of Free Red Hat 9.0 offers...
Thanks again one and all!
Josh
div jwcid=@Border
form jwcid=@Form async= ognl:true updateComponents =
ognl:{'bform'}
delegate=bean:delegate clientValidationEnabled=ognl: false
div jwcid=[EMAIL PROTECTED]
div jwcid=@bf:BeanForm
properties =
literal:firstName{required},lastName{required},company{required},dateCreated{required}
bean = ognl: restaurant save=listener:save /
/div
/form
/div
On 9/3/06, Jesse Kuhnert [EMAIL PROTECTED] wrote:
Hehe...I have to admit - as much as I love programming with the
exceptionally good Qt toolkit - I like using the gnome desktop much more
than KDE :)
On 9/3/06, Josh Long [EMAIL PROTECTED] wrote:
ROFL! that's the best response ever!!
I'm sorry about your awkward weekend though!
So you get to upgrade linux and I'm stuck on SuSe 9.2 or 3. Seems like
everyones updating without me. But I will not be jealous. It doesn't
suit me. I finally uninstalled Red Hat 9 at best a year ago.. thought
that was progress. OK, so I'm jealous. My coworker switched from kde
to gnome of late and they've got some twisted OS X expose-style
effects built in, now... I have alt+tab.
OK, anyway, I will follow up with (the simialarly sainted, generous,
and benevolent) Daniel and hopefully we'll resolve this. It'll be fun.
I'll have ajax-ready, one-liner forms. I could provide a full-page
editable form for an object with 20 properties using nothing more than
div jwcid=mPojo / that works with ajax and validation if I get
this working in 4.1! I can just imagine the hair that'll fall out when
the web designer sees it.. Imagine it...!
Thanks again,
Josh
On 9/3/06, Jesse Kuhnert [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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
[EMAIL PROTECTED]/Test/$BeanForm.rows]:
properties
org.apache.tapestry.BindingException
Unable to read OGNL expression 'parsed OGNL expression' of
[EMAIL PROTECTED]/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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Jesse Kuhnert
Tapestry/Dojo/(and a dash of TestNG), team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind.
