you can generate the stack traces.... -igor
On Dec 19, 2007 1:45 PM, Pills <[EMAIL PROTECTED]> wrote: > > > igor.vaynberg wrote: > > > > can you show us the two stack traces? > > > > -igor > > > > There is no really stack trace. I have this output in my console when I > launch it from eclipse. > > <code> > 19 déc. 2007 22:22:57 org.apache.catalina.core.AprLifecycleListener init > INFO: The Apache Tomcat Native library which allows optimal performance in > production environments was not found on the java.library.path: C:\Program > Files\MyEclipse 6.0\bin;C:\Program Files\MyEclipse > 6.0\myeclipse\eclipse\plugins\com.genuitec.eclipse.easie.tomcat.myeclipse_6.0.1.zmyeclipse601200710\tomcat\bin > 19 déc. 2007 22:22:57 org.apache.coyote.http11.Http11Protocol init > INFO: Initialisation de Coyote HTTP/1.1 sur http-8080 > 19 déc. 2007 22:22:57 org.apache.catalina.startup.Catalina load > INFO: Initialization processed in 1315 ms > 19 déc. 2007 22:22:57 org.apache.catalina.core.StandardService start > INFO: Démarrage du service Catalina > 19 déc. 2007 22:22:57 org.apache.catalina.core.StandardEngine start > INFO: Starting Servlet Engine: Apache Tomcat/6.0.13 > ******************************************************************** > *** WARNING: Wicket is running in DEVELOPMENT mode. *** > *** ^^^^^^^^^^^ *** > *** Do NOT deploy to your live server(s) without changing this. *** > *** See Application#getConfigurationType() for more information. *** > ******************************************************************** > 19 déc. 2007 22:23:07 org.apache.coyote.http11.Http11Protocol start > INFO: Démarrage de Coyote HTTP/1.1 sur http-8080 > 19 déc. 2007 22:23:07 org.apache.jk.common.ChannelSocket init > INFO: JK: ajp13 listening on /0.0.0.0:8009 > 19 déc. 2007 22:23:07 org.apache.jk.server.JkMain start > INFO: Jk running ID=0 time=0/140 config=null > 19 déc. 2007 22:23:07 org.apache.catalina.startup.Catalina start > INFO: Server startup in 10228 ms > session constructor > session constructor > </code> > > The two last lines are writed by the session's constructor, and both from by > the connection of one user. > > Basically, my code is very simple (my authenticated web application returns > my authenticated web session's class in its getWebSessionClass() method, and > there is nothing speical in the constructor) > > After that, each connection calls this constructor only one time > -- > View this message in context: > http://www.nabble.com/-AuthenticatedWebSession--Constructor-called-twice-tp14420125p14425981.html > > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
