3:22 p.m.
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)
Components: core
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
Priority: Critical
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
10:29 a.m.
New subject: [JBoss JIRA] Commented: (JBCOMMON-6) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/JBCOMMON-6?page=comments#action_12344332 ]
Darren Hartford commented on JBCOMMON-6:
----------------------------------------
Adding support for the Eclipse 'bundleresource' URL would also be a huge benefit.
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)
Components: core
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
Priority: Critical
Original Estimate: 4 hours
Remaining Estimate: 4 hours
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
10:41 a.m.
New subject: [JBoss JIRA] Updated: (JBCOMMON-6) Archive Browser does not support jar:file: url protocol
[ 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
10:41 a.m.
New subject: [JBoss JIRA] Moved: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/EJBTHREE-719?page=all ]
Adrian Brock moved JBCOMMON-6 to EJBTHREE-719:
----------------------------------------------
Project: EJB 3.0 (was: JBoss Common)
Key: EJBTHREE-719 (was: JBCOMMON-6)
Component/s: (was: core)
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: EJBTHREE-719
URL: http://jira.jboss.com/jira/browse/EJBTHREE-719
Project: EJB 3.0
Issue Type: Bug
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
10:44 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/EJBTHREE-719?page=comments#action_12344336 ]
Adrian Brock commented on EJBTHREE-719:
---------------------------------------
Moved the EJB3 project since I don't see what this archive browsing offers over its
more feature complete precursor org.jboss.net.URLLister[Factory]?
This should in any case be replaced with the VFS.
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: EJBTHREE-719
URL: http://jira.jboss.com/jira/browse/EJBTHREE-719
Project: EJB 3.0
Issue Type: Bug
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
6:34 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/EJBTHREE-719?page=comments#action_12348114 ]
Mehdi Bahribayli commented on EJBTHREE-719:
-------------------------------------------
I am using Hibernate EntityManager+Spring+Axis2 and bundled them all in an aar archive.
Thus proposed workaround does not work for me. Any estimation on how long it will take to
fix it?
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: EJBTHREE-719
URL: http://jira.jboss.com/jira/browse/EJBTHREE-719
Project: EJB 3.0
Issue Type: Bug
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
10:37 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/EJBTHREE-719?page=comments#action_12349213 ]
Markus ?llinger commented on EJBTHREE-719:
------------------------------------------
We are using this in OSGi so it would be good if it could recognize other protocols as
well (e.g. bundle: for OSGi environments).
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: EJBTHREE-719
URL: http://jira.jboss.com/jira/browse/EJBTHREE-719
Project: EJB 3.0
Issue Type: Bug
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
4:07 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/EJBTHREE-719?page=comments#action_12351804 ]
Graeme Dougal commented on EJBTHREE-719:
----------------------------------------
Currently having exactly the same issue attempting to deploy an EJB 3 in Weblogic 10 using
Hibernate Entity Manager
Everything packaged up in an EAR file as per Mehdi Bahribayli above
This is quite an urgent issue for us with regards proving an EJB3 JPA solution in Weblogic
10 so would appreciate any kind of estimate on when this may be resolved
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: EJBTHREE-719
URL: http://jira.jboss.com/jira/browse/EJBTHREE-719
Project: EJB 3.0
Issue Type: Bug
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
5:11 a.m.
New subject: [JBoss JIRA] Assigned: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/EJBTHREE-719?page=all ]
Dimitris Andreadis reassigned EJBTHREE-719:
-------------------------------------------
Assignee: Carlo de Wolf (was: Dimitris Andreadis)
I don't know why this was assigned to me? Assigning to Carlo to decide how to handle
this case.
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: EJBTHREE-719
URL: http://jira.jboss.com/jira/browse/EJBTHREE-719
Project: EJB 3.0
Issue Type: Bug
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: Carlo de Wolf
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
8:03 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/EJBTHREE-719?page=comments#action_12352331 ]
Norbert Kenderesi commented on EJBTHREE-719:
--------------------------------------------
I submitted a patch for this issue with which the exception won't be thrown in case of
weblogic 9.2 (which uses URL beginning with zip and ending with '!/' characters),
and it also works with url types jar:file, jar and zip:file... I hope it's ok, because
this is my first patch here.
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: EJBTHREE-719
URL: http://jira.jboss.com/jira/browse/EJBTHREE-719
Project: EJB 3.0
Issue Type: Bug
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: Carlo de Wolf
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
7:31 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/EJBTHREE-719?page=all ]
Emmanuel Bernard updated EJBTHREE-719:
--------------------------------------
Fix Version/s: EJB 3.0 RC10 - FD
Affects Version/s: EJB 3.0 RC9 - FD
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: EJBTHREE-719
URL: http://jira.jboss.com/jira/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
Assigned To: Carlo de Wolf
Fix For: EJB 3.0 RC10 - FD
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
7:33 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/EJBTHREE-719?page=comments#action_12353026 ]
Emmanuel Bernard commented on EJBTHREE-719:
-------------------------------------------
Carlo, AFAIR, I tested the latest jboss-common-core.jar (has to be post nov 15th) with a
customer and it fixed the issue. You'd better embed that version with AS 4.2. Applying
the Norbert's patch might also be interesting
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: EJBTHREE-719
URL: http://jira.jboss.com/jira/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
Assigned To: Carlo de Wolf
Fix For: EJB 3.0 RC10 - FD
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
7:35 p.m.
New subject: [JBoss JIRA] Reopened: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/EJBTHREE-719?page=all ]
Emmanuel Bernard reopened EJBTHREE-719:
---------------------------------------
oups
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: EJBTHREE-719
URL: http://jira.jboss.com/jira/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
Assigned To: Carlo de Wolf
Fix For: EJB 3.0 RC10 - FD
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
7:35 p.m.
New subject: [JBoss JIRA] Closed: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/EJBTHREE-719?page=all ]
Emmanuel Bernard closed EJBTHREE-719.
-------------------------------------
Resolution: Done
note this is the version that will be used by HEM 3.2.2 (and probably 3.2.1, can't be
sure)
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: EJBTHREE-719
URL: http://jira.jboss.com/jira/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
Assigned To: Carlo de Wolf
Fix For: EJB 3.0 RC10 - FD
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
7:07 a.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/EJBTHREE-719?page=all ]
Carlo de Wolf updated EJBTHREE-719:
-----------------------------------
Fix Version/s: AS 4.2.0 CR2
(was: AS 4.2.0 CR1)
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: EJBTHREE-719
URL: http://jira.jboss.com/jira/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
Assigned To: Carlo de Wolf
Fix For: AS 4.2.0 CR2
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
8:01 a.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/EJBTHREE-719?page=all ]
Carlo de Wolf updated EJBTHREE-719:
-----------------------------------
Fix Version/s: AS 4.2.0 GA
(was: AS 4.2.0 CR2)
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: EJBTHREE-719
URL: http://jira.jboss.com/jira/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
Assigned To: Carlo de Wolf
Fix For: AS 4.2.0 GA
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
4:52 a.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/EJBTHREE-719?page=all ]
Carlo de Wolf updated EJBTHREE-719:
-----------------------------------
Fix Version/s: Branch_4_2
(was: AS 4.2.0 GA)
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: EJBTHREE-719
URL: http://jira.jboss.com/jira/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
Assigned To: Carlo de Wolf
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:12 a.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/EJBTHREE-719?page=all ]
Carlo de Wolf updated EJBTHREE-719:
-----------------------------------
Fix Version/s: Branch_4_2
(was: AS 4.2.1)
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: EJBTHREE-719
URL: http://jira.jboss.com/jira/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
Assigned To: Carlo de Wolf
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:16 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/EJBTHREE-719?page=comments#action_12392493 ]
Ethan Allen commented on EJBTHREE-719:
--------------------------------------
? - has this issue been fixed ? I have the same problem with WebLogic 10/WebLogic
Workshop 10.1. The comments suggest that it may be fixed ... ?
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: EJBTHREE-719
URL: http://jira.jboss.com/jira/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
Assigned To: Carlo de Wolf
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:59 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/EJBTHREE-719?page=comments#action_12392530 ]
Carlo de Wolf commented on EJBTHREE-719:
----------------------------------------
http://opensource.atlassian.com/projects/hibernate/browse/EJB-326
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: EJBTHREE-719
URL: http://jira.jboss.com/jira/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
Assigned To: Carlo de Wolf
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:59 a.m.
New subject: [JBoss JIRA] Assigned: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/EJBTHREE-719?page=all ]
Carlo de Wolf reassigned EJBTHREE-719:
--------------------------------------
Assignee: Emmanuel Bernard (was: Carlo de Wolf)
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: EJBTHREE-719
URL: http://jira.jboss.com/jira/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
Assigned To: 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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:19 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[ http://jira.jboss.com/jira/browse/EJBTHREE-719?page=comments#action_12392646 ]
Ethan Allen commented on EJBTHREE-719:
--------------------------------------
I appreciate the rsponse, Carlo, but ... that link takes me to a discussion of a possible
fix that would create other problems - seems to indicate that no fix has been made. Is
that what you were trying to say ?
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: EJBTHREE-719
URL: http://jira.jboss.com/jira/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
Assigned To: 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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:18 a.m.
New subject: [JBoss JIRA] Resolved: (EJBTHREE-719) Archive Browser does not support jar:file: url protocol
[
https://jira.jboss.org/browse/EJBTHREE-719?page=com.atlassian.jira.plugin...
]
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
5219
days inactive
6681
days old
22 comments
11 participants
participants (11)
-
Adrian Brock (JIRA) -
Carlo de Wolf (JIRA) -
Chris Mercer (JIRA)
-
Darren Hartford (JIRA)
-
Dimitris Andreadis (JIRA)
-
Emmanuel Bernard (JIRA)
-
Ethan Allen (JIRA)
-
Graeme Dougal (JIRA)
-
Markus ?llinger (JIRA)
-
Mehdi Bahribayli (JIRA)
-
Norbert Kenderesi (JIRA)