You would at least need to change their names to be unique within scope of its packaging (in terms of Web Archive, EJB JAR, etc.): JPA allows to define multiple persistence units in a single persistence.xml file so Since I didn't have much in common with Tomcat I will just provide a link to a similar question:.#database.url=jdbc:mysql://localhost:3306/testĭatabase.url=jdbc:log4jdbc:mysql://localhost:3306/testĭatabase.driver=net.sf.log4jdbc.DriverSpy The following is all you need to get up and running with a non-JNDI datasource.Įxample Spring Configuration (non-JNDI): Ĭlasspath:profiles/Ĭlasspath:profiles/Ĭlasspath:profiles/ How do you set the active profile without recompiling? No, you only need a minimal persistence.xml when using Spring or perhaps not at all.ģ. How do you configure persistence.xml for multiple environments? Should the jdbc connection props even be in persistence.xml Or, you can use a non-JNDI datasource i.e configured in Spring and perhaps using profiles.Ģ. If you are using JNDI approach then you may have multiple datasources defined and can specify that one used in you application via profile properties however the actual definition will have nothing to do with Spring. You can use the Tomcat datasourse configuration however the datasource definition will have nothing to do with Spring or Spring profiles. Can you still use the Tomcat datasource configuration? If so how does it know which profile to use? How do you set the active profile without recompiling?ġ. I've seen different examples so I'm a little confused how to implement.Ĭan you still use the Tomcat datasource configuration? If so how does it know which profile to use? My persistence.xml currently looks like this. I really only need to handle different database settings at this point but later I may need additional bean configuration depending on environment.

I've seen examples such as Unable to use JNDI DataSource provided by Tomcat in Spring?.

I want to implement environment profiles in my Spring JSON API application to handle multiple environments, development, testing, production.

Jpe Java Prolog Environment