[
http://opensource.atlassian.com/projects/hibernate/browse/EJB-193?page=co...
]
Max Rydahl Andersen commented on EJB-193:
-----------------------------------------
was this on irc or the forum we discussed this ? been a while so can't remember the
details ;)
anyhow what i do remember were that as Benjamin states that some autoscanning of the
classloaders (non-portably) were still going on even though you disabled autoscanning.
and that resulted in the scanner to fail (because of at that time errors in it with
respect to whitespace or specific url) ...there were some other issue but that part
i've forgotten.
Make it possible to disable autodiscovery
-----------------------------------------
Key: EJB-193
URL:
http://opensource.atlassian.com/projects/hibernate/browse/EJB-193
Project: Hibernate Entity Manager
Type: New Feature
Versions: 3.2.0.cr1
Reporter: Benjamin Hawkes-Lewis
Currently even if hibernate.archive.autodetection is set to an empty string
(""), Hibernate still tries to open a zipped EJB packaging. Apparently, it's
looking for orm.xml. Given that auto discovery support for Java SE containers is not
required by the spec, and therefore may never be complete, it would be good to be able to
turn it off.
--
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