I will try that, thanks. I'll look into the redirect more, I can see why it is
a bad idea.
-Original Message-
From: Thiago H de Paula Figueiredo
To: Tapestry users
Sent: Tue, Sep 27, 2016 10:12 am
Subject: Re: Problem with POST requests
On Tue, 27 Sep 2016 10:50:29 -0300, wrote:
>
On Tue, 27 Sep 2016 10:50:29 -0300, wrote:
Object onActivate(EventContext eventContext) {
if(eventContext instanceof CategoryEvent) {
CategoryEvent event = (CategoryEvent) eventContext;
category = event.getCachedCategory();
setSearchRequestFuture(
public class EntityLinkTransformer implements PageRenderLinkTransformer{
@Override
public PageRenderRequestParameters decodePageRenderRequest(Request request)
{
if(StringUtils.isNotEmpty(request.getPath())) {
CachedCategory category;
Product product;
onActivate() will be invoked for GET and POST and even during link
generation (I think). You shouldn't do any "work" in this method. Better
yet, remove the method all together and use @PageActivationContext.
If you have "work" needed for render only you should use @SetupRender
On 27 Sep 2016 2:12
On Fri, 23 Sep 2016 22:32:45 -0300, Kalle Korhonen
wrote:
Just the packaging has changed, add dependency to commons:
org.apache.tapestry
commons
5.4.1
This dependency should be already there due to the tapestry-ioc and
tapestry-core
packages already depending on the commons one. Th
Hi!
Could you please post the code of your component and the page? I'm having a
hard time understanding your scenario from your description.
Are you using a component or page as code that will upload something
to ElasticSearch when it is requested but not sending any response
back to the browser?
