Bug 1178234

Summary: [GSS] (6.4.z) @MTOM.enabled is not honored
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Chris Dolphy <cdolphy>
Component: Web ServicesAssignee: Alessio Soldano <asoldano>
Status: CLOSED CURRENTRELEASE QA Contact: Rostislav Svoboda <rsvoboda>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbaranow, cdewolf, chaowan, jawilson, jbliznak, klape, psotirop
Target Milestone: CR1   
Target Release: EAP 6.4.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1179986, 1219165    
Attachments:
Description Flags
MTOM patch for jbossws cxf 4.3.x none

Description Chris Dolphy 2015-01-02 23:48:57 UTC
Description of problem:
If you specify @MTOM(enabled=false) MTOM will still be enabled.

Version-Release number of selected component (if applicable):
JBossWS-CXF 4.3.1

How reproducible:
Create web service method with @MTOM(enabled=false) annotation on the class.

Steps to Reproduce:
1. Create MTOM web service with @MTOM(enabled=false)
2. Enable mtom on client


Actual results:
It will still send responses as if MTOM is enabled.

Expected results:
MTOM should not be used.

Additional info:
https://issues.jboss.org/browse/JBWS-3863

Comment 1 JBoss JIRA Server 2015-01-07 10:44:58 UTC
Alessio Soldano <asoldano> updated the status of jira JBWS-3863 to Resolved

Comment 2 Kyle Lape 2015-01-08 01:37:37 UTC
The fix is in JBossWS-CXF, not Apache CXF, so I'm changing the linked upgrade BZ.

Comment 4 Panagiotis Sotiropoulos 2015-03-16 14:05:37 UTC
Assigning back to Alessio as the there is a patch already.

Comment 5 Panagiotis Sotiropoulos 2015-03-16 14:17:54 UTC
Created attachment 1002290 [details]
MTOM patch for jbossws cxf 4.3.x

Comment 10 Rostislav Svoboda 2015-04-23 11:40:24 UTC
Please include test in AS TS or component TS.

I tried reproducer from  Comment 8, here is some feedback:
 - I can't compile it as it depends on SNAPSHOT stuff
 - it's testing that rss.png is transported 
 - it doesn't check if it was encoded using base64 or attached to the soap as attachment (application/octet-stream) - please check for example http://www.crosschecknet.com/intro_to_mtom.php to see the attachment example
 - why is test depending on org.jboss.test.integration.mtom.MtomTestCase-output.txt file, when the test is refactored it can cause troubles

Comment 11 Panagiotis Sotiropoulos 2015-04-23 12:57:20 UTC
Rostislav can you check the test again? Can you compile now? -- https://github.com/panossot/eap-additional-testsuite/tree/master/web/src/test/java/org/jboss/test/integration/mtom . I will try, also to add an additional test with what you ask.

Comment 12 Rostislav Svoboda 2015-04-23 14:56:42 UTC
I can compile now, but please enhance the test and please consider including it into AS TS.

Comment 13 Panagiotis Sotiropoulos 2015-04-24 07:22:57 UTC
Added an additional testCase that proves the soap message does not use xop-format (MTOM) : https://github.com/panossot/eap-additional-testsuite/blob/master/web/src/test/java/org/jboss/test/integration/mtom/MtomSaopTestCase.java

Comment 15 JBoss JIRA Server 2015-04-25 20:24:57 UTC
Alessio Soldano <asoldano> updated the status of jira JBWS-3863 to Closed

Comment 16 Panagiotis Sotiropoulos 2015-05-04 07:24:35 UTC
JBossWS-CXF 4.3.5.Final has been tagged by Alessio :
http://anonsvn.jboss.org/repos/jbossws/stack/cxf/tags/jbossws-cxf-4.3.5.Final/

Comment 17 Panagiotis Sotiropoulos 2015-05-05 09:00:32 UTC
Updating the link for mtom test cases : https://github.com/panossot/eap-additional-testsuite/tree/master/web/src/test/java/org/jboss/test/integration/mtom

Comment 18 Jan Blizňák 2015-06-23 13:48:54 UTC
Verified with 6.4.2.CP.CR1

Comment 19 Petr Penicka 2017-01-17 10:19:03 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.

Comment 20 Petr Penicka 2017-01-17 10:19:07 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.