[AXIS2-3671] JAXWS: @MTOM annotation not respected in some circumstances

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.4
• Component/s: jaxws
• Assignee: Rich Scheuerle
• Reporter: Rich Scheuerle
• Created: 27/Mar/08 15:26
• Updated: 03/Apr/08 01:40
• Resolved: 03/Apr/08 01:36

Description

Problem:
JAXWS 2.1 introduced an @MTOM annotation for the endpoint.
If present the @MTOM annotation should be used to enable/disable MTOM
If not present, the BindingType should be used to enable/disable MTOM.

The following cases are currently failing:

// Should enable MTOM
@WebService(...)
@MTOM
public class ...{

// Should enable MTOM
@WebService(...)
@MTOM(enabled=true)
public class ...{

// Should disable MTOM
@WebService(...)
@BindingType(SOAPBinding.SOAP11HTTP_MTOM_BINDING)
@MTOM(enabled= false)
public class ...{

I have representative failing tests in my sandbox. I will be committing the new tests and changes today for RC3.

Thanks,
Rich

Issue Links

• is related to: AXIOM-12 OMOutputFormat: doSWA and doOptimize should be mutually exclusive...plus we need doOptimizeThreshold