Hi Sagara, 2009/5/1 Sagara Gunathunga <[email protected]> > > Hi Jeremy , > BTW in Woden ErrorHandlerImpl we used S.O.P statements to handle > warnings/errors/fatalErrors , but if we use a logging framework (such > as log4j) to handle those stuff instead of S.O.P statements , users > can control it using logging configuration and no need to implement > custom error handlers.
Yes, my thoughts entirely. > > I think we have to think about such improvement in Woden side too. We > already have a JIRA issue related to logging [1] , Any way we can > discuss this matter further in Woden -dev list . Since Woden is a utility and is therefore always going to be used in the context of something else (like Axis2) then whatever the logging strategy we'll need to direct Woden logging / tracing to an arbitrary logging mechanism. SLF4J seems to be popular and doesn't suffer the classloader issues of JCL (apparently although I haven't gone into it). > > > [1] - http://issues.apache.org/jira/browse/WODEN-71
