Thanks for the information, Charlie! I modified your simplesample and
was able to reproduce the problem. Here is the svn diff against HEAD:
Index: src/main/java/com/totsp/sample/server/
SampleRemoteServiceImpl.java
===================================================================
--- src/main/java/com/totsp/sample/server/
SampleRemoteServiceImpl.java (revision 932)
+++ src/main/java/com/totsp/sample/server/
SampleRemoteServiceImpl.java (working copy)
@@ -5,12 +5,13 @@
import com.google.gwt.user.server.rpc.RemoteServiceServlet;
import com.totsp.sample.client.SampleRemoteService;
-import org.apache.log4j.Logger;
+import org.apache.commons.logging.Log;
+import org.apache.commons.logging.LogFactory;
public class SampleRemoteServiceImpl extends RemoteServiceServlet
implements
SampleRemoteService {
- private static final Logger LOG = Logger.getLogger
(SampleRemoteServiceImpl.class);
+ private static final Log LOG = LogFactory.getLog
(SampleRemoteServiceImpl.class);
public String doComplimentMe() {
LOG.debug("Some logging stuff - where does it end up! (see
src/main/resources/log4j.xml)");
Index: pom.xml
===================================================================
--- pom.xml (revision 932)
+++ pom.xml (working copy)
@@ -63,6 +63,12 @@
<classifier>${platform}</classifier>
<scope>provided</scope>
</dependency>
+
+ <dependency>
+ <groupId>commons-logging</groupId>
+ <artifactId>commons-logging</artifactId>
+ <version>1.1</version>
+ </dependency>
<dependency>
<groupId>log4j</groupId>
@@ -217,4 +223,4 @@
</activation>
</profile>
</profiles>
-</project>
\ No newline at end of file
+</project>
By using commons-logging, which should automatically find the log4j on
the classpath + log4j.properties, the logging from the server code no
longer appears to System.out nor to the file appender... :-(
My project makes extensive use of commons-logging because some sub-
modules in my project form .jars which are used as libraries in other
projects.. I don't control the plethora of projects exploiting these
libraries, and our company policy is to use commons-logging instead of
the specific log4j. Any ideas??
Thanks in advance,
-jesse
On Nov 17, 1:31 pm, Charlie Collins <[EMAIL PROTECTED]> wrote:
> Good info Dave, yes, thanks.
>
> I have never run into this myself, but I configure myloggingjust
> like the sample I linked in this thread:
>
> private static final Logger LOG = Logger.getLogger(MyClass.class);
>
> So I guess I am hooked into log4j directly (which is fine by me
> actually, but might explain why others see this "issue" and I don't).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"gwt-maven" 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-maven?hl=en
-~----------~----~----~----~------~----~------~--~---
