[jira] Updated: (CXF-2804) Allow ability to reset values in ResponseTimeCounter

[ https://issues.apache.org/jira/browse/CXF-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seumas Soltysik updated CXF-2804: - Attachment: cxf-2804.patch Patch to be applied at rt/management level. Also, I have a question abo

[jira] Created: (CXF-2804) Allow ability to reset values in ResponseTimeCounter

Allow ability to reset values in ResponseTimeCounter Key: CXF-2804 URL: https://issues.apache.org/jira/browse/CXF-2804 Project: CXF Issue Type: Improvement Components: JAX-WS Run

[jira] Updated: (CXF-2793) Provide capability for JMS client to specify separate ReplyTo queue and listener queue

[ https://issues.apache.org/jira/browse/CXF-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seumas Soltysik updated CXF-2793: - Attachment: cxf-2793-trunk.patch I have attached a second patch specifically for the trunk. > Prov

[jira] Commented: (CXF-2793) Provide capability for JMS client to specify separate ReplyTo queue and listener queue

[ https://issues.apache.org/jira/browse/CXF-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862820#action_12862820 ] Seumas Soltysik commented on CXF-2793: -- The attached patch is based off the 2.1.x-fixes

[jira] Updated: (CXF-2793) Provide capability for JMS client to specify separate ReplyTo queue and listener queue

[ https://issues.apache.org/jira/browse/CXF-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seumas Soltysik updated CXF-2793: - Attachment: CXF-2793.patch Attaching patch for requested feature. > Provide capability for JMS cli

[jira] Created: (CXF-2793) Provide capability for JMS client to specify separate ReplyTo queue and listener queue

Provide capability for JMS client to specify separate ReplyTo queue and listener queue -- Key: CXF-2793 URL: https://issues.apache.org/jira/browse/CXF-2793 Project: C

[jira] Updated: (CXF-2760) implement useMessageIDAsCorrelationID for JMS Client

[ https://issues.apache.org/jira/browse/CXF-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seumas Soltysik updated CXF-2760: - Attachment: cxf-2760.patch Attaching patch file based upon feed-back from Willem and Christian. >

[jira] Commented: (CXF-2760) implement useMessageIDAsCorrelationID for JMS Client

[ https://issues.apache.org/jira/browse/CXF-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858913#action_12858913 ] Seumas Soltysik commented on CXF-2760: -- Christian, Any thoughts on the issues raised on

[jira] Commented: (CXF-2760) implement useMessageIDAsCorrelationID for JMS Client

[ https://issues.apache.org/jira/browse/CXF-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857437#action_12857437 ] Seumas Soltysik commented on CXF-2760: -- Started a thread to discuss this on the dev list

[jira] Commented: (CXF-2760) implement useMessageIDAsCorrelationID for JMS Client

[ https://issues.apache.org/jira/browse/CXF-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857197#action_12857197 ] Seumas Soltysik commented on CXF-2760: -- Ok. I think I have a better idea of how this fea

[jira] Updated: (CXF-2760) implement useMessageIDAsCorrelationID for JMS Client

[ https://issues.apache.org/jira/browse/CXF-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seumas Soltysik updated CXF-2760: - Attachment: (was: cxf-2760.patch) > implement useMessageIDAsCorrelationID for JMS Client >

[jira] Commented: (CXF-2760) implement useMessageIDAsCorrelationID for JMS Client

[ https://issues.apache.org/jira/browse/CXF-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857131#action_12857131 ] Seumas Soltysik commented on CXF-2760: -- It looks like what is on the trunk is trying to

[jira] Commented: (CXF-2760) implement useMessageIDAsCorrelationID for JMS Client

[ https://issues.apache.org/jira/browse/CXF-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857113#action_12857113 ] Seumas Soltysik commented on CXF-2760: -- I have made the fix to an internal branch off th

[jira] Commented: (CXF-2760) implement useMessageIDAsCorrelationID for JMS Client

[ https://issues.apache.org/jira/browse/CXF-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857104#action_12857104 ] Seumas Soltysik commented on CXF-2760: -- As stated in the MQSeries world clients acting a

[jira] Commented: (CXF-2760) implement useMessageIDAsCorrelationID for JMS Client

[ https://issues.apache.org/jira/browse/CXF-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857094#action_12857094 ] Seumas Soltysik commented on CXF-2760: -- I created the patch from the 2.1.x branch with t

[jira] Commented: (CXF-2760) implement useMessageIDAsCorrelationID for JMS Client

[ https://issues.apache.org/jira/browse/CXF-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856544#action_12856544 ] Seumas Soltysik commented on CXF-2760: -- Any ideas as to when this patch might get review

[jira] Issue Comment Edited: (CXF-2760) implement useMessageIDAsCorrelationID for JMS Client

[ https://issues.apache.org/jira/browse/CXF-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855673#action_12855673 ] Seumas Soltysik edited comment on CXF-2760 at 4/10/10 11:09 PM: ---

[jira] Updated: (CXF-2760) implement useMessageIDAsCorrelationID for JMS Client

[ https://issues.apache.org/jira/browse/CXF-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seumas Soltysik updated CXF-2760: - Fix Version/s: 2.1.4 (was: 2.0.12) Affects Version/s: 2.1.4

[jira] Updated: (CXF-2760) implement useMessageIDAsCorrelationID for JMS Client

[ https://issues.apache.org/jira/browse/CXF-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seumas Soltysik updated CXF-2760: - Attachment: cxf-2760.patch > implement useMessageIDAsCorrelationID for JMS Client > ---

[jira] Updated: (CXF-2760) implement useMessageIDAsCorrelationID for JMS Client

[ https://issues.apache.org/jira/browse/CXF-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seumas Soltysik updated CXF-2760: - Description: MQSeries servers often use the message ID of and incoming message as the correlation

[jira] Created: (CXF-2760) implement useMessageIDAsCorrelationID for JMS Client

implement useMessageIDAsCorrelationID for JMS Client Key: CXF-2760 URL: https://issues.apache.org/jira/browse/CXF-2760 Project: CXF Issue Type: New Feature Components: Transports

[jira] Created: (CXF-2543) CXF client processes bar() response message when making foo() request

CXF client processes bar() response message when making foo() request - Key: CXF-2543 URL: https://issues.apache.org/jira/browse/CXF-2543 Project: CXF Issue Type: Bug

[jira] Commented: (CXF-2398) JMS Connections are not closed when JCA recycles CXF proxy

[ https://issues.apache.org/jira/browse/CXF-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746178#action_12746178 ] Seumas Soltysik commented on CXF-2398: -- 6.5.4.4 "The container always drives the cleanup

[jira] Commented: (CXF-2398) JMS Connections are not closed when JCA recycles CXF proxy

[ https://issues.apache.org/jira/browse/CXF-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746145#action_12746145 ] Seumas Soltysik commented on CXF-2398: -- Keep in mind that the following structure: Handl

[jira] Commented: (CXF-2398) JMS Connections are not closed when JCA recycles CXF proxy

[ https://issues.apache.org/jira/browse/CXF-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746115#action_12746115 ] Seumas Soltysik commented on CXF-2398: -- I understand your comments regarding a proxy per

[jira] Updated: (CXF-2398) JMS Connections are not closed when JCA recycles CXF proxy

[ https://issues.apache.org/jira/browse/CXF-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seumas Soltysik updated CXF-2398: - Attachment: CXF-2398.patch2 Patch to fix modify how client proxy is destroyed in ManagedConnection.

[jira] Reopened: (CXF-2398) JMS Connections are not closed when JCA recycles CXF proxy

[ https://issues.apache.org/jira/browse/CXF-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seumas Soltysik reopened CXF-2398: -- Further testing and reading of the JCA spec indicate that destroying the client proxy when close is

[jira] Updated: (CXF-2398) JMS Connections are not closed when JCA recycles CXF proxy

[ https://issues.apache.org/jira/browse/CXF-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seumas Soltysik updated CXF-2398: - Attachment: CXF-2398.patch Patch allows JCA to call Client.destroy() which in turn will close the

[jira] Created: (CXF-2398) JMS Connections are not closed when JCA recycles CXF proxy

JMS Connections are not closed when JCA recycles CXF proxy -- Key: CXF-2398 URL: https://issues.apache.org/jira/browse/CXF-2398 Project: CXF Issue Type: Bug Components: Integr

[jira] Updated: (CXF-2372) Allow JMS XAResource to participate in J2EE transaction

[ https://issues.apache.org/jira/browse/CXF-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seumas Soltysik updated CXF-2372: - Attachment: CXF-2372.patch3 Ok. One more time. Patch tested this time. > Allow JMS XAResource to p

[jira] Updated: (CXF-2372) Allow JMS XAResource to participate in J2EE transaction

[ https://issues.apache.org/jira/browse/CXF-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seumas Soltysik updated CXF-2372: - Attachment: CXF-2372.patch2 Agreed regarding comments on patch. See new patch for modifications and

[jira] Updated: (CXF-2372) Allow JMS XAResource to participate in J2EE transaction

[ https://issues.apache.org/jira/browse/CXF-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seumas Soltysik updated CXF-2372: - Attachment: CXF-2372.patch > Allow JMS XAResource to participate in J2EE transaction >

[jira] Created: (CXF-2372) Allow JMS XAResource to participate in J2EE transaction

Allow JMS XAResource to participate in J2EE transaction --- Key: CXF-2372 URL: https://issues.apache.org/jira/browse/CXF-2372 Project: CXF Issue Type: Improvement Components: Inte

[jira] Updated: (CXF-2145) Proxy in JCA connector throws exception due to concurrency issues

[ https://issues.apache.org/jira/browse/CXF-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seumas Soltysik updated CXF-2145: - Attachment: patch3.txt One more time. > Proxy in JCA connector throws exception due to concurrency

[jira] Updated: (CXF-2145) Proxy in JCA connector throws exception due to concurrency issues

[ https://issues.apache.org/jira/browse/CXF-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seumas Soltysik updated CXF-2145: - Attachment: patch2.txt This second patch simplifies the process of retreiving a new endpoint for ea

[jira] Updated: (CXF-2145) Proxy in JCA connector throws exception due to concurrency issues

[ https://issues.apache.org/jira/browse/CXF-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seumas Soltysik updated CXF-2145: - Attachment: patch.txt This is patch for 2.0.x but undoubted needs to also be applied to 2.1.x and

[jira] Created: (CXF-2145) Proxy in JCA connector throws exception due to concurrency issues

Proxy in JCA connector throws exception due to concurrency issues - Key: CXF-2145 URL: https://issues.apache.org/jira/browse/CXF-2145 Project: CXF Issue Type: Bug Comp

[jira] Updated: (CXF-2075) Error in spring config file reported as a missing config file during initialization of BusApplicationContext

[ https://issues.apache.org/jira/browse/CXF-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seumas Soltysik updated CXF-2075: - Attachment: patch.txt Attached is a patch for this issue. the patch logs the initial exception afte

[jira] Commented: (CXF-2075) Error in spring config file reported as a missing config file during initialization of BusApplicationContext

[ https://issues.apache.org/jira/browse/CXF-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678040#action_12678040 ] Seumas Soltysik commented on CXF-2075: -- Sergey you suggested holding onto the original e

[jira] Commented: (CXF-2075) Error in spring config file reported as a missing config file during initialization of BusApplicationContext

[ https://issues.apache.org/jira/browse/CXF-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677410#action_12677410 ] Seumas Soltysik commented on CXF-2075: -- Sergey, thanks for the input. One additional is

[jira] Created: (CXF-2075) Error in spring config file reported as a missing config file during initialization of BusApplicationContext

Error in spring config file reported as a missing config file during initialization of BusApplicationContext Key: CXF-2075 URL: https://issues.apache.org/

[jira] Closed: (CXF-2032) JMSCorrelationID set by user causes client to not receive reply

[ https://issues.apache.org/jira/browse/CXF-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seumas Soltysik closed CXF-2032. Resolution: Invalid > JMSCorrelationID set by user causes client to not receive reply > -

[jira] Commented: (CXF-2032) JMSCorrelationID set by user causes client to not receive reply

[ https://issues.apache.org/jira/browse/CXF-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672774#action_12672774 ] Seumas Soltysik commented on CXF-2032: -- Marat, you are absolutely correct. I missed the

[jira] Created: (CXF-2032) JMSCorrelationID set by user causes client to not receive reply

JMSCorrelationID set by user causes client to not receive reply --- Key: CXF-2032 URL: https://issues.apache.org/jira/browse/CXF-2032 Project: CXF Issue Type: Bug Componen

[jira] Created: (CXF-1805) Use of Content-Type in JMS Header not in line with JMS specification

Use of Content-Type in JMS Header not in line with JMS specification Key: CXF-1805 URL: https://issues.apache.org/jira/browse/CXF-1805 Project: CXF Issue Type: Bug