[
http://opensource.atlassian.com/projects/hibernate/browse/EJB-264?page=co...
]
Chris Lenz commented on EJB-264:
--------------------------------
I also found now another solution and report here:
http://lists.jboss.org/pipermail/hibernate-issues/2006-December/002794.html
but I think the real error must be in the method:
JarVisitor:
public static final JarVisitor getVisitor(URL jarUrl, Filter[] filters) throws
IllegalArgumentException {
becaus the protocol bundleresource is unknown
Ejb3Configuration always uses JarVisitor
----------------------------------------
Key: EJB-264
URL:
http://opensource.atlassian.com/projects/hibernate/browse/EJB-264
Project: Hibernate Entity Manager
Type: Bug
Versions: 3.2.2
Environment: Eclipse RCP
Reporter: Chris Lenz
I reported the problem also under:
http://forum.hibernate.org/viewtopic.php?p=2339386#2339386
Ejb3Configuration allways uses JarVisitor, even if it is a File. It's very hard to
describe my error, but the method doProcess for the InputStreamZippedJarVisitor creates
for me allways a null pointer exception if I export my product out of eclipse. Inside
Eclipse I get an error in the doProcess method, the exception is catched and the programm
runs thrugh.
I used the newest version from svn
Chris
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira