Hi,
If Session.get() is called then a new Wicket Session is created. Unless
Session#bind() is called this session is temporary, i.e. it will be
discarded at the end of the request cycle.
If #bind() is called then a Http Session is created too and the Wicket
Session is stored in it as an
Thank you, Martin!
I have such stackTrace for all of the newSession() calls:
1)com.alee.urait.web.Urait.newSession(Urait.java:89)
2)org.apache.wicket.Application.fetchCreateAndSetSession(Application.java:1557)
3)org.apache.wicket.Session.get(Session.java:168)
com.alee.urait.web.Urait.newSession(Urait.java:89)
org.apache.wicket.Application.fetchCreateAndSetSession(Application.java:1557)
org.apache.wicket.Session.get(Session.java:168)
org.apache.wicket.request.handler.render.PageRenderer.*getSessionId*(PageRenderer.java:101)
Thank you, Sven!
I have created an issue, but I don't know it it right in it's description.
https://issues.apache.org/jira/browse/WICKET-5191
But can I do any hack now to get rid of this problem?
--
View this message in context:
A quickstart would help to identify the issue.
Sven
On 05/16/2013 01:59 PM, Michael Zhavzharov wrote:
Thank you, Sven!
I have created an issue, but I don't know it it right in it's description.
https://issues.apache.org/jira/browse/WICKET-5191
But can I do any hack now to get rid of this
It is attached to the ticket now.
On Thu, May 16, 2013 at 3:54 PM, Sven Meier s...@meiers.net wrote:
A quickstart would help to identify the issue.
Sven
On 05/16/2013 01:59 PM, Michael Zhavzharov wrote:
Thank you, Sven!
I have created an issue, but I don't know it it right in it's
