Colm O hEigeartaigh created CXF-9279:
----------------------------------------

             Summary: Remove ObjectMessage and StreamMessage support from the 
JMS transport
                 Key: CXF-9279
                 URL: https://issues.apache.org/jira/browse/CXF-9279
             Project: CXF
          Issue Type: Improvement
            Reporter: Colm O hEigeartaigh
            Assignee: Colm O hEigeartaigh
             Fix For: 4.3.0


The JMS transport only needs TextMessage and BytesMessage payloads. SOAP over 
JMS allows only these two types, and CXF only ever uses String or byte[] 
content.

For 4.3.0 we will remove support for ObjectMessage and StreamMessage:
 * Inbound ObjectMessage and StreamMessage are no longer read. SOAP/JMS 
endpoints reply with an unsupportedJMSMessageFormat fault.
 * messageType=binary always sends a BytesMessage.
 * The allowObjectMessages and useObjectMessageFallback configuration options 
are removed.

This removes the transport’s remaining Java deserialization paths and 
simplifies its configuration.

_Migration:_ Remove allowObjectMessages and useObjectMessageFallback from 
Spring, Blueprint or Java configuration. If these options appear as JMS URI 
parameters, they are ignored. Applications that exchange messages with older 
CXF versions using messageType=binary with useObjectMessageFallback should 
switch to messageType=byte or text.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to