You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Radu Manolescu (JIRA)" <ji...@apache.org> on 2008/06/13 20:19:45 UTC

[jira] Commented: (CXF-1538) message.getContent(OutputStream.class) cannot be null

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

Radu Manolescu commented on CXF-1538:
-------------------------------------

We are hitting this problem while trying to create secure SOAP messages. Is there any workaround at this time?

> message.getContent(OutputStream.class) cannot be null
> -----------------------------------------------------
>
>                 Key: CXF-1538
>                 URL: https://issues.apache.org/jira/browse/CXF-1538
>             Project: CXF
>          Issue Type: Bug
>          Components: Core, JAX-WS Runtime
>         Environment: snapshot 20080414
>            Reporter: Gyorgy Orban
>             Fix For: 2.1.1
>
>
> SAAJOutEndingInterceptor assumes that message.getContent(OutputStream.class) is not null. It causes problems when we try to add a SOAPHandler. I wonder if it would be possible to check first if the OutputStream is available in the message and not throw an exception in case we have only an XMLStreamWriter? The reason why we keep only XMLStreamWriter on the message is that we use a binary xml stream implementation of STAX which writes binary data to the underlying stream, so once the XMLStreamWriter is created the OutputStream cannot be used directly any more.

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