Do you see stack traces here?
  http://allen-sauer.com/com.allen_sauer.gwt.log.demo.LogDemo/LogDemo.html


On Thu, Mar 31, 2011 at 12:50 PM, mayumi <[email protected]> wrote:

> I am using the latest gwt-log and latest GWT, I tried including:
>        <set-property name="compiler.emulatedStack" value="true" />
>        <set-configuration-property
> name="compiler.emulatedStack.recordLineNumbers"
>                value="true" />
>        <set-configuration-property
> name="compiler.emulatedStack.recordFileNames"
>                value="true" />
> and still I don't see any exceptions logged in either Console or
> Chrome Development Console.
>
> I tried your example above, and I saw a error logged in Chrome
> Development Console.
>
> Just for one more information my DD looks like:
>
>  <servlet>
>  <servlet-name>remoteLoggerServiceImpl</servlet-name>
>  <servlet-
> class>com.allen_sauer.gwt.log.server.RemoteLoggerServiceImpl
>  </servlet-class>
>  </servlet>
>  <servlet-mapping>
>  <servlet-name>remoteLoggerServiceImpl</servlet-name>
>  <url-pattern>/bam/gwt-log</url-pattern>
>  </servlet-mapping>
>
> I still don't see any exception shown on console. When you refer to
> "console" are you suffering to to "Development Mode" Console
> ("Development Mode" tab in eclipse)
> or Console ("Console" tab in eclipse). I also don't see any logs in
> Chrome's console (Inspect element, console).
>
> Thank you so much.
>
>
> On Mar 31, 2:14 pm, Fred Sauer <[email protected]> wrote:
> > Latest version is available here:
> >  http://code.google.com/p/gwt-log/downloads/list
> >
> > Version compatibility is:
> >  http://code.google.com/p/gwt-log/wiki/GettingStarted
> >
> > You should be able to see log messages, similar to the one in this test
> app:
> >
> http://allen-sauer.com/com.allen_sauer.gwt.log.demo.LogDemo/LogDemo.html
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Thu, Mar 31, 2011 at 12:07 PM, mayumi <[email protected]>
> wrote:
> > > Thank you so much for the reply:
> >
> > > My gwt-log version is: Created-By: 17.1-b03-307 (Apple Inc.) ( I found
> > > in the Manifest)
> >
> > > You're right I cannot find a logging information on console. I read in
> > > "Getting Started Guide"
> > > that ConsoleLogger are enabled as a default so to test this I threw an
> > > uncaught exception explicitly to see the
> > > error on console, but nothing was logged there.
> > > Only exception I saw was an exception on "Development Mode" console,
> > > but I expect an exceptions shown in console not there.
> >
> > > Could you please let me know how I can set the emulated stack traces
> > > on?
> >
> > > Thank you so much again.
> >
> > > On Mar 31, 1:56 pm, Fred Sauer <[email protected]> wrote:
> > > > Are you seeing the log information on the client (i.e. in the
> DivLogger
> > > or
> > > > ConsoleLogger)? If not, you may want to turn on emulated stack traces
> in
> > > > your .gwt.xml file
> >
> > > > What version of gwt-log are you using? Please be sure you are on the
> > > latest.
> >
> > > > On Thu, Mar 31, 2011 at 11:49 AM, mayumi <[email protected]>
> > > wrote:
> > > > > Hi, I am using gwt-logs currently with GWT and GAE. I have my
> module
> > > > > configured as explained in Getting Started:
> > > > >        <inherits name="com.allen_sauer.gwt.log.gwt-log-OFF" />
> > > > >        <inherits
> name="com.allen_sauer.gwt.log.gwt-log-RemoteLogger" />
> > > > >        <extend-property name="log_level" values="DEBUG" />
> >
> > > > > And I have my entry point class with:
> > > > >        Log.setUncaughtExceptionHandler()
> >
> > > > > The problem is when I get Uncaught Exception on the client side,
> all I
> > > > > get in my GAE logs is:
> > > > > "com.allen_sauer.gwt.log.server.ServerLogImplJDK14 log: Uncaught
> > > > > Exception:"
> > > > > I want to include more information on the source of the exception
> (ex:
> > > > > class name, parameter, error type, exception stack trace). How do I
> > > > > configure to do this?
> >
> > > > > Thank you so much.
> >
> > > > > --
> > > > > You received this message because you are subscribed to the Google
> > > Groups
> > > > > "gwt-log" group.
> > > > > To post to this group, send email to [email protected].
> > > > > To unsubscribe from this group, send email to
> > > > > [email protected].
> > > > > For more options, visit this group at
> > > > >http://groups.google.com/group/gwt-log?hl=en.
> >
> > > > --
> > > > Fred Sauer
> > > > Developer Advocate
> > > > Google Inc.
> > > > 1600 Amphitheatre Parkway
> > > > Mountain View, CA 94043
> > > > [email protected]
> >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "gwt-log" group.
> > > To post to this group, send email to [email protected].
> > > To unsubscribe from this group, send email to
> > > [email protected].
> > > For more options, visit this group at
> > >http://groups.google.com/group/gwt-log?hl=en.
> >
> > --
> > Fred Sauer
> > Developer Advocate
> > Google Inc.
> > 1600 Amphitheatre Parkway
> > Mountain View, CA 94043
> > [email protected]
>
> --
> You received this message because you are subscribed to the Google Groups
> "gwt-log" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/gwt-log?hl=en.
>
>


-- 
Fred Sauer
Developer Advocate
Google Inc.
1600 Amphitheatre Parkway
Mountain View, CA 94043
[email protected]

-- 
You received this message because you are subscribed to the Google Groups 
"gwt-log" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/gwt-log?hl=en.

Reply via email to