This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

Valkyrie RefreshableValueHolder bug

May 29th, 2011, 04:50 PM

First of all, big thanks to Lieven for your efforts on valkyrie, really nice to finally have spring 3 support etc!
I've been porting my "hobby-app" and the spring rcp->valkyrie transition went really smooth. The only problems i had was mostly javaconfig and aspectj related, takes a while to get the hang of things. Also had some strange problems with properties not being autowired properly etc but found workarounds for all those issues now.

However, I ran into a problem in RefreshableValueHolder. In the constructor it calls refresh() (unless lazy is set.) Refresh in turn calls setValue() etc that finally accesses the @Autowired valueChangeDetector of AbstractValueModel. Since this is all called from the constructor, valueChangeDetector hasn't been wired yet. Don't know if there is somewhere to report bugs yet so posting it here.