- 
                Notifications
    
You must be signed in to change notification settings  - Fork 3k
 
Migration Guide 2.17
Adding a CDI interceptor annotation such as @Transactional to a private method was never supported, and used to result in a warning in logs because the annotation is ignored.
When such an annotation is ignored, Quarkus will now trigger a build failure instead:
javax.enterprise.inject.spi.DeploymentException: @Transactional will have no effect on method com.acme.MyBean.myMethod() because the method is private. [...]
Ideally you should remove such annotations since they are ignored, but if that's not possible, set the configuration property quarkus.arc.fail-on-intercepted-private-method to false to revert to the previous behavior (warnings in logs).
- Class 
org.jboss.resteasy.reactive.server.core.multipart.MultipartFormDataOutputhas been moved toorg.jboss.resteasy.reactive.server.multipart.MultipartFormDataOutput - Class 
org.jboss.resteasy.reactive.server.core.multipart.PartItemhas been moved toorg.jboss.resteasy.reactive.server.multipart.PartItem 
Using persistence.xml files and quarkus.hibernate-orm.* configuration properties in the same application will fail
When configuring the Hibernate ORM extension through both a persistence.xml file and quarkus.hibernate-orm.* properties in application.properties, Quarkus used to ignore quarkus.hibernate-orm.* properties, even though documentation stated the application would fail to start.
Quarkus will now fail as expected when it can detect such situations.
You can still chose between persistence.xml and quarkus.hibernate-orm.* properties:
- To ignore 
persistence.xmlfiles, set the configuration propertyquarkus.hibernate-orm.persistence-xml.ignoretotrue. - To use 
persistence.xml files, remove allquarkus.hibernate-orm.*properties fromapplication.properties. 
Use quarkus.hibernate-orm.quote-identifiers.strategy = all instead.