Re: Grid component customization

Dear Thiago,

first thanks for this solution, but can you please propose a solution 
which works under Tapestry 5.3.8? This would be great.

Anyway, I tried to migrate our applications to 5.4.3 yesterday and 
nearly succeeded, but only nearly, due to problems with the removed 
javassist lib.
ut this would be another topic in this support list.

Thanks and Best Regards
Erich


Am 28.11.2017 16:32, schrieb Thiago H. de Paula Figueiredo:
> On Tue, Nov 28, 2017 at 6:33 AM, Erich Gormann<[email protected]>  wrote:
>
>> Dear all,
>>
> Hi!
>
>
>> I wanted to customize the GridColumns component, which is embedded inside
>> the Grid component, by trying different approaches.
>>
>> Finally I failed, because it was neither possible by a request filter
>> replacing the GridColumns component at runtime with my customized one,
>
> This wasn't expected to work, but I'm curious in how you tried to do it. :)
>
>
>> nor did it work to use an own template for the Grid component pointing to
>> my customized version of GridColumns.
>>
>> What is the best way to do this? The GridColumns component is a private
>> component inside the Grid and I wonder how to replace it.
>>
> Contribute to the ComponentOverride distributed configuration, which is a
> Map<Class, Class>, the key being the component or page or mixin class to be
> replaced, the value being the replacement.
>
> Here's an example from Tapestry's test suite:
>
> @Contribute(ComponentReplacer.class)
> public static void
> overridePageAndComponentAndMixin(MappedConfiguration<Class, Class>
> configuration) {
>      configuration.add(OverridenPage.class, OverridePage.class);
>      configuration.add(OverridenComponent.class, OverrideComponent.class);
>      configuration.add(OverridenMixin.class, OverrideMixin.class);
> }
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]