Thanks Thiago, I'm aware I have to add MyActivationRequestParameter, just
wanted to be sure I was using public static void provideTransformWorkers in
my app module the same as Tapestry is using it in there module.
Yes lance, it would be a great feature especially when working with multi
facet searches. Examples would be the side bar filter search on amazon,
homedopt, ebay etc.
Ebay uses unencoded pipes in their urls creating a really nice clean url,
example make=ford|chevy&color=blue|black|white compared to
make=ford$007chevy&color=blue$007black$007white
I'll work on this stuff tonight, hopefully I'll get something working.
Thanks Guys.
On Wed, Sep 3, 2014 at 11:49 AM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Wed, 03 Sep 2014 12:36:15 -0300, George Christman <
> gchrist...@cardaddy.com> wrote:
>
> So would I just add that exact method to my AppModule along with my owe
>> annotation annotation instance?
>>
>
> You'll need to write your own worker and annotation, so you'll need to
> adapt the line you posted here.
>
> If you add this to your AppModule
>
> configuration.addInstance("ActivationRequestParameter",
> ActivationRequestParameterWorker.class);
>
> you'll override the ActivationRequestParameterWorker from Tapestry
> instead of adding a new one. You'll need something like this:
>
> configuration.addInstance("MyActivationRequestParameter",
> MyActivationRequestParameterWorker.class);
>
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
--
George Christman
www.CarDaddy.com
P.O. Box 735
Johnstown, New York
