cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] Commented: (CXF-1669) MTOM does not work when add WSS4J interceptors(UsernameToken and Timestamp)
Date Fri, 27 Jun 2008 16:59:45 GMT


Daniel Kulp commented on CXF-1669:

Do you know if metro enrypts/signs the mtom attachments as well or are they passed in the
clear?   If you are OK with them being passed in the clear, it's a simple.  Line 73 of the
WSS4JOutInterceptor turns off the mtom stuff.   You can just add an interceptor immediately
after the WSS4JOutInterceptor to turn it back on.  (or subclass the WSS4JOutInterceptor and
reset it after calling super.handleMessage(msg))

> MTOM does not work when add WSS4J interceptors(UsernameToken and Timestamp)
> ---------------------------------------------------------------------------
>                 Key: CXF-1669
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.1
>         Environment: Windows Xp,
> JDK 1.5 update 11
> apache CXF 2.1 release
>            Reporter: naveen bhat
>   Original Estimate: 72h
>  Remaining Estimate: 72h
> I have wriitten an Apache CXF client with the following specification,
> 1. MTOM attachment enabled(implemented by refering
> 2. WS-Secuirty features namely, UsernameToken and Timestamp (implemented by refering link)
> As per my observation, i see that the MTOM attachment gets inlined in the soap body of
request, when i enable either of  WS-Security features(UsernameToken or Timestamp).But when
i disable WSS4J interceptors i see that client sends the data as MTOM attachment.
> I suspect  WSS4J interceptor is causing the problem.Kindly help me in this regard.
> Note: I added WSS4J interceptors programmatically.
> Thanks in advance,
> Navin Bhat

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message