And I've already fixed it (in the 5.0.8 nightly snapshot).
On Jan 3, 2008 6:22 PM, Mark Horn <[EMAIL PROTECTED]> wrote:
> Thanks Howard. I have created the bug in JIRA it is
>
> https://issues.apache.org/jira/browse/TAPESTRY-2013
>
>
> On 1/3/08, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> > T
Thanks Howard. I have created the bug in JIRA it is
https://issues.apache.org/jira/browse/TAPESTRY-2013
On 1/3/08, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> That is strange, it should work as you have shown it. I know this
> behavior works ... there are unit tests to verify it.
>
> Ooops,
That is strange, it should work as you have shown it. I know this
behavior works ... there are unit tests to verify it.
Ooops, please file a bug. I see the problem; BeanEditForm supports
informal parameters, but BeanEditor does not!
On Jan 3, 2008 1:05 PM, Mark Horn <[EMAIL PROTECTED]> wrote:
>
Josh - thanks for the suggestion and link. Unfortunately the
still does not work.
I did find this listing that talks about the same issue
http://www.nabble.com/Can-we-use-Text-Area-for-String-field-in-BeanEditor--td13920248.html#a13920248
At the end Howard suggests the use of a new Annotation
I believe you need to add Cell to the end of your parameter name.
This question comes up a lot, so if that doesn't work you should be able to
find some examples by searching the list.
http://www.nabble.com/Tapestry---User-f340.html indexes this list for
searching.
Josh
On Jan 3, 2008 1:05 PM, Ma
I'm sorry if the answer for this is out there, but I have not been
able to find it. I'm trying to use a BeanEditor and defined a
TextArea for a property instead of the default TextField.
Here is a snip-it form my template file