Getting org.xml.sax.SAXParseException in Hibernate 5.2

@dreab8 : It looks good after changing the order, Can you please let me know as to if there are any other changes that have happened related to this? It worked in Hibernate 4.3 with the earlier schema as well.
Would like to know if there have been any other changes in the schema order, one of them i am aware of is cache and tuplizer order change, which has been discussed at Getting NPE while using <cache usage="read-only"/> in HBMXML in Hibernate 5.2.11