Hello,
I am not sure if this can be of any help, but originally after adding cxf
dependencies that I picked myself by hand I experienced strange behaviour of
very simple code, e.g.:
public class SLF4JLoggerTest {
public static final Logger LOGGER =
LoggerFactory.getLogger(SLF4JLoggerTest.class);
@Test
public void testLogging() {
SL4JHelper.init();
LOGGER.info("test");
ch.qos.logback.classic.Logger logger =
(ch.qos.logback.classic.Logger) LOGGER;
logger.info("test2");
System.out.println(logger.isTraceEnabled());
}
}
I got some MethodNotFound exception on one of the base interface classes of
slf4j that isTraceEnabled() does not exist. Stepping with the debugger
through the problem did not show any issues. I assumed that it must have had
something to do with some bytecode enhancements in the background, but I
could not find any hints that byte code enhancement would happen.
I got rid of the problem by replacing the maven dependencies that I picked
by hand by those dependencies here:
http://cwiki.apache.org/CXF20DOC/building-your-cxf-project-with-maven.html
I still do not know what the original problem was due to.
Would it be possible that the CXF team creates a maven project that only
bundles the most common needed dependencies to run CXF, so that instead of
having to depend on a set of CXF modules it would be sufficient to only
include this one?
Many thanks,
Christian
--
View this message in context:
http://www.nabble.com/CXF-Maven-Dependencies-tp18781050p18825550.html
Sent from the cxf-user mailing list archive at Nabble.com.
