Thanks, Christian! Would be great to have a solution, but just in case I'll prepare for separate persistence bundles anyways.
Best Regards, Jochen 2015-07-30 21:22 GMT+02:00 Christian Schneider <[email protected]>: > The functionality is not standard in custom namespaces. So it is no bug. > Unfortunately I do not know how to implement the replacement. I already > asked on the dev list if anyone knows how to do it. > If it is rather simple I can add it then. > > Christian > > > Am 30.07.2015 um 10:59 schrieb Jochen Walz: > >> Hello, >> >> when trying to define the persistence unit as property in blueprint, the >> property is not resolved when used in the jpa namespace: >> >> <cm:property-placeholder persistent-id="persistence"> >> <cm:default-properties> >> <cm:property name="persistenceunitname" >> value="default_persistenceunit" /> >> </cm:default-properties> >> </cm:property-placeholder> >> >> <bean id="dbManager" >> class="DBManagerImpl" >> scope="singleton" init-method="init"> >> <jpa:context property="entityManager" >> unitname="${persistenceunitname}" /> >> <tx:transaction method="*" value="Required"/> >> </bean> >> >> ... >> >> I saw some question for the same topic, but the solution was to use >> datasources. In my case, I'd like to use different persistence units to be >> able to access different databases (and some of the persistence unit >> settings are DB specific). >> >> I'm using version 1.0.2 of the JPA container and 1.0.4 for the JPA >> Container Blueprint integration. >> >> Is this a bug in Aries JPA, or would that be a new feature to make the >> property resolution work? >> >> Best Regards, >> >> Jochen >> > >
