[hibernate-issues] [JIRA] (HSEARCH-3853) Forward failures to resolve beans from Spring/CDI

Yoann Rodière (JIRA) jira at hibernate.atlassian.net
Wed Mar 4 02:40:06 EST 2020


Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A58fa1ced-171a-4c00-97e8-5d70d442cc4b ) *created* an issue

Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiMmFkZmMwYmUzMmQ1NDQzNGI3MzkxOWIwNDllNzdlMzciLCJwIjoiaiJ9 ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-3853?atlOrigin=eyJpIjoiMmFkZmMwYmUzMmQ1NDQzNGI3MzkxOWIwNDllNzdlMzciLCJwIjoiaiJ9 ) HSEARCH-3853 ( https://hibernate.atlassian.net/browse/HSEARCH-3853?atlOrigin=eyJpIjoiMmFkZmMwYmUzMmQ1NDQzNGI3MzkxOWIwNDllNzdlMzciLCJwIjoiaiJ9 ) Forward failures to resolve beans from Spring/CDI ( https://hibernate.atlassian.net/browse/HSEARCH-3853?atlOrigin=eyJpIjoiMmFkZmMwYmUzMmQ1NDQzNGI3MzkxOWIwNDllNzdlMzciLCJwIjoiaiJ9 )

Issue Type: Improvement Assignee: Unassigned Components: engine Created: 03/Mar/2020 23:40 PM Fix Versions: 6.0.0.Beta-backlog-low-priority Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A58fa1ced-171a-4c00-97e8-5d70d442cc4b )

See https://discourse.hibernate.org/t/indexation-post-treatment/3753/19

One problem that prevents us from forwarding such failures is that we fall back to using reflection when we can't find a bean using Spring/CDI, and Hibernate ORM (who manages this fallback) does not preserve both stack traces, just the one from the fallback.

One solution would be to change Hibernate ORM so that it preserves both stack traces and gives a clearer error message.

Another solution would be to change the format of bean references so that the user tells us precisely whether they want a Spring/CDI bean or an instantiation through reflection; that way, we would not have to fall back anymore. For exemple require a "bean:"/"classpath:" prefix in string references. The problem would still be there for references by type ( Class<?> ), though.

( https://hibernate.atlassian.net/browse/HSEARCH-3853#add-comment?atlOrigin=eyJpIjoiMmFkZmMwYmUzMmQ1NDQzNGI3MzkxOWIwNDllNzdlMzciLCJwIjoiaiJ9 ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3853#add-comment?atlOrigin=eyJpIjoiMmFkZmMwYmUzMmQ1NDQzNGI3MzkxOWIwNDllNzdlMzciLCJwIjoiaiJ9 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100121- sha1:d2b7993 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hibernate-issues/attachments/20200304/4ca5730f/attachment.html 


More information about the hibernate-issues mailing list