thanks ... should have thought of that! :) On 12/23/05, Maurice Marrink [EMAIL PROTECTED] wrote:
You could always use a different model (containing just the fileuploadobject) for the fileupload and the compoundmodel for the rest of theform. then in the onsubmit you could get both models set the
What you do here is quite harmless... The page is already in the
session (page map and all), so the extra reference to it doesn't hurt.
The problem comes when you attach a business object to your page:
/** Dont do this */
class MyPage extends WebPage {
private MyVeryLargeObject subject;
//
See http://www.wicket-wiki.org.uk/wiki/index.php/Migrate-1.2 and yes,
with the release of 1.2 we will provide a summary (bullet points) of
the changes.
Change log (always up to date):
http://cvs.sourceforge.net/viewcvs.py/wicket/wicket/xdocs/changes.xml?view=markup
Juergen
On 12/27/05, Gili
Added to the wiki at http://www.wicket-wiki.org.uk/wiki/index.php/Best_Practices_and_Gotchas#Wicket_Servlet_Mapping
regards
On 12/27/05, Martijn Dashorst [EMAIL PROTECTED] wrote:
What you do here is quite harmless... The page is already in the
session (page map and all), so the extra reference to
shh, of course. The response shouldn't just be the panel - it should be
an entire Page! That makes sense.
Thanks for your help, I'll keep my progress posted here.
Emergence Dinterstage wrote:
On 12/28/05, R.J. Lorimer [EMAIL PROTECTED] wrote:
ComponentRequestTarget re-renders components
this was due to a new check we introduced. basically it would throw an error if you try to add a component that already had a parent set. this would help users catch errors in certain situtations, but obviously caused problems in others.
i changed it so now the component is removed from its
Thanks for the quick answer.
I've digged a little bit in the code, because now that I know what
you've done to suppress the bug, I think the initial idea was
interesting (throwing the exception).
I saw that the bug occurs because OrderedRepeatingView calls
super.removeAll() (i.e.
