@Steve
yes, 100% agree with you that it is not wise to have multiple persistence.xml files in the way the current OSGi JPA spec defines it.
I just want to split up my domain model in multiple bundles. The current spec says to do this I must put into every bundle a persistence.xml.
There could be two solutions, the first one which just says which configuration in which persistence.xml wins or an alternative way in specifying entities. The dream would be a plugable domain model
@Steve
yes, 100% agree with you that it is not wise to have multiple persistence.xml files in the way the current OSGi JPA spec defines it.
I just want to split up my domain model in multiple bundles. The current spec says to do this I must put into every bundle a persistence.xml.
There could be two solutions, the first one which just says which configuration in which persistence.xml wins or an alternative way in specifying entities. The dream would be a plugable domain model