I've never fully understand tapestry's whacky url encoding. I'm sure
there's a reason for it.
I'm pretty sure you can override the tapestry URLEncoder to use the more
normal java.net.URLEncoder and java.net.URLDecoder
http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/services/URLEncoder
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 sear
> Aren't you talking about different things: ActivationRequestParameter vs.
PageActivationContext ?
Yes, my mistake. I can see this being a nice feature for
ActivationRequestParameter.
I'm guessing a proper fix will need to look at the generic type of the
field to properly support type coercion f
On Wed, 03 Sep 2014 12:36:15 -0300, George Christman
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 y
So would I just add that exact method to my AppModule along with my owe
annotation annotation instance?
On Wed, Sep 3, 2014 at 11:33 AM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Wed, 03 Sep 2014 12:30:14 -0300, George Christman <
> gchrist...@cardaddy.com> wrote:
>
> Thank
On Wed, 03 Sep 2014 12:30:14 -0300, George Christman
wrote:
Thanks Thiago, what would I need to do to get tapestry to see my
annotation. I see this in the tapestry app module.
@Contribute(ComponentClassTransformWorker2.class) @Primary public
static
void provideTransformWorkers( Ordered
Thanks Thiago, what would I need to do to get tapestry to see my
annotation. I see this in the tapestry app module.
@Contribute(ComponentClassTransformWorker2.class) @Primary public static
void provideTransformWorkers( OrderedConfiguration<
ComponentClassTransformWorker2> configuration, MetaWo
On Wed, 03 Sep 2014 11:58:33 -0300, Dmitry Gusev
wrote:
Aren't you talking about different things: ActivationRequestParameter vs.
PageActivationContext ?
Yeah, Lance is talking about activation context, while George about
request parameters.
https://issues.apache.org/jira/browse/TAP5-14
Yes, but I get what he was saying. I'll take a look at the tap worker
method tonight and see if I can't figure out how to get a custom one
working. Dmitry, do you know what I'll need to do in my app module to get
my custom annotation working?
On Wed, Sep 3, 2014 at 10:58 AM, Dmitry Gusev
wrote:
Aren't you talking about different things: ActivationRequestParameter vs.
PageActivationContext ?
On Wed, Sep 3, 2014 at 5:31 PM, George Christman
wrote:
> I'd like to just create my own then since it handles the urls so well. How
> would I go about doing that lance?
>
>
> On Wed, Sep 3, 2014 a
I'd like to just create my own then since it handles the urls so well. How
would I go about doing that lance?
On Wed, Sep 3, 2014 at 2:23 AM, Lance Java
wrote:
> @PageActivationContext is a convenience annotation that ultimately creates
> onActivate(..) and onPassivate() methods on your page. I
@PageActivationContext is a convenience annotation that ultimately creates
onActivate(..) and onPassivate() methods on your page. I think you're
surpassing what it was designed for.
You should just declare onActivate(..) and onPassivate() instead (or maybe
create your own @PageActivationContexts a
Hi guys, I'm wondering if there is a way to customize the
ActivationRequestParameter to accept a list? What I'm looking to do is pass
a list of strings into the ActivationRequestParameter and ultimately form a
query parameter in the URL like so
make=chevy|ford
My thought was something like this.
13 matches
Mail list logo
