0003760: multipe persistence units in persistence.xml

(0004313)
georgbuschbeck
11-25-09 01:35

Just Checked, Problem persists in 4.0.2

(0004427)
ferg
02-12-10 16:32

I'm working through the JavaEE specs on this one for 4.0.4.

I'm not sure it's possible to have a non-activated persistence-unit because of bytecode enchancement (basically, Resin needs to activate the provider before any class could possibly be loaded).

However, it may be possible to catch the exception and only throw it when the application requests the EntityManager or EntityManagerFactory.

(0004428)
georgbuschbeck
02-15-10 02:34

well main problem is, we are using memcached for 2nd level caching this way:

<property name="hibernate.memcached.servers" value="memcached.service:11211 memcached1.service:11211" />
<property name="hibernate.cache.provider_class" value="com.googlecode.hibernate.memcached.MemcachedCacheProvider" />

this caching has the problem, that it will block, till it can establish a connection to theses memcached servers ....

(0004429)
ferg
02-15-10 15:29

env/0e13

Resin 4.0.4 will have a com.caucho.env.jpa.DisabledPersistenceProvider that you can use as the <provider> tag in the persistence.xml. You can selectively enable the persistence units with a <jpa-persistence-unit name="foo"> in the resin-web.xml (you'll need to add the actual <provider>.)

Looking through the JPA 2.0 specification, I can't see any way to avoid calling a PersistenceProvider for each persistence-unit, because those need to be configured before the classloaders are live (because of bytecode enhancemtn.) But it is possible to create a dummy PersistenceProvider that does nothing on startup.

Issue History
Date Modified	Username	Field	Change
11-13-09 01:52	georgbuschbeck	New Issue
11-23-09 02:46	georgbuschbeck	Issue Monitored: georgbuschbeck
11-25-09 01:35	georgbuschbeck	Note Added: 0004313
02-12-10 16:32	ferg	Note Added: 0004427
02-15-10 02:34	georgbuschbeck	Note Added: 0004428
02-15-10 15:29	ferg	Note Added: 0004429
02-15-10 15:30	ferg	Assigned To	=> ferg
02-15-10 15:30	ferg	Status	new => closed
02-15-10 15:30	ferg	Resolution	open => fixed
02-15-10 15:30	ferg	Fixed in Version	=> 4.0.4

Notes
(0004313) georgbuschbeck 11-25-09 01:35	Just Checked, Problem persists in 4.0.2

(0004427) ferg 02-12-10 16:32	I'm working through the JavaEE specs on this one for 4.0.4. I'm not sure it's possible to have a non-activated persistence-unit because of bytecode enchancement (basically, Resin needs to activate the provider before any class could possibly be loaded). However, it may be possible to catch the exception and only throw it when the application requests the EntityManager or EntityManagerFactory.

(0004428) georgbuschbeck 02-15-10 02:34	well main problem is, we are using memcached for 2nd level caching this way: <property name="hibernate.memcached.servers" value="memcached.service:11211 memcached1.service:11211" /> <property name="hibernate.cache.provider_class" value="com.googlecode.hibernate.memcached.MemcachedCacheProvider" /> this caching has the problem, that it will block, till it can establish a connection to theses memcached servers ....

(0004429) ferg 02-15-10 15:29	env/0e13 Resin 4.0.4 will have a com.caucho.env.jpa.DisabledPersistenceProvider that you can use as the <provider> tag in the persistence.xml. You can selectively enable the persistence units with a <jpa-persistence-unit name="foo"> in the resin-web.xml (you'll need to add the actual <provider>.) Looking through the JPA 2.0 specification, I can't see any way to avoid calling a PersistenceProvider for each persistence-unit, because those need to be configured before the classloaders are live (because of bytecode enhancemtn.) But it is possible to create a dummy PersistenceProvider that does nothing on startup.

Relationships