[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4417) Scanning jars and using eclipses classloader is not good to do in OpenMappingFileUtilEjb3
[
https://jira.jboss.org/jira/browse/JBIDE-4417?page=com.atlassian.jira.plu...
]
Vitali Yemialyanchyk commented on JBIDE-4417:
---------------------------------------------
I create Hibernate issue:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3948
I'll remember this issue and will pay attention for new Hibernate versions for
Ejb3Configuration updates.
for while I leave it unchanged...
I see, currently, we throw FileNotFoundException in the case of no matching resource
found,
do you think message box be better?
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