[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-1121) Work on a proper classloader strategy

[Scott Marlow (JIRA)]

    [ https://hibernate.onjira.com/browse/HSEARCH-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46555#comment-46555 ] 

Scott Marlow commented on HSEARCH-1121:
---------------------------------------

[this link might be helpful|https://community.jboss.org/wiki/ModuleCompatibleClassloadingGuide], it mentions how the TCCL might not be right for non-EE threads.



> Work on a proper classloader strategy
> -------------------------------------
>
>                 Key: HSEARCH-1121
>                 URL: https://hibernate.onjira.com/browse/HSEARCH-1121
>             Project: Hibernate Search
>          Issue Type: Improvement
>            Reporter: Emmanuel Bernard
>
> Today we mostly expect the TCCL to be correct plus a minor ad-hoc fixes to make CapeDwarf and Modeshape work but it would be better to offer a clean way to define the classloaders.
> introduce various classes of classloaders:
> - Hibernate Search module classloader
> - Application classloader
> Or maybe it should rather be:
> - entity classloader
> - analyzer classloader
> - interceptor classloader
> - ...
> Each classloader could then be provided by implementing a ClassloaderService class? It's unclear to me how things are bootstrapped in a modular environment and how such info is propagated or what best practices are.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira