@glassfishrobot Commented
Reported by moodysalem

@glassfishrobot Commented
kalgon said:
Can't you just create your own javax.persistence.spi.PersistenceUnitInfo and do something like this to begin with? (no package scanning)

for (PersistenceProvider provider : PersistenceProviderResolverHolder.getPersistenceProviderResolver().getPersistenceProviders()) {
	return provider.createContainerEntityManagerFactory(persistenceUnifInfo, properties);
}

@glassfishrobot Commented
ondrejm said:
The above piece of code is great stuff, it's a pity almost noone knows that something like this is possible.
Though, I'd welcome more declarative way that makes it possible to combine with @PersistenceUnit, which everybody knows how to use.

Something like having a CDI producer with methods marked with @PersistenceUnitDefinition qualifier:

public class PersisteneConfig {
  @Produces
  @PersistenceUnitDefinition(name = "puMain")
  public PersistenceUnitInfo puMainInfo() {
    return persistenceUnitInfo;
  }

  @Produces
  @PersistenceUnitDefinition(name = "puMain")
  public Map puMainProperties() {
    return properties;
  }
}

If CDI producer would be too late in the lifecycle, or dependency on CDI is not convenient, than some kind of listener executed soon enough in the lifecycle.

@glassfishrobot Commented
This issue was imported from java.net JIRA JPA_SPEC-114

• Issue Imported From: https://github.com/javaee/jpa-spec/issues/114
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @ldemichiel

I think this needs a bit more justification. Isn't the JPA SPI doing all this for example for the Spring world? Maybe this should just be closed to reduce clutter or marked as very low priority so the focus can be on higher impact work?

Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker

Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.

This was done by #465.