[JBoss JIRA] (WFLY-2859) Treating all JAX-RS components as CDI Beans has some negative consequences
by Ronald Sigal (Jira)
[ https://issues.jboss.org/browse/WFLY-2859?page=com.atlassian.jira.plugin.... ]
Ronald Sigal commented on WFLY-2859:
------------------------------------
[~matt.drees], we should be able to close this, right?
> Treating all JAX-RS components as CDI Beans has some negative consequences
> --------------------------------------------------------------------------
>
> Key: WFLY-2859
> URL: https://issues.jboss.org/browse/WFLY-2859
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, REST
> Affects Versions: 8.0.0.CR1, 16.0.0.Beta1
> Reporter: Matt Drees
> Assignee: Stuart Douglas
> Priority: Major
>
> It seems that wildfly is now treating all jax-rs Providers and Resources as CDI Beans. This is probably fine most of the time, but there are some Provider classes that cause UnproxyableResolutionException (WELD-001437) errors, due to the fact that resteasy-cdi attempts to get bean reference whose type is identical to the bean class.
> See the forum link for a specific instance of this.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (JGRP-2371) SSL_KEY_EXCHANGE needs to support separate client and server SSLContexts
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/JGRP-2371?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated JGRP-2371:
---------------------------------
Description: Given the integration with Elytron, it differentiates between SSLContexts for client and server. The protocol needs to separate these too in order to support Elytron integration. Blocks WFLY-12164. (was: Given the integration with Elytron, it differentiates between SSLContexts for client and server. The protocol needs to separate these too in order to support Elytron integration. )
> SSL_KEY_EXCHANGE needs to support separate client and server SSLContexts
> ------------------------------------------------------------------------
>
> Key: JGRP-2371
> URL: https://issues.jboss.org/browse/JGRP-2371
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.1.3
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
> Fix For: 4.1.4
>
>
> Given the integration with Elytron, it differentiates between SSLContexts for client and server. The protocol needs to separate these too in order to support Elytron integration. Blocks WFLY-12164.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4442) [DMN Designer] Extract HashUtil from stunner to a even more reusable place
by Guilherme Gomes (Jira)
Guilherme Gomes created DROOLS-4442:
---------------------------------------
Summary: [DMN Designer] Extract HashUtil from stunner to a even more reusable place
Key: DROOLS-4442
URL: https://issues.jboss.org/browse/DROOLS-4442
Project: Drools
Issue Type: Task
Reporter: Guilherme Gomes
Assignee: Guilherme Gomes
Today the HashUtil cannot be used into drools-wb. HashUtil must be extract to a more generic place.
---
The {{GuidedDecisionTableGraphEditorPresenter}} motivated the creation of this JIRA. It has a similar logic implemented (since its module doesn't depend on stunner).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (JGRP-2370) SSL_KEY_EXCHANGE creates key_store in init() even if SSLContext is already provided
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/JGRP-2370?page=com.atlassian.jira.plugin.... ]
Radoslav Husar edited comment on JGRP-2370 at 8/16/19 4:39 PM:
---------------------------------------------------------------
Blocks WFLY-12164 – Elytron integration.
was (Author: rhusar):
Blocks WFLY-12164.
> SSL_KEY_EXCHANGE creates key_store in init() even if SSLContext is already provided
> -----------------------------------------------------------------------------------
>
> Key: JGRP-2370
> URL: https://issues.jboss.org/browse/JGRP-2370
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.1.3
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
> Fix For: 4.1.4
>
>
> This causes protocol initialization to fail if the setSSLContext(..) was used.
> {noformat}
> 17:55:10,947 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 82) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee: java.lang.IllegalStateException: java.io.FileNotFoundException: keystore.jks
> at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:70)
> at org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Caused by: java.lang.IllegalStateException: java.io.FileNotFoundException: keystore.jks
> at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:116)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:58)
> at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:67)
> ... 7 more
> Caused by: java.io.FileNotFoundException: keystore.jks
> at org.jgroups.protocols.SSL_KEY_EXCHANGE.init(SSL_KEY_EXCHANGE.java:170)
> at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:857)
> at org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:845)
> at org.jgroups.JChannel.<init>(JChannel.java:155)
> at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:116)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:96)
> ... 9 more
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months