On 5/18/22 9:15 AM, Scott Marlow wrote:
WildFly is currently failing to deploy applications that have
"hibernate.id.new_generator_mappings" (USE_NEW_ID_GENERATOR_MAPPINGS)
set to false [1], since that option is removed from Hibernate ORM 6.
Words matter :-) I meant to say that WildFly is checking at application
deployment time if the application persistence.xml has the
"hibernate.id.new_generator_mappings" property set to false and if so,
throwing the [2] failure.
> The application deployment failure message [2] is basically:
>
> "
> hibernate.id.new_generator_mappings set to false is not supported,
> remove the setting or set to true. Refer to Hibernate ORM migration
> documentation for how to update the next id state in the application
> database.
> "
>
> Any suggestions for updates to the ^ deployment failure message?
> Should the deployment failure message link to the `idgeneratortype`
> section [3] of the ORM 6 migration doc?
>
> Scott
>
> [1]
>
https://github.com/wildfly/wildfly/blob/main/jpa/hibernate6/src/main/java...
> [2]
>
https://github.com/wildfly/wildfly/blob/6096ea6059fa7e21337fafc4e6061d730...
> [3]
>
https://github.com/hibernate/hibernate-orm/blob/6.0/migration-guide.adoc#...
>