Hi Yuri, Yes the compile-gwt-dev was showing up the info logs. However, I could not see the logs from the DoMLogger from JsoSearchBuilderImpl. It may be mistake, but I just see the remote logger logs.
Also, the gwt UI code with the logging panel using the compile-gwt-dev is showing some unstable UI behavior with shiny's when used with FF 4. It was very random.It is working fine with Chrome though. I am saying this because I am not sure if it was meant to work only with Chrome. Thanks, Gokul On Mon, May 16, 2011 at 10:28 PM, Yuri Z <vega...@gmail.com> wrote: > You don't have to build the jar for debugging purposes. There are targets > in > the build.xml ant script that allow to run/debug the server from the > compiled classes. > > 2011/5/16 Gokul Jeyapaul <gokul.jeyap...@googlemail.com> > > > Sure Yuri. I will try that. Till now, I was just trying to use the normal > > "ant" command and was doing a whole build. > > > > On Mon, May 16, 2011 at 6:25 PM, Yuri Z <vega...@gmail.com> wrote: > > > > > Actually client side log levels are set in the WebClient.gwt.xml. > > > But what command do you use to compile the GWT to javascript? > > > There are 3 targets for the gwt compilation in the build.xml: > > > compile-gwt - which is the "production" mode without stack emulation > and > > > logging panel disabled. > > > compile-gwt-demo - with stack emulation and remote logging enabled but > > with > > > logging panel disabled. > > > compile-gwt-dev - with stack emulation and logging panel enabled. > > > I think you need compile-gwt-dev for developing purposes. > > > so try to recompile with: > > > ant compile-gwt-dev > > > > > > > > > 2011/5/16 Gokul Jeyapaul <gokul.jeyap...@googlemail.com> > > > > > > > Hi Yuri, > > > > > > > > I tried it, some how unable to get it working. > > > > > > > > Do I have to set the log levels some where else apart from while > > > starting > > > > the server? I am starting the server from command prompt like > > > > > > > > java -Dorg.eclipse.jetty.util.log.DEBUG=true > > > > -Djava.security.auth.login.config="jaas.config" > > > > -Dwave.server.config=server.config -jar > dist\waveinabox-server-0.3.jar > > > > > > > > or Should I look for log files rather than the console for logs? > > > > > > > > Thanks, > > > > Gokul > > > > > > > > > > > > On Sat, May 14, 2011 at 10:59 PM, Yuri Z <vega...@gmail.com> wrote: > > > > > > > > > Try DomLogger. Take a look at JsoSearchBuilderImpl for example. > > > > > > > > > > 2011/5/14 Gokul Jeyapaul <gokul.jeyap...@googlemail.com> > > > > > > > > > > > Hi all, > > > > > > > > > > > > Some help on this would be really helpful in understanding the > > code > > > > > flow. > > > > > > Thanks again for your time and patience. > > > > > > > > > > > > Regards, > > > > > > Gokul > > > > > > > > > > > > On Fri, May 13, 2011 at 3:26 PM, Gokul Jeyapaul < > > > > > > gokul.jeyap...@googlemail.com> wrote: > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > I was just trying to understand the wave code base better, and > I > > > > > wanted > > > > > > to > > > > > > > added some logs(debug or info) in some UI related classes(eg: > > > > > > > SearchPresenter). > > > > > > > > > > > > > > I used org.waveprotocol.box.webclient.util.Log class's info > > method > > > > for > > > > > > > this. But I don't get to see the logs in the console, I think I > > am > > > > > > missing > > > > > > > some step(s) here. Some help will be really nice. > > > > > > > > > > > > > > Thanks, > > > > > > > Gokul > > > > > > > > > > > > > > > > > > > > > > > > > > > >
