September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10494) HHH-12651 org.hibernate.Session.*Query(Ljava/lang/String) methods return different types in 5.1 and 5.3

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10494?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10494: --------------------------------- Fix Version/s: 14.0.0.Beta2 > HHH-12651 org.hibernate.Session.*Query(Ljava/lang/String) methods return different types in 5.1 and 5.3 > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-10494 > URL: https://issues.jboss.org/browse/WFLY-10494 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 13.0.0.Final > Reporter: Martin Simka > Assignee: Scott Marlow > Priority: Blocker > Labels: blocker-WF14 > Fix For: 14.0.0.Beta2 > > > https://hibernate.atlassian.net/browse/HHH-12651 > although mentioned in HHH-12424, it doesn't seem to be resolved > in 5.1 > org.hibernate.Session.createQuery(Ljava/lang/String;)Lorg/hibernate/Query > in 5.3 > org.hibernate.Session.createQuery(Ljava/lang/String;)Lorg/hibernate.query.Query > It happens when code compiled with Hibernate ORM 5.1 is run with Hibernate ORM 5.3 > I attached very simple reproducer class. > {code} > # compile with Hibernate 5.1 > javac App.java -cp ~/.m2/repository/org/hibernate/hibernate-core/5.1.9.Final/hibernate-core-5.1.9.Final.jar > # run with 5.1 => ok > java -cp .:/home/msimka/.m2/repository/org/hibernate/hibernate-core/5.1.9.Final/hibernate-core-5.1.9.Final.jar App > # run with 5.3 => fail > java -cp .:/home/msimka/.m2/repository/org/hibernate/hibernate-core/5.3.1.Final/hibernate-core-5.3.1.Final.jar:/home/msimka/.m2/repository/javax/persistence/javax.persistence-api/2.2/javax.persistence-api-2.2.jar App > Exception in thread "main" java.lang.NoSuchMethodError: org.hibernate.Session.createQuery(Ljava/lang/String;)Lorg/hibernate/Query; > at App.main(App.java:35) > {code} > other methods with the same issue: > java.lang.NoSuchMethodError: org.hibernate.Session.getNamedQuery(Ljava/lang/String;)Lorg/hibernate/Query; > java.lang.NoSuchMethodError: org.hibernate.Session.createSQLQuery(Ljava/lang/String;)Lorg/hibernate/SQLQuery; -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-440) Create a Istio Cleanup Job

by Guilherme Baufaker Rêgo (JIRA)

Guilherme Baufaker Rêgo created SWSQE-440: --------------------------------------------- Summary: Create a Istio Cleanup Job Key: SWSQE-440 URL: https://issues.jboss.org/browse/SWSQE-440 Project: Kiali QE Issue Type: Sub-task Reporter: Guilherme Baufaker Rêgo Assignee: Guilherme Baufaker Rêgo This Job will handle all the deletion that needs to be done before installing/reinstalling istio -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-419) Enhance Maistra Pipeline Support

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-419?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reopened SWSQE-419: ------------------------------------------- > Enhance Maistra Pipeline Support > -------------------------------- > > Key: SWSQE-419 > URL: https://issues.jboss.org/browse/SWSQE-419 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > Maistra Pipeline would need to have some additions to have better support (Some of them include) > - Remove Maistra Job from Upstream Pipeline (SWSQE-423) > - Add Minimal CR option (this will install default versions listed on istio-operator) - (SWSQE-429) > > - Include Option to run or not run Kiali Istio Checker > > - Crate Maistra Message Bus Job (SWSQE-424) > - Include Bookinfo, Include E2E Test Run, Include UI Test Run (SWSQE-430) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (ELYWEB-21) Release Elytron Web 1.3.0.CR1

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELYWEB-21: -------------------------------------- Summary: Release Elytron Web 1.3.0.CR1 Key: ELYWEB-21 URL: https://issues.jboss.org/browse/ELYWEB-21 Project: Elytron Web Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.3.CR1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4134) Upgrade Elytron Web to 1.3.0.CR1

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-4134: ---------------------------------------- Summary: Upgrade Elytron Web to 1.3.0.CR1 Key: WFCORE-4134 URL: https://issues.jboss.org/browse/WFCORE-4134 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4133) Upgrade WildFly Elytron to 1.7.0.CR2

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-4133: ---------------------------------------- Summary: Upgrade WildFly Elytron to 1.7.0.CR2 Key: WFCORE-4133 URL: https://issues.jboss.org/browse/WFCORE-4133 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (ELYWEB-20) Upgrade to WildFly Elytron 1.7.0.CR2

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELYWEB-20: -------------------------------------- Summary: Upgrade to WildFly Elytron 1.7.0.CR2 Key: ELYWEB-20 URL: https://issues.jboss.org/browse/ELYWEB-20 Project: Elytron Web Issue Type: Component Upgrade Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.3.0.CR1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (ELY-1685) Incorrectly named attribute match-user in authentication-context in Elytron subsystem

by Jan Kalina (JIRA)

Jan Kalina created ELY-1685: ------------------------------- Summary: Incorrectly named attribute match-user in authentication-context in Elytron subsystem Key: ELY-1685 URL: https://issues.jboss.org/browse/ELY-1685 Project: WildFly Elytron Issue Type: Bug Components: XML Reporter: Jan Kalina Assignee: Jan Kalina Priority: Critical Fix For: 1.1.0.Beta49 Rule matcher {{match-user}} in authentication-context in Elytron subsystem internally uses {{org.wildfly.security.auth.client.MatchUserRule}}. This matcher works based on passed userinfo. However naming of {{match-user}} in Elytron subsystem indicates that just user part of userinfo should be used in matching. Also description in CLI is not correct, it says: _The user to match against._ It means one of following should be changed: * name of {{match-user}} * functionality of {{MatchUserRule}} Since Elytron client configuration file includes for the same matcher with name {{match-userinfo}} then I suggest to rename attribute {{match-user}} in {{authentication-context}} in Elytron subsystem to {{match-userinfo}} and improve description in CLI and XSD. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-11083) Incorrectly named attribute match-user in authentication-context in Elytron subsystem

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-11083?page=com.atlassian.jira.plugin... ] Jan Kalina moved ELY-1685 to WFLY-11083: ---------------------------------------- Project: WildFly (was: WildFly Elytron) Key: WFLY-11083 (was: ELY-1685) Component/s: Documentation (was: XML) Fix Version/s: (was: 1.1.0.Beta49) > Incorrectly named attribute match-user in authentication-context in Elytron subsystem > ------------------------------------------------------------------------------------- > > Key: WFLY-11083 > URL: https://issues.jboss.org/browse/WFLY-11083 > Project: WildFly > Issue Type: Bug > Components: Documentation > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Critical > Labels: user_experience > > Rule matcher {{match-user}} in authentication-context in Elytron subsystem internally uses {{org.wildfly.security.auth.client.MatchUserRule}}. This matcher works based on passed userinfo. However naming of {{match-user}} in Elytron subsystem indicates that just user part of userinfo should be used in matching. > Also description in CLI is not correct, it says: _The user to match against._ > It means one of following should be changed: > * name of {{match-user}} > * functionality of {{MatchUserRule}} > Since Elytron client configuration file includes for the same matcher with name {{match-userinfo}} then I suggest to rename attribute {{match-user}} in {{authentication-context}} in Elytron subsystem to {{match-userinfo}} and improve description in CLI and XSD. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10208) [Artemis 2.x upgrade] Bad constant used in PropertySQLProviderFactory

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10208?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10208: --------------------------------- Fix Version/s: 14.0.0.Final > [Artemis 2.x upgrade] Bad constant used in PropertySQLProviderFactory > --------------------------------------------------------------------- > > Key: WFLY-10208 > URL: https://issues.jboss.org/browse/WFLY-10208 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Blocker > Labels: feature-branch-blocker > Fix For: 14.0.0.Final > > > There is bad constant used on line \[1\]. The SQL should release backup lock so BACKUP_LOCK_ROW_ID should be used instead of LIVE_LOCK_ROW_ID. > \[1\] https://github.com/jmesnil/wildfly/blob/be3af696141c9a6755583a5d1ab82f851... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2018