[juddi-Users] jUUDI & JWSDP 1.2 (best solution so far)

[Francisco Cuenca <mc...@matiascuenca.com.ar>]

         I got around to do more testing under jwsdp, so I wanted to keep 
the list updated in case somebody has the same scenario.
         I checked out the latest juddi code and observed the new axis.jar 
doesn't solve the problem. My cleanest solution so far is to copy 
log4j-1.2.8.jar into common/lib and to put a log4j.properties file on 
common/classes. With this changes I can run juddi unmodified on jwsdp.
         I hope this helps others

                 Matias
PS: This is the content of my log4j.properties (an spin-off of juddi's file)

# Uncomment to have log4j be verbose while parsing this file
#log4j.debug

# CONSOLE is set to be a ConsoleAppender using a PatternLayout.
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=- %m%n
log4j.appender.CONSOLE.Threshold=INFO

# LOGFILE is set to be a RollingFileAppender appender using a TTCCLayout.
log4j.appender.LOGFILE=org.apache.log4j.RollingFileAppender
log4j.appender.LOGFILE.layout=org.apache.log4j.TTCCLayout
log4j.appender.LOGFILE.layout.ContextPrinting=true
log4j.appender.LOGFILE.layout.DateFormat=ISO8601
log4j.appender.LOGFILE.MaxFileSize=10MB
log4j.appender.LOGFILE.MaxBackupIndex=3
log4j.appender.LOGFILE.File=../logs/launcher.server.log

# Set root category priority to DEBUG and its appender to LOGFILE.
#log4j.rootCategory=WARN, LOGFILE
log4j.rootCategory=INFO, LOGFILE
#log4j.rootCategory=DEBUG, LOGFILE

# Set the Axis enterprise logger category to FATAL and its only appender to 
CONSOLE.
log4j.logger.org.apache.axis.enterprise=FATAL, CONSOLE