You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by "Scott F. Walter" <sc...@vivare.com> on 2005/07/18 19:55:18 UTC

T4: Table Issues

Everyone.

I am having some issues with using contrib:TableView components with 
beta 2 and was wondering if anyone has noticed these?

These issues are only visible if you are using the 4.0 DTD.  I have 
defined a contrib:TableView component in a page as:

    <component id="tableView" type="contrib:TableView">
        <binding name="source" value="ognl:autoApprovalRules"/>
        <binding name="columns">
            name
        </binding>
        <binding name="pageSize" value="ognl:10"/>
        <binding  name="initialSortColumn" value="name"/>               
        <binding  name="initialSortOrder" value="false"/>               
    </component>

1.  I get an ognl.NoSuchPropertyException for the "column" binding 
unless I prefix my columns with a display name and a colon.  The above 
"column" binding fails, to get it to work I had to do something like this:

        <binding name="columns">
            My Name:name
        </binding>

2.  If I setup the "column" binding as I did in #1 and I have a page 
message space, the value from the properties file is never rendered, it 
always uses the display name that is hard coded into the "column" binding.

3.  I get an ognl.NoSuchPropertyException for the "initialSortColumn" 
binding unless I prefix my column with a display name and a colon.  The 
above "column" binding fails, to get it to work I had to do something 
like this:

<binding  name="initialSortColumn" value="mickey mouse:name"/>

You will notice the value before the colon, doesn't even match what I 
have for item #1.

4.  Inital sorting does not work, even if I have the same value before 
the colon for "columns" and "initialSortColumn" bindings.  Its probably 
related to #3.

Before I report these as bugs, I just wanted to get your input.

thank, scott.


-- 

Scott F. Walter 	Scott F. Walter
Principal Consultant
Vivare, Inc.

E: scott.walter@vivare.com
E: scott@scottwalter.com
Visit scottwalter.com <http://scottwalter.com> --Point.  Click.  Explore!




---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


Re: Table Issues

Posted by Mind Bridge <mi...@yahoo.com>.
Hi,

In beta2 I have set up the default bindings for Table, but I have not set
them up for TableView. As a result, everything you type in there is taken as
OGNL. Try to replace the columns binding with:

         <binding name="columns">
             'name'
         </binding>

or with:

         <binding name="columns">
             literal:name
         </binding>

and I believe that would fix a number of issues.


Similarly,

    <binding  name="initialSortColumn" value="name"/>

should become

    <binding  name="initialSortColumn" value="literal:name"/>


Please add a bug if you want. Table, FormTable, and TableView should have
exactly the same defaults.

-mb

----- Original Message ----- 
From: "Scott F. Walter" <sc...@vivare.com>
To: <ta...@jakarta.apache.org>
Sent: Monday, July 18, 2005 8:55 PM
Subject: T4: Table Issues


> Everyone.
>
> I am having some issues with using contrib:TableView components with
> beta 2 and was wondering if anyone has noticed these?
>
> These issues are only visible if you are using the 4.0 DTD.  I have
> defined a contrib:TableView component in a page as:
>
>     <component id="tableView" type="contrib:TableView">
>         <binding name="source" value="ognl:autoApprovalRules"/>
>         <binding name="columns">
>             name
>         </binding>
>         <binding name="pageSize" value="ognl:10"/>
>         <binding  name="initialSortColumn" value="name"/>
>         <binding  name="initialSortOrder" value="false"/>
>     </component>
>
> 1.  I get an ognl.NoSuchPropertyException for the "column" binding
> unless I prefix my columns with a display name and a colon.  The above
> "column" binding fails, to get it to work I had to do something like this:
>
>         <binding name="columns">
>             My Name:name
>         </binding>
>
> 2.  If I setup the "column" binding as I did in #1 and I have a page
> message space, the value from the properties file is never rendered, it
> always uses the display name that is hard coded into the "column" binding.
>
> 3.  I get an ognl.NoSuchPropertyException for the "initialSortColumn"
> binding unless I prefix my column with a display name and a colon.  The
> above "column" binding fails, to get it to work I had to do something
> like this:
>
> <binding  name="initialSortColumn" value="mickey mouse:name"/>
>
> You will notice the value before the colon, doesn't even match what I
> have for item #1.
>
> 4.  Inital sorting does not work, even if I have the same value before
> the colon for "columns" and "initialSortColumn" bindings.  Its probably
> related to #3.
>
> Before I report these as bugs, I just wanted to get your input.
>
> thank, scott.
>
>
> -- 
>
> Scott F. Walter Scott F. Walter
> Principal Consultant
> Vivare, Inc.
>
> E: scott.walter@vivare.com
> E: scott@scottwalter.com
> Visit scottwalter.com <http://scottwalter.com> --Point.  Click.  Explore!
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org