The data is not serializable and is needed in several pages as a part
of one
transaction
- Not serializable:
Well that is a hick up. This of course also means that you can not do
clustering. I would put the data directly in the HTTP session, or in
your own sub class of Wicket's WebSession. I
to retrieve the modified data e.g. from session or pagemap. Or to save its
state between requests which would just be a bit inconvenient.
--
View this message in context:
http://www.nabble.com/Custom-PageMap-tp19073327p19084160.html
Sent from the Wicket - User mailing list archive at Nabble.com
of detachable model
to retrieve the modified data e.g. from session or pagemap. Or to save its
state between requests which would just be a bit inconvenient.
--
View this message in context:
http://www.nabble.com/Custom-PageMap-tp19073327p19084160.html
Sent from the Wicket - User mailing list
--
View this message in context:
http://www.nabble.com/Custom-PageMap-tp19073327p19084492.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e
On Thu, Aug 21, 2008 at 10:22 AM, John Patterson [EMAIL PROTECTED] wrote:
I was just considering storing the unit-of-work in the PageMap meta-data.
I haven't used that. Session is more in my comfort zone ;)
What exactly is the problem with detecting the different browser windows?
When does it
in 1.3 with the new Disk based store we dont need by default the window
detection yes
so it is turned off by default.
Also the detection is pretty good but not completely solid!
It will always be very hard to really detect and play nicely under all
circumstances
For example if you have 1
if it is not 100 percent reliable. Sometimes that is
enough.
--
View this message in context:
http://www.nabble.com/Custom-PageMap-tp19073327p19086969.html
Sent from the Wicket - User mailing list archive at Nabble.com
in context:
http://www.nabble.com/Custom-PageMap-tp19073327p19073327.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
John, if you keep your conversation data in the component (as a java
field), and you work with listeners in that component (e.g. with a
Link), that data is available in the listener (e.g. Link's onClick
callback method).
While coding the component you should not worry about where that data is
for a browser window?
John
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Custom-PageMap-tp19073327p19082028
10 matches
Mail list logo