[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4417) Scanning jars and using eclipses classloader is not good to do in OpenMappingFileUtilEjb3

[Vitali Yemialyanchyk (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12470587#action_12470587 ] 

Vitali Yemialyanchyk commented on JBIDE-4417:
---------------------------------------------

OpenMappingUtilsEjb3 was based on Ejb3Configuration private functions with small modifications.
The ideal situation if we can use Ejb3Configuration without OpenMappingUtilsEjb3.
For me, the most preferable solution is to ask hibernate team for Ejb3Configuration changes,
cause Ejb3Configuration can provide "list of paths to ejb3 resource configuration files" easily.
And it is seems natural if Ejb3Configuration provide this info, this is my IMHO.
This is easy to impement feature and I can create patch for Ejb3Configuration.
What do you think about patch to Ejb3Configuration?

> Scanning jars and using eclipses classloader is not good to do in OpenMappingFileUtilEjb3
> -----------------------------------------------------------------------------------------
>
>                 Key: JBIDE-4417
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4417
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Hibernate
>    Affects Versions: 3.1.0.M1
>            Reporter: Max Rydahl Andersen
>            Assignee: Vitali Yemialyanchyk
>             Fix For: 3.1.0.M2
>
>
> Why are we using the current thread classloader (eclipses classloader) and jarvisitor to load resources when Eclipse already got all this info ?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira