Ah yea, I screwed up the example in my email, but yes, it's declared
like so:
@Parameter(required = true)
List<String> fooList;
Mind you it works for the "normal" static cases, and the case where it's
passed as a property (#1 and #2), but not inside a <t:loop>.
Casey Link
Outskirts Labs { https://outskirtslabs.com }
Technology for Changemakers
On 10/23/2015 10:36 AM, Nathan Quirynen wrote:
> Just checking to be sure, but are you sure you didn't forget the
> @Parameter on the fooList property in your component?
>
> Nathan
>
> On 23/10/15 10:14, Casey Link wrote:
>> This is a strange one.
>>
>> I have a Foo component that wraps a progressive display (not sure if
>> that part is relevant). One of the parameters to this component is a
>> list of strings, "t:fooList":
>>
>> @Property
>> List<String> fooList;
>>
>> In the page I'm trying to include it in, it works as expected if I set
>> fooList with:
>>
>> 1. t:fooList="list:literal:aFoo"
>> 2. t:fooList="prop:someFooList"
>>
>> But if I wrap my Foo component in a <t:loop> and try to set the fooList
>> that way, I get errors:
>>
>> <t:loop t:source="listofFooLists" t:value="aFooList">
>> <t:foo t:fooList="prop:aFooList" />
>> </t:loop>
>>
>> where those properties are:
>> public List<List<String>> listofFooLists(){...}
>>
>> @Property
>> List<String> aFooList;
>>
>> The specific error is an NPE in the Foo component when it tries to
>> access it's fooList field.
>>
>> I'm not sure if being a progressiveDisplay component has anything to do
>> with it, but somewhere along the way the fooList is being nulled. By
>> printing out ${aFooList} besides mt <t:foo/> I can see that what is
>> being passed to the component is indeed, not null.
>>
>> I'd appreciate any advice, as this is quite a stumper for me.
>>
>> Cheers,
>> Casey
>>
>>
> <mailto:nat...@pensionarchitects.be>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
