no problem
On 10/20/08, Steve <[EMAIL PROTECTED]> wrote:
>
> Sorry i completely missed that on the getting started page.
>
> <servlet>
> <servlet-name>gwt-log-remote-logger-servlet</servlet-name>
> <servlet-
> class>com.allen_sauer.gwt.log.server.RemoteLoggerServiceImpl</servlet-
> class>
> </servlet>
>
> <servlet-mapping>
> <servlet-name>gwt-log-remote-logger-servlet</servlet-name>
> <url-pattern>/gwt-log</url-pattern>
> </servlet-mapping>
>
>
> Thanks anyway,
> Steve
> On Oct 20, 8:30 am, Steve <[EMAIL PROTECTED]> wrote:
>> Ah that is likely to be my problem as it works in hosted and web mode
>> but the messages arent getting logged when i deployed it to tomcat.
>>
>> what servlet and servlet mapping would i need to add?
>>
>> Regards steve.
>>
>> p.s. this is a great tool. realy effective and easy to use. thanks :)
>>
>>
>>
>> > On Oct 18, 1:25 pm, [EMAIL PROTECTED] wrote:
>> > In hosted mode the /gwt-log servlet is automatically setup. In your
>> > case (JBoss) you need to define the servlet in your web.xml. The key
>> > is the HTTP 404 error that the client end of the remote logger is
>> > running into.
>>
>> > Fred
>> > On 10/17/08, cmr <[EMAIL PROTECTED]> wrote:
>>
>> > > My .gwt.xml file entry:
>>
>> > > <set-property name="log_RemoteLogger" value="ENABLED" />
>> > > <extend-property name="log_level" values="DEBUG,WARN"/>
>>
>> > > My GWT code has the following line in a LayoutContainer class'
>> > > onRender()
>>
>> > > Log.debug("Entering onRender");
>>
>> > > I have packaged gwt-log.jar in my .ear file. But I don't see the log
>> > > message in my JBoss server log or any exceptions in GUI. But if I
>> > > interactively change the log level to INFO I see the following
>> > > exception.
>>
>> > > [gwt-log] Temporarily setting the current (runtime) log level filter
>> > > to 'INFO'
>> > > gwt-log] Removing 'com.allen_sauer.gwt.log.client.RemoteLogger' due to
>> > > unexecpted exception
>> > > java.lang.RuntimeException:
>> > > Remote logging will be suspended due to communication failure with
>> > > com.allen_sauer.gwt.log.client.RemoteLoggerService_Proxy at
>> > >http://localhost:8080/dWeb/gwt-log
>> > > at com.allen_sauer.gwt.log.client.RemoteLogger
>> > > $1.onFailure(RemoteLogger.java:45)
>> > > at
>> > > com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived(RequestCallbackAdapter.java:
>> > > 217)
>> > > at
>> > > com.google.gwt.http.client.Request.fireOnResponseReceivedImpl(Request.java:
>> > > 254)
>> > > at
>> > > com.google.gwt.http.client.Request.fireOnResponseReceivedAndCatch(Request.java:
>> > > 226)
>> > > at
>> > > com.google.gwt.http.client.Request.fireOnResponseReceived(Request.java:
>> > > 217)
>> > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> > > at
>> > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
>> > > 39)
>> > > at
>> > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
>> > > 25)
>> > > at java.lang.reflect.Method.invoke(Method.java:597)
>> > > at
>> > > com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)
>> > > at
>> > > com.google.gwt.dev.shell.ie.IDispatchImpl.callMethod(IDispatchImpl.java:
>> > > 126)
>> > > at
>> > > com.google.gwt.dev.shell.ie.IDispatchProxy.invoke(IDispatchProxy.java:
>> > > 155)
>> > > at
>> > > com.google.gwt.dev.shell.ie.IDispatchImpl.Invoke(IDispatchImpl.java:
>> > > 294)
>> > > at
>> > > com.google.gwt.dev.shell.ie.IDispatchImpl.method6(IDispatchImpl.java:
>> > > 194)
>> > > at
>> > > org.eclipse.swt.internal.ole.win32.COMObject.callback6(COMObject.java:
>> > > 117)
>> > > at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native
>> > > Method)
>> > > at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1925)
>> > > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:
>> > > 2966)
>> > > at com.google.gwt.dev.GWTShell.pumpEventLoop(GWTShell.java:720)
>> > > at com.google.gwt.dev.GWTShell.run(GWTShell.java:593)
>> > > at com.google.gwt.dev.GWTShell.main(GWTShell.java:357)
>>
>> > > Caused by: com.google.gwt.user.client.rpc.StatusCodeException:
>>
>> > > HTTP Status 404 - /dWeb/gwt-log
>>
>> > > --------------------------------------------------------------------------------
>>
>> > > type Status report
>>
>> > > message /dWeb/gwt-log
>>
>> > > description The requested resource (/dWeb/gwt-log) is not available.
>>
>> > > Thanks for any help.
>> > > cmr
>>
>> > --
>> > Fred Sauer
>> > [EMAIL PROTECTED] Hide quoted text -
>>
>> > - Show quoted text -- Hide quoted text -
>>
>> - Show quoted text -
> >
>
--
Fred Sauer
[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
-~----------~----~----~----~------~----~------~--~---