Hi,
Have been able to merge the DivLogger to the 1.6 and 1.7 branch
and works as expected. Thank u.
I have an architectural question.
We have multiple GWT modules and we have a single FoundationModule.
This Foundation Module is inherited by all Modules. We define
<inherits name="com.allen_sauer.gwt.log.gwt-log-FATAL" />
as our default log Level, such that other Modules inheriting the
Foundation inherit the least used Level.
But I would like to give the individual modules the ability to add Log
Levels that should be compiled in
as well as which Loggers they want to "ENABLE"
It try doing this in a module that inherits the Foundation
<extend-property name="log_level" values="DEBUG"/>
<set-property name="log_ConsoleLogger" value="DISABLED" />
<set-property name="log_DivLogger" value="ENABLED" />
<set-property name="log_FirebugLogger" value="DISABLED" />
<set-property name="log_GWTLogger" value="ENABLED" />
<set-property name="log_SystemLogger" value="DISABLED" />
I do get the my Loggers react to the ENABLE/DISABLE hint , but
Log.debug does not work ( Log.fatal does as it is the level is
compile in through the foundation )..
Is there way to add/override the Log Level through gwt.xml of some
other module u have inherited?
We want the writers of the modules, to make the decision on which
level they want to work with.
On Nov 17, 10:34 pm, Fred Sauer <[email protected]> wrote:
> On Tue, Nov 17, 2009 at 10:21 AM, Vishal <[email protected]> wrote:
> > We are planning to move to GWT2 , but essentially a whole release
> > cycle has to be planned and that will take time.
>
> > I will readily do the DivLogger back port,
> > Is there an svn branch I can co and work with.
>
> > Sure, just browse here:
>
> http://code.google.com/p/gwt-log/updates/list
>
> I think this commit covers it:
> http://code.google.com/p/gwt-log/source/detail?r=423
>
> This baseline you want is here:
> http://code.google.com/p/gwt-log/source/browse/#svn/branches
> or
> http://code.google.com/p/gwt-log/source/browse/#svn/tags
>
> Fred
>
> > On Nov 17, 2:30 am, Fred Sauer <[email protected]> wrote:
> > > Vishal,
>
> > > I new release (gwt-log-3.0.0.jar, to be used with GWT 2.0) should be
> > > available for download here:
> > > http://code.google.com/p/gwt-log/downloads/list
>
> > > I have no immediate plans to back port the DivLogger change, but you are
> > > free to do so yourself.
>
> > > Are there reasons you are unable to move to a newer version of GWT?
>
> > > Thanks
> > > Fred
>
> > > On Mon, Nov 16, 2009 at 6:27 AM, Vishal <[email protected]>
> > wrote:
> > > > Hello Fred,
> > > > We are planning to use gwt-log-2.4.6 for our evaluation
> > > > and subsequent useage ( on production ) , before we migrate to GWT2.
> > > > If it is not big trouble , is it possible to merge the changes to
> > > > DivLogger to the the gwt-log-2.4.6 official release. We want to go on
> > > > production with the DivLogger and hence this request ( as well as
> > > > DivLogger being one of the standout reasons we like gwt-log ) ...
>
> > > > "DivLogger automagically becomes visible when a new message is
> > > > emitted" seems to make the use of any workarounds impossible.
>
> > > > Thanking u in anticipation.
> > > > Vishal
>
> > > > On Nov 13, 11:30 am, Vishal <[email protected]> wrote:
> > > > > And for gwt-linux-1.6.4...
> > > > > We are not yet on GWT2 or GWT1.7 .. and it seems the trunk depends on
> > > > > artifacts that are in the higher releases.
>
> > > > > On Nov 13, 10:24 am, Vishal <[email protected]> wrote:
>
> > > > > > Thank u for incorporating the DivLogger (visible/invisible) chnages
> > to
> > > > > > trunk.
> > > > > > Is it possible to cut an official release for the change made?
>
> > > > > > On Nov 7, 6:24 pm, Fred Sauer <[email protected]> wrote:
>
> > > > > > > Thanks! This is helpful.
>
> > > > > > > On Fri, Nov 6, 2009 at 4:56 PM, Vishal <
> > [email protected]>
> > > > wrote:
>
> > > > > > > > Few things...
>
> > > > > > > > * The Incubator logging , does not give us a declarative way of
> > > > > > > > compiling out Loggers ( Or may be it is not that obvious ).
> > > > > > > > * The Remote Logger is a a good example of defensive pgming,
> > the
> > > > > > > > default Remote Logger in Incubator, will result in too many
> > RPCs.
> > > > > > > > * The ability to compile out the Log Levels is a neat trick. I
> > > > think
> > > > > > > > your code makes it possible to keep the compiled code lean and
> > > > small
> > > > > > > > * Though we do not use it , the server side Remote Logging
> > seems
> > > > to
> > > > > > > > marry the Log4J appy server side Logging with the GWT client
> > side
> > > > > > > > logging. That obviously is an asset.
> > > > > > > > * The docs seems more mature for gwt-log.
> > > > > > > > * Not sure if Incubator has the ability to set a Custom Widget
> > > > > > > > Container for a DivLogger .. This allows us to have a hidden
> > Widget
> > > > on
> > > > > > > > client browser that may be brought to life ( unhidden ) with
> > some
> > > > > > > > trick.
>
> > > > > > > > I may be wrong about the paucity of the same on the Incubator..
> > but
> > > > it
> > > > > > > > sure seems to lack few things we need and desire.
>
> > > > > > > > We are carrying out further analysis and will report further.
>
> > > > > > > > On Nov 6, 1:53 am, Fred Sauer <[email protected]> wrote:
> > > > > > > > > On Thu, Nov 5, 2009 at 8:52 PM, Vishal <
> > > > [email protected]>
> > > > > > > > wrote:
>
> > > > > > > > > > Sorry , I should have known that. It seems that when u
> > disable,
> > > > u
> > > > > > > > > > compile the Logger out .
> > > > > > > > > > The reason I was confused , was that I saw
>
> > > > > > > > > > Module declares a servlet class
> > > > > > > > > > 'com.allen_sauer.gwt.log.server.RemoteLoggerServiceImpl',
> > but
> > > > the
> > > > > > > > > > web.xml has no corresponding declaration; please add the
> > > > following
> > > > > > > > > > lines to your web.xml:
> > > > > > > > > > <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>/wellbeing/gwt-log</url-pattern>
> > > > > > > > > > </servlet-mapping>
>
> > > > > > > > > > in my hosted mode .
>
> > > > > > > > > > I guess , the above is something I can ignore as it it an
> > > > addition
>
> > > > > > > > > > <servlet path="/gwt-log"
>
> > > > class="com.allen_sauer.gwt.log.server.RemoteLoggerServiceImpl"/>
>
> > > > > > > > > > in the gwt-log-impl.gwt.xml, which causes the above
> > warning.
>
> > > > > > > > > That's correct. I think I need to implement this issue:
> > > > > > > >http://code.google.com/p/gwt-log/issues/detail?id=26
>
> > > > > > > > > And I know this may be a naive question.. We like your impl
> > > > better> than
> > > > > > > > the one in incubator, do u :)?
>
> > > > > > > > > Thanks. Can I ask what you like better?
>
> > > > > > > > > Also, anything you like less?
>
> > > > > > > > > > On Nov 5, 2:08 pm, Fred Sauer <[email protected]> wrote:
> > > > > > > > > > > You can disable the RemoteLogger (see the GettingStarted
> > > > wiki) and
> > > > > > > > add
> > > > > > > > > > your
> > > > > > > > > > > own.
>
> > > > > > > > > > > Fred
>
> > > > > > > > > > > On Thu, Nov 5, 2009 at 7:50 PM, Vishal <
> > > > [email protected]>
> > > > > > > > > > wrote:
>
> > > > > > > > > > > > Thank u,
> > > > > > > > > > > > By implementing Logger, I got it to work.
>
> > > > > > > > > > > > Here is what I would like to do.
>
> > > > > > > > > > > > * Add an injectable LogService.
> > > > > > > > > > > > * The LogService creates the CustomLogger and injects
> > into
> > > > it , our
> > > > > > > > > > > > ActionService ( RPC ).
> > > > > > > > > > > > * The ActionService will based on the algorithm we
> > define
> > > > in
> > > > > > > > > > > > CustomLogger , send the Logs across.
>
> > > > > > > > > > > > In this whole design , we desire to remove RemoteLogger
> > (
> > > > the
> > > > > > > > default
> > > > > > > > > > > > RemoteLogger ) from being added to the List of Loggers.
> > > > > > > > > > > > Is that possible?
> > > > > > > > > > > > We of course want to retain all the other Loggers.
>
> > > > > > > > > > > > On Nov 5, 1:43 pm, Fred Sauer <[email protected]>
> > wrote:
> > > > > > > > > > > > > Note that the gwt-log source contains both client and
> > > > server
> > > > > > > > versions
> > > > > > > > > > of
> > > > > > > > > > > > the
> > > > > > > > > > > > > same Java classes, which can be confusing.
>
> > > > > > > > > > > > > On Thu, Nov 5, 2009 at 7:02 PM, Vishal <
> > > > > > > > [email protected]>
> > > > > > > > > > > > wrote:
>
> > > > > > > > > > > > > > Hi,
> > > > > > > > > > > > > > We wanted to do the same thing, implement a
> > > > > > > > > > CustomRemoteLogger..
> > > > > > > > > > > > > > Of course we extended AbstractLogger, yet we have
>
> > > > > > > > > > > > > > "This class must implement the inherited abstract
> > > > method
> > > > > > > > > > > > > > AbstractLogger.log(int, String), but cannot
> > override it
> > > > since
> > > > > > > > it is
> > > > > > > > > > > > > > not visible from OurLogger. Either make the type
> > > > abstract or
> > > > > > > > make
> > > > > > > > > > the
> > > > > > > > > > > > > > inherited method visible "
>
> > > > > > > > > > > > > > nskmda, Did u extend AbstractLogger and if u did
> > get
> > > > this to
> > > > > > > > > > compile?
>
> > > > > > > > > > > > > > On Sep 29, 10:37 am, nskmda <[email protected]>
> > wrote:
> > > > > > > > > > > > > > > Thanks, Fred.
> > > > > > > > > > > > > > > I tried it. It works perfectly.
>
> > > > > > > > > > > > > > > Dmitry
>
> > > > > > > > > > > > > > > On Sep 28, 5:03 pm, Fred Sauer <
> > [email protected]>
> > > > wrote:
>
> > > > > > > > > > > > > > > > That's the right approach. You can include the
> > > > logger in
> > > > > > > > your
> > > > > > > > > > > > > > onModuleLoad()
> > > > > > > > > > > > > > > > to make it easy.
> > > > > > > > > > > > > > > > Fred
>
> > > > > > > > > > > > > > > > On Mon, Sep 28, 2009 at 4:03 PM, nskmda <
> > > > [email protected]>
> > > > > > > > > > wrote:
>
> > > > > > > > > > > > > > > > > Do I get it right that I need to implement
> > the
> > > > Logger
> > > > > > > > > > interface
> > > > > > > > > > > > (or
> > > > > > > > > > > > > > > > > extend the AbstractLogger)?
> > > > > > > > > > > > > > > > > Is there any easier way to register my logger
> > > > > > > > declaratively
> > > > > > > > > > in
> > > > > > > > > > > > GWT
> > > > > > > > > > > > > > > > > config instead of registering it at runtime
> > via
> > > > > > > > > > Log.addLogger?
> > > > > > > > > > > > > > > > > Will I have to always use
> > > > > > > > > > > > Log.getLogger(MyLoggerClass.class).debug at
> > > > > > > > > > > > > > > > > runtime?
>
> > > > > > > > > > > > > > > > > On Sep 28, 3:16 pm, Fred Sauer <
> > > > [email protected]>
> > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > Sure. Should be easy to do.
>
> > > > > > > > > > > > > > > > > > On Mon, Sep 28, 2009 at 2:57 PM, nskmda <
>
> ...
>
> read more »
--
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=.
