transaction-manager-ref namespace attribute not propagated into bean configuration [DATAJPA-15]

[spring-projects-issues]

Rain Wang opened DATAJPA-15 and commented

My App has a transactionMangername that is not a "transactionManager" name, I had set the the attribute of the entity-manager-factory-ref, but the app still scan the "tranactionManager"

---

Attachments:

• mylyn-context.zip (2.09 kB)

Issue Links:

• DATACMNS-12 Make usage of transactions optional for repositories
  ("depends on")

Referenced from: commits b884e73

1 votes, 1 watchers

[spring-projects-issues]

Oliver Drotbohm commented

entity-manager-factory-ref is (as the name suggests) to point the EntityManagerFactory bean to be used to obtain an EntityManager from. To point the repositories to use a transaction manager named other than transactionManager use the transaction-manager-ref attribute. Make sure your transaction manager uses the same EntityManagerFactory that you hand to the repositories element

[spring-projects-issues]

jokeway commented

hi,Oliver Gierke
I think the bug title should be changed to:
Why do not the attribute of the transaction-manager-ref be valid?
The method postProcessBeanDefinition had nothing to do with transaction-manager-ref config.

[spring-projects-issues]

Oliver Drotbohm commented

Sorry, I don't get you at all. What's wrong with transaction-manager-ref? Lowering the severity until we actually now what's wrong

[spring-projects-issues]

jokeway commented

The code in 'hades' process the transaction-manager-ref :

beanDefinitionBuilder.addPropertyValue("transactionManager",
        context.getTransactionManagerRef());

Missing in 'spring-data'

[spring-projects-issues]

Oliver Drotbohm commented

Ah, I see. Well spotted, thanks for filing!

[spring-projects-issues]

Oliver Drotbohm commented

Should be fixed and available in the snapshot tonight