March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12964) org.jboss.as.test.integration.jpa.cfgfile.CfgFileTestCase fails

by Ingo Weiss (Jira)

[ https://issues.redhat.com/browse/WFLY-12964?page=com.atlassian.jira.plugi... ] Ingo Weiss updated WFLY-12964: ------------------------------ Labels: downstream_dependency (was: ) > org.jboss.as.test.integration.jpa.cfgfile.CfgFileTestCase fails > --------------------------------------------------------------- > > Key: WFLY-12964 > URL: https://issues.redhat.com/browse/WFLY-12964 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Gail Badner > Assignee: Gail Badner > Priority: Major > Labels: downstream_dependency > Fix For: 19.0.0.Beta1, 19.0.0.Final > > > The following fixes in Hibernate ORM 5.3.15.Final cause {{org.jboss.as.test.integration.jpa.cfgfile.CfgFileTestCase}} to fail: > https://hibernate.atlassian.net/browse/HHH-13432 > https://hibernate.atlassian.net/browse/HHH-12858 > There are 2 assertions in the test that fail with those fixes because the Map returned by {{EntityManagerFactory#getProperties}}: > 1) does not contain a value for property {{hibernate.connection.driver_class}}. > 2) contains a property for {{hibernate.connection.datasource}} that is a {{WildFlyDataSource}} instance, instead of the String {{"java:jboss/datasources/ExampleDS"}}. > For 1), Hibernate ORM removes the {{hibernate.connection.driver_class}} property from its copy because it makes no sense when a datasource is provided via {{hibernate.connection.datasource}}. > For 2), Hibernate ORM replaces the {{String}} value for {{hibernate.connection.datasource}} with the {{WildFlyDataSource}} instance. > I reviewed the JPA 2.2 specification and discussed this issue with [~smarlow], and we agreed that these were acceptable changes to the copy of properties that Hibernate ORM contains. > I have confirmed that these fixes do not cause any Jakarta standalone TCK failures. > The fix will involve replacing references to those properties with properties that Hibernate ORM does not change. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13176) Add jboss-ejb-client_1_3.xsd schema

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-13176?page=com.atlassian.jira.plugi... ] Cheng Fang reassigned WFLY-13176: --------------------------------- Assignee: Ranabir Chakraborty (was: Cheng Fang) > Add jboss-ejb-client_1_3.xsd schema > ------------------------------------ > > Key: WFLY-13176 > URL: https://issues.redhat.com/browse/WFLY-13176 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Cheng Fang > Assignee: Ranabir Chakraborty > Priority: Major > > WildFly currently (2020-02-28) includes schemas 1.0, 1.1, 1.2, but not 1.3: > {code} > ./src/main/resources/schema/jboss-ejb-client_1_1.xsd > ./src/main/resources/schema/jboss-ejb-client_1_0.xsd > ./src/main/resources/schema/jboss-ejb-client_1_2.xsd > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1946) Release WildFly Elytron 1.10.6.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1946: ------------------------------------- Summary: Release WildFly Elytron 1.10.6.Final Key: ELY-1946 URL: https://issues.redhat.com/browse/ELY-1946 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.10.6.CR1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1944) The org.wildfly.security:wildfly-elytron artefact incorrectly contains the Elytron CDI extension

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1944?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved ELY-1944. ----------------------------------- Resolution: Done > The org.wildfly.security:wildfly-elytron artefact incorrectly contains the Elytron CDI extension > ------------------------------------------------------------------------------------------------ > > Key: ELY-1944 > URL: https://issues.redhat.com/browse/ELY-1944 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.10.6.CR1, 1.11.3.CR1 > > > This means if the artefact is included in a deployment the JWT activation is incorrectly triggered but with some dependencies missing leading to an error such as the following. > {code} > 09:46:44,391 WARN [org.jboss.modules.define] (MSC service thread 1-1) Failed to define class org.wildfly.security.mp.jwt.JWTCDIExtension in Module "deployment.XXXX.ear" from Service Module Loader: java.lang.NoClassDefFoundError: Failed to link org/wildfly/security/mp/jwt/JWTCDIExtension (Module "deployment.XXXX.ear" from Service Module Loader): io/smallrye/jwt/auth/cdi/SmallRyeJWTAuthCDIExtension > at java.lang.ClassLoader.defineClass1(ClassLoader.java) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4848) JavaDoc generation doesn't work with JDK11 in droolsjbpm-knowledge repository

by Marek Novotny (Jira)

[ https://issues.redhat.com/browse/DROOLS-4848?page=com.atlassian.jira.plug... ] Marek Novotny closed DROOLS-4848. --------------------------------- > JavaDoc generation doesn't work with JDK11 in droolsjbpm-knowledge repository > ----------------------------------------------------------------------------- > > Key: DROOLS-4848 > URL: https://issues.redhat.com/browse/DROOLS-4848 > Project: Drools > Issue Type: Bug > Components: build > Affects Versions: 7.30.0.Final > Reporter: Tibor Zimanyi > Assignee: Marek Novotny > Priority: Major > Fix For: 7.34.0.Final > > > When building droolsjbpm-knowledge repository using JDK 11, the build fails on JavaDoc generation with message: > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (default) on project kie-api: Execution default of goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar failed: version can neither be null, empty nor blank -> [Help 1] > This is caused by commit [1], which moved some properties to a separate bom. This bom is imported into kie-parent, but with imporing bom, its properties cannot be used, so they are not visible to javadoc plugin configuration at 2 places, e.g. here [2]. I expect the JavaDoc build fails similarly in all reopsitories where it is used, when running the build using JDK 11. > [1] https://github.com/kiegroup/droolsjbpm-build-bootstrap/commit/5ef60cb79e9... > [2] https://github.com/kiegroup/droolsjbpm-build-bootstrap/blob/master/pom.xm... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13279) Support for multiple security realms - Distributed Identities Community docs

by Martin Mazánek (Jira)

[ https://issues.redhat.com/browse/WFLY-13279?page=com.atlassian.jira.plugi... ] Martin Mazánek updated WFLY-13279: ---------------------------------- Description: WFCORE-4485 Community docs (was: By stacking LoginModules it was possible using PicketBox to attempt to authenticate using one remote store and if that failed try the next store in the list. This RFE is to consider the use case where identities could be located across multiple stores and how they are aggregated together. Additionally this use case should consider how the authorization information could be loaded from multiple sources and merged. This RFE is not about fail over in the event of a realm being unavailable although it may be related. This RFE is created as a result of comparing the differences between the PicketBox JAAS architecture and the Elytron architecture so I would not recommend this proceeds without some real world use cases identified. ) Summary: Support for multiple security realms - Distributed Identities Community docs (was: Support for multiple security realms - Distributed Identities) > Support for multiple security realms - Distributed Identities Community docs > ---------------------------------------------------------------------------- > > Key: WFLY-13279 > URL: https://issues.redhat.com/browse/WFLY-13279 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Martin Mazánek > Assignee: Martin Mazánek > Priority: Major > Labels: CD17-Deferred, EAP-CD19, Previous_RFE > > WFCORE-4485 Community docs -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13278) CommandDispatcher cannot optimize marshalling of user command responses

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13278?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13278: -------------------------------- Description: Currently, all CommandDispatcher instances created from a given CommandDispatcherFactory share a single response marshaller. This means that the marshaller used by WF for its internal command responses is the same as the one used to marshal user command responses. This limits the extent to which commands may optimize marshalling of their responses, or indeed, use a different marshaller (e.g. ProtoStream). We can remove the limitations above by using a distinct response mashaller for each CommandDispatcher. > CommandDispatcher cannot optimize marshalling of user command responses > ----------------------------------------------------------------------- > > Key: WFLY-13278 > URL: https://issues.redhat.com/browse/WFLY-13278 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 19.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > Currently, all CommandDispatcher instances created from a given CommandDispatcherFactory share a single response marshaller. This means that the marshaller used by WF for its internal command responses is the same as the one used to marshal user command responses. This limits the extent to which commands may optimize marshalling of their responses, or indeed, use a different marshaller (e.g. ProtoStream). > We can remove the limitations above by using a distinct response mashaller for each CommandDispatcher. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4889) Support for multiple security realms - Distributed Identities

by Martin Mazánek (Jira)

Martin Mazánek created WFCORE-4889: -------------------------------------- Summary: Support for multiple security realms - Distributed Identities Key: WFCORE-4889 URL: https://issues.redhat.com/browse/WFCORE-4889 Project: WildFly Core Issue Type: Feature Request Components: Security Reporter: Martin Mazánek Assignee: Martin Mazánek By stacking LoginModules it was possible using PicketBox to attempt to authenticate using one remote store and if that failed try the next store in the list. This RFE is to consider the use case where identities could be located across multiple stores and how they are aggregated together. Additionally this use case should consider how the authorization information could be loaded from multiple sources and merged. This RFE is not about fail over in the event of a realm being unavailable although it may be related. This RFE is created as a result of comparing the differences between the PicketBox JAAS architecture and the Elytron architecture so I would not recommend this proceeds without some real world use cases identified. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13279) Support for multiple security realms - Distributed Identities

by Martin Mazánek (Jira)

[ https://issues.redhat.com/browse/WFLY-13279?page=com.atlassian.jira.plugi... ] Martin Mazánek moved WFCORE-4889 to WFLY-13279: ----------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-13279 (was: WFCORE-4889) Component/s: Security (was: Security) > Support for multiple security realms - Distributed Identities > ------------------------------------------------------------- > > Key: WFLY-13279 > URL: https://issues.redhat.com/browse/WFLY-13279 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Martin Mazánek > Assignee: Martin Mazánek > Priority: Major > Labels: CD17-Deferred, EAP-CD19, Previous_RFE > > By stacking LoginModules it was possible using PicketBox to attempt to authenticate using one remote store and if that failed try the next store in the list. > This RFE is to consider the use case where identities could be located across multiple stores and how they are aggregated together. > Additionally this use case should consider how the authorization information could be loaded from multiple sources and merged. > This RFE is not about fail over in the event of a realm being unavailable although it may be related. > This RFE is created as a result of comparing the differences between the PicketBox JAAS architecture and the Elytron architecture so I would not recommend this proceeds without some real world use cases identified. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13278) CommandDispatcher cannot optimize marshalling of user command responses

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13278: ----------------------------------- Summary: CommandDispatcher cannot optimize marshalling of user command responses Key: WFLY-13278 URL: https://issues.redhat.com/browse/WFLY-13278 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 19.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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 March 2020