Just to round up the discussion, did you consider java.util.logging?
thanks,
dims
On 10/08/2009 04:55 AM, Sagara Gunathunga wrote:
On Thu, Oct 8, 2009 at 10:52 AM, Amila Suriarachchi
<amilasuriarach...@gmail.com> wrote:
On Thu, Oct 8, 2009 at 2:50 AM, Andreas Veithen<andreas.veit...@gmail.com>
wrote:
For Axis2 it's a bit of an overkill to add SLF4J because of a single
instruction in a single dependency that is triggered by a single
feature in Axis2... But OK, if Woden decides to use SLF4J, we don't
have the choice.
Adding SLF4J require at least two new dependencies to Woden dependent
projects. yes, sometimes it's an overkill. In other way limiting to
one longing implementation is not a good option for an utility
project like Woden. We swung with those two thoughts and finally
decide to use SLF facade and Log4j as the implementation.
Now we need to decide two things:
- How to integrate SLF4J with our current logging approach? Should we
use the SLF4J to JCL bridge or the log4j implementation of SLF4J?
if there is no any special advantage of using SLF4J bridge lets use log4j
implementation since we already shift the log4j with axis2.
- At what level to add the dependency? In axis2-kernel or only in the
distribution?
Lets add only to distribution since log4j also added only to distribution.
I have updated Woden 1.0-SNAPSHOTs , Now when you build the Axis2
Maven should able to add SLF4J as a transitive dependency. please try
to build and if it fail update the list.
Thanks,
thanks,
Amila.
Any thoughts?
Andreas
On Wed, Oct 7, 2009 at 07:31, Sagara Gunathunga
<sagara.gunathu...@gmail.com> wrote:
Hi Andreas,
So far Woden used it's own logging class based on SOP statements.
After having a discussion now we moved to SLF4J API because as a
utility project it's better to support for a Logging Facade. I think
Axis2 need to add SLF4J-API and either commons-binding or
log4j-binding as a dependency.
Thanks ,
On Wed, Oct 7, 2009 at 3:24 AM, Andreas Veithen (JIRA)<j...@apache.org>
wrote:
[
https://issues.apache.org/jira/browse/AXIS2-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762798#action_12762798
]
Andreas Veithen commented on AXIS2-4334:
----------------------------------------
The change in Woden causes a build failure:
wsdl20-codegen:
[echo] Running codegen for WSDL 2.0
[java] Exception in thread "main" java.lang.NoClassDefFoundError:
org/slf4j/LoggerFactory
[java] at
org.apache.woden.internal.ErrorHandlerImpl.<clinit>(ErrorHandlerImpl.java:37)
[java] at
org.apache.woden.internal.ErrorReporterImpl.<init>(ErrorReporterImpl.java:130)
[java] at
org.apache.woden.internal.BaseWSDLFactory.<init>(BaseWSDLFactory.java:39)
[java] at
org.apache.woden.internal.DOMWSDLFactory.<init>(DOMWSDLFactory.java:30)
[java] at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
[java] at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
[java] at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
[java] at
java.lang.reflect.Constructor.newInstance(Constructor.java:501)
[java] at java.lang.Class.newInstance0(Class.java:350)
[java] at java.lang.Class.newInstance(Class.java:303)
[java] at
org.apache.woden.WSDLFactory.newInstance(WSDLFactory.java:63)
[java] at
org.apache.woden.WSDLFactory.newInstance(WSDLFactory.java:51)
[java] at
org.apache.axis2.description.WSDL20ToAxisServiceBuilder.readInTheWSDLFile(WSDL20ToAxisServiceBuilder.java:1200)
[java] at
org.apache.axis2.description.WSDL20ToAxisServiceBuilder.readInTheWSDLFile(WSDL20ToAxisServiceBuilder.java:1176)
[java] at
org.apache.axis2.description.WSDL20ToAxisServiceBuilder.<init>(WSDL20ToAxisServiceBuilder.java:153)
[java] at
org.apache.axis2.description.WSDL20ToAllAxisServicesBuilder.<init>(WSDL20ToAllAxisServicesBuilder.java:53)
[java] at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerationEngine.java:102)
[java] at
org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
[java] at
org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
[java] Java Result: 1
Did Woden switch from commons-logging to SLF4J?
Cannot turn off stdout messages when using WSDL 2.0
---------------------------------------------------
Key: AXIS2-4334
URL: https://issues.apache.org/jira/browse/AXIS2-4334
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.4.1
Reporter: Deyan Popov
Attachments: patch.txt, simple_doc.wsdl, WSDL20Experiment.java
Axis2 writes to stdout when using WSDL 2.0 and I cannot find a way to
turn it off. When some of the namespace URIs inside the WSDL 2.0 document
are not accessible, I see warning messages like:
Woden[Warning],0:0,Description-1001,The targetNamespace '
http://www.example.org/simple_doc/' is not dereferencable.
These messages seem to come from the Apache Woden library and are not
written via Log4j. According to the Woden User Guide there is a default
ErrorHandler which writes to stdout and that ErrorHandler can be replaced.
But I don't see how this can be done via the Axis2 API - in particular the
org.apache.axis2.description.WSDL20ToAllAxisServicesBuilder class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
