Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-1705

JPA persistence units make use of SerializableValidatorFactory instead of using the JNDI bound default ValidatorFactory

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 8.0.0.Beta1
    • 8.0.0.Alpha2
    • EE, JPA / Hibernate
    • None

    Description

      I think there is no need for SerializableValidatorFactory. LazyValidatorFactory should be used at all times to also ensure that CDI injection works.

      Attachments

        Issue Links

          is blocked by

          Feature Request - Feature requests from customers and/or users WFLY-2032 component upgrade to jipijapa 1.0.0.Beta1

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Task - Represents a small unit of work that is not end-user facing. WFLY-409 JPA should allow for a bean validator factory per persistence unit or per application deployment

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Reopened

          Activity

            People

              fjuma1@redhat.com Farah Juma
              hardy.ferentschik_jira Hardy Ferentschik (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: