Hello, I have just switched from Aries JPA 1.0.4 to 2.3.0, used in combination with EclipseLink 2.6.1. With a H2 database, it works smoothly, and much better than with 1.0.4.
However, I also have a PostgreSQL database where I have organized tables in several schemas. Typically I use a common datasource for the different persistence bundles, and each persistence bundle has a mapping file orm.xml to cope with the according schema: <?xml version="1.0" encoding="UTF-8"?> <entity-mappings xmlns="http://java.sun.com/xml/ns/persistence/orm"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://java.sun.com/xml/ns/persistence/orm orm_2_0.xsd" version="2.0"> <persistence-unit-metadata> <persistence-unit-defaults> <schema>schema_one</schema> </persistence-unit-defaults> </persistence-unit-metadata> </entity-mappings> In the persistence.xml, the mapping file is referenced with <mapping-file>META-INF/orm.xml</mapping-file> That mapping file seems not to work any longer. I receive some "relation xyz does not exist" exception, and when switching on fine logging for EclipseLink, it becomes obvious that the schema name is not used for accessing the tables (just /SELECT .... FROM MyTable/ instead of /SELECT .... FROM schema_one.MyTable/) . Of course I could use something like url=jdbc:postgresql://localhost:5432/mydb?currentSchema=schema_one when defining the data source - but this way I would need one data source per persistence bundle. Is there something special I need to do to re-activate the orm.xml file? Regards, Jochen -- View this message in context: http://karaf.922171.n3.nabble.com/Aries-JPA-2-3-0-mapping-file-not-used-tp4047501.html Sent from the Karaf - User mailing list archive at Nabble.com.
