- This topic has 3 replies, 3 voices, and was last updated 18 years, 4 months ago by Brian Fernandes.
-
AuthorPosts
-
Randy BurgessMemberI have a Spring application context that I’ve been using for several months. In ME 4.1.1 I had no problems with it but as soon as I loaded this project in 5.0 GA I got a validation error on a BeanNameAutoProxyCreator bean. Here is the bean definition:
<bean id="autoProxyCreator" class="org.springframework.aop.framework.autoproxy.BeanNameAutoProxyCreator"> <property name="interceptorNames"> <list> <idref local="matchAllTxInterceptor" /> <idref bean="hibInterceptor" /> </list> </property> <property name="beanNames"> <list> <idref local="StoreLoginsDAO" /> <idref local="CustomersDAO" /> <idref local="StoresDAO" /> <idref local="ProductTypesDAO"/> <idref local="ProductClassListDAO"/> <idref local="VendorListDAO"/> </list> </property> </bean>
The error is “Error registering bean in file…: Unexpected failure during bean definition parsing; nested exception is java.lang.IllegalArgumentException: Bean name must not be empty.
If I add the name attribute to the <bean> element I still get the same error. This bean is right out of the Spring documentation.
Brian FernandesModeratorRandy,
I was able to replicate this issue locally and it seems to be caused by regression in some other validation fix.
Your file is completely valid, but this validation bug gives you a false negative. You may ignore this error for now or use a <ref> or <value> element instead of the <idref> as we will validate <ref> elements as well.
I apologize for the inconvenience caused, do let us know how it goes.
Best,
Brian.
Mathias BrökelmannMemberis there a timeline when this problem get fixed?
Brian FernandesModeratorThe problem has been fixed locally and the fix will be released in the next MyEclipse release. The management has not yet put the next release down on the timeline so I don’t know when this may be.
I apologize for the iconvenience caused,
Brian. -
AuthorPosts