We're using Eclipse 3.4.1 with SpringSource dm Server 1.0. There are two Targeted Runtimes defined (Project / Properties / Targeted Runtimes).
The one we setup is called
SpringSource dm Server (Runtime) v1.0
There is one pre-defined called
We find that, even though we select SpringSource dm Server (Runtime) v1.0, Eclipse seems to frequently change the Targeted Runtime back to SpringSource v1.0.
Yes, we click Apply and OK on the properties screen.
Anyone seen that before? Any idea how to fix it?
Here are images of our Targeted Runtimes and Run Configuration screens.
Does Spring-MVC annotation based bean validation support for collection-based property ? (Spring-MVC)
Spring 2 Hibernate Annotation
Two approaches of task distribution in a multi tier application
You need to go into your Run/Debug configuration and change the execution environment there to point to the desired target..
What's the most AGILE APPROACH to validate Spring-MVC command (speeds up validation implementation on server side) ? (Spring-MVC)
Personally, I think this behaviour is confusing.
ConstraintViolationException VS DataIntegrityViolationException
I recommend filing a bug against Eclipse to make this easier to use..
Testing an AspectJ Aspect
map url to controller
Can't set LevelRangeFilter for log4j