T5: select within table grid

[Axel Mannhardt]

Hi,

I am trying to show a table with a column with comboboxes, but the GridDataSource does not seem to accept a the value type for the generic select model necessary for the combobox.

The most promising stuff i tried is a table containing a column with Longs and one with the selected entry of the available entries for the combo box. The available entries for the combo box are the same for each row.

If I try to specify the combobox parameter directly (as PositionSelection), the "BeanModel does not contain that property". The using an indirect value (slotPosition-Cell) takes care of that, the encoder is meant to do the mapping, but then:

__
Processing of request failed with uncaught exception: Failure writing parameter value of component cms/pages/draft/configuration/Edit:selectedposition: org.apache.tapestry.ioc.internal.util.TapestryException

...

Caused by: org.apache.tapestry.ioc.internal.util.TapestryException [at classpath:com/freiheit/shopping24/extranet/cms/presentation/pages/pages/draft/configuration/EditConfiguration.html, line 55, column 25]
        at org.apache.tapestry.internal.bindings.PropBinding.set(PropBinding.java:71)
        at org.apache.tapestry.internal.structure.InternalComponentResourcesImpl.writeParameter(InternalComponentResourcesImpl.java:250)
        ... 88 more
Caused by: java.lang.NullPointerException
        at $PropertyConduit_119cce2381b.set($PropertyConduit_119cce2381b.java)
        at org.apache.tapestry.internal.bindings.PropBinding.set(PropBinding.java:67)

I have the feeling I am doing something the wrong way, it should not be so hard to nest these basic elements, is it?

Thanks,
Axel Mannhardt

___________________

                <form t:type="form" t:id="form" t:clientValidation="false">
           
                        <table t:type="grid"
                            t:id="SlotGrid"
                            t:source="sourceRows" <!-- of type : GridDataSource (ComponentConfigurationRowModel) -->
                            t:row="sourceRow"
                            t:model="rowModel">
                                       
                        <t:parameter name="slotPositionCell"> <!-- of type: Long -->
                            <select name="selectedPosition" id="selectedPosition"
                            t:type="select"
                            t:id="selectedPosition"
                            t:model="positionSelectModel" <!-- of type GenericSelectModel<PositionSelection> -->
                            t:value="component.selectedPosition"
                            t:encoder="positionSelectEncoder"
                                onchange="JavaScript:document.editSlotsForm.submit()"
                            />
                        </t:parameter>
<!-- ... -->

                        </table>
                </form>

___________________________


   
    private final ValueEncoder<PositionSelection> _encoder = new ValueEncoder<PositionSelection>() {
        public String toClient(PositionSelection arg0) {
            return new Long(0).toString();
        };
       
        public PositionSelection toValue(String arg0) {
            return _availableSlots.get(0);
        };
    };
   
    public ValueEncoder<PositionSelection> getPositionSelectEncoder() {
        return _encoder;
    }

//container for combo box values
    public class PositionSelection implements Labeled, Identifiable<Long> {
        final private String _text;
        final private Long _position;
       
        public PositionSelection(String text, Long position) {
            _text = text;
            _position = position;
        }
        public Long getId() {
            return _position;
        }
        public String getLabel() {
            return _text;
    }

//container for row values
    public class ComponentConfigurationRowModel{
        private Long _slotPosition;
        private PositionSelection _selectedPosition;
        public Long getSlotPosition() {
       //getter and setter omitted
    }

[kranga]

In looking at converting from T3 to T5, I've to deal with constructs such
as:

class="ognl:menuClassName('home')"  where getMenuClassName uses the
parameter to compare with the page's "id" passed in to determine if this is
the currentPage or not. So the template has multiple links with constructs
such as:

class="ognl:menuClassName('about')"
class="ognl:menuClassName('contact')" etc.

How do I do this in T5 given that prop bindings to methods cannot accept
arguments? I'm sure there is a workaround, I just can't seem to find one.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Robert Zeigler]

Fastest solution is the t5components module, which re-introduces the  
ognl binding:
http://87.193.218.134:8080/t5components/t5c-commons/howto_ognlbinding.html

Cheers,

Robert

On May 9, 2008, at 5/99:52 AM , kranga wrote:

> In looking at converting from T3 to T5, I've to deal with constructs  
> such as:
>
> class="ognl:menuClassName('home')"  where getMenuClassName uses the  
> parameter to compare with the page's "id" passed in to determine if  
> this is the currentPage or not. So the template has multiple links  
> with constructs such as:
>
> class="ognl:menuClassName('about')"
> class="ognl:menuClassName('contact')" etc.
>
> How do I do this in T5 given that prop bindings to methods cannot  
> accept arguments? I'm sure there is a workaround, I just can't seem  
> to find one.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jonathan Barker]

I missed that functionality as well.  I use the ognl binding available in
the t5components library.

http://87.193.218.134:8080/t5components/index.html


I remember trying something complicated once, and I had problems with values
being cached that should not have been, but it worked beautifully for the
menu problem.

> -----Original Message-----
> From: kranga [mailto:kranga@...]
> Sent: Friday, May 09, 2008 10:53 AM
> To: Tapestry users
> Subject: T5: Calling method with parameter in prop
>
> In looking at converting from T3 to T5, I've to deal with constructs such
> as:
>
> class="ognl:menuClassName('home')"  where getMenuClassName uses the
> parameter to compare with the page's "id" passed in to determine if this
> is
> the currentPage or not. So the template has multiple links with constructs
> such as:
>
> class="ognl:menuClassName('about')"
> class="ognl:menuClassName('contact')" etc.
>
> How do I do this in T5 given that prop bindings to methods cannot accept
> arguments? I'm sure there is a workaround, I just can't seem to find one.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Marcus Veloso]

Hi Axel.

Maybe this help,

"Adding Columns Example" at
http://tapestry.formos.com/nightly/tapestry5/tapestry-core/ref/org/apache/tapestry/corelib/components/Grid.html

Marcus

[Howard Lewis Ship]

In 5.1 I want to extend the Tapestry property expression language
quite a bit further to address this (invoking methods), as well as map
and array ceation ... basically, all the cool OGNL stuff people miss.

On Fri, May 9, 2008 at 7:52 AM, kranga <kranga@...> wrote:

> In looking at converting from T3 to T5, I've to deal with constructs such
> as:
>
> class="ognl:menuClassName('home')"  where getMenuClassName uses the
> parameter to compare with the page's "id" passed in to determine if this is
> the currentPage or not. So the template has multiple links with constructs
> such as:
>
> class="ognl:menuClassName('about')"
> class="ognl:menuClassName('contact')" etc.
>
> How do I do this in T5 given that prop bindings to methods cannot accept
> arguments? I'm sure there is a workaround, I just can't seem to find one.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

--
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Sven Homburg]

howard,

you make us jobless ;-)

2008/5/9 Howard Lewis Ship <hlship@...>:

> In 5.1 I want to extend the Tapestry property expression language
> quite a bit further to address this (invoking methods), as well as map
> and array ceation ... basically, all the cool OGNL stuff people miss.
>
> On Fri, May 9, 2008 at 7:52 AM, kranga <kranga@...> wrote:
> > In looking at converting from T3 to T5, I've to deal with constructs such
> > as:
> >
> > class="ognl:menuClassName('home')"  where getMenuClassName uses the
> > parameter to compare with the page's "id" passed in to determine if this
> is
> > the currentPage or not. So the template has multiple links with
> constructs
> > such as:
> >
> > class="ognl:menuClassName('about')"
> > class="ognl:menuClassName('contact')" etc.
> >
> > How do I do this in T5 given that prop bindings to methods cannot accept
> > arguments? I'm sure there is a workaround, I just can't seem to find one.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@...
> > For additional commands, e-mail: users-help@...
> >
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

--
with regards
Sven Homburg
http://tapestry5-components.googlecode.com

[Howard Lewis Ship]

Nope; I just want to let you create Insanely Great things, using T5 as the base.

On Fri, May 9, 2008 at 9:10 AM, Sven Homburg <homburgs@...> wrote:

> howard,
>
> you make us jobless ;-)
>
> 2008/5/9 Howard Lewis Ship <hlship@...>:
>
>> In 5.1 I want to extend the Tapestry property expression language
>> quite a bit further to address this (invoking methods), as well as map
>> and array ceation ... basically, all the cool OGNL stuff people miss.
>>
>> On Fri, May 9, 2008 at 7:52 AM, kranga <kranga@...> wrote:
>> > In looking at converting from T3 to T5, I've to deal with constructs such
>> > as:
>> >
>> > class="ognl:menuClassName('home')"  where getMenuClassName uses the
>> > parameter to compare with the page's "id" passed in to determine if this
>> is
>> > the currentPage or not. So the template has multiple links with
>> constructs
>> > such as:
>> >
>> > class="ognl:menuClassName('about')"
>> > class="ognl:menuClassName('contact')" etc.
>> >
>> > How do I do this in T5 given that prop bindings to methods cannot accept
>> > arguments? I'm sure there is a workaround, I just can't seem to find one.
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@...
>> > For additional commands, e-mail: users-help@...
>> >
>> >
>>
>>
>>
>> --
>> Howard M. Lewis Ship
>>
>> Creator Apache Tapestry and Apache HiveMind
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>
>
> --
> with regards
> Sven Homburg
> http://tapestry5-components.googlecode.com
>

--
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Sven Homburg]

we will see what can we do ....

2008/5/9 Howard Lewis Ship <hlship@...>:

> Nope; I just want to let you create Insanely Great things, using T5 as the
> base.
>
> On Fri, May 9, 2008 at 9:10 AM, Sven Homburg <homburgs@...>
> wrote:
> > howard,
> >
> > you make us jobless ;-)
> >
> > 2008/5/9 Howard Lewis Ship <hlship@...>:
> >
> >> In 5.1 I want to extend the Tapestry property expression language
> >> quite a bit further to address this (invoking methods), as well as map
> >> and array ceation ... basically, all the cool OGNL stuff people miss.
> >>
> >> On Fri, May 9, 2008 at 7:52 AM, kranga <kranga@...> wrote:
> >> > In looking at converting from T3 to T5, I've to deal with constructs
> such
> >> > as:
> >> >
> >> > class="ognl:menuClassName('home')"  where getMenuClassName uses the
> >> > parameter to compare with the page's "id" passed in to determine if
> this
> >> is
> >> > the currentPage or not. So the template has multiple links with
> >> constructs
> >> > such as:
> >> >
> >> > class="ognl:menuClassName('about')"
> >> > class="ognl:menuClassName('contact')" etc.
> >> >
> >> > How do I do this in T5 given that prop bindings to methods cannot
> accept
> >> > arguments? I'm sure there is a workaround, I just can't seem to find
> one.
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: users-unsubscribe@...
> >> > For additional commands, e-mail: users-help@...
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> Howard M. Lewis Ship
> >>
> >> Creator Apache Tapestry and Apache HiveMind
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@...
> >> For additional commands, e-mail: users-help@...
> >>
> >>
> >
> >
> > --
> > with regards
> > Sven Homburg
> > http://tapestry5-components.googlecode.com
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

--
with regards
Sven Homburg
http://tapestry5-components.googlecode.com

[Andreas Pardeike-2]

Hi,

Don't know what you folks do, but I have created a bunch of custom
bindings for different cases. The only thing I actually miss is the
ability to COMBINE them.

I.e., I have added a binding

equals:foo=bar

where foo and bar can be other binding objects or literals. I use
it successfully for switch/case situations like in

<t:if test="equals:foo='abc'"></t:if>
<t:if test="equals:foo='def'"></t:if>
..
<t:if test="equals:foo='xyz'"></t:if>

without the need to write a lot of getters.

Now, I also have

map:foo.bar

where foo is suppose to be a HashMap and it will call foo.get(bar).

As a result, all I want is the ability to have a way to specify foo and
bar with the same binding prefix as in the beginning.

For example, if I have a object that has a getter that returns a
hashmap, I would love to write

----------------------
map:(prop:obj.foo).bar
----------------------

which would call

obj.getFoo().get('bar')

If I could get this working (I don't care about the syntax), I would be
able to fulfill all my need by writing (and maybe contributing) a few
custom bindings.


On 9 maj 2008, at 18.31, Sven Homburg wrote:

>
> we will see what can we do ....
>
> 2008/5/9 Howard Lewis Ship <hlship@...>:
>
>> Nope; I just want to let you create Insanely Great things, using T5  
>> as the
>> base.
>>
>> On Fri, May 9, 2008 at 9:10 AM, Sven Homburg  
>> <homburgs@...>
>> wrote:
>>
>>> howard,
>>>
>>> you make us jobless ;-)
>>>
>>> 2008/5/9 Howard Lewis Ship <hlship@...>:
>>>
>>>> In 5.1 I want to extend the Tapestry property expression language
>>>> quite a bit further to address this (invoking methods), as well  
>>>> as map
>>>> and array ceation ... basically, all the cool OGNL stuff people  
>>>> miss.
>>>>
>>>> On Fri, May 9, 2008 at 7:52 AM, kranga <kranga@...> wrote:
>>>>> In looking at converting from T3 to T5, I've to deal with  
>>>>> constructs
>> such
>>>>> as:
>>>>>
>>>>> class="ognl:menuClassName('home')"  where getMenuClassName uses  
>>>>> the
>>>>> parameter to compare with the page's "id" passed in to determine  
>>>>> if
>> this
>>>> is
>>>>> the currentPage or not. So the template has multiple links with
>>>> constructs
>>>>> such as:
>>>>>
>>>>> class="ognl:menuClassName('about')"
>>>>> class="ognl:menuClassName('contact')" etc.
>>>>>
>>>>> How do I do this in T5 given that prop bindings to methods cannot
>> accept
>>>>> arguments? I'm sure there is a workaround, I just can't seem to  
>>>>> find
>> one.
>>>>>
>>>>
>>>> Howard M. Lewis Ship
>>>
>>> Sven Homburg
>>
>> Howard M. Lewis Ship
>>
>
> Sven Homburg

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Howard Lewis Ship]

Mor expression language would be great; the pain is when you pull
values out of a Map  or Collection and lose their type, at which point
you also lose annotations and components such as BeanEditor and Grid
no longer operate as expected.

But I agree that having a few boolean operators in the expression
language would be great: eq, lt, gt, gteq, lteq, etc.

On Mon, May 12, 2008 at 2:26 AM, Andreas Pardeike <ap@...> wrote:

> Hi,
>
>  Don't know what you folks do, but I have created a bunch of custom
>  bindings for different cases. The only thing I actually miss is the
>  ability to COMBINE them.
>
>  I.e., I have added a binding
>
>  equals:foo=bar
>
>  where foo and bar can be other binding objects or literals. I use
>  it successfully for switch/case situations like in
>
>  <t:if test="equals:foo='abc'"></t:if>
>  <t:if test="equals:foo='def'"></t:if>
>  ..
>  <t:if test="equals:foo='xyz'"></t:if>
>
>  without the need to write a lot of getters.
>
>  Now, I also have
>
>  map:foo.bar
>
>  where foo is suppose to be a HashMap and it will call foo.get(bar).
>
>  As a result, all I want is the ability to have a way to specify foo and
>  bar with the same binding prefix as in the beginning.
>
>  For example, if I have a object that has a getter that returns a
>  hashmap, I would love to write
>
>  ----------------------
>  map:(prop:obj.foo).bar
>  ----------------------
>
>  which would call
>
>  obj.getFoo().get('bar')
>
>  If I could get this working (I don't care about the syntax), I would be
>  able to fulfill all my need by writing (and maybe contributing) a few
>  custom bindings.
>
>
>
>
>  On 9 maj 2008, at 18.31, Sven Homburg wrote:
>
> >
> >
> >
> >
> > we will see what can we do ....
> >
> > 2008/5/9 Howard Lewis Ship <hlship@...>:
> >
> >
> > >
> > >
> > >
> > > Nope; I just want to let you create Insanely Great things, using T5 as
> the
> > > base.
> > >
> > > On Fri, May 9, 2008 at 9:10 AM, Sven Homburg <homburgs@...>
> > > wrote:
> > >
> > >
> > > > howard,
> > > >
> > > > you make us jobless ;-)
> > > >
> > > > 2008/5/9 Howard Lewis Ship <hlship@...>:
> > > >
> > > >
> > > > > In 5.1 I want to extend the Tapestry property expression language
> > > > > quite a bit further to address this (invoking methods), as well as
> map
> > > > > and array ceation ... basically, all the cool OGNL stuff people
> miss.
> > > > >
> > > > > On Fri, May 9, 2008 at 7:52 AM, kranga <kranga@...> wrote:
> > > > >
> > > > > > In looking at converting from T3 to T5, I've to deal with
> constructs
> > > > > >
> > > > >
> > > >
> > > such
> > >
> > > >
> > > > >
> > > > > > as:
> > > > > >
> > > > > > class="ognl:menuClassName('home')"  where getMenuClassName uses
> the
> > > > > > parameter to compare with the page's "id" passed in to determine
> if
> > > > > >
> > > > >
> > > >
> > > this
> > >
> > > >
> > > > > is
> > > > >
> > > > > > the currentPage or not. So the template has multiple links with
> > > > > >
> > > > > constructs
> > > > >
> > > > > > such as:
> > > > > >
> > > > > > class="ognl:menuClassName('about')"
> > > > > > class="ognl:menuClassName('contact')" etc.
> > > > > >
> > > > > > How do I do this in T5 given that prop bindings to methods cannot
> > > > > >
> > > > >
> > > >
> > > accept
> > >
> > > >
> > > > >
> > > > > > arguments? I'm sure there is a workaround, I just can't seem to
> find
> > > > > >
> > > > >
> > > >
> > > one.
> > >
> > > >
> > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > Howard M. Lewis Ship
> > > > >
> > > >
> > > > Sven Homburg
> > > >
> > >
> > > Howard M. Lewis Ship
> > >
> > >
> >
> > Sven Homburg
> >
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: users-unsubscribe@...
>  For additional commands, e-mail: users-help@...
>
>

--
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Blower, Andy]

This should be done with care though IMO. To me, one big advantage of T5 over JSP's with EL or OGNL is that you are forced to keep the logic out of the templates for the most part. Simple comparisons and single parameter accessors seem okay, but I've always been surprised when seeing people on the list want full OGNL functionality. Maybe I've had too many issues with overcomplicated JSP's that have subsequently been broken by designers over the years to want to the temptation any more... lol.

> -----Original Message-----
> From: Howard Lewis Ship [mailto:hlship@...]
> Sent: 12 May 2008 21:59
> To: Tapestry users
> Subject: Re: T5: Calling method with parameter in prop
>
> Mor expression language would be great; the pain is when you pull
> values out of a Map  or Collection and lose their type, at which point
> you also lose annotations and components such as BeanEditor and Grid
> no longer operate as expected.
>
> But I agree that having a few boolean operators in the expression
> language would be great: eq, lt, gt, gteq, lteq, etc.
>
> On Mon, May 12, 2008 at 2:26 AM, Andreas Pardeike <ap@...> wrote:
> > Hi,
> >
> >  Don't know what you folks do, but I have created a bunch of custom
> >  bindings for different cases. The only thing I actually miss is the
> >  ability to COMBINE them.
> >
> >  I.e., I have added a binding
> >
> >  equals:foo=bar
> >
> >  where foo and bar can be other binding objects or literals. I use
> >  it successfully for switch/case situations like in
> >
> >  <t:if test="equals:foo='abc'"></t:if>
> >  <t:if test="equals:foo='def'"></t:if>
> >  ..
> >  <t:if test="equals:foo='xyz'"></t:if>
> >
> >  without the need to write a lot of getters.
> >
> >  Now, I also have
> >
> >  map:foo.bar
> >
> >  where foo is suppose to be a HashMap and it will call foo.get(bar).
> >
> >  As a result, all I want is the ability to have a way to specify foo
> and
> >  bar with the same binding prefix as in the beginning.
> >
> >  For example, if I have a object that has a getter that returns a
> >  hashmap, I would love to write
> >
> >  ----------------------
> >  map:(prop:obj.foo).bar
> >  ----------------------
> >
> >  which would call
> >
> >  obj.getFoo().get('bar')
> >
> >  If I could get this working (I don't care about the syntax), I would
> be
> >  able to fulfill all my need by writing (and maybe contributing) a
> few
> >  custom bindings.
> >
> >
> >
> >
> >  On 9 maj 2008, at 18.31, Sven Homburg wrote:
> >
> > >
> > >
> > >
> > >
> > > we will see what can we do ....
> > >
> > > 2008/5/9 Howard Lewis Ship <hlship@...>:
> > >
> > >
> > > >
> > > >
> > > >
> > > > Nope; I just want to let you create Insanely Great things, using
> T5 as
> > the
> > > > base.
> > > >
> > > > On Fri, May 9, 2008 at 9:10 AM, Sven Homburg
> <homburgs@...>
> > > > wrote:
> > > >
> > > >
> > > > > howard,
> > > > >
> > > > > you make us jobless ;-)
> > > > >
> > > > > 2008/5/9 Howard Lewis Ship <hlship@...>:
> > > > >
> > > > >
> > > > > > In 5.1 I want to extend the Tapestry property expression
> language
> > > > > > quite a bit further to address this (invoking methods), as
> well as
> > map
> > > > > > and array ceation ... basically, all the cool OGNL stuff
> people
> > miss.
> > > > > >
> > > > > > On Fri, May 9, 2008 at 7:52 AM, kranga <kranga@...>
> wrote:
> > > > > >
> > > > > > > In looking at converting from T3 to T5, I've to deal with
> > constructs
> > > > > > >
> > > > > >
> > > > >
> > > > such
> > > >
> > > > >
> > > > > >
> > > > > > > as:
> > > > > > >
> > > > > > > class="ognl:menuClassName('home')"  where getMenuClassName
> uses
> > the
> > > > > > > parameter to compare with the page's "id" passed in to
> determine
> > if
> > > > > > >
> > > > > >
> > > > >
> > > > this
> > > >
> > > > >
> > > > > > is
> > > > > >
> > > > > > > the currentPage or not. So the template has multiple links
> with
> > > > > > >
> > > > > > constructs
> > > > > >
> > > > > > > such as:
> > > > > > >
> > > > > > > class="ognl:menuClassName('about')"
> > > > > > > class="ognl:menuClassName('contact')" etc.
> > > > > > >
> > > > > > > How do I do this in T5 given that prop bindings to methods
> cannot
> > > > > > >
> > > > > >
> > > > >
> > > > accept
> > > >
> > > > >
> > > > > >
> > > > > > > arguments? I'm sure there is a workaround, I just can't
> seem to
> > find
> > > > > > >
> > > > > >
> > > > >
> > > > one.
> > > >
> > > > >
> > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > Howard M. Lewis Ship
> > > > > >
> > > > >
> > > > > Sven Homburg
> > > > >
> > > >
> > > > Howard M. Lewis Ship
> > > >
> > > >
> > >
> > > Sven Homburg
> > >
> >
> >
> >  --------------------------------------------------------------------
> -
> >  To unsubscribe, e-mail: users-unsubscribe@...
> >  For additional commands, e-mail: users-help@...
> >
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[joshcanfield]

On Tue, May 13, 2008 at 2:21 AM, Blower, Andy
<Andrew.Blower@...> wrote:
> This should be done with care though IMO. To me, one big advantage of T5 over JSP's with
> EL or OGNL is that you are forced to keep the logic out of the templates for the most part.
> Simple comparisons and single parameter accessors seem okay, but I've always been
> surprised when seeing people on the list want full OGNL functionality. Maybe I've had too
> many issues with overcomplicated JSP's that have subsequently been broken by designers
> over the years to want to the temptation any more... lol.

Yeah, I'd agree with that. Getting code out of the templates is a good
thing. Let the framework allow for OGNL type extensions to be built as
add-ons. Turning them into first class core features will encourage
people to use them...

>
> > -----Original Message-----
> > From: Howard Lewis Ship [mailto:hlship@...]
> > Sent: 12 May 2008 21:59
> > To: Tapestry users
> > Subject: Re: T5: Calling method with parameter in prop
> >
> > Mor expression language would be great; the pain is when you pull
> > values out of a Map  or Collection and lose their type, at which point
> > you also lose annotations and components such as BeanEditor and Grid
> > no longer operate as expected.
> >
> > But I agree that having a few boolean operators in the expression
> > language would be great: eq, lt, gt, gteq, lteq, etc.
> >
> > On Mon, May 12, 2008 at 2:26 AM, Andreas Pardeike <ap@...> wrote:
> > > Hi,
> > >
> > >  Don't know what you folks do, but I have created a bunch of custom
> > >  bindings for different cases. The only thing I actually miss is the
> > >  ability to COMBINE them.
> > >
> > >  I.e., I have added a binding
> > >
> > >  equals:foo=bar
> > >
> > >  where foo and bar can be other binding objects or literals. I use
> > >  it successfully for switch/case situations like in
> > >
> > >  <t:if test="equals:foo='abc'"></t:if>
> > >  <t:if test="equals:foo='def'"></t:if>
> > >  ..
> > >  <t:if test="equals:foo='xyz'"></t:if>
> > >
> > >  without the need to write a lot of getters.
> > >
> > >  Now, I also have
> > >
> > >  map:foo.bar
> > >
> > >  where foo is suppose to be a HashMap and it will call foo.get(bar).
> > >
> > >  As a result, all I want is the ability to have a way to specify foo
> > and
> > >  bar with the same binding prefix as in the beginning.
> > >
> > >  For example, if I have a object that has a getter that returns a
> > >  hashmap, I would love to write
> > >
> > >  ----------------------
> > >  map:(prop:obj.foo).bar
> > >  ----------------------
> > >
> > >  which would call
> > >
> > >  obj.getFoo().get('bar')
> > >
> > >  If I could get this working (I don't care about the syntax), I would
> > be
> > >  able to fulfill all my need by writing (and maybe contributing) a
> > few
> > >  custom bindings.
> > >
> > >
> > >
> > >
> > >  On 9 maj 2008, at 18.31, Sven Homburg wrote:
> > >
> > > >
> > > >
> > > >
> > > >
> > > > we will see what can we do ....
> > > >
> > > > 2008/5/9 Howard Lewis Ship <hlship@...>:
> > > >
> > > >
> > > > >
> > > > >
> > > > >
> > > > > Nope; I just want to let you create Insanely Great things, using
> > T5 as
> > > the
> > > > > base.
> > > > >
> > > > > On Fri, May 9, 2008 at 9:10 AM, Sven Homburg
> > <homburgs@...>
> > > > > wrote:
> > > > >
> > > > >
> > > > > > howard,
> > > > > >
> > > > > > you make us jobless ;-)
> > > > > >
> > > > > > 2008/5/9 Howard Lewis Ship <hlship@...>:
> > > > > >
> > > > > >
> > > > > > > In 5.1 I want to extend the Tapestry property expression
> > language
> > > > > > > quite a bit further to address this (invoking methods), as
> > well as
> > > map
> > > > > > > and array ceation ... basically, all the cool OGNL stuff
> > people
> > > miss.
> > > > > > >
> > > > > > > On Fri, May 9, 2008 at 7:52 AM, kranga <kranga@...>
> > wrote:
> > > > > > >
> > > > > > > > In looking at converting from T3 to T5, I've to deal with
> > > constructs
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > such
> > > > >
> > > > > >
> > > > > > >
> > > > > > > > as:
> > > > > > > >
> > > > > > > > class="ognl:menuClassName('home')"  where getMenuClassName
> > uses
> > > the
> > > > > > > > parameter to compare with the page's "id" passed in to
> > determine
> > > if
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > this
> > > > >
> > > > > >
> > > > > > > is
> > > > > > >
> > > > > > > > the currentPage or not. So the template has multiple links
> > with
> > > > > > > >
> > > > > > > constructs
> > > > > > >
> > > > > > > > such as:
> > > > > > > >
> > > > > > > > class="ognl:menuClassName('about')"
> > > > > > > > class="ognl:menuClassName('contact')" etc.
> > > > > > > >
> > > > > > > > How do I do this in T5 given that prop bindings to methods
> > cannot
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > accept
> > > > >
> > > > > >
> > > > > > >
> > > > > > > > arguments? I'm sure there is a workaround, I just can't
> > seem to
> > > find
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > one.
> > > > >
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > > Howard M. Lewis Ship
> > > > > > >
> > > > > >
> > > > > > Sven Homburg
> > > > > >
> > > > >
> > > > > Howard M. Lewis Ship
> > > > >
> > > > >
> > > >
> > > > Sven Homburg
> > > >
> > >
> > >
> > >  --------------------------------------------------------------------
> > -
> > >  To unsubscribe, e-mail: users-unsubscribe@...
> > >  For additional commands, e-mail: users-help@...
> > >
> > >
> >
> >
> >
> > --
> > Howard M. Lewis Ship
> >
> > Creator Apache Tapestry and Apache HiveMind
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@...
> > For additional commands, e-mail: users-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

--
--
TheDailyTube.com. Sign up and get the best new videos on the internet
delivered fresh to your inbox.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Toby Hobson]

I'm not sure I like the idea of a framework FORCING me to do something, IMHO poorly structured code should be prevented by coding standards and peer reviews, not a rigid framework. Just moving the logic from a JSP/Template to a Java class doesn't necessarily mean it's cleaner. Sometimes it is actually clearer to put some logic in the template.

In my experience T4 and 5 have proved to be very flexible, more so than JSF etc. so I'm surprised that there isn't some primitive form of EL in the TML.

Anyway, like I said, just one user's opinion!

Toby

----- Original Message ----
From: Josh Canfield <josh@...>
To: Tapestry users <users@...>
Sent: Tuesday, 13 May, 2008 5:55:26 PM
Subject: Re: T5: Calling method with parameter in prop

On Tue, May 13, 2008 at 2:21 AM, Blower, Andy
<Andrew.Blower@...> wrote:
> This should be done with care though IMO. To me, one big advantage of T5 over JSP's with
> EL or OGNL is that you are forced to keep the logic out of the templates for the most part.
> Simple comparisons and single parameter accessors seem okay, but I've always been
> surprised when seeing people on the list want full OGNL functionality. Maybe I've had too
> many issues with overcomplicated JSP's that have subsequently been broken by designers
> over the years to want to the temptation any more... lol.

Yeah, I'd agree with that. Getting code out of the templates is a good
thing. Let the framework allow for OGNL type extensions to be built as
add-ons. Turning them into first class core features will encourage
people to use them...

>
> > -----Original Message-----
> > From: Howard Lewis Ship [mailto:hlship@...]
> > Sent: 12 May 2008 21:59
> > To: Tapestry users
> > Subject: Re: T5: Calling method with parameter in prop
> >
> > Mor expression language would be great; the pain is when you pull
> > values out of a Map  or Collection and lose their type, at which point
> > you also lose annotations and components such as BeanEditor and Grid
> > no longer operate as expected.
> >
> > But I agree that having a few boolean operators in the expression
> > language would be great: eq, lt, gt, gteq, lteq, etc.
> >
> > On Mon, May 12, 2008 at 2:26 AM, Andreas Pardeike <ap@...> wrote:
> > > Hi,
> > >
> > >  Don't know what you folks do, but I have created a bunch of custom
> > >  bindings for different cases. The only thing I actually miss is the
> > >  ability to COMBINE them.
> > >
> > >  I.e., I have added a binding
> > >
> > >  equals:foo=bar
> > >
> > >  where foo and bar can be other binding objects or literals. I use
> > >  it successfully for switch/case situations like in
> > >
> > >  <t:if test="equals:foo='abc'"></t:if>
> > >  <t:if test="equals:foo='def'"></t:if>
> > >  ..
> > >  <t:if test="equals:foo='xyz'"></t:if>
> > >
> > >  without the need to write a lot of getters.
> > >
> > >  Now, I also have
> > >
> > >  map:foo.bar
> > >
> > >  where foo is suppose to be a HashMap and it will call foo.get(bar).
> > >
> > >  As a result, all I want is the ability to have a way to specify foo
> > and
> > >  bar with the same binding prefix as in the beginning.
> > >
> > >  For example, if I have a object that has a getter that returns a
> > >  hashmap, I would love to write
> > >
> > >  ----------------------
> > >  map:(prop:obj.foo).bar
> > >  ----------------------
> > >
> > >  which would call
> > >
> > >  obj.getFoo().get('bar')
> > >
> > >  If I could get this working (I don't care about the syntax), I would
> > be
> > >  able to fulfill all my need by writing (and maybe contributing) a
> > few
> > >  custom bindings.
> > >
> > >
> > >
> > >
> > >  On 9 maj 2008, at 18.31, Sven Homburg wrote:
> > >
> > > >
> > > >
> > > >
> > > >
> > > > we will see what can we do ....
> > > >
> > > > 2008/5/9 Howard Lewis Ship <hlship@...>:
> > > >
> > > >
> > > > >
> > > > >
> > > > >
> > > > > Nope; I just want to let you create Insanely Great things, using
> > T5 as
> > > the
> > > > > base.
> > > > >
> > > > > On Fri, May 9, 2008 at 9:10 AM, Sven Homburg
> > <homburgs@...>
> > > > > wrote:
> > > > >
> > > > >
> > > > > > howard,
> > > > > >
> > > > > > you make us jobless ;-)
> > > > > >
> > > > > > 2008/5/9 Howard Lewis Ship <hlship@...>:
> > > > > >
> > > > > >
> > > > > > > In 5.1 I want to extend the Tapestry property expression
> > language
> > > > > > > quite a bit further to address this (invoking methods), as
> > well as
> > > map
> > > > > > > and array ceation ... basically, all the cool OGNL stuff
> > people
> > > miss.
> > > > > > >
> > > > > > > On Fri, May 9, 2008 at 7:52 AM, kranga <kranga@...>
> > wrote:
> > > > > > >
> > > > > > > > In looking at converting from T3 to T5, I've to deal with
> > > constructs
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > such
> > > > >
> > > > > >
> > > > > > >
> > > > > > > > as:
> > > > > > > >
> > > > > > > > class="ognl:menuClassName('home')"  where getMenuClassName
> > uses
> > > the
> > > > > > > > parameter to compare with the page's "id" passed in to
> > determine
> > > if
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > this
> > > > >
> > > > > >
> > > > > > > is
> > > > > > >
> > > > > > > > the currentPage or not. So the template has multiple links
> > with
> > > > > > > >
> > > > > > > constructs
> > > > > > >
> > > > > > > > such as:
> > > > > > > >
> > > > > > > > class="ognl:menuClassName('about')"
> > > > > > > > class="ognl:menuClassName('contact')" etc.
> > > > > > > >
> > > > > > > > How do I do this in T5 given that prop bindings to methods
> > cannot
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > accept
> > > > >
> > > > > >
> > > > > > >
> > > > > > > > arguments? I'm sure there is a workaround, I just can't
> > seem to
> > > find
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > one.
> > > > >
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > > Howard M. Lewis Ship
> > > > > > >
> > > > > >
> > > > > > Sven Homburg
> > > > > >
> > > > >
> > > > > Howard M. Lewis Ship
> > > > >
> > > > >
> > > >
> > > > Sven Homburg
> > > >
> > >
> > >
> > >  --------------------------------------------------------------------
> > -
> > >  To unsubscribe, e-mail: users-unsubscribe@...
> > >  For additional commands, e-mail: users-help@...
> > >
> > >
> >
> >
> >
> > --
> > Howard M. Lewis Ship
> >
> > Creator Apache Tapestry and Apache HiveMind
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@...
> > For additional commands, e-mail: users-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

--
--
TheDailyTube.com. Sign up and get the best new videos on the internet
delivered fresh to your inbox.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[joshcanfield]

Hey Toby,

> I'm not sure I like the idea of a framework FORCING me to do something

I agree with the sentiment, but in this case isn't it misplaced? I
suppose you are forced to consider which binding implementation to
use, but that feels more like flexibility. Tapestry should make
integrating and implementing new bindings really easy. Plugging a
module into your project with those bindings should be easy too.

We have OGNL, EL, juel, jexl, and others... is there a need for
tapestry to implement this again?

> In my experience T4 and 5 have proved to be very flexible, more so than JSF etc. so I'm surprised that
> there isn't some primitive form of EL in the TML.

There is, it's just VERY primitive. :)
I don't think building the kitchen sink into the framework makes it
more flexible. Being able to add it on later, if you need it is
flexible, and also what we have now (the OGNL binding referred to
earlier in this thread)

> Anyway, like I said, just one user's opinion!

Yep, it's good to discuss stuff. Hopefully it'll be useful for someone
down the road...

Josh

On Tue, May 13, 2008 at 10:33 AM, Toby Hobson
<toby.hobson@...> wrote:
> I'm not sure I like the idea of a framework FORCING me to do something, IMHO poorly structured code should be prevented by coding standards and peer reviews, not a rigid framework. Just moving the logic from a JSP/Template to a Java class doesn't necessarily mean it's cleaner. Sometimes it is actually clearer to put some logic in the template.
>
> In my experience T4 and 5 have proved to be very flexible, more so than JSF etc. so I'm surprised that there isn't some primitive form of EL in the TML.
>
> Anyway, like I said, just one user's opinion!
>
> Toby
>

--
--
TheDailyTube.com. Sign up and get the best new videos on the internet
delivered fresh to your inbox.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Szemere Szemere]

I agree with the sentiments above - the framework should provide basic
services and give others the ability to extend it. However I think there is
a lot of value in making it easy for folks to use popular bindings. I for
one, am not a big fan of having to incorporate additional code into my
project to handle common extensions.

From what I know, OGNL has a special place in Tapestry history - adding it
in an optional "3rd party/contrib" module (but still part of Tapestry
standard download) should help adoption of T5.

Szemere

[Chris Lewis-5]

tapestry5-components provides an ognl binding like it worked in t4. See

http://code.google.com/p/tapestry5-components/

and

http://87.193.218.134:8080/t5components/t5c-commons/howto_ognlbinding.html

chris

Szemere Szemere wrote:

> I agree with the sentiments above - the framework should provide basic
> services and give others the ability to extend it. However I think there is
> a lot of value in making it easy for folks to use popular bindings. I for
> one, am not a big fan of having to incorporate additional code into my
> project to handle common extensions.
>
> >From what I know, OGNL has a special place in Tapestry history - adding it
> in an optional "3rd party/contrib" module (but still part of Tapestry
> standard download) should help adoption of T5.
>
> Szemere
>
>  

--
http://thegodcode.net


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Blower, Andy]

I think, in hindsight, maybe 'forcing' was the wrong word! Maybe 'encouraged' is more apt since it's so easy to add an OGNL mapping? I just think it's best if this is not part of T5 out of the box.

> -----Original Message-----
> From: Toby Hobson [mailto:toby.hobson@...]
> Sent: 13 May 2008 18:34
> To: Tapestry users
> Subject: Re: T5: Calling method with parameter in prop
>
> I'm not sure I like the idea of a framework FORCING me to do something,
> IMHO poorly structured code should be prevented by coding standards and
> peer reviews, not a rigid framework. Just moving the logic from a
> JSP/Template to a Java class doesn't necessarily mean it's cleaner.
> Sometimes it is actually clearer to put some logic in the template.
>
> In my experience T4 and 5 have proved to be very flexible, more so than
> JSF etc. so I'm surprised that there isn't some primitive form of EL in
> the TML.
>
> Anyway, like I said, just one user's opinion!
>
> Toby
>
> ----- Original Message ----
> From: Josh Canfield <josh@...>
> To: Tapestry users <users@...>
> Sent: Tuesday, 13 May, 2008 5:55:26 PM
> Subject: Re: T5: Calling method with parameter in prop
>
> On Tue, May 13, 2008 at 2:21 AM, Blower, Andy
> <Andrew.Blower@...> wrote:
> > This should be done with care though IMO. To me, one big advantage of
> T5 over JSP's with
> > EL or OGNL is that you are forced to keep the logic out of the
> templates for the most part.
> > Simple comparisons and single parameter accessors seem okay, but I've
> always been
> > surprised when seeing people on the list want full OGNL
> functionality. Maybe I've had too
> > many issues with overcomplicated JSP's that have subsequently been
> broken by designers
> > over the years to want to the temptation any more... lol.
>
> Yeah, I'd agree with that. Getting code out of the templates is a good
> thing. Let the framework allow for OGNL type extensions to be built as
> add-ons. Turning them into first class core features will encourage
> people to use them...
>
>
> >
> > > -----Original Message-----
> > > From: Howard Lewis Ship [mailto:hlship@...]
> > > Sent: 12 May 2008 21:59
> > > To: Tapestry users
> > > Subject: Re: T5: Calling method with parameter in prop
> > >
> > > Mor expression language would be great; the pain is when you pull
> > > values out of a Map  or Collection and lose their type, at which
> point
> > > you also lose annotations and components such as BeanEditor and
> Grid
> > > no longer operate as expected.
> > >
> > > But I agree that having a few boolean operators in the expression
> > > language would be great: eq, lt, gt, gteq, lteq, etc.
> > >
> > > On Mon, May 12, 2008 at 2:26 AM, Andreas Pardeike <ap@...>
> wrote:
> > > > Hi,
> > > >
> > > >  Don't know what you folks do, but I have created a bunch of
> custom
> > > >  bindings for different cases. The only thing I actually miss is
> the
> > > >  ability to COMBINE them.
> > > >
> > > >  I.e., I have added a binding
> > > >
> > > >  equals:foo=bar
> > > >
> > > >  where foo and bar can be other binding objects or literals. I
> use
> > > >  it successfully for switch/case situations like in
> > > >
> > > >  <t:if test="equals:foo='abc'"></t:if>
> > > >  <t:if test="equals:foo='def'"></t:if>
> > > >  ..
> > > >  <t:if test="equals:foo='xyz'"></t:if>
> > > >
> > > >  without the need to write a lot of getters.
> > > >
> > > >  Now, I also have
> > > >
> > > >  map:foo.bar
> > > >
> > > >  where foo is suppose to be a HashMap and it will call
> foo.get(bar).
> > > >
> > > >  As a result, all I want is the ability to have a way to specify
> foo
> > > and
> > > >  bar with the same binding prefix as in the beginning.
> > > >
> > > >  For example, if I have a object that has a getter that returns a
> > > >  hashmap, I would love to write
> > > >
> > > >  ----------------------
> > > >  map:(prop:obj.foo).bar
> > > >  ----------------------
> > > >
> > > >  which would call
> > > >
> > > >  obj.getFoo().get('bar')
> > > >
> > > >  If I could get this working (I don't care about the syntax), I
> would
> > > be
> > > >  able to fulfill all my need by writing (and maybe contributing)
> a
> > > few
> > > >  custom bindings.
> > > >
> > > >
> > > >
> > > >
> > > >  On 9 maj 2008, at 18.31, Sven Homburg wrote:
> > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > we will see what can we do ....
> > > > >
> > > > > 2008/5/9 Howard Lewis Ship <hlship@...>:
> > > > >
> > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Nope; I just want to let you create Insanely Great things,
> using
> > > T5 as
> > > > the
> > > > > > base.
> > > > > >
> > > > > > On Fri, May 9, 2008 at 9:10 AM, Sven Homburg
> > > <homburgs@...>
> > > > > > wrote:
> > > > > >
> > > > > >
> > > > > > > howard,
> > > > > > >
> > > > > > > you make us jobless ;-)
> > > > > > >
> > > > > > > 2008/5/9 Howard Lewis Ship <hlship@...>:
> > > > > > >
> > > > > > >
> > > > > > > > In 5.1 I want to extend the Tapestry property expression
> > > language
> > > > > > > > quite a bit further to address this (invoking methods),
> as
> > > well as
> > > > map
> > > > > > > > and array ceation ... basically, all the cool OGNL stuff
> > > people
> > > > miss.
> > > > > > > >
> > > > > > > > On Fri, May 9, 2008 at 7:52 AM, kranga <kranga@...>
> > > wrote:
> > > > > > > >
> > > > > > > > > In looking at converting from T3 to T5, I've to deal
> with
> > > > constructs
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > such
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > > as:
> > > > > > > > >
> > > > > > > > > class="ognl:menuClassName('home')"  where
> getMenuClassName
> > > uses
> > > > the
> > > > > > > > > parameter to compare with the page's "id" passed in to
> > > determine
> > > > if
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > this
> > > > > >
> > > > > > >
> > > > > > > > is
> > > > > > > >
> > > > > > > > > the currentPage or not. So the template has multiple
> links
> > > with
> > > > > > > > >
> > > > > > > > constructs
> > > > > > > >
> > > > > > > > > such as:
> > > > > > > > >
> > > > > > > > > class="ognl:menuClassName('about')"
> > > > > > > > > class="ognl:menuClassName('contact')" etc.
> > > > > > > > >
> > > > > > > > > How do I do this in T5 given that prop bindings to
> methods
> > > cannot
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > accept
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > > arguments? I'm sure there is a workaround, I just can't
> > > seem to
> > > > find
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > one.
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > > Howard M. Lewis Ship
> > > > > > > >
> > > > > > >
> > > > > > > Sven Homburg
> > > > > > >
> > > > > >
> > > > > > Howard M. Lewis Ship
> > > > > >
> > > > > >
> > > > >
> > > > > Sven Homburg
> > > > >
> > > >
> > > >
> > > >  ----------------------------------------------------------------
> ----
> > > -
> > > >  To unsubscribe, e-mail: users-unsubscribe@...
> > > >  For additional commands, e-mail: users-help@...
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Howard M. Lewis Ship
> > >
> > > Creator Apache Tapestry and Apache HiveMind
> > >
> > > -------------------------------------------------------------------
> --
> > > To unsubscribe, e-mail: users-unsubscribe@...
> > > For additional commands, e-mail: users-help@...
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@...
> > For additional commands, e-mail: users-help@...
> >
> >
>
>
>
> --
> --
> TheDailyTube.com. Sign up and get the best new videos on the internet
> delivered fresh to your inbox.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>
>

[Axel Mannhardt]

Marcus-11 wrote:

Hi Axel.

Maybe this help,

"Adding Columns Example" at
http://tapestry.formos.com/nightly/tapestry5/tapestry-core/ref/org/apache/tapestry/corelib/components/Grid.html

Marcus

Thanks for your answer, sorry it took me so long to respond. Actually, it did not help. I ended up using additional row indices, incremented in getters/setters, initialized in setuprender. This way I was able to store the model for the select component outside of the griddatasource. I am pretty sure, there is a more elegant solution, but I have not found it by now. The next step I would take would be looking if I really have to use a griddatasource and if avoiding it solves the problem.

Axel