[
https://issues.apache.org/jira/browse/CXF-6255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322041#comment-14322041
]
Richard O'Sullivan commented on CXF-6255:
-----------------------------------------
Thank you Colm for explaining ""Request does not contain Security header, but
it's a fault." However, it's not clear to me what course of action will resolve
this warning? Use case: I see this warning when Camel CXF receives a SoapFault
when calling a remote web service. The remote web service sometimes replies
with a SoapFault to indicate a validation issue -- it's a business thing.
Should the warning be resoved by a) something the remote web service configures
or b) something I can configure in Camel CXF? Do you know if there is something
at http://cxf.apache.org/docs/ws-securitypolicy.html that I can configure to
address this warning?
> WSS4JInInterceptor: "Security header, but it's a fault"
> -------------------------------------------------------
>
> Key: CXF-6255
> URL: https://issues.apache.org/jira/browse/CXF-6255
> Project: CXF
> Issue Type: Improvement
> Reporter: Richard O'Sullivan
> Priority: Minor
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When CXF processes a SoapFault it logs this WARNing: "Request does not
> contain Security header, but it's a fault.". The message is logged from the
> handleMessage at WSS4JInInterceptor in the package
> org.apache.cxf.ws.security.wss4j.
> The message is cryptic but I think it is intended to be an INFO or DEBUG
> instead of a WARN.
> If I'm correct please make this an INFO or a DEBUG; otherwise, rewrite the
> message to indicate a course of action to eliminate the warning.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
