On 3/23/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> Hmm,
>
> FeedbackMessages belong to the page they are put on. There is nothing that
> prevents you from doing the following:
>
> Page target = new MyPage();
> target.info("My superduper infomessage");
> setResponsePage(target);
Duh, I totally overlooked that this works now (it didn't in old Wicket
versions). Just changed CDApp. However, you're out of luck when don't
have access to the new page instance, e.g. when you redirect to a
bookmarkable page using setResponsePage(Class).
> As a user of the BreadCrumbs component, I don't want to have to distribute
> the model of the component across my pages. That would clutter the
> interfaces. I think this is what Sprign WebFlow and Seam are targeting:
> state that spans multiple requests/pages. IMO feedback panels touch this
> same subject.
Sounds right. Though if I remember correctly, even Seam puts it in the
session - though as an implementation detail. If we had MetaData for
sessions (yes, another case where
http://jroller.com/page/JonathanLocke/20060321 would work out well),
you could have such bread crumbs - they would be distributing their
model in the session's metadata.
Eelco
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
