I don't think this ever happened... It certainly did not happen by design if it did happen.
Change By:	Steve Ebersole (01/Jun/13 11:32 AM)
Description:	I'm Currently {{JpaSchemaGenerator}} is not sure when this bug was introduced, maybe HHH-8113 was the wrong fix picking up stuff contributed by enabled {{org . I might have not seen this for a few weeks hibernate . The JPASchemaGenerator ignores @NotNull constraints integrator . The attached screenshots show the call stacks for the Column#setNullable() method during bootstrap with schema generation enabled spi . The first call stack shows that JPASchemaGenerator only uses AnnotationBinder and Ejb3Column to determine whether Integrator}} ( the column Integerators are activated after JpaSchemaGenerator is nullable run) . The second call stack is buildSessionFactory This includes contributions from Bean Validation ( ) running right after performGeneration() well , here the BeanValidationIntegrator Hibernate Validator anyway, when DDL enforcement is called enabled), Envers and even Hibernate Spatial .
Issue Type:	Bug Improvement
Summary:	Have JPA schema generator ignores Bean Validation constraints generation include work done by Integrators

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira