Errors when Java Config declared TransactionProxyFactoryBean's target bean depends on an annotation declared bean that depends on another bean [SPR-16480] #21024
Comments
|
Juergen Hoeller commented Have you tried whether it makes any difference on |
|
Andrew H commented Oh! I knew I was forgetting something... Just tried with 5.0.4.BUILD-SNAPSHOT but I got the following exception (which I'm guessing is unrelated?): With 4.3.15.BUILD-SNAPSHOT I still see the error. (This is with adding the repository http://repo.spring.io/snapshot to my pom) |
|
Juergen Hoeller commented This seems unrelated indeed... but shouldn't happen nonetheless. Any special XML namespace declaration of yours there? Regular XML bean definition files should run on 5.0.x without any issues, whether 5.0.3 or 5.0.4. As for 4.3.15, that refinement hasn't been backported yet. I intend to go through a bunch of backports on Monday, including this one. |
|
Andrew H commented Ah oops. Yes, its explicitly referring to the 4.3 schemas. Give me a minute to google what its supposed to have and I shall try again. |
|
Andrew H commented I changed it to this, still get that exception. <beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:context="http://www.springframework.org/schema/context"
xmlns:tx= "http://www.springframework.org/schema/tx"
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context.xsd
http://www.springframework.org/schema/tx
http://www.springframework.org/schema/tx/spring-tx.xsd"> |
spring-projects-issues
added
type: bug
|
I am afraid there is nothing more actionable at this time. |
snicoll
removed
the
status: waiting-for-triage
Andrew H opened SPR-16480 and commented
This may be another manifestation of #20973 which I reported last week, but it affects Java configured TransactionProxyFactoryBean and it results in multiple exceptions being logged and the creation of the context failing.
It may be reproduced with the following bean configuration in Spring 4.3.14 or 5.0.3:
transactionManager - A no-op dummy implementation of PlatformTransactionManager
javaBazBean - A TransactionProxyFactoryBean whose target is an instance of BazBean, this is declared in a
@Beanmethod of a@Configurationclass and expects to be injected with a PlatformTransactionManager and an instance of BarBeanbarBean - A BarBean declared using
@Component, its constructor takes a FooBeanfooBean - A FooBean (declared using XML or
@Component), its constructor takes no argumentsThere is no circular reference yet it complains barBean (which depends only on fooBean) is still in creation, logging this exception in the attempt to create each of the beans that depends on barBean:
"org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'barBean': Requested bean is currently in creation: Is there an unresolvable circular reference?"
As with #20973, the order of annotated bean creation plays a role:
If you declare another bean using
@Componentthat depends on a BarBean and its classname comes alphabetically before BarBean - say "Aardvard" for example, then the errors vanish (and a WARNING appears instead), but if you rename Aardvark to Zebra, the errors will return.I have created and attached a small sample project to demonstrate the issue. (The main() class is named BeanCreationError).
Background information: I was attempting to replace some old XML configuration with annotation based configuration in order to reap compile-time error checking benefits. Unfortunately annotation based transaction configuration does not yet seem to provide for setting targetProxyClass at the bean level (#8346 has now been waiting 11 years for triage) hence my attempt to use Java Config with TransactionProxyFactoryBean in the hopes of reproducing the original XML configurations in Java.. This however is blocked by the above problem.
Affects: 4.3.14, 5.0.3
Attachments:
Issue Links:
The text was updated successfully, but these errors were encountered: