July 2020 - jboss-jira - Jboss List Archives

[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)

4 years, 2 months

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)

4 years, 2 months

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)

4 years, 2 months

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)

4 years, 2 months

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)

4 years, 2 months

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)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4461) Use date picker for LocalDate

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4461?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4461: -------------------------------- Tester: Jan Stastny (was: Anna Dupliak) > Use date picker for LocalDate > ----------------------------- > > Key: DROOLS-4461 > URL: https://issues.redhat.com/browse/DROOLS-4461 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor, Guided Rule Editor, Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > We should use the date picker for LocalDate like we do for Date. > h2. Acceptance test > - Guided rule condition (/) > - Guided rule action (/) > - Guided rule template condition (/) > - Guided rule template action (/) > - Guided decision table simple condition (/) > - Guided decision table BRL condition (/) > - Guided decision table simple action (/) > - Guided decision table BRL action (/) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem

by Richard Achmatowicz (Jira)

[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ] Richard Achmatowicz commented on WFLY-13433: -------------------------------------------- Added more resources: {noformat} TimerServiceResourceDefinition FileDataStoreResourceDefinition DatabaseDataStoreResourceDefinition FilePassivationStoreResourceDefinition ClusterPassivationStoreResourceDefinition {noformat} > Improve capability support in EJB3 subsystem > -------------------------------------------- > > Key: WFLY-13433 > URL: https://issues.redhat.com/browse/WFLY-13433 > Project: WildFly > Issue Type: Enhancement > Components: EJB > Affects Versions: 20.0.0.Beta1 > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Priority: Major > > Survey all external subsystem dependencies and introduce capability based dependencies where required. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem

by Richard Achmatowicz (Jira)

[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ] Richard Achmatowicz edited comment on WFLY-13433 at 7/2/20 7:36 PM: -------------------------------------------------------------------- Added more resources: {noformat} TimerServiceResourceDefinition FileDataStoreResourceDefinition DatabaseDataStoreResourceDefinition FilePassivationStoreResourceDefinition ClusterPassivationStoreResourceDefinition{noformat} was (Author: rachmato): Added more resources: {noformat} TimerServiceResourceDefinition FileDataStoreResourceDefinition DatabaseDataStoreResourceDefinition FilePassivationStoreResourceDefinition ClusterPassivationStoreResourceDefinition {noformat} > Improve capability support in EJB3 subsystem > -------------------------------------------- > > Key: WFLY-13433 > URL: https://issues.redhat.com/browse/WFLY-13433 > Project: WildFly > Issue Type: Enhancement > Components: EJB > Affects Versions: 20.0.0.Beta1 > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Priority: Major > > Survey all external subsystem dependencies and introduce capability based dependencies where required. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13642) Legacy store=remote throws NCDFE at runtime

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13642: ----------------------------------- Summary: Legacy store=remote throws NCDFE at runtime Key: WFLY-13642 URL: https://issues.redhat.com/browse/WFLY-13642 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 20.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 20.0.1.Final The remote-store references a marshaller from the infinispan jboss-marshalling module, which WF does not include, thus throws a NoClassDefFoundError at runtime if one is configured. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2020