cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] Commented: (CXF-398) XMLBinding Provider<Source> implementations can not receive Multipart/Related messages
Date Wed, 31 Jan 2007 18:39:05 GMT


Sergey Beryozkin commented on CXF-398:

After this patch applied the follwing needs to be done :

* New Jira issue opened for creating LazyAttachmentMap which will defer the actual reading
of the attachments until Provider<Source> will actually request them

* for Provider<SoapBody> : on response a Provider implementation may wish to return
Message.OUTBOUND_MESSAGE_ATTACHMENTS, which will need to be converted in
to out Message.setAttachments;  org.apache.cxf.jaxws.ProviderChainObserver.onMessage() will
need AttachmentOutInterceptor added too to handle this case

* Clarify if Provider<DataSource> implementations need to get the root part only as
DataSource, if yes then it will require a single line change to ProviderChainObserver which
does not (in the attached path) adds AttachmentInInterceptor for Provider<DataSource>

> XMLBinding Provider<Source> implementations can not receive Multipart/Related messages

> ---------------------------------------------------------------------------------------
>                 Key: CXF-398
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.0-RC
>         Environment: Windows
>            Reporter: Sergey Beryozkin
>             Fix For: 2.0-RC
>         Attachments: rt_provider_attachment.patch
> XMLBinding Provider<Source> implementaions should be able to get the root part
of Multipart/Related messages as input Source in invoke(Source) and other (XML, text,  binary)
attachments as MesageContext.INBOUND_MESSAGE_ATTACHMENTS

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

View raw message