Example of ModalWindow misleading
---------------------------------
Key: WICKET-2295
URL: https://issues.apache.org/jira/browse/WICKET-2295
Project: Wicket
Issue Type: Improvement
Components: wicket-examples
Affects Versions: 1.4-RC4
Reporter: Live Nono
Priority: Minor
cf :
http://www.nabble.com/Example-of-ModalWindow-misleading-td23631464.html#a23631464
The example here :
http://www.wicket-library.com/wicket-examples/ajax/modal-window.1 is
pretty misleading : passing components between components/page is
quite broken as can be seen in the past discussion on the mailing list
(serialization issue can arise and makes both sides using different
references of the same object "logically speaking").
However, as it is in the example, I first used it considering that it
should be ok to do so.
Could it be changed in some way ?
On the bigger picture, I guess it raises again the issue of the
"recommended" way of communicating between the page and the modal
window, which currently doesn't exist (session, database...??).
However, this example is currently completely misleading, so even so
comments to explicit the issue would be welcomed.
thanks again
nono
=> Re: Example of ModalWindow misleading
Click to flag this post
by Matej Knopp-2 May 21, 2009; 12:07am :: Rate this Message: - Use ratings to
moderate (?)
Reply | Reply to Author | Print | View Threaded | Show Only this Message
I think modal window example could be fixed by using
getPageReference() to pass page reference between pages instead of
page instance.
-Matej
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
