Mauro,
Is your problem occurring in web mode or hosted mode?

Fred

2009/5/30 Mauro De Lucca <[email protected]>

>
> I am having the same problem, were you able to find out what was the
> problem David?
>
> On May 15, 12:19 pm, Fred Sauer <[email protected]> wrote:
> > David,
> > Beware that there are two sets of *.java source code in the gwt-log jar
> for
> > logging. The GWT compiler (when inheriting from gwt-log) and the Java
> > compiler each will pickup different copies. This is because there's a
> > different implementation intended for client code (GWT) consumption and
> > server code (JVM) consumption.
> >
> > HTH
> > Fred
> >
> >
> >
> > On Fri, May 15, 2009 at 6:36 AM, David <[email protected]> wrote:
> >
> > > Fred,
> >
> > > Thanks for the reply.  You're right, that seems to work.  After
> > > investigating some more, it appears that this is only failing in some
> > > test classes we're using for our junit tests in our build.  It is
> > > working in our main application (even though the calls there appear to
> > > be exactly the same as in the test classes).  I'll investigate this
> > > further.  Thanks again for the help and sorry for the confusion
> > > before.
> >
> > > David
> >
> > > On May 14, 1:14 pm, Fred Sauer <[email protected]> wrote:
> > > > David,
> > > > I just created a sample project using the Eclipse Plugin, GWT 1.6.4
> and
> > > > gwt-log-2.6.0.jar and added Log.info("foo"). Everything appears to
> work
> > > > fine. Perhaps there's something else that's causing the issue?
> >
> > > > I've emailed you a zipped up project for you to compare with.
> >
> > > > Thanks
> > > > Fred
> >
> > > > On Thu, May 14, 2009 at 7:59 AM, David <[email protected]> wrote:
> >
> > > > > I'm attempting to upgrade from gwt-log 2.5.3 to gwt-log 2.6.0 since
> > > > > I've recently upgraded to gwt 1.6.4 and the compatibility table on
> gwt-
> > > > > log's "Getting Started" page states that 2.6.0 should be used with
> gwt
> > > > > 1.6.4.
> >
> > > > > I'm seeing a problem after upgrading gwt-log that I didn't
> previously
> > > > > see with gwt-log 2.5.3 (when using it with either gwt 1.5.3 or
> > > > > 1.6.4).  After only changing to use the gwt-log 2.6.0 jar instead
> of
> > > > > the gwt-log 1.5.3 jar, I now get the following:
> >
> > > > > java.lang.NullPointerException
> > > > >    at com.allen_sauer.gwt.log.client.Log.info(Log.java:448)
> > > > >    at com.allen_sauer.gwt.log.client.Log.info(Log.java:400)
> > > > >    ...
> >
> > > > > from this line of code:
> >
> > > > > Log.info("foo");
> >
> > > > > I took a quick look at the source, and it appears that some changes
> > > > > have been made to Log.java, moving it to the top-level server
> > > > > directory and adding some dependencies to a remote logger.  Is
> there
> > > > > something I need to update to get this to work again?  I didn't see
> a
> > > > > migration guide, but I could have missed it.  If there is one,
> could
> > > > > you please point me to it?
> >
> > > > > Thanks,
> > > > > David
> >
> > > > --
> > > > Fred Sauer
> > > > Developer Advocate
> > > > Google Inc. 1600 Amphitheatre Parkway
> > > > Mountain View, CA 94043
> > > > [email protected]
> >
> > > > --
> > > > Fred Sauer
> > > > Developer Advocate
> > > > Google Inc. 1600 Amphitheatre Parkway
> > > > Mountain View, CA 94043
> > > > [email protected]
> >
> > > > --
> > > > Fred Sauer
> > > > Developer Advocate
> > > > Google Inc. 1600 Amphitheatre Parkway
> > > > Mountain View, CA 94043
> > > > [email protected]
> >
> > --
> > Fred Sauer
> > Developer Advocate
> > Google Inc. 1600 Amphitheatre Parkway
> > Mountain View, CA 94043
> > [email protected]
> >
>


-- 
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to