July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5478) Propagate DataDictionary to avoid "Object" returned types

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5478: ---------------------------------------- Summary: Propagate DataDictionary to avoid "Object" returned types Key: DROOLS-5478 URL: https://issues.redhat.com/browse/DROOLS-5478 Project: Drools Issue Type: Sub-task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi FieldRef and Apply functions does not define directly the returned type. Propagating DataDictionary will allow to avoid generic "Object" return and replace it with specific one -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2484) SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2484?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2484: -------------------------------- Actually, I added a field {{use_native_if_available}} to {{SSL_KEY_EXCHANGE}} (default: {{false}}), and pass it to {{SSLContextFactory}} when getting a context. > SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL > ------------------------------------------------- > > Key: JGRP-2484 > URL: https://issues.redhat.com/browse/JGRP-2484 > Project: JGroups > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 5.0.0.Final > > > WildFly OpenSSL provides a high-performance implementation of SSLContext. > While SSL_KEY_EXCHANGE supports passing custom SSLContext instances through the programmatic API, this is not possible through the declarative API. > It should be possible to detect the presence of WildFly OpenSSL on the classpath and use it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2484) SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2484?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2484: -------------------------------- If you run {{ant encrypt}}, the testsuite hangs. Without WF's openssl, it passes. I'm going to restructure this slightly, so that this is disabled by default, and enabled when setting {{org.jgroups.openssl}} to {{true}}, until this is fixed > SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL > ------------------------------------------------- > > Key: JGRP-2484 > URL: https://issues.redhat.com/browse/JGRP-2484 > Project: JGroups > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 5.0.0.Final > > > WildFly OpenSSL provides a high-performance implementation of SSLContext. > While SSL_KEY_EXCHANGE supports passing custom SSLContext instances through the programmatic API, this is not possible through the declarative API. > It should be possible to detect the presence of WildFly OpenSSL on the classpath and use it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5477) Support instance of in the same way as Legacy Drools

by Luca Molteni (Jira)

Luca Molteni created DROOLS-5477: ------------------------------------ Summary: Support instance of in the same way as Legacy Drools Key: DROOLS-5477 URL: https://issues.redhat.com/browse/DROOLS-5477 Project: Drools Issue Type: Bug Components: executable model Reporter: Luca Molteni Assignee: Luca Molteni -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5030) EmbeddedServer can't interact with version <12

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFCORE-5030?page=com.atlassian.jira.plug... ] Yeray Borges Santana reassigned WFCORE-5030: -------------------------------------------- Assignee: Yeray Borges Santana (was: James Perkins) > EmbeddedServer can't interact with version <12 > ------------------------------------------------ > > Key: WFCORE-5030 > URL: https://issues.redhat.com/browse/WFCORE-5030 > Project: WildFly Core > Issue Type: Bug > Components: Embedded > Affects Versions: 12.0.1.Final > Reporter: Jean Francois Denise > Assignee: Yeray Borges Santana > Priority: Critical > > I am in context where an embedded server version 12.x is started for a version 11 (or 10) of wildfly-core. > This occurs with Bootable JAR maven plugin that depends on 12.x for its CLI support. > This can also happen using CLI shaded client JAR of WildFly 20 to start an embedded server for a WildFly 19 installation. > The problem has been introduced by https://issues.redhat.com/browse/WFCORE-4893 that defined a new method not supported by older versions. > The EmbeddedServer should be able to fallback to legacy logic if the new method is not present. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2484) SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/JGRP-2484?page=com.atlassian.jira.plugin... ] Tristan Tarrant commented on JGRP-2484: --------------------------------------- This would be an issue if the class had fields of types from the optional classes. However we are simply calling static methods, which means that the classloading is triggered only on invocation. I have verified that this works by removing {noformat} lib/wildfly-openssl-1.0.10.jar{noformat} and running the functional testsuite (which passed with 0 errors) > SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL > ------------------------------------------------- > > Key: JGRP-2484 > URL: https://issues.redhat.com/browse/JGRP-2484 > Project: JGroups > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 5.0.0.Final > > > WildFly OpenSSL provides a high-performance implementation of SSLContext. > While SSL_KEY_EXCHANGE supports passing custom SSLContext instances through the programmatic API, this is not possible through the declarative API. > It should be possible to detect the presence of WildFly OpenSSL on the classpath and use it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5029) server group deployment resource doesn't include deployment content attribute and correct "mananged" value

by Chao Wang (Jira)

[ https://issues.redhat.com/browse/WFCORE-5029?page=com.atlassian.jira.plug... ] Chao Wang commented on WFCORE-5029: ----------------------------------- I can confirm my previous comment in JBEAP-19768 that the missing deployment content under server group deployment resource causes incorrect value in web console. > server group deployment resource doesn't include deployment content attribute and correct "mananged" value > ---------------------------------------------------------------------------------------------------------- > > Key: WFCORE-5029 > URL: https://issues.redhat.com/browse/WFCORE-5029 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 13.0.0.Beta1 > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > > Unmanaged deploys show a checkmark that they are "managed" if you view the deployment under Server Groups. The deployment does however show correctly that it is un-managed in the Content Repository section. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5029) server group deployment resource doesn't include deployment content attribute and correct "mananged" value

by Chao Wang (Jira)

[ https://issues.redhat.com/browse/WFCORE-5029?page=com.atlassian.jira.plug... ] Chao Wang updated WFCORE-5029: ------------------------------ Summary: server group deployment resource doesn't include deployment content attribute and correct "mananged" value (was: Unmanaged deploys in a domain show as "managed" under server-groups) > server group deployment resource doesn't include deployment content attribute and correct "mananged" value > ---------------------------------------------------------------------------------------------------------- > > Key: WFCORE-5029 > URL: https://issues.redhat.com/browse/WFCORE-5029 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 13.0.0.Beta1 > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > > Unmanaged deploys show a checkmark that they are "managed" if you view the deployment under Server Groups. The deployment does however show correctly that it is un-managed in the Content Repository section. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5030) EmbeddedServer can't interact with version <12

by Jean Francois Denise (Jira)

Jean Francois Denise created WFCORE-5030: -------------------------------------------- Summary: EmbeddedServer can't interact with version <12 Key: WFCORE-5030 URL: https://issues.redhat.com/browse/WFCORE-5030 Project: WildFly Core Issue Type: Bug Components: Embedded Affects Versions: 12.0.1.Final Reporter: Jean Francois Denise Assignee: James Perkins I am in context where an embedded server version 12.x is started for a version 11 (or 10) of wildfly-core. This occurs with Bootable JAR maven plugin that depends on 12.x for its CLI support. This can also happen using CLI shaded client JAR of WildFly 20 to start an embedded server for a WildFly 19 installation. The problem has been introduced by https://issues.redhat.com/browse/WFCORE-4893 that defined a new method not supported by older versions. The EmbeddedServer should be able to fallback to legacy logic if the new method is not present. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5029) Unmanaged deploys in a domain show as "managed" under server-groups

by Chao Wang (Jira)

[ https://issues.redhat.com/browse/WFCORE-5029?page=com.atlassian.jira.plug... ] Chao Wang moved JBEAP-19817 to WFCORE-5029: ------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-5029 (was: JBEAP-19817) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Management (was: Management) (was: Web Console) Affects Version/s: 13.0.0.Beta1 (was: 7.3.1.GA) Fix Version/s: (was: 7.3.3.GA) > Unmanaged deploys in a domain show as "managed" under server-groups > ------------------------------------------------------------------- > > Key: WFCORE-5029 > URL: https://issues.redhat.com/browse/WFCORE-5029 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 13.0.0.Beta1 > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > > Unmanaged deploys show a checkmark that they are "managed" if you view the deployment under Server Groups. The deployment does however show correctly that it is un-managed in the Content Repository section. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2020