October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4732) Upgrade wildfly-server-provisioning-maven-plugin from 1.1.12 to 1.1.13

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4732: ---------------------------------------- Summary: Upgrade wildfly-server-provisioning-maven-plugin from 1.1.12 to 1.1.13 Key: WFCORE-4732 URL: https://issues.jboss.org/browse/WFCORE-4732 Project: WildFly Core Issue Type: Component Upgrade Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry https://github.com/wildfly/wildfly-build-tools/compare/1.2.12.Final...1.2... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4732) Upgrade wildfly-server-provisioning-maven-plugin from 1.2.12 to 1.2.13

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4732?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4732: ------------------------------------- Summary: Upgrade wildfly-server-provisioning-maven-plugin from 1.2.12 to 1.2.13 (was: Upgrade wildfly-server-provisioning-maven-plugin from 1.1.12 to 1.1.13) > Upgrade wildfly-server-provisioning-maven-plugin from 1.2.12 to 1.2.13 > ---------------------------------------------------------------------- > > Key: WFCORE-4732 > URL: https://issues.jboss.org/browse/WFCORE-4732 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > https://github.com/wildfly/wildfly-build-tools/compare/1.2.12.Final...1.2... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AG-131) Change the data structure used to track JDBC resources

by Luis Barreiro (Jira)

[ https://issues.jboss.org/browse/AG-131?page=com.atlassian.jira.plugin.sys... ] Luis Barreiro closed AG-131. ---------------------------- Resolution: Done > Change the data structure used to track JDBC resources > ------------------------------------------------------ > > Key: AG-131 > URL: https://issues.jboss.org/browse/AG-131 > Project: Agroal > Issue Type: Enhancement > Components: pool > Affects Versions: 1.6 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Major > Fix For: 1.7 > > > Currently, the JDBC resources are tracked in a StampedCopyOnWrireArrayList that is a data structure optimized for when reads are much more often that writes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12714) [18.0.x] Upgrade Hibernate Validator to 6.0.18

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12714: --------------------------------------- Summary: [18.0.x] Upgrade Hibernate Validator to 6.0.18 Key: WFLY-12714 URL: https://issues.jboss.org/browse/WFLY-12714 Project: WildFly Issue Type: Component Upgrade Components: Bean Validation Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 19.0.0.Beta1 Tracker for Hibernate Validator upgrade to pick up incorporated fixes. https://github.com/hibernate/hibernate-validator/compare/6.0.17.Final...6... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12714) [18.0.x] Upgrade Hibernate Validator to 6.0.18

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12714?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12714: ------------------------------------ Fix Version/s: 18.0.1.Final (was: 19.0.0.Beta1) > [18.0.x] Upgrade Hibernate Validator to 6.0.18 > ---------------------------------------------- > > Key: WFLY-12714 > URL: https://issues.jboss.org/browse/WFLY-12714 > Project: WildFly > Issue Type: Component Upgrade > Components: Bean Validation > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 18.0.1.Final > > > Tracker for Hibernate Validator upgrade to pick up incorporated fixes. > https://github.com/hibernate/hibernate-validator/compare/6.0.17.Final...6... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12667) Upgrade Hibernate Validator to 6.0.18

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12667?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12667: ------------------------------------ Description: Tracker for Hibernate Validator upgrade to pick up incorporated fixes. https://github.com/hibernate/hibernate-validator/compare/6.0.17.Final...6... was:Tracker for Hibernate Validator upgrade to pick up incorporated fixes. > Upgrade Hibernate Validator to 6.0.18 > ------------------------------------- > > Key: WFLY-12667 > URL: https://issues.jboss.org/browse/WFLY-12667 > Project: WildFly > Issue Type: Component Upgrade > Components: Bean Validation > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 19.0.0.Beta1 > > > Tracker for Hibernate Validator upgrade to pick up incorporated fixes. > https://github.com/hibernate/hibernate-validator/compare/6.0.17.Final...6... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4731) Include the wildfly-openssl s390 binding

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4731: ---------------------------------------- Summary: Include the wildfly-openssl s390 binding Key: WFCORE-4731 URL: https://issues.jboss.org/browse/WFCORE-4731 Project: WildFly Core Issue Type: Enhancement Components: Build System, Security Reporter: Brian Stansberry Assignee: Darran Lofthouse The wildfly-openssl project include s390 bindings; we should include them. https://github.com/wildfly/wildfly-openssl/tree/1.0.8.Final/linux-s390x The code was there for the 1.0.8 release but it doesn't look like that variant was built and pushed to nexus: https://repository.jboss.org/org/wildfly/openssl/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4730) Include the wildfly-openssl s390 binding

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4730: ---------------------------------------- Summary: Include the wildfly-openssl s390 binding Key: WFCORE-4730 URL: https://issues.jboss.org/browse/WFCORE-4730 Project: WildFly Core Issue Type: Enhancement Components: Build System, Security Reporter: Brian Stansberry Assignee: Darran Lofthouse The wildfly-openssl project include s390 bindings; we should include them. https://github.com/wildfly/wildfly-openssl/tree/1.0.8.Final/linux-s390x The code was there for the 1.0.8 release but it doesn't look like that variant was built and pushed to nexus: https://repository.jboss.org/org/wildfly/openssl/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (HIBERNATE-171) property ordering in DDL when using schema generation

by nimo stephan (Jira)

nimo stephan created HIBERNATE-171: -------------------------------------- Summary: property ordering in DDL when using schema generation Key: HIBERNATE-171 URL: https://issues.jboss.org/browse/HIBERNATE-171 Project: Hibernate Integration Issue Type: Enhancement Reporter: nimo stephan Assignee: Steve Ebersole Would be nice to have a new jpa/hibernate annotation to define the ordering within an ddl schema generation on an entity class: {code:java} @Entity @Table(name = "users") // jpa schema generation will use the following property order when creating DDL @TablePropertyOrder(value = { "idUser", "username", "email"}) public class User { ..} {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (HIBERNATE-170) Support "TIMESTAMP WITH TIME ZONE" for OffsetDateTime and ZonedDateTime

by nimo stephan (Jira)

[ https://issues.jboss.org/browse/HIBERNATE-170?page=com.atlassian.jira.plu... ] nimo stephan edited comment on HIBERNATE-170 at 10/27/19 4:01 AM: ------------------------------------------------------------------ I guess, a simpler solution would be to use the correct columnDefinition for OffsetDateTime and ZonedDateTime by default. Actually, user must manually put columnDefinition = "TIMESTAMP WITH TIME ZONE" to add the offset of OffsetDateTime. But if db supports it, hibernate can add the correct columnDefinition by default. Actually it uses for all types of java dates the columnDefinition of "TIMESTAMP" which is not correct for OffsetDateTime and ZonedDateTime. {code:java} // user must add columnDefinition manually, // would be better if Hibernate uses this columnDefinition by default if database supports it @Column(name = "timestamp", columnDefinition = "TIMESTAMP WITH TIME ZONE") private OffsetDateTime timestamp; {code} was (Author: nimo22): I guess, a simpler solution would be to use the correct columnDefinition for OffsetDateTime and ZonedDateTime by default. Actually, user must manually put columnDefinition = "TIMESTAMP WITH TIME ZONE" to add the offset of OffsetDateTime. But if db supports it, hibernate can add the correct columnDefinition by default. Actually it uses for all types of java dates the columnDefinition of "TIMESTAMP" which is not correct for OffsetDateTime and ZonedDateTime. {code:java} @Column(name = "timestamp", columnDefinition = "TIMESTAMP WITH TIME ZONE") private OffsetDateTime timestamp; {code} > Support "TIMESTAMP WITH TIME ZONE" for OffsetDateTime and ZonedDateTime > ----------------------------------------------------------------------- > > Key: HIBERNATE-170 > URL: https://issues.jboss.org/browse/HIBERNATE-170 > Project: Hibernate Integration > Issue Type: Enhancement > Reporter: nimo stephan > Assignee: Steve Ebersole > Priority: Major > > Something like this is supported in JPA 2.2: > {code:java} > @Column(name = "timestamp") > private OffsetDateTime timestamp; > {code} > However, the offset is NOT persisted in the database even if the database could support it. For example, when using H2 database, then Hibernate could map this "OffsetDateTime" to the sql datatype "TIMESTAMP WITH TIME ZONE" (because H2 supports it) instead of the datatype "TIMESTAMP". > Actually, user assumes that when using "OffsetDateTime" with JPA Annotation, JPA maps the offset as well. But this is not the case. Hibernate could also integrate a fallback for databases which does NOT support "TIMESTAMP WITH TIME ZONE". On schema generation, it could create and store something like "OffsetDateTime" or "ZonedDateTime" into two columns to avoid this manual mapping: > {code:java} > @Column(name = "created_on") > private Instant timestamp; > @Column(name = "display_offset") > private int offset; > {code} > Hibernate can make use of its own "HibernateCompositeType" to store one property (OffsetDateTime) into two sql columns (timestamp and offset). > With the solution above (by using either "TIMESTAMP WITH TIME ZONE" or the fallback), Hibernate/JPA could map the "OffsetDateTime" and "ZonedDateTime" correctly and completely with an offset or timezone. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

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 October 2019