cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-1760) jms transport don't support MTOM
Date Tue, 19 May 2009 07:18:45 GMT

    [ https://issues.apache.org/jira/browse/CXF-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710648#action_12710648
] 

Willem Jiang commented on CXF-1760:
-----------------------------------

When use the MTOM, we need to make sure the message type be binary.
In LiuCong's patch , we will check the message type in the JMSconduit send method , where
we can tell if the message has the attachments.
If the message type is text and it has the attachment messages,  a configuration error will
be thrown.

@Liu Cong,
Your patch addresses this issue, that is great. But you didn't change the old JMS MTOM test,
so it was failed if you applied patch.
I changed the old JMS MTOM test to catch that JMS configuration exception and also updated
the exception's message for it .
Please check them out.


> jms transport don't support MTOM
> --------------------------------
>
>                 Key: CXF-1760
>                 URL: https://issues.apache.org/jira/browse/CXF-1760
>             Project: CXF
>          Issue Type: Bug
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>             Fix For: 2.0.9, 2.1.3
>
>         Attachments: cxf-jms.patch
>
>
> mtom can't work over jms transport because miss content-type in the protocol header,
but the content-type is important for AttachmentInIntecepor to parse the attachment in the
message

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


Mime
View raw message