Tonight I finally bit the bullet and built a release of wicketstuff-core to
match the 1.4-rc2 tag of Wicket. Now if you are using wicket 1.4-rc2, you
can also include any artifact that's a child of wicketstuff-core with the
version 1.4-rc2 as well, without having to home build your own.
The repo
thats the whole idea.
warnings/error (debug.error is fine by me) when we notice a Page reference
So that people can pick it up and change them
Then in 1.5 we will remove the code (and maybe throw just hard exceptions
right away)
Or if we can really fix it.
johan
On Tue, Mar 3, 2009 at 10:44,
welcome aboard.
mf
Am 03.03.2009 um 17:24 schrieb Igor Vaynberg:
done
-igor
On Tue, Mar 3, 2009 at 7:19 AM, Antony Stubbs
wrote:
sourceforge account: astubbs1
I want to work on gmap2 and bring wicket-contrib-groovy back to life.
Regards,
Antony Stubbs,
NZ
http://www.jeremythomerson.com/blog/2008/11/17/wicket-quickstart-tutorial/
On Tue, Mar 3, 2009 at 10:41 AM, Michael Mosmann wrote:
> Am Dienstag, den 03.03.2009, 08:18 -0800 schrieb Igor Vaynberg:
> > quickstart
>
> what does this mean?
>
> > and jira.
>
> done.
>
> mm:)
>
>
>
--
Jeremy Thom
On Tue, Mar 3, 2009 at 5:41 PM, Michael Mosmann wrote:
> Am Dienstag, den 03.03.2009, 08:18 -0800 schrieb Igor Vaynberg:
> > quickstart
>
> what does this mean?
http://www.nabble.com/Form-GET-doesn%27t-call-onSubmit-method-td19780009.html#a19785452
Maarten
>
>
> > and jira.
>
> done.
>
> m
Am Dienstag, den 03.03.2009, 08:18 -0800 schrieb Igor Vaynberg:
> quickstart
what does this mean?
> and jira.
done.
mm:)
Sorry to hijack your discussion, I just want to say that even if you
keep the serialization magic, adding warning/ error logs when such
references are found, at least in the development configuration, would
be a big plus, because these references not only may cause problems in
wicket core code, the
done
-igor
On Tue, Mar 3, 2009 at 7:19 AM, Antony Stubbs wrote:
> sourceforge account: astubbs1
>
> I want to work on gmap2 and bring wicket-contrib-groovy back to life.
>
> Regards,
> Antony Stubbs,
> NZ
>
>
quickstart and jira.
-igor
On Tue, Mar 3, 2009 at 2:07 AM, Michael Mosmann wrote:
> Hi,
>
> i wonder, if i do something wrong. But first the Code:
>
>
> import java.util.ArrayList;
> import java.util.Arrays;
> import java.util.Collection;
> im
sourceforge account: astubbs1
I want to work on gmap2 and bring wicket-contrib-groovy back to life.
Regards,
Antony Stubbs,
NZ
Hi,
i wonder, if i do something wrong. But first the Code:
import java.util.ArrayList;
import java.util.Arrays;
import java.util.Collection;
import java.util.List;
import org.apache.wicket.extensions.markup.html.form.palette.Palette;
import or
that looks the best to me
add the getPageReference() in 1.4 so people are going to play with it
and add a warning in the current code (that should be really simple and
point to the getPageReference())
Because if we remove it from 1.4 now when it is already RC this would mean
some breaks that are
I talked to Johan and he seems to feel quite strongly against removing
the code. So we can add PageReference, add warning when serializing
"nested" pages with message how to fix it (use page reference). And
the magic code will be gone in 1.5.
-Matej
On Tue, Mar 3, 2009 at 8:29 AM, Johan Compagner
done,
https://issues.apache.org/jira/browse/WICKET-2139
thanks igor
--
View this message in context:
http://www.nabble.com/RequestLogger-change---include-Page-Parameters-for-BookmarkablePages-tp22295982p22305001.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
14 matches
Mail list logo
