[ 
https://issues.apache.org/jira/browse/AXIS2-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706771#action_12706771
 ] 

Sagara Gunathunga  commented on AXIS2-4334:
-------------------------------------------

This issue is  related to Woden ErrorHandler Implementation because it use 
S.O.P statements. In Woden side there is a JIRA issue [1] related to 
logging,AFAIK it will  address this  issue too.  But as a alternative approach 
Axis2 could  implement it's own ErrorHandler and set to the  WSDLReader inside 
the WSDL20ToAxisServiceBuilder. [2] is a thread related to this issue. 

[1] - http://issues.apache.org/jira/browse/WODEN-71
[2]-  
http://www.nabble.com/How-to-turn-off-stdout-messages-when-using-WSDL-2.0---td23312341.html

> 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: 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.

Reply via email to