[jira] [Updated] (CXF-9003) Name clash when two SEIs have a same name method in the same Java package

[ https://issues.apache.org/jira/browse/CXF-9003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Palaga updated CXF-9003: -- Description: Originally reported for Quarkus CXF:

[jira] [Created] (CXF-9003) Name clash when two SEIs have a same name method in the same Java package

Peter Palaga created CXF-9003: - Summary: Name clash when two SEIs have a same name method in the same Java package Key: CXF-9003 URL: https://issues.apache.org/jira/browse/CXF-9003 Project: CXF

[jira] [Created] (CXF-8983) cxf-services-sts-core should depend on cxf-rt-rs-security-jose instead of cxf-rt-rs-security-jose-jaxrs

Peter Palaga created CXF-8983: - Summary: cxf-services-sts-core should depend on cxf-rt-rs-security-jose instead of cxf-rt-rs-security-jose-jaxrs Key: CXF-8983 URL: https://issues.apache.org/jira/browse/CXF-8983

[jira] [Commented] (CXF-8971) Introduce a customerizedAlgorithmSuite and make all parameters of it configurable

[ https://issues.apache.org/jira/browse/CXF-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814374#comment-17814374 ] Peter Palaga commented on CXF-8971: --- [~ffang] thanks for bringing up the option to implement this via

[jira] [Commented] (CXF-8971) Introduce a customerizedAlgorithmSuite and make all parameters of it configurable

[ https://issues.apache.org/jira/browse/CXF-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808775#comment-17808775 ] Peter Palaga commented on CXF-8971: --- [~coheigea] do you perhaps see any alternative/easier way to run CXF

[jira] [Comment Edited] (CXF-8971) Introduce a customerizedAlgorithmSuite and make all parameters of it configurable

[ https://issues.apache.org/jira/browse/CXF-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808768#comment-17808768 ] Peter Palaga edited comment on CXF-8971 at 1/19/24 6:21 PM: bq. It would be

[jira] [Commented] (CXF-8971) Introduce a customerizedAlgorithmSuite and make all parameters of it configurable

[ https://issues.apache.org/jira/browse/CXF-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808768#comment-17808768 ] Peter Palaga commented on CXF-8971: --- bq. It would be great that we can introduce a fully configurable

[jira] [Commented] (CXF-8967) More informative message should be given if multiple security bindings co-exist in ws-securitypolicy

[ https://issues.apache.org/jira/browse/CXF-8967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803706#comment-17803706 ] Peter Palaga commented on CXF-8967: --- Perfect, thanks1 > More informative message should be given if

[jira] [Comment Edited] (CXF-8967) More informative message should be given if multiple security bindings co-exist in ws-securitypolicy

[ https://issues.apache.org/jira/browse/CXF-8967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803706#comment-17803706 ] Peter Palaga edited comment on CXF-8967 at 1/5/24 9:05 PM: --- Perfect, thanks!

[jira] [Commented] (CXF-8967) Body and elements not signed with security.enable.streaming = true

[ https://issues.apache.org/jira/browse/CXF-8967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803356#comment-17803356 ] Peter Palaga commented on CXF-8967: --- Thanks [~ffang], should I create a new issue or we can just rename

[jira] [Commented] (CXF-8967) Body and elements not signed with security.enable.streaming = true

[ https://issues.apache.org/jira/browse/CXF-8967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803347#comment-17803347 ] Peter Palaga commented on CXF-8967: --- Thanks a lot [~ffang] for the explanation and fix in

[jira] [Updated] (CXF-8968) OpenTelemetryClientFeature cannot be used as a CDI bean unless it has a no-args constructor

[ https://issues.apache.org/jira/browse/CXF-8968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Palaga updated CXF-8968: -- Summary: OpenTelemetryClientFeature cannot be used as a CDI bean unless it has a no-args constructor

[jira] [Created] (CXF-8968) OpenTelemetryClientFeature cannot be used a CDI bean without the no-args constructor

Peter Palaga created CXF-8968: - Summary: OpenTelemetryClientFeature cannot be used a CDI bean without the no-args constructor Key: CXF-8968 URL: https://issues.apache.org/jira/browse/CXF-8968 Project:

[jira] [Updated] (CXF-8967) Body and elements not signed with security.enable.streaming = true

[ https://issues.apache.org/jira/browse/CXF-8967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Palaga updated CXF-8967: -- Description: This might have a similar cause like CXF-8940. I am unfortunately not sure at all how to

[jira] [Created] (CXF-8967) Body and elements not signed with security.enable.streaming = true

Peter Palaga created CXF-8967: - Summary: Body and elements not signed with security.enable.streaming = true Key: CXF-8967 URL: https://issues.apache.org/jira/browse/CXF-8967 Project: CXF Issue

[jira] [Commented] (CXF-8911) Allow creating a custom CXFHttpAsyncResponseConsumer

[ https://issues.apache.org/jira/browse/CXF-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782899#comment-17782899 ] Peter Palaga commented on CXF-8911: --- Sorry for the late response and thanks for the ideas, [~reta] and

[jira] [Comment Edited] (CXF-8911) Allow creating a custom CXFHttpAsyncResponseConsumer

[ https://issues.apache.org/jira/browse/CXF-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782899#comment-17782899 ] Peter Palaga edited comment on CXF-8911 at 11/4/23 3:52 PM: Sorry for the late

[jira] [Commented] (CXF-8940) ws-security.must-understand works only if security.enable.streaming is true

[ https://issues.apache.org/jira/browse/CXF-8940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782895#comment-17782895 ] Peter Palaga commented on CXF-8940: --- Thanks for fixing this [~ffang]! The

[jira] [Closed] (CXF-8949) Move CxfMessageHeadersRelayTest to camel-cxf-soap

[ https://issues.apache.org/jira/browse/CXF-8949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Palaga closed CXF-8949. - Resolution: Invalid This is where I should have created it:

[jira] [Commented] (CXF-8949) Move CxfMessageHeadersRelayTest to camel-cxf-soap

[ https://issues.apache.org/jira/browse/CXF-8949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779075#comment-17779075 ] Peter Palaga commented on CXF-8949: --- Oh, I am so sorry for the noise. Of course this belongs to Camel.

[jira] [Created] (CXF-8949) Move CxfMessageHeadersRelayTest to camel-cxf-soap

Peter Palaga created CXF-8949: - Summary: Move CxfMessageHeadersRelayTest to camel-cxf-soap Key: CXF-8949 URL: https://issues.apache.org/jira/browse/CXF-8949 Project: CXF Issue Type: Bug

[jira] [Commented] (CXF-8940) ws-security.must-understand works only if security.enable.streaming is true

[ https://issues.apache.org/jira/browse/CXF-8940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17775302#comment-17775302 ] Peter Palaga commented on CXF-8940: --- I can see WSSecurityInterceptorProvider being created and registered

[jira] [Updated] (CXF-8940) ws-security.must-understand works only if security.enable.streaming is true

[ https://issues.apache.org/jira/browse/CXF-8940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Palaga updated CXF-8940: -- Description: I am unfortunately not sure at all how to reproduce this with plain CXF. If a test is

[jira] [Updated] (CXF-8940) ws-security.must-understand works only if security.enable.streaming is true

[ https://issues.apache.org/jira/browse/CXF-8940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Palaga updated CXF-8940: -- Description: I am unfortunately not sure at all how to reproduce this with plain CXF. If a test is

[jira] [Created] (CXF-8940) ws-security.must-understand works only if security.enable.streaming is true

Peter Palaga created CXF-8940: - Summary: ws-security.must-understand works only if security.enable.streaming is true Key: CXF-8940 URL: https://issues.apache.org/jira/browse/CXF-8940 Project: CXF

[jira] (CXF-8885) HttpClient SelectorManager threads run indefinitely causing OOM

[ https://issues.apache.org/jira/browse/CXF-8885 ] Peter Palaga deleted comment on CXF-8885: --- was (Author: ppalaga): This is issue could by summed up as follows: if an application creates clients more frequently (e.g. per request) than once at

[jira] [Commented] (CXF-8885) HttpClient SelectorManager threads run indefinitely causing OOM

[ https://issues.apache.org/jira/browse/CXF-8885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17761791#comment-17761791 ] Peter Palaga commented on CXF-8885: --- This is issue could by summed up as follows: if an application

[jira] [Created] (CXF-8911) Allow creating a custom CXFHttpAsyncResponseConsumer

Peter Palaga created CXF-8911: - Summary: Allow creating a custom CXFHttpAsyncResponseConsumer Key: CXF-8911 URL: https://issues.apache.org/jira/browse/CXF-8911 Project: CXF Issue Type: New

[jira] [Created] (CXF-8834) "Operation [{.../wsdl}Issue] already exists" when calling JaxWsServerFactoryBean.create() for SecurityTokenService

Peter Palaga created CXF-8834: - Summary: "Operation [{.../wsdl}Issue] already exists" when calling JaxWsServerFactoryBean.create() for SecurityTokenService Key: CXF-8834 URL: