[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-227?page=co... ] Philippe Lefebvre commented on EJB-227: --------------------------------------- My apologies for this early conclusion, as I can see at line 50 of PersistenceXmlLoader.java, the parser is indeed validating. After further investigation, the problem is with the exclude-unlisted-classes element: in the schema, it's declared as a boolean type but in the code (line 152), whenever the tag is present, it is assumed to be true. This is in line with the EJB3 Specification but allows for errors where there is a "false" in the tag. I guess the value inside should be checked, as a safety net. Something like: metadata.setExcludeUnlistedClasses(!"false".equalsIgnoreCase(element.getTextContent())); -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-227?page=all ] Emmanuel Bernard resolved EJB-227: ---------------------------------- Fix Version: (was: 3.2.1) Resolution: Won't Fix Unfortunately, metadata.setExcludeUnlistedClasses(!"false".equalsIgnoreCase(element.getTextContent())); is not possible, there is no way to differenciate a default value from an explicit one. If you know how to, please provide a patch :-) -- 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