[jbossws-issues] [JBoss JIRA] Commented: (JBWS-1949) Metro MTOM ignores content-type on attachment part

Heiko Braun (JIRA) jira-events at lists.jboss.org
Tue Aug 5 10:31:04 EDT 2008


    [ https://jira.jboss.org/jira/browse/JBWS-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12423646#action_12423646 ] 

Heiko Braun commented on JBWS-1949:
-----------------------------------

Let's say a MTOM enabled service returns a DataHandler that contains an image, content-type would be "image/jpeg". Response get's serialized (XOP encoded), but when the client does access the attachment part the content-type will be "application/octet-stream". If you now call getContent(), which is driven by the underlying content-type you'll receive a byte[] instead of an Image. The original content-type information simply get's lost. 



> Metro MTOM ignores content-type on attachment part
> --------------------------------------------------
>
>                 Key: JBWS-1949
>                 URL: https://jira.jboss.org/jira/browse/JBWS-1949
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-metro
>    Affects Versions: jbossws-metro-3.0.0
>            Reporter: Heiko Braun
>            Assignee: Richard Opalka
>             Fix For:  jbossws-metro-3.0.3
>
>
> It turns everything into application/octet-stream on a DataHandler instance, even though the attachment part contains an explicit content-type.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jbossws-issues mailing list