Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Initializing JPATraversableResolver fails with IllegalAccessException

Description

If JPA is on the classpath, HV uses a default TraversableResolver to handle non-initialized JPA proxies properly.

However creation of this JPATraversableResolver fails with

java.lang.IllegalAccessException: Class org.hibernate.validator.internal.util.privilegedactions.NewInstance can not access a member of class org.hibernate.validator.internal.engine.resolver.JPATraversableResolver with modifiers ""

which is logged only on debug-level and the implementation continues with the TraverseAllTraversableResolver.

Please find simple test case here https://github.com/abenneke/sandbox/tree/master/hibernate-validator-traversable

Environment

None

Activity

Show:

Guillaume SmetMay 15, 2018 at 11:16 AM

Note: this is a regression introduced in 6.0.3.Final.

Andreas BennekeApril 30, 2018 at 4:31 PM

Perfect, thank you!

Guillaume SmetApril 30, 2018 at 4:30 PM

Probably sometime next week.

I released a new version of the Bean Validation TCK today and I need to integrate a few PRs.

Andreas BennekeApril 30, 2018 at 1:36 PM

Yes, it does.

Thanks for the quick fix!

Are there already any schedules for 6.0.10?

Guillaume SmetApril 30, 2018 at 12:58 PM

can you check that my PR fixes your issue?

Thanks!

Fixed

Details

Assignee

Reporter

Bug Testcase Reminder (view)

Bug reports should generally be accompanied by a test case!

Bug Testcase Reminder (edit)

Bug reports should generally be accompanied by a test case!

Participants

Andreas Benneke
Guillaume Smet

Pull Request

https://github.com/hibernate/hibernate-validator/pull/951

Components

Fix versions

Affects versions

Priority

Created April 30, 2018 at 11:22 AM
Updated May 15, 2018 at 11:16 AM
Resolved May 3, 2018 at 1:08 PM