Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

inner "bean" element with "parent" attribute is forced to have an "id" [SPR-380] #5110

Closed
spring-projects-issues opened this issue Oct 7, 2004 · 1 comment
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: bug A general bug
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Davide Baroncelli opened SPR-380 and commented

I tried using an inner bean definition with a "parent" definition, as in what follows:

<bean id="outer" class="blah.blah">
<property name="p">
<bean parent="inherited">
...blahblahblah...
</bean>
</property>
</bean>
<bean id="inherited">
...blahblah...
</bean>

but this fails with an error: "Error registering bean with name '' defined in class path resource [applicationContext.xml]: Child bean definition has neither 'id' nor 'name'".

I think this should be allowed, isn't it? Anyway, adding an "id" property to the inner bean seems to be a suitable workaround.


Affects: 1.1.1

Issue Links:

  • SWF-381 Make it easier to assign a flow definition an identifier when registering it in a registry
@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

Thanks for the report! This has already been fixed in CVS a couple of days ago, to be part of 1.1.2. Feel free to give a current CVS snapshot a try!

Juergen

@spring-projects-issues spring-projects-issues added type: bug A general bug in: core Issues in core modules (aop, beans, core, context, expression) labels Jan 10, 2019
@spring-projects-issues spring-projects-issues added this to the 1.1.2 milestone Jan 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: bug A general bug
Projects
None yet
Development

No branches or pull requests

2 participants