automatically marking pages as stateless: is this really a good idea?
I'm wondering whether it still is a good idea to automatically mark pages as stateless if there are no 'statefull' components/ callbacks on it. It's not so much a problem that the page isn't stored - it isn't as there aren't any non-bookmarkable callbacks to it - but it can be a problem that a session isn't automatically created. See for example http://www.nabble.com/Re%3A-noob-question-about-wicket-p3903.html I'm not sure... on the one hand I like it that Wicket tries to be as efficient as it can be with storing stuff and creating sessions. On the other hand, like the referenced thread shows (if I'm right there), it can lead to situations people don't immediately understand. I'm leaning towards prefering the current situation, but I thought this would be a good time to get your opinions on this. Cheers, Eelco
Re: remove test scope for slf4j in pom.xml
Oleg Taranenko a écrit : Hello Jean-Baptiste, Wednesday, June 13, 2007, 12:35:39 PM, you wrote: * Oleg Taranenko: Now I'm viewing wicket stuffs und some projects not started under mvn jetty:run reason of Please mention the WS projects at fault, we need to fix them. pickwick ;) Hi, I've just fixed it, have fun with pickwick ;) -- Vincent others are forgeted after my "workaround" had been founded...
Re: remove test scope for slf4j in pom.xml
* Oleg Taranenko: > Hmm... So why slf4j-api not scoped to test? Because the slf4j API is used everywhere in Wicket classes. Don't worry we are fixing Pickwick right now, and obviously WS Dojo as well. -- Jean-Baptiste Quenot aka John Banana Qwerty http://caraldi.com/jbq/
Re: remove test scope for slf4j in pom.xml
Hmm... So why slf4j-api not scoped to test?
> It is in fact the project you are trying to run that is at fault here.
> Wicket doesn't prescribe which logging framework one should use.
> Therefore the examples projects need to choose their own logging
> implementation. This holds for the wicket-examples from Apache as well
> as for wicket stuff related projects.
> Therefore, test is correct (for the wicket framework
> libraries).
> Martijn
> On 6/13/07, Oleg Taranenko <[EMAIL PROTECTED]> wrote:
>> Hello, wicket-dev,
>>
>> Now I'm viewing wicket stuffs und some projects not started under
>> mvn jetty:run reason of
>>
>> ...
>> 2007-06-13 09:32:42.952::INFO: jetty-6.1.4rc1
>> 2007-06-13 09:32:43.687::INFO: No Transaction manager found - if your
>> webapp requires one, please c
>> onfigure one.
>> 2007-06-13 09:32:44.155::WARN: failed wicket
>> java.lang.NoClassDefFoundError: org/slf4j/impl/StaticLoggerBinder
>> at org.slf4j.LoggerFactory.(LoggerFactory.java:57)
>> at
>> org.apache.wicket.protocol.http.WicketFilter.(WicketFilter.java:71)
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>> Method)
>> at
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:
>>
>>
>> I'm using trunk version of the Wicket and jdk 1.5.
>>
>> Artefact slf4j-log4j12-1.3.1.jar is not included into startup
>> classpath for jetty! Removing line 411 in the pom.xml
>> will bug disappear.
>>
>> ${trunk}/pom.xml
>>
>> 408
>> 409org.slf4j
>> 410slf4j-log4j12
>> 411test
>> 412
>>
>>
>> Could this line be removed from pom.xml?
>> May be file a Jira issue?
>>
>> --
>>
>> Oleg Taranenko
>> mailto:[EMAIL PROTECTED]
>>
>>
>>
--
Mit freundlichen Grüßen
Oleg Taranenko
mailto:[EMAIL PROTECTED]
Re[2]: remove test scope for slf4j in pom.xml
Hello Jean-Baptiste, Wednesday, June 13, 2007, 12:35:39 PM, you wrote: > * Oleg Taranenko: >> Now I'm viewing wicket stuffs und some projects not started >> under mvn jetty:run reason of > Please mention the WS projects at fault, we need to fix them. pickwick ;) others are forgeted after my "workaround" had been founded... -- Best regards, Olegmailto:[EMAIL PROTECTED]
Re: remove test scope for slf4j in pom.xml
* Oleg Taranenko: > Now I'm viewing wicket stuffs und some projects not started > under mvn jetty:run reason of Please mention the WS projects at fault, we need to fix them. -- Jean-Baptiste Quenot aka John Banana Qwerty http://caraldi.com/jbq/
Re: remove test scope for slf4j in pom.xml
On Wednesday, June 13, 2007, 10:21:21 AM, Martijn <[EMAIL PROTECTED]> wrote: > On 6/13/07, Oleg Taranenko <[EMAIL PROTECTED]> wrote: >> Wednesday, June 13, 2007, 10:44:32 AM, you wrote: >> > It is in fact the project you are trying to run that is at fault here. >> > Wicket doesn't prescribe which logging framework one should use. >> > Therefore the examples projects need to choose their own logging >> > implementation. This holds for the wicket-examples from Apache as well >> > as for wicket stuff related projects. >> Hmm... So why slf4j-api not scoped to test? > Because that is the API to which we program. slf4j-log4j is an > implementation. Read up on the subject here: http://sfl4j.org That's http://www.slf4j.org/ :-) Basically, you program using the -api, then when you deploy, you add one of the implentation jars, e.g. slf4j-nop.jar, slf4j-simple.jar, slf4j-log4j12.jar, slf4j-log4j13.jar, slf4j-jdk14.jar or slf4j-jcl.jar, depending which actual logging implementation you want the logging to end up at. /Gwyn
Re: Re[2]: remove test scope for slf4j in pom.xml
On 6/13/07, Oleg Taranenko <[EMAIL PROTECTED]> wrote: Wednesday, June 13, 2007, 10:44:32 AM, you wrote: > It is in fact the project you are trying to run that is at fault here. > Wicket doesn't prescribe which logging framework one should use. > Therefore the examples projects need to choose their own logging > implementation. This holds for the wicket-examples from Apache as well > as for wicket stuff related projects. Hmm... So why slf4j-api not scoped to test? Because that is the API to which we program. slf4j-log4j is an implementation. Read up on the subject here: http://sfl4j.org Martijn -- Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.6 contains a very important fix. Download Wicket now! http://wicketframework.org
Re[2]: remove test scope for slf4j in pom.xml
Hello Martijn,
Wednesday, June 13, 2007, 10:44:32 AM, you wrote:
> It is in fact the project you are trying to run that is at fault here.
> Wicket doesn't prescribe which logging framework one should use.
> Therefore the examples projects need to choose their own logging
> implementation. This holds for the wicket-examples from Apache as well
> as for wicket stuff related projects.
Hmm... So why slf4j-api not scoped to test?
> Therefore, test is correct (for the wicket framework
> libraries).
> Martijn
> On 6/13/07, Oleg Taranenko <[EMAIL PROTECTED]> wrote:
>> Hello, wicket-dev,
>>
>> Now I'm viewing wicket stuffs und some projects not started under
>> mvn jetty:run reason of
>>
>> ...
>> 2007-06-13 09:32:42.952::INFO: jetty-6.1.4rc1
>> 2007-06-13 09:32:43.687::INFO: No Transaction manager found - if your
>> webapp requires one, please c
>> onfigure one.
>> 2007-06-13 09:32:44.155::WARN: failed wicket
>> java.lang.NoClassDefFoundError: org/slf4j/impl/StaticLoggerBinder
>> at org.slf4j.LoggerFactory.(LoggerFactory.java:57)
>> at
>> org.apache.wicket.protocol.http.WicketFilter.(WicketFilter.java:71)
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>> Method)
>> at
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:
>>
>>
>> I'm using trunk version of the Wicket and jdk 1.5.
>>
>> Artefact slf4j-log4j12-1.3.1.jar is not included into startup
>> classpath for jetty! Removing line 411 in the pom.xml
>> will bug disappear.
>>
>> ${trunk}/pom.xml
>>
>> 408
>> 409org.slf4j
>> 410slf4j-log4j12
>> 411test
>> 412
>>
>>
>> Could this line be removed from pom.xml?
>> May be file a Jira issue?
>>
>> --
>>
>> Oleg Taranenko
>> mailto:[EMAIL PROTECTED]
>>
>>
>>
--
Best regards,
Olegmailto:[EMAIL PROTECTED]
Re: remove test scope for slf4j in pom.xml
It is in fact the project you are trying to run that is at fault here.
Wicket doesn't prescribe which logging framework one should use.
Therefore the examples projects need to choose their own logging
implementation. This holds for the wicket-examples from Apache as well
as for wicket stuff related projects.
Therefore, test is correct (for the wicket framework libraries).
Martijn
On 6/13/07, Oleg Taranenko <[EMAIL PROTECTED]> wrote:
Hello, wicket-dev,
Now I'm viewing wicket stuffs und some projects not started under
mvn jetty:run reason of
...
2007-06-13 09:32:42.952::INFO: jetty-6.1.4rc1
2007-06-13 09:32:43.687::INFO: No Transaction manager found - if your webapp
requires one, please c
onfigure one.
2007-06-13 09:32:44.155::WARN: failed wicket
java.lang.NoClassDefFoundError: org/slf4j/impl/StaticLoggerBinder
at org.slf4j.LoggerFactory.(LoggerFactory.java:57)
at
org.apache.wicket.protocol.http.WicketFilter.(WicketFilter.java:71)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:
I'm using trunk version of the Wicket and jdk 1.5.
Artefact slf4j-log4j12-1.3.1.jar is not included into startup
classpath for jetty! Removing line 411 in the pom.xml
will bug disappear.
${trunk}/pom.xml
408
409org.slf4j
410slf4j-log4j12
411test
412
Could this line be removed from pom.xml?
May be file a Jira issue?
--
Oleg Taranenko
mailto:[EMAIL PROTECTED]
--
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.6 contains a very important fix. Download Wicket now!
http://wicketframework.org
remove test scope for slf4j in pom.xml
Hello, wicket-dev,
Now I'm viewing wicket stuffs und some projects not started under
mvn jetty:run reason of
...
2007-06-13 09:32:42.952::INFO: jetty-6.1.4rc1
2007-06-13 09:32:43.687::INFO: No Transaction manager found - if your webapp
requires one, please c
onfigure one.
2007-06-13 09:32:44.155::WARN: failed wicket
java.lang.NoClassDefFoundError: org/slf4j/impl/StaticLoggerBinder
at org.slf4j.LoggerFactory.(LoggerFactory.java:57)
at
org.apache.wicket.protocol.http.WicketFilter.(WicketFilter.java:71)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:
I'm using trunk version of the Wicket and jdk 1.5.
Artefact slf4j-log4j12-1.3.1.jar is not included into startup
classpath for jetty! Removing line 411 in the pom.xml
will bug disappear.
${trunk}/pom.xml
408
409org.slf4j
410slf4j-log4j12
411test
412
Could this line be removed from pom.xml?
May be file a Jira issue?
--
Oleg Taranenko
mailto:[EMAIL PROTECTED]
