Hi Pandu,
Have you tried placing both the cactus.properties and the
logging_server.properties under WEB-INF/classes ?
I had this problem before and I resolved by putting them in classes directory. If you
put them under classes, you need not give the complete path for logging_server
properties. Just say log4j.configuration = logging_server.properties
Hope this helps !
Thanks,
Nalini.
[EMAIL PROTECTED] wrote:
I am running the test through browser (Servlet test Runner). Thanks for
your prompt replies.
|---------+---------------------------->
| | "Vincent Massol" |
| | | | com> |
| | |
| | 07/15/2004 02:50 |
| | AM |
| | Please respond to|
| | "Cactus Users |
| | List" |
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
| |
| To: "'Cactus Users List'" |
| cc: |
| Subject: RE: cactus logging configuration issues |
>------------------------------------------------------------------------------------------------------------------------------|
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: jeudi 15 juillet 2004 00:48
> To: Cactus Users List
> Subject: RE: cactus logging configuration issues
>
>
>
>
>
> Hi
> Thanks for the suggestions. I only have a server (no client)in my case
> (WAS
> test server running in WSAD). I updated with the 1.6.1 version of cactus.
> So I made the cactus.properties and logging_server.properties.
You also need a logging_client.properties. The reason for the "Not a valid
response" will of course be present in this file! (Cactus client part
calling the Cactus server part).
How are you executing your Cactus tests (browser, Ant, Maven, etc)?
[snip]
> logging_server.properties
> #
>
--------------------------------------------------------------------------
> ---
> # Logging properties
> #
>
--------------------------------------------------------------------------
> ---
>
> # Disable logging by default when running the tests. If you wish to use a
> # logging subsystem, uncomment the line below. That will let Commons
> logging
> # decide automatically of a suitable logging system for you. You can also
> force
> # commons-logging to use a specific logging system. For more info, see
> # http://jakarta.apache.org/commons/logging
>
> # Disable logging
> #org.apache.commons.logging.Log = org.apache.commons.logging.impl.NoOpLog
>
> # Force to use JDK 1.4 logging
> #org.apache.commons.logging.Log =
> org.apache.commons.logging.impl.Jdk14Logger
>
> # Force to use Log4J logging
> #org.apache.commons.logging.Log =
> org.apache.commons.logging.impl.Log4JLogger
Can you uncomment the line to force commons logging to use Log4J logging
which is what you want I think?
[snip]
-Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
