Hi,
I tried "Remember Me" functionality here:
http://tynamo-federatedaccounts.tynamo.org/ (live demo webapp) but the user
isn't remembered.
When I check the "Remember Me" checkbox and login, the cookie "rememberMe"
is created. After I close the browser and reopen it again I'm not logged
in. Am I
Hi Travis, a few Q's
1. Have you configured the ignored paths as documented here:
http://tapestry.apache.org/configuration#Configuration-ConfiguringIgnoredPaths
2. If so, what's your config?
3. If not, how does this work?
4. Give an example t5 url?
5. Give an example t4 / JSP url
6. Give an e
On Mon, 24 Feb 2014 19:53:59 -0300, Boris Horvat
wrote:
Anyone has any idea about this? :)
I already gave you my suggestion.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---
It's actually the JSP that needs to be aware of the tapestry requests.
We are injecting tapestry 5 services that have dependencies on the tapestry
5 request into the
JSP or tapestry 4 pages. Without this code it breaks.
Also we are calling cleanupThread().
I've tried storeServletRequestResponse
It's pretty hacky what you're doing. I think you'll also need to call
Registry.cleanupThread() to give Tapestry a chance to cleanup any PerThread
values that are created during your quasi half arsed Tapestry request ;)
http://tapestry.apache.org/5.3.7/apidocs/org/apache/tapestry5/ioc/Registry.html
Hmm... This could well be the source of your problem. I think you'll also
need to call ResponseGlobals. storeServletRequestResponse(...)
I'm not sure I fully understand your non-tapestry flow. Why do you need
Tapestry to be aware of the JSP requests?
I'm assuming you have contributed to the ignor
Anyone has any idea about this? :)
On Sat, Feb 22, 2014 at 10:07 PM, Boris Horvat wrote:
> In case it helps the method is defined like this
>
> function showUploadProgress() {
> var showUploadProgress = function(id, fileName) {
> alert(123)
> $('.photo').removeClass('photo').
I've looked at the request/response traffic and nothing looks unusual.
In fact the JSONObject that is passed to
JSONObjectEventResultProcessor.processResultValue(JSONObject value)
looks perfectly fine.
We do have a custom filter, which enables tapestry injection in
non-tapestry 5 environments, (i.
Hi all,
There's a new JumpStart preview demo for Tapestry 5.4. You can use it here:
http://jumpstart.doublenegative.com.au/jumpstart7/
The biggest change is in the Ajax Components CRUD example. I'm very pleased
that it now works without an activation context, activation request paramete
