[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol

[Carlo de Wolf (JIRA)]

     [ https://jira.jboss.org/browse/EJBTHREE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carlo de Wolf resolved EJBTHREE-719.
------------------------------------

    Resolution: Out of Date


This issue is reported against a version which is no longer maintained,
which means that it will not receive a fix. As a result we are closing
this bug.

If you can reproduce this bug against a currently maintained version of 
JBoss EJB 3 please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

> Archive Browser does not support jar:file: url protocol
> -------------------------------------------------------
>
>                 Key: EJBTHREE-719
>                 URL: https://jira.jboss.org/browse/EJBTHREE-719
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: jdk 1.5.8
> jboss 4.0.4ga
> hibernate 3.2cr2
> hibernate entity manager 3.2.0.CR1
> Using ejb3/entity manager annotations
>            Reporter: Chris Mercer
>            Assignee: Emmanuel Bernard
>             Fix For: Branch_4_2
>
>
> We have a seperate jar file that contains all of our model/entity objects.  This jar gets put in the WEB-INF/lib directory, since we are only using wars and not ears.  Using the hibernate auto-discovery feature causes an exception to occur. In this configuration.
> Caused by: java.lang.RuntimeException: NOT IMPLEMENTED
> 	at org.jboss.util.file.ArchiveBrowser.getBrowser(ArchiveBrowser.java:42)
> 	at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:541)
> 	... 148 more
> org.jboss.util.file.ArchiveBrowser.getBrowser(URL url, Filter filter) only supports URLS that have a protocol of "file".  However, jars have a protocol of "jar:file:" and therefore it will throw a RuntimeException saying "NOT IMPLEMENTED" (at least according to my debugger).  There is already a JarArchiveBrowser class, the ArchiveBrowser just needs to recognize the protocol and handle it.  
> This also affects Hibernate entity manager, since it gets included in the jboss-archive-browsing.jar in order to handle the auto-discovery of mapped entities feature.  
> I've marked this as critical, since it effects entity manager features (though its only advanced hibernate only functionality)

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