[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=12470615#action_12470615 ] 

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

if we decide hibernate entity manager is a right place for this functionality, we just get rid of OpenMappingUtilsEjb3;
in other case OpenMappingUtilsEjb3 should be re-written, certainly.
Consider OpenMappingUtilsEjb3 as a sketch-prove-of-concept, first easiest way was "cut-and-past".
The result could be small enough and be a good alternative to the patch. I'll try to rewrite it.

> 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