You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Chris Lintz <ch...@gmail.com> on 2007/10/29 19:38:19 UTC
Is Beta5 coming soon? Beta4 has caused these issues for us....
Any chance of getting a Beta5 out soon. As luck would have it, Beta4 to say
the least has been frustrating for us.
So far beta4 has caused these problems in our app (all stuff that worked in
Beta3)
1) AJAXLink is broke when using the Crypted URL encoding strategy.
2) StringResourceModel change on toString() method (this is fine, we
refactored and are now using getString() )
3) UpdateFeedback gone -
http://www.nabble.com/1.3.0-beta4%3A-updateFeedback%28%29-gone--tf4707707.html
4) Pages are stateful now because of -
http://www.nabble.com/Stateless-page-creating-session-tf4604432.html#a13147396
Any chance of getting a Wicket beta5 out with at least the stateless page
fix? We have a high traffic site so the thought of generating some where
in the neighborhood of hundreds of thousands session IDs on disk for pages
as simple as a WebMarkupcontainer and a Label is very scary thought.
chris
--
View this message in context: http://www.nabble.com/Is-Beta5-coming-soon---Beta4-has-caused-these-issues-for-us....-tf4713647.html#a13473915
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by Erik van Oosten <e....@grons.nl>.
Hi,
You mostly get NoSuchMethodErrors if one of the slf4j jars on your
classpath is too old. But I guess you already knew that. You may find
more help on the sl4j site.
Regards,
Erik.
PS. on the dev list there was a vote with the result that Wicket 1.3 RC1
will be build (not released?) on Sunday.
landry soules wrote:
> Hello
>
> Please Al, what is the fix for this problem with slf4j ?
> I spent half a day trying every possible combination between log4j and
> slf4j, and got nothing but a strong headache ( and "NoSuchMethodError") !!!
>
>
>
--
Erik van Oosten
http://2008.rubyenrails.nl/
http://day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by Cristi Manole <cr...@gmail.com>.
This is what i use :
log4j-1.2.15.jar
slf4j-api-1.4.3.jar
slf4j-log4j12-1.4.3.jar
with wicket 1.3.0beta4.
I got the same annoying exception before upgrading to those log4j/slf4 versions.
On Nov 3, 2007 1:24 PM, Erik van Oosten <e....@grons.nl> wrote:
>
> And what is the version of your slfj-api.jar?
>
> Erik.
>
>
> landry soules wrote:
> > Thanks for your answers, but still no success :
> > I tried (once again) to use maven to generate a brand new project, but
> > eclipse freezes when i import the project generated with "mvn
> > eclipse:eclipse -DdownloadSources=true"...
> >
> > Is there something i'm missing ? In my classpath, i have
> > slf4j-log4j12-1.4.2.jar + log4j-1.2.14.jar, and still the infamous
> > "NoSuchMethodError"
> >
> > Should i better rollback to wicket 1.3 beta2 ?
> >
> >
> >
> >
>
> --
> Erik van Oosten
> http://2008.rubyenrails.nl/
> http://day-to-day-stuff.blogspot.com/
>
>
> ---------------------------------------------------------------------
>
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by Erik van Oosten <e....@grons.nl>.
And what is the version of your slfj-api.jar?
Erik.
landry soules wrote:
> Thanks for your answers, but still no success :
> I tried (once again) to use maven to generate a brand new project, but
> eclipse freezes when i import the project generated with "mvn
> eclipse:eclipse -DdownloadSources=true"...
>
> Is there something i'm missing ? In my classpath, i have
> slf4j-log4j12-1.4.2.jar + log4j-1.2.14.jar, and still the infamous
> "NoSuchMethodError"
>
> Should i better rollback to wicket 1.3 beta2 ?
>
>
>
>
--
Erik van Oosten
http://2008.rubyenrails.nl/
http://day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by Johan Compagner <jc...@gmail.com>.
are you really sure that you dont have also an older version somewhere
in the classpath? you can try to start java with -verbose:gc
On 11/2/07, landry soules <la...@gmail.com> wrote:
> Actually, i didn't go on with maven, since my project is already quite
> advanced now, i don't want to reconfigure it to use maven. I just tried to
> create a sample project to figure out what is the correct combination of
> slf4j/log4j to use (bad idea, since it appears to be broken in the original
> wicket pom).
> So i'm back in my real eclipse project, and this neverending error :
>
> Exception in thread "ModificationWatcher Task" java.lang.NoSuchMethodError:
> org.slf4j.Logger.isTraceEnabled()Z
> at org.apache.wicket.util.thread.Task$1.run(Task.java:103)
> at java.lang.Thread.run(Thread.java:595)
>
> even though i'm using slf4j-log4j12-1.4.2.jar + log4j-1.2.14.jar.
>
>
>
> 2007/11/2, Gwyn Evans <gw...@gmail.com>:
> >
> > Hi landry,
> >
> > Did you modify the SLF version specified in the created pom.xml before
> > trying to import it?
> >
> > /Gwyn
> >
> > Friday, November 2, 2007, 8:36:37 PM, landry soules <
> > landry.p.soules@gmail.com> wrote:
> >
> > ls> Thanks for your answers, but still no success :
> > ls> I tried (once again) to use maven to generate a brand new project, but
> > ls> eclipse freezes when i import the project generated with "mvn
> > ls> eclipse:eclipse -DdownloadSources=true"...
> >
> > ls> Is there something i'm missing ? In my classpath, i have
> > ls> slf4j-log4j12-1.4.2.jar + log4j-1.2.14.jar, and still the infamous
> > ls> "NoSuchMethodError"
> >
> > ls> Should i better rollback to wicket 1.3 beta2 ?
> >
> >
> > ls> 2007/11/2, Gerolf Seitz <ge...@gmail.com>:
> > >>
> > >> you have to use slf4j version 1.4.2 (instead of 1.0.x) in your pom file
> > >>
> > >> Gerolf
> > >>
> > >> On Nov 2, 2007 8:11 PM, landry soules <la...@gmail.com>
> > wrote:
> > >>
> > >> > Hello
> > >> >
> > >> > Please Al, what is the fix for this problem with slf4j ?
> > >> > I spent half a day trying every possible combination between log4j
> > and
> > >> > slf4j, and got nothing but a strong headache ( and
> > "NoSuchMethodError")
> > >> > !!!
> > >> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by Eelco Hillenius <ee...@gmail.com>.
> I finally won't take your time anymore with my problem of dependencies : it
> was a simple PEBCAK !
> I got the following error :
> Exception in thread "ModificationWatcher Task" java.lang.NoSuchMethodError:
> org.apache.log4j.Logger.isTraceEnabled()Z
>
> It was coming from log4j.Logger, not from slf4j.Logger, and the cause was i
> used cayenne.jar (wich contains cayenne and all its dependencies, including
> an older version of log4j) , instead of cayenne-nodeps.jar !
Nasty :-)
Eelco
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by landry soules <la...@gmail.com>.
Hello guys
I finally won't take your time anymore with my problem of dependencies : it
was a simple PEBCAK !
I got the following error :
Exception in thread "ModificationWatcher Task" java.lang.NoSuchMethodError:
org.apache.log4j.Logger.isTraceEnabled()Z
It was coming from log4j.Logger, not from slf4j.Logger, and the cause was i
used cayenne.jar (wich contains cayenne and all its dependencies, including
an older version of log4j) , instead of cayenne-nodeps.jar !
Al, i owe you a beer if you come to Paris ;-)
Thanks a lot for your patience.
2007/11/4, Al Maw <wi...@almaw.com>:
>
> landry soules wrote:
> > Sorry Al, but you lost your money ;-)
> >
> > I put back slf4j-api-1.4.2.jar , and still the same problem... Using the
> > jars suggested by Cristi doesn't help either. But since it seems i'm the
> > only one to still have the problem, must be a problem with my classpath.
> I
> > will recheck after deploying the project in a war. Maybe it's just
> eclipse
> > WTP that does some weird things with my classpath.
> > As always, thanks a lot for your support, guys.
>
> Gah. Can't believe you haven't sorted this issue out yet!
>
> It's conceptually really simple...
>
> org.slf4j.Logger#isTraceEnabled()
>
> ...is a method in the org.slf4j.Logger interface. That interface is in
> the main SLF4J API JAR.
>
> The isTraceEnabled() method, according to the javadoc, has been
> available in that interface since version 1.4.
>
> So you either don't have slf4j-api-1.4.x on your classpath, or you also
> have a version prior to 1.4 also your classpath which is being picked up
> instead.
>
> If both of those two things weren't the case, you wouldn't be having
> this issue.
>
> To check the classpath of a running project in Eclipse, Right click on
> the root node in the debug dialog and choose "Properties". You can find
> the classpath in the dialog that is shown.
>
>
> Regards,
>
> Al
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by Al Maw <wi...@almaw.com>.
landry soules wrote:
> Sorry Al, but you lost your money ;-)
>
> I put back slf4j-api-1.4.2.jar , and still the same problem... Using the
> jars suggested by Cristi doesn't help either. But since it seems i'm the
> only one to still have the problem, must be a problem with my classpath. I
> will recheck after deploying the project in a war. Maybe it's just eclipse
> WTP that does some weird things with my classpath.
> As always, thanks a lot for your support, guys.
Gah. Can't believe you haven't sorted this issue out yet!
It's conceptually really simple...
org.slf4j.Logger#isTraceEnabled()
...is a method in the org.slf4j.Logger interface. That interface is in
the main SLF4J API JAR.
The isTraceEnabled() method, according to the javadoc, has been
available in that interface since version 1.4.
So you either don't have slf4j-api-1.4.x on your classpath, or you also
have a version prior to 1.4 also your classpath which is being picked up
instead.
If both of those two things weren't the case, you wouldn't be having
this issue.
To check the classpath of a running project in Eclipse, Right click on
the root node in the debug dialog and choose "Properties". You can find
the classpath in the dialog that is shown.
Regards,
Al
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by Frank Bille <fr...@apache.org>.
On 11/4/07, landry soules <la...@gmail.com> wrote:
>
> (eclipse only retains the newer lines, erasing the olders)
Preferences -> Run/Debug -> Console -> Limit console output
Frank
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by landry soules <la...@gmail.com>.
Actually, it seems that the option "class" is useful in my case, not "gc"
I couldn't find yet slf4j.Logger among the thousands lines generated(eclipse
only retains the newer lines, erasing the olders), but i found something
interesting :
log4j.Logger is loaded from cayenne.jar...
I'm quite puzzled : do i have to start spamming cayenne users list ? Or is
this a bug (or at least a dangerous implementation) in beta4, that can cause
problems not only with Cayenne, but also with some other frameworks ? Or
maybe i can change the classpath load order in eclipse ?
Thanks for your support.
2007/11/4, Johan Compagner <jc...@gmail.com>:
>
> no i don't think Al lost,
> 1.4.2 or 1.4.3 that shouldn't matter
> But somewhere in your classpath you have and old version of 1 of the jars
>
> Please start the java process up with -verbose:gc and see what jar file it
> gives for org.slf4j.Logger
>
> johan
>
>
>
> On 11/4/07, landry soules <la...@gmail.com> wrote:
> >
> > Sorry Al, but you lost your money ;-)
> >
> > I put back slf4j-api-1.4.2.jar , and still the same problem... Using the
> > jars suggested by Cristi doesn't help either. But since it seems i'm the
> > only one to still have the problem, must be a problem with my classpath.
> I
> > will recheck after deploying the project in a war. Maybe it's just
> eclipse
> > WTP that does some weird things with my classpath.
> > As always, thanks a lot for your support, guys.
> >
> > 2007/11/3, Al Maw <wi...@almaw.com>:
> > >
> > > landry soules wrote:
> > > > Actually, i didn't go on with maven, since my project is already
> quite
> > > > advanced now, i don't want to reconfigure it to use maven. I just
> > tried
> > > to
> > > > create a sample project to figure out what is the correct
> combination
> > of
> > > > slf4j/log4j to use (bad idea, since it appears to be broken in the
> > > original
> > > > wicket pom).
> > > > So i'm back in my real eclipse project, and this neverending error :
> > > >
> > > > Exception in thread "ModificationWatcher Task"
> > > java.lang.NoSuchMethodError:
> > > > org.slf4j.Logger.isTraceEnabled()Z
> > > > at org.apache.wicket.util.thread.Task$1.run(Task.java:103)
> > > > at java.lang.Thread.run(Thread.java:595)
> > > >
> > > > even though i'm using slf4j-log4j12-1.4.2.jar + log4j-1.2.14.jar.
> > >
> > > You also need slf4j-api-1.4.2.jar. I'd lay money on your not having
> that
> > > version on your classpath (or having an earlier version as well).
> > >
> > > Regards,
> > >
> > > Al
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
>
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by Johan Compagner <jc...@gmail.com>.
no i don't think Al lost,
1.4.2 or 1.4.3 that shouldn't matter
But somewhere in your classpath you have and old version of 1 of the jars
Please start the java process up with -verbose:gc and see what jar file it
gives for org.slf4j.Logger
johan
On 11/4/07, landry soules <la...@gmail.com> wrote:
>
> Sorry Al, but you lost your money ;-)
>
> I put back slf4j-api-1.4.2.jar , and still the same problem... Using the
> jars suggested by Cristi doesn't help either. But since it seems i'm the
> only one to still have the problem, must be a problem with my classpath. I
> will recheck after deploying the project in a war. Maybe it's just eclipse
> WTP that does some weird things with my classpath.
> As always, thanks a lot for your support, guys.
>
> 2007/11/3, Al Maw <wi...@almaw.com>:
> >
> > landry soules wrote:
> > > Actually, i didn't go on with maven, since my project is already quite
> > > advanced now, i don't want to reconfigure it to use maven. I just
> tried
> > to
> > > create a sample project to figure out what is the correct combination
> of
> > > slf4j/log4j to use (bad idea, since it appears to be broken in the
> > original
> > > wicket pom).
> > > So i'm back in my real eclipse project, and this neverending error :
> > >
> > > Exception in thread "ModificationWatcher Task"
> > java.lang.NoSuchMethodError:
> > > org.slf4j.Logger.isTraceEnabled()Z
> > > at org.apache.wicket.util.thread.Task$1.run(Task.java:103)
> > > at java.lang.Thread.run(Thread.java:595)
> > >
> > > even though i'm using slf4j-log4j12-1.4.2.jar + log4j-1.2.14.jar.
> >
> > You also need slf4j-api-1.4.2.jar. I'd lay money on your not having that
> > version on your classpath (or having an earlier version as well).
> >
> > Regards,
> >
> > Al
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by landry soules <la...@gmail.com>.
Sorry Al, but you lost your money ;-)
I put back slf4j-api-1.4.2.jar , and still the same problem... Using the
jars suggested by Cristi doesn't help either. But since it seems i'm the
only one to still have the problem, must be a problem with my classpath. I
will recheck after deploying the project in a war. Maybe it's just eclipse
WTP that does some weird things with my classpath.
As always, thanks a lot for your support, guys.
2007/11/3, Al Maw <wi...@almaw.com>:
>
> landry soules wrote:
> > Actually, i didn't go on with maven, since my project is already quite
> > advanced now, i don't want to reconfigure it to use maven. I just tried
> to
> > create a sample project to figure out what is the correct combination of
> > slf4j/log4j to use (bad idea, since it appears to be broken in the
> original
> > wicket pom).
> > So i'm back in my real eclipse project, and this neverending error :
> >
> > Exception in thread "ModificationWatcher Task"
> java.lang.NoSuchMethodError:
> > org.slf4j.Logger.isTraceEnabled()Z
> > at org.apache.wicket.util.thread.Task$1.run(Task.java:103)
> > at java.lang.Thread.run(Thread.java:595)
> >
> > even though i'm using slf4j-log4j12-1.4.2.jar + log4j-1.2.14.jar.
>
> You also need slf4j-api-1.4.2.jar. I'd lay money on your not having that
> version on your classpath (or having an earlier version as well).
>
> Regards,
>
> Al
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by Al Maw <wi...@almaw.com>.
landry soules wrote:
> Actually, i didn't go on with maven, since my project is already quite
> advanced now, i don't want to reconfigure it to use maven. I just tried to
> create a sample project to figure out what is the correct combination of
> slf4j/log4j to use (bad idea, since it appears to be broken in the original
> wicket pom).
> So i'm back in my real eclipse project, and this neverending error :
>
> Exception in thread "ModificationWatcher Task" java.lang.NoSuchMethodError:
> org.slf4j.Logger.isTraceEnabled()Z
> at org.apache.wicket.util.thread.Task$1.run(Task.java:103)
> at java.lang.Thread.run(Thread.java:595)
>
> even though i'm using slf4j-log4j12-1.4.2.jar + log4j-1.2.14.jar.
You also need slf4j-api-1.4.2.jar. I'd lay money on your not having that
version on your classpath (or having an earlier version as well).
Regards,
Al
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by landry soules <la...@gmail.com>.
Actually, i didn't go on with maven, since my project is already quite
advanced now, i don't want to reconfigure it to use maven. I just tried to
create a sample project to figure out what is the correct combination of
slf4j/log4j to use (bad idea, since it appears to be broken in the original
wicket pom).
So i'm back in my real eclipse project, and this neverending error :
Exception in thread "ModificationWatcher Task" java.lang.NoSuchMethodError:
org.slf4j.Logger.isTraceEnabled()Z
at org.apache.wicket.util.thread.Task$1.run(Task.java:103)
at java.lang.Thread.run(Thread.java:595)
even though i'm using slf4j-log4j12-1.4.2.jar + log4j-1.2.14.jar.
2007/11/2, Gwyn Evans <gw...@gmail.com>:
>
> Hi landry,
>
> Did you modify the SLF version specified in the created pom.xml before
> trying to import it?
>
> /Gwyn
>
> Friday, November 2, 2007, 8:36:37 PM, landry soules <
> landry.p.soules@gmail.com> wrote:
>
> ls> Thanks for your answers, but still no success :
> ls> I tried (once again) to use maven to generate a brand new project, but
> ls> eclipse freezes when i import the project generated with "mvn
> ls> eclipse:eclipse -DdownloadSources=true"...
>
> ls> Is there something i'm missing ? In my classpath, i have
> ls> slf4j-log4j12-1.4.2.jar + log4j-1.2.14.jar, and still the infamous
> ls> "NoSuchMethodError"
>
> ls> Should i better rollback to wicket 1.3 beta2 ?
>
>
> ls> 2007/11/2, Gerolf Seitz <ge...@gmail.com>:
> >>
> >> you have to use slf4j version 1.4.2 (instead of 1.0.x) in your pom file
> >>
> >> Gerolf
> >>
> >> On Nov 2, 2007 8:11 PM, landry soules <la...@gmail.com>
> wrote:
> >>
> >> > Hello
> >> >
> >> > Please Al, what is the fix for this problem with slf4j ?
> >> > I spent half a day trying every possible combination between log4j
> and
> >> > slf4j, and got nothing but a strong headache ( and
> "NoSuchMethodError")
> >> > !!!
> >> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by Gwyn Evans <gw...@gmail.com>.
Hi landry,
Did you modify the SLF version specified in the created pom.xml before
trying to import it?
/Gwyn
Friday, November 2, 2007, 8:36:37 PM, landry soules <la...@gmail.com> wrote:
ls> Thanks for your answers, but still no success :
ls> I tried (once again) to use maven to generate a brand new project, but
ls> eclipse freezes when i import the project generated with "mvn
ls> eclipse:eclipse -DdownloadSources=true"...
ls> Is there something i'm missing ? In my classpath, i have
ls> slf4j-log4j12-1.4.2.jar + log4j-1.2.14.jar, and still the infamous
ls> "NoSuchMethodError"
ls> Should i better rollback to wicket 1.3 beta2 ?
ls> 2007/11/2, Gerolf Seitz <ge...@gmail.com>:
>>
>> you have to use slf4j version 1.4.2 (instead of 1.0.x) in your pom file
>>
>> Gerolf
>>
>> On Nov 2, 2007 8:11 PM, landry soules <la...@gmail.com> wrote:
>>
>> > Hello
>> >
>> > Please Al, what is the fix for this problem with slf4j ?
>> > I spent half a day trying every possible combination between log4j and
>> > slf4j, and got nothing but a strong headache ( and "NoSuchMethodError")
>> > !!!
>> >
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by landry soules <la...@gmail.com>.
Thanks for your answers, but still no success :
I tried (once again) to use maven to generate a brand new project, but
eclipse freezes when i import the project generated with "mvn
eclipse:eclipse -DdownloadSources=true"...
Is there something i'm missing ? In my classpath, i have
slf4j-log4j12-1.4.2.jar + log4j-1.2.14.jar, and still the infamous
"NoSuchMethodError"
Should i better rollback to wicket 1.3 beta2 ?
2007/11/2, Gerolf Seitz <ge...@gmail.com>:
>
> you have to use slf4j version 1.4.2 (instead of 1.0.x) in your pom file
>
> Gerolf
>
> On Nov 2, 2007 8:11 PM, landry soules <la...@gmail.com> wrote:
>
> > Hello
> >
> > Please Al, what is the fix for this problem with slf4j ?
> > I spent half a day trying every possible combination between log4j and
> > slf4j, and got nothing but a strong headache ( and "NoSuchMethodError")
> > !!!
> >
> >
> >
> >
> > 2007/10/30, Al Maw <wi...@almaw.com>:
> > >
> > > Chris Lintz wrote:
> > > > Any chance of getting a Beta5 out soon. As luck would have it,
> Beta4
> > > to say
> > > > the least has been frustrating for us.
> > > >
> > > > So far beta4 has caused these problems in our app (all stuff that
> > worked
> > > in
> > > > Beta3)
> > > >
> > > > 1) AJAXLink is broke when using the Crypted URL encoding strategy.
> > > > 2) StringResourceModel change on toString() method (this is fine, we
> > > > refactored and are now using getString() )
> > > > 3) UpdateFeedback gone -
> > > >
> > >
> >
> http://www.nabble.com/1.3.0-beta4%3A-updateFeedback%28%29-gone--tf4707707.html
> > > > 4) Pages are stateful now because of -
> > > >
> > >
> >
> http://www.nabble.com/Stateless-page-creating-session-tf4604432.html#a13147396
> > > >
> > > > Any chance of getting a Wicket beta5 out with at least the stateless
> > > page
> > > > fix? We have a high traffic site so the thought of generating some
> > > where
> > > > in the neighborhood of hundreds of thousands session IDs on disk for
> > > pages
> > > > as simple as a WebMarkupcontainer and a Label is very scary thought.
> > >
> > > Additionally, the maven 2 quickstart is broken because it uses the
> wrong
> > > version of slf4j-log4j (which results in a NoSuchMethodError). Easy to
> > > fix if you know how, but not good that you should have to. ;-(
> > >
> > > +1 on getting beta 5 out ASAP.
> > >
> > > Al
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
>
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by Gerolf Seitz <ge...@gmail.com>.
you have to use slf4j version 1.4.2 (instead of 1.0.x) in your pom file
Gerolf
On Nov 2, 2007 8:11 PM, landry soules <la...@gmail.com> wrote:
> Hello
>
> Please Al, what is the fix for this problem with slf4j ?
> I spent half a day trying every possible combination between log4j and
> slf4j, and got nothing but a strong headache ( and "NoSuchMethodError")
> !!!
>
>
>
>
> 2007/10/30, Al Maw <wi...@almaw.com>:
> >
> > Chris Lintz wrote:
> > > Any chance of getting a Beta5 out soon. As luck would have it, Beta4
> > to say
> > > the least has been frustrating for us.
> > >
> > > So far beta4 has caused these problems in our app (all stuff that
> worked
> > in
> > > Beta3)
> > >
> > > 1) AJAXLink is broke when using the Crypted URL encoding strategy.
> > > 2) StringResourceModel change on toString() method (this is fine, we
> > > refactored and are now using getString() )
> > > 3) UpdateFeedback gone -
> > >
> >
> http://www.nabble.com/1.3.0-beta4%3A-updateFeedback%28%29-gone--tf4707707.html
> > > 4) Pages are stateful now because of -
> > >
> >
> http://www.nabble.com/Stateless-page-creating-session-tf4604432.html#a13147396
> > >
> > > Any chance of getting a Wicket beta5 out with at least the stateless
> > page
> > > fix? We have a high traffic site so the thought of generating some
> > where
> > > in the neighborhood of hundreds of thousands session IDs on disk for
> > pages
> > > as simple as a WebMarkupcontainer and a Label is very scary thought.
> >
> > Additionally, the maven 2 quickstart is broken because it uses the wrong
> > version of slf4j-log4j (which results in a NoSuchMethodError). Easy to
> > fix if you know how, but not good that you should have to. ;-(
> >
> > +1 on getting beta 5 out ASAP.
> >
> > Al
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by landry soules <la...@gmail.com>.
Hello
Please Al, what is the fix for this problem with slf4j ?
I spent half a day trying every possible combination between log4j and
slf4j, and got nothing but a strong headache ( and "NoSuchMethodError") !!!
2007/10/30, Al Maw <wi...@almaw.com>:
>
> Chris Lintz wrote:
> > Any chance of getting a Beta5 out soon. As luck would have it, Beta4
> to say
> > the least has been frustrating for us.
> >
> > So far beta4 has caused these problems in our app (all stuff that worked
> in
> > Beta3)
> >
> > 1) AJAXLink is broke when using the Crypted URL encoding strategy.
> > 2) StringResourceModel change on toString() method (this is fine, we
> > refactored and are now using getString() )
> > 3) UpdateFeedback gone -
> >
> http://www.nabble.com/1.3.0-beta4%3A-updateFeedback%28%29-gone--tf4707707.html
> > 4) Pages are stateful now because of -
> >
> http://www.nabble.com/Stateless-page-creating-session-tf4604432.html#a13147396
> >
> > Any chance of getting a Wicket beta5 out with at least the stateless
> page
> > fix? We have a high traffic site so the thought of generating some
> where
> > in the neighborhood of hundreds of thousands session IDs on disk for
> pages
> > as simple as a WebMarkupcontainer and a Label is very scary thought.
>
> Additionally, the maven 2 quickstart is broken because it uses the wrong
> version of slf4j-log4j (which results in a NoSuchMethodError). Easy to
> fix if you know how, but not good that you should have to. ;-(
>
> +1 on getting beta 5 out ASAP.
>
> Al
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by Al Maw <wi...@almaw.com>.
Chris Lintz wrote:
> Any chance of getting a Beta5 out soon. As luck would have it, Beta4 to say
> the least has been frustrating for us.
>
> So far beta4 has caused these problems in our app (all stuff that worked in
> Beta3)
>
> 1) AJAXLink is broke when using the Crypted URL encoding strategy.
> 2) StringResourceModel change on toString() method (this is fine, we
> refactored and are now using getString() )
> 3) UpdateFeedback gone -
> http://www.nabble.com/1.3.0-beta4%3A-updateFeedback%28%29-gone--tf4707707.html
> 4) Pages are stateful now because of -
> http://www.nabble.com/Stateless-page-creating-session-tf4604432.html#a13147396
>
> Any chance of getting a Wicket beta5 out with at least the stateless page
> fix? We have a high traffic site so the thought of generating some where
> in the neighborhood of hundreds of thousands session IDs on disk for pages
> as simple as a WebMarkupcontainer and a Label is very scary thought.
Additionally, the maven 2 quickstart is broken because it uses the wrong
version of slf4j-log4j (which results in a NoSuchMethodError). Easy to
fix if you know how, but not good that you should have to. ;-(
+1 on getting beta 5 out ASAP.
Al
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by Frank Bille <fr...@apache.org>.
On 10/30/07, Johan Compagner <jc...@gmail.com> wrote:
>
> +1
> i hope that i can close more issues tonight and the comming nights.
> so that the issues are down a little bit when beta5 is released.
>
> johan
johan++
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by Johan Compagner <jc...@gmail.com>.
+1
i hope that i can close more issues tonight and the comming nights.
so that the issues are down a little bit when beta5 is released.
johan
On 10/29/07, Frank Bille <fr...@apache.org> wrote:
>
> Well, I have time on sunday to build the release. What do the other devs
> think?
>
> Frank
>
>
> On 10/29/07, Chris Lintz <ch...@gmail.com> wrote:
> >
> >
> > Any chance of getting a Beta5 out soon. As luck would have it, Beta4
> to
> > say
> > the least has been frustrating for us.
> >
> > So far beta4 has caused these problems in our app (all stuff that worked
> > in
> > Beta3)
> >
> > 1) AJAXLink is broke when using the Crypted URL encoding strategy.
> > 2) StringResourceModel change on toString() method (this is fine, we
> > refactored and are now using getString() )
> > 3) UpdateFeedback gone -
> >
> >
> http://www.nabble.com/1.3.0-beta4%3A-updateFeedback%28%29-gone--tf4707707.html
> > 4) Pages are stateful now because of -
> >
> >
> http://www.nabble.com/Stateless-page-creating-session-tf4604432.html#a13147396
> >
> > Any chance of getting a Wicket beta5 out with at least the stateless
> page
> > fix? We have a high traffic site so the thought of generating some
> where
> > in the neighborhood of hundreds of thousands session IDs on disk for
> pages
> > as simple as a WebMarkupcontainer and a Label is very scary thought.
> >
> >
> >
> >
> > chris
> > --
> > View this message in context:
> >
> http://www.nabble.com/Is-Beta5-coming-soon---Beta4-has-caused-these-issues-for-us....-tf4713647.html#a13473915
> > Sent from the Wicket - User mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by Frank Bille <fr...@apache.org>.
Well, I have time on sunday to build the release. What do the other devs
think?
Frank
On 10/29/07, Chris Lintz <ch...@gmail.com> wrote:
>
>
> Any chance of getting a Beta5 out soon. As luck would have it, Beta4 to
> say
> the least has been frustrating for us.
>
> So far beta4 has caused these problems in our app (all stuff that worked
> in
> Beta3)
>
> 1) AJAXLink is broke when using the Crypted URL encoding strategy.
> 2) StringResourceModel change on toString() method (this is fine, we
> refactored and are now using getString() )
> 3) UpdateFeedback gone -
>
> http://www.nabble.com/1.3.0-beta4%3A-updateFeedback%28%29-gone--tf4707707.html
> 4) Pages are stateful now because of -
>
> http://www.nabble.com/Stateless-page-creating-session-tf4604432.html#a13147396
>
> Any chance of getting a Wicket beta5 out with at least the stateless page
> fix? We have a high traffic site so the thought of generating some where
> in the neighborhood of hundreds of thousands session IDs on disk for pages
> as simple as a WebMarkupcontainer and a Label is very scary thought.
>
>
>
>
> chris
> --
> View this message in context:
> http://www.nabble.com/Is-Beta5-coming-soon---Beta4-has-caused-these-issues-for-us....-tf4713647.html#a13473915
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by Matej Knopp <ma...@gmail.com>.
Looks like the FormComponentFeedbackBorder is not fixed yet. Will fix today.
-Matej
On 10/29/07, Eelco Hillenius <ee...@gmail.com> wrote:
> > 4) Pages are stateful now because of -
> > http://www.nabble.com/Stateless-page-creating-session-tf4604432.html#a13147396
>
> Ah, I missed this. I fixed the example yesterday, thinking I missed a
> deliberate change. But turns out it was a bug after all. Also here, we
> need to have a test case. Anyone care to help with that?
>
> Eelco
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Is Beta5 coming soon? Beta4 has caused these issues for us....
Posted by Eelco Hillenius <ee...@gmail.com>.
> 4) Pages are stateful now because of -
> http://www.nabble.com/Stateless-page-creating-session-tf4604432.html#a13147396
Ah, I missed this. I fixed the example yesterday, thinking I missed a
deliberate change. But turns out it was a bug after all. Also here, we
need to have a test case. Anyone care to help with that?
Eelco
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org