On Tue, 07 Oct 2014 16:10:07 -0300, akshay <akshayestat...@gmail.com>
wrote:
Hi Thiago,
Hi!
In the application ,the SSO object is created by the
contributeApplicationstateManager method().
No. It's created by the ApplicationStateManager service, using the
contributed ApplicationStateCreator implementations, when it needs to be
created and only then.
When I debug, I see that the requestHandler method gets called first.
Since I try to use a SSO object, which is infact not created and only
gets
created post the contributeApplicationstateManager () call.
That's not correct. It's not contributeApplicationStateManager() the
method being called. It's the create() method of the
ApplicationStateCreator instance you contributed to the
ApplicationStateManager service.
I intend to find a solution, where in I can use the SSO object in my
requestHandler class.
You can use it any time in any piece of code being executed as part of a
request. I'm sorry, but you're misunderstading how Tapestry works.
--
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
