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?
On Sun, 25 Sep 2016 09:56:24 -0300, <rapidtransit...@aol.com> wrote:
I'm using Elasticsearch, my first implementation involved processing a
user request (verifying that there facet filters are valid) in the
request chain and then sending a redirect short circuiting the request
pipeline. Now here's the problem. I moved the processing into a
component to make it more modular and way less fragile. The problem is
the actual search/facet filter happens during the GET request and it is
injected into the EventContext and when they hit the page the request
result is assigned in the onActivate event. The problem is on the POST
request the page components are still looking for those values as if it
was trying to render the template. I just did a workaround and made a
NullSearchRequest value but it just seems like a hacky workaround and I
keep having to check if a value is null for properties that are never
called on that are never used in a POST request. Anyone know a good
work around?
Sent from AOL Mobile Mail
--
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
