[tichkent]

Hi there,

If I try to use a custom typed value in a Spring injected collection (making
use of custom property editors to convert the string to an instance of the
correct type) MyEclipse incorrectly gives an error – even though the file
is completely valid and runs fine as far as Spring is concerned.

As a simple example, try the following Spring XML file.

<?xml version=”1.0″ encoding=”UTF-8″?>
<!DOCTYPE beans PUBLIC “-//SPRING//DTD BEAN//EN” “http://www.springframework.org/dtd/spring-beans.dtd”&gt;
<beans>
<bean id=”test” class=”Test”>
<property name=”testProp”>
<list>
<value type=”Test2″>Test2</value>
</list>
</property>
</bean>
</beans>

and both classes Test and Test2 exist – MyEclipse incorrectly reports an error:

“Error registering bean with name ‘test’ defined in file [C:\Projects\test\src\test-spring.xml]:
Value type class [Test2] not found; nested exception is java.lang.ClassNotFoundException: Test2″

The classes are fine (just standard POJOs with the required setters) and Spring
can correctly instantiate the structure – just MyEclipse doesn’t seem to have the
correct classpath set up for parsing <value type=”…”> style constructs. This is
very offputting as we run our project with all Eclipse warnings switched on and
don’t allow any warnings to be checked in.

I hope this can be fixed up as we now rely on MyEclipse’s fantastic Spring abilities!

Thanks,

Richard Kent

Configuration:

*** Date: Mon Apr 03 15:36:29 BST 2006

*** Platform Details:

*** System properties:
apple.laf.useScreenMenuBar=true
awt.toolkit=sun.awt.windows.WToolkit
com.apple.mrj.application.apple.menu.about.name=ArgoUML
eclipse.application=org.eclipse.ui.ide.workbench
eclipse.buildId=M20060118-1600
eclipse.commands=-os
win32
-ws
win32
-arch
x86
-launcher
C:\eclipse312\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
fc4_3c
-vm
C:\jdk15\bin\javaw.exe
eclipse.product=org.eclipse.sdk.ide
eclipse.startTime=1144073689968
eclipse.vm=C:\jdk15\bin\javaw.exe
eclipse.vmargs=-Duser.language=en
-Xms128M
-Xmx512M
-XX:PermSize=64M
-XX:MaxPermSize=128M
-Dosgi.splashLocation=C:\Program Files\MyEclipse\eclipse\MyEclipseSplash.bmp
-jar
C:\eclipse312\startup.jar
eof=eof
file.encoding=Cp1252
file.encoding.pkg=sun.io
file.separator=\
gef.imageLocation=/org/argouml/Images
java.awt.graphicsenv=sun.awt.Win32GraphicsEnvironment
java.awt.printerjob=sun.awt.windows.WPrinterJob
java.class.path=C:\eclipse312\startup.jar
java.class.version=49.0
java.endorsed.dirs=C:\jdk15\jre\lib\endorsed
java.ext.dirs=C:\jdk15\jre\lib\ext
java.home=C:\jdk15\jre=
<snip>

[Riyad Kalla]

Richard I am looking into this. Also for future reference please use the MyEclipse > About MyEclipse > Configuration Summary button when posting your version info, it’s smaller and more digestable than the huge About > Configuration Summary.

[Riyad Kalla]

Richard,
I just looked into this and it was fixed in 5.0Milestone1. We don’t encourage people in production environments to upgrade to milestone releases usually because they aren’t as fully tested as our GA releases, but it depends on how bad this issue is effecting your team. So far in our testing we haven’t had any major (or even minor) bugs reported with 5.0 M1, so you might want to try it out yourself and roll it out slowly to your team if it works. Again there may be bugs in the Eclipse platform that pose a problem to your team, so if you do choose to roll it out, do it slowly.

[Author]

Posts