[jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-6) Archive Browser does not support jar:file: url protocol

[Adrian Brock (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBCOMMON-6?page=all ]

Adrian Brock updated JBCOMMON-6:
--------------------------------

     Original Estimate:     (was: 4 hours)
    Remaining Estimate:     (was: 4 hours)
              Priority: Major  (was: Critical)

"FOR COMMITTERS USE ONLY" means exactly that.

> Archive Browser does not support jar:file: url protocol
> -------------------------------------------------------
>
>                 Key: JBCOMMON-6
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-6
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         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
>         Assigned To: Dimitris Andreadis
>
> 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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira