[JBoss JIRA] (WFLY-10494) HHH-12651 org.hibernate.Session.*Query(Ljava/lang/String) methods return different types in 5.1 and 5.3
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-10494?page=com.atlassian.jira.plugin... ]
Scott Marlow resolved WFLY-10494.
---------------------------------
Resolution: Done
> 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
>
> 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, 11 months
[JBoss JIRA] (JBEE-196) JSP and JSTL missing from EE 7 BOM
by Eduardo Martins (JIRA)
[ https://issues.jboss.org/browse/JBEE-196?page=com.atlassian.jira.plugin.s... ]
Eduardo Martins commented on JBEE-196:
--------------------------------------
Ok, probably not on this week tho...
> JSP and JSTL missing from EE 7 BOM
> ----------------------------------
>
> Key: JBEE-196
> URL: https://issues.jboss.org/browse/JBEE-196
> Project: JBoss JavaEE Spec APIs
> Issue Type: Bug
> Affects Versions: JavaEE 7 Spec APIs 1.1.0.Final
> Reporter: Rich DiCroce
> Assignee: Eduardo Martins
>
> jboss-javaee-7.0 version 1.0.4 includes JSP and JSTL. Version 1.1.0 and later effectively do not, because they declare those dependencies to be provided scope for some reason. Servlet would also be affected, except JACC has a transitive dependency on it.
> This bug appears to have been introduced as part of resolving JBEE-170.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBEE-196) JSP and JSTL missing from EE 7 BOM
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/JBEE-196?page=com.atlassian.jira.plugin.s... ]
Scott Marlow commented on JBEE-196:
-----------------------------------
[~emartins] could you please look at this BOM issue?
CC [~swd847]
> JSP and JSTL missing from EE 7 BOM
> ----------------------------------
>
> Key: JBEE-196
> URL: https://issues.jboss.org/browse/JBEE-196
> Project: JBoss JavaEE Spec APIs
> Issue Type: Bug
> Affects Versions: JavaEE 7 Spec APIs 1.1.0.Final
> Reporter: Rich DiCroce
> Assignee: Eduardo Martins
>
> jboss-javaee-7.0 version 1.0.4 includes JSP and JSTL. Version 1.1.0 and later effectively do not, because they declare those dependencies to be provided scope for some reason. Servlet would also be affected, except JACC has a transitive dependency on it.
> This bug appears to have been introduced as part of resolving JBEE-170.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBEE-196) JSP and JSTL missing from EE 7 BOM
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/JBEE-196?page=com.atlassian.jira.plugin.s... ]
Scott Marlow reassigned JBEE-196:
---------------------------------
Assignee: Eduardo Martins (was: Scott Marlow)
> JSP and JSTL missing from EE 7 BOM
> ----------------------------------
>
> Key: JBEE-196
> URL: https://issues.jboss.org/browse/JBEE-196
> Project: JBoss JavaEE Spec APIs
> Issue Type: Bug
> Affects Versions: JavaEE 7 Spec APIs 1.1.0.Final
> Reporter: Rich DiCroce
> Assignee: Eduardo Martins
>
> jboss-javaee-7.0 version 1.0.4 includes JSP and JSTL. Version 1.1.0 and later effectively do not, because they declare those dependencies to be provided scope for some reason. Servlet would also be affected, except JACC has a transitive dependency on it.
> This bug appears to have been introduced as part of resolving JBEE-170.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (LOGMGR-199) Reinitialize the output stream when it fails on Windows
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/LOGMGR-199?page=com.atlassian.jira.plugin... ]
James Perkins edited comment on LOGMGR-199 at 7/24/18 11:15 AM:
----------------------------------------------------------------
A note for the implementation. When reporting the error the output stream should probably be closed. We should allow a number, likely allowed to be overridden, of retires before a complete failure and no more retries will be attempted.
was (Author: jamezp):
A note for the implementation. We should allow a number, likely allowed to be overridden, of retires before a complete failure and no more retries will be attempted.
> Reinitialize the output stream when it fails on Windows
> -------------------------------------------------------
>
> Key: LOGMGR-199
> URL: https://issues.jboss.org/browse/LOGMGR-199
> Project: JBoss Log Manager
> Issue Type: Bug
> Components: core
> Affects Versions: 2.0.8.Final, 2.1.0.Final
> Reporter: Teresa Miyar
>
> After the fix https://issues.jboss.org/browse/LOGMGR-154 we can still observe that the log file when using periodic file size rotation on Windows it stops logging, one solution discussed is to reinitialize the output stream when this happens.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months