[
https://issues.apache.org/jira/browse/CXF-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marat Bedretdinov updated CXF-2366:
-----------------------------------
Attachment: CXF-2366.2009-28-13-42.patch
The following patch implements the stated requirement and is generated against
http://svn.apache.org/repos/asf/cxf/branches/2.1.x-fixes repository
> Allow for 1-way over JMS requests to set replyTo destination in JMS message
> when explicitly enabled
> ---------------------------------------------------------------------------------------------------
>
> Key: CXF-2366
> URL: https://issues.apache.org/jira/browse/CXF-2366
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.2, 2.1.5
> Reporter: Marat Bedretdinov
> Fix For: 2.1.6, 2.2.3
>
> Attachments: CXF-2366.2009-28-13-42.patch
>
>
> Some of the users of cxf requested that it should be possible to have one-way
> calls over JMS set JMS Message replyTo field with WSDL or invocation context
> provided destination.
> If a user has a named replyToDestination set in WSDL or spring Config for a
> given WSDL port and then using a proxy associated with that port client makes
> a one way call, the JMS Message's replyTo filed will be set with the
> replyToDestination from Spring config or WSDL in that order of priority
> respectfully.
> This will only be the case once the user specifically enables this behaviour
> by setting jms:clientcon...@enforsespec = false. By default CXF applications
> will function as before this change.
> The user can still specifically disable this behaviour on per request basis
> even when by default it is desirable to set and propagate replyTo for one-way
> calls by putting a property in the invocation conext
> JMSConstants.JMS_SET_REPLY_TO = false;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
