[jira] [Commented] (CXF-6778) Invalid replyDestination is cached after jms connection has been reset

[ https://issues.apache.org/jira/browse/CXF-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975634#comment-15975634 ] Christian Schneider commented on CXF-6778: -- I will look into it tomorrow. I think w

[jira] [Commented] (CXF-6778) Invalid replyDestination is cached after jms connection has been reset

[ https://issues.apache.org/jira/browse/CXF-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975508#comment-15975508 ] Grzegorz Majer commented on CXF-6778: - It doesn't fix the problem. As I described earlie

[jira] [Created] (CXF-7342) org.apache.cxf.attachment.AttachmentUtilTest.xml fails with jdk 9 preview

Adam Anderson created CXF-7342: -- Summary: org.apache.cxf.attachment.AttachmentUtilTest.xml fails with jdk 9 preview Key: CXF-7342 URL: https://issues.apache.org/jira/browse/CXF-7342 Project: CXF

[jira] [Commented] (CXF-7339) NPE in org.apache.cxf.common.util.CacheMap.remove

[ https://issues.apache.org/jira/browse/CXF-7339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974999#comment-15974999 ] ASF GitHub Bot commented on CXF-7339: - Github user asoldano commented on the issue:

[jira] [Created] (CXF-7341) org.apache.cxf.transport.jms.RequestResponseTest.testRequestTopicResponseStaticQueue times out with jdk9 preview

Adam Anderson created CXF-7341: -- Summary: org.apache.cxf.transport.jms.RequestResponseTest.testRequestTopicResponseStaticQueue times out with jdk9 preview Key: CXF-7341 URL: https://issues.apache.org/jira/browse/CXF

[jira] [Commented] (CXF-7339) NPE in org.apache.cxf.common.util.CacheMap.remove

[ https://issues.apache.org/jira/browse/CXF-7339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974955#comment-15974955 ] Andy McCright commented on CXF-7339: Hi Alessio, This is a legitimate bug, but instead

[jira] [Resolved] (CXF-7340) Make it possible to set the SignatureLocation in the XmlSecOutInterceptor from the SignatureProperties

[ https://issues.apache.org/jira/browse/CXF-7340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CXF-7340. -- Resolution: Fixed > Make it possible to set the SignatureLocation in the XmlSecOutIntercep

[jira] [Closed] (CXF-3235) Introduce a switch for the soap/jms spec transport to turn off SoapJMSInInterceptor

[ https://issues.apache.org/jira/browse/CXF-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider closed CXF-3235. Resolution: Won't Fix Assignee: Christian Schneider I think we can now expect clients to

[jira] [Assigned] (CXF-7340) Make it possible to set the SignatureLocation in the XmlSecOutInterceptor from the SignatureProperties

[ https://issues.apache.org/jira/browse/CXF-7340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned CXF-7340: Assignee: Colm O hEigeartaigh > Make it possible to set the SignatureLocation in the

[jira] [Commented] (CXF-7340) Make it possible to set the SignatureLocation in the XmlSecOutInterceptor from the SignatureProperties

[ https://issues.apache.org/jira/browse/CXF-7340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974784#comment-15974784 ] ASF GitHub Bot commented on CXF-7340: - Github user asfgit closed the pull request at:

[jira] [Updated] (CXF-7340) Make it possible to set the SignatureLocation in the XmlSecOutInterceptor from the SignatureProperties

[ https://issues.apache.org/jira/browse/CXF-7340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CXF-7340: - Fix Version/s: 3.1.12 > Make it possible to set the SignatureLocation in the XmlSecOutInterc

[jira] [Closed] (CXF-6016) Documentation listed for JMSConfiguration does not compile for 3.0.1 release.

[ https://issues.apache.org/jira/browse/CXF-6016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider closed CXF-6016. Resolution: Not A Bug Assignee: Christian Schneider There is no setting for max concurre

[jira] [Resolved] (CXF-6624) [SOAP][JMS] javax.jms.IllegalStateException when setting the exception listener

[ https://issues.apache.org/jira/browse/CXF-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved CXF-6624. -- Resolution: Not A Problem I don't think this is an issue in the CXF JMS transport. It look

[jira] [Assigned] (CXF-6624) [SOAP][JMS] javax.jms.IllegalStateException when setting the exception listener

[ https://issues.apache.org/jira/browse/CXF-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider reassigned CXF-6624: Assignee: Christian Schneider > [SOAP][JMS] javax.jms.IllegalStateException when sett

[jira] [Resolved] (CXF-7079) JMSConduit – is not removing entry from corelationMap if relpyMessage is null (timeout)

[ https://issues.apache.org/jira/browse/CXF-7079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved CXF-7079. -- Resolution: Fixed Assignee: Christian Schneider Fix Version/s: 3.0.13

[jira] [Commented] (CXF-7001) Update JAX-RS SpringBoot starter to support scanning JAX-RS Applications

[ https://issues.apache.org/jira/browse/CXF-7001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974758#comment-15974758 ] ASF GitHub Bot commented on CXF-7001: - Github user sberyozkin commented on the issue:

[jira] [Commented] (CXF-7001) Update JAX-RS SpringBoot starter to support scanning JAX-RS Applications

[ https://issues.apache.org/jira/browse/CXF-7001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974740#comment-15974740 ] ASF GitHub Bot commented on CXF-7001: - GitHub user deki opened a pull request: http

[jira] [Resolved] (CXF-6531) Exception-triggerring messages are re-delivered in endless loop

[ https://issues.apache.org/jira/browse/CXF-6531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved CXF-6531. -- Resolution: Not A Problem Can be solved by using redelivery limits > Exception-triggerrin

[jira] [Resolved] (CXF-6778) Invalid replyDestination is cached after jms connection has been reset

[ https://issues.apache.org/jira/browse/CXF-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved CXF-6778. -- Resolution: Fixed Waiting for feedback on solution. > Invalid replyDestination is cached

[jira] [Commented] (CXF-7340) Make it possible to set the SignatureLocation in the XmlSecOutInterceptor from the SignatureProperties

[ https://issues.apache.org/jira/browse/CXF-7340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974631#comment-15974631 ] ASF GitHub Bot commented on CXF-7340: - GitHub user spark404 opened a pull request:

[jira] [Created] (CXF-7340) Make it possible to set the SignatureLocation in the XmlSecOutInterceptor from the SignatureProperties

Hugo Trippaers created CXF-7340: --- Summary: Make it possible to set the SignatureLocation in the XmlSecOutInterceptor from the SignatureProperties Key: CXF-7340 URL: https://issues.apache.org/jira/browse/CXF-7340

[jira] [Commented] (CXF-6778) Invalid replyDestination is cached after jms connection has been reset

[ https://issues.apache.org/jira/browse/CXF-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974592#comment-15974592 ] Christian Schneider commented on CXF-6778: -- I added a commit on master to reset the

[jira] [Commented] (CXF-6531) Exception-triggerring messages are re-delivered in endless loop

[ https://issues.apache.org/jira/browse/CXF-6531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974560#comment-15974560 ] Christian Schneider commented on CXF-6531: -- Apart from this we could allow to defin

[jira] [Commented] (CXF-6937) Dealing with empty soap:body together with MIME-Attachment in wsdl

[ https://issues.apache.org/jira/browse/CXF-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974542#comment-15974542 ] fred assi commented on CXF-6937: I will be investigating this issue > Dealing with empty so

[jira] [Assigned] (CXF-6531) Exception-triggerring messages are re-delivered in endless loop

[ https://issues.apache.org/jira/browse/CXF-6531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider reassigned CXF-6531: Assignee: Christian Schneider > Exception-triggerring messages are re-delivered in en

[jira] [Commented] (CXF-6531) Exception-triggerring messages are re-delivered in endless loop

[ https://issues.apache.org/jira/browse/CXF-6531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974468#comment-15974468 ] Christian Schneider commented on CXF-6531: -- You need to configure your broker to de