[ 
http://issues.ops4j.org/browse/PAXWICKET-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213#action_14213
 ] 

Andreas Pieber commented on PAXWICKET-10:
-----------------------------------------

I'm experimenting right now with a third approach to directly attach the 
WicketApplication instead. Let's see how this works

> Cannot store data in session context
> ------------------------------------
>
>                 Key: PAXWICKET-10
>                 URL: http://issues.ops4j.org/browse/PAXWICKET-10
>             Project: Pax Wicket
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Peter Neubauer
>            Assignee: Andreas Pieber
>             Fix For: 1.0.0
>
>         Attachments: service.patch, sessionViaApplication.patch
>
>
> In one page I want to store some data in user session and get it back in 
> another page.
> Cannot extend PaxWicketSession (final class) and add own attributes.
> Cannot use wicket.Session.setAttribute, because is protected.
> Cannot create own Session object in Application, because cannot set own 
> SessionFactory.
> So, how can I do it?
> In Februar, Edward Yakop wrote answered to Peter Neubauer 
> (http://lists.ops4j.org/pipermail/general/2007q1/001346.html):
> ----
> > Then, would it be a good addition to be able to register your own
> > MySpecialEnhancedWebSession in PaxWicket, since that is the way Wicket
> > folks recommends to store custom data in the session?
> Perhaps we could let user to attach their data in the session. Since,
> we're in evolving stage, it seems a safer thing to do.
> ----
> I think, that clear solution is a must.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to