This is the simplest EntityQuery ever, but for any other case, from a more complex one, to unwrap methods or other dynamically calculated lists, not caching the results will be a performance issue. Maybe even a concurrent request could change some parameter that would end up giving different result set.
Yes, but who has ever guaranteed you that the value binding of a datatable would be evaluated once and only once.
@Pete: This might be fixable by modyfing UISeamCommandBase.getSelection() and UISelection to directly set the datamodel instead of the datamodel value expression.
Regards
Felix
Hi there, sorry for the delay, just got a sample minimal test case, here it is:
http://bco.homelinux.org/cosas/slinkerror.zip
Complete ear + war + jar + src + build.xml ;)
I'm running it on jBoss 4.2.1 + Seam2.
This link doesn't work.
it does work, I just happen to have lousy bandwidth (and a dynamic dns)
I can't get anything. Can you email me the file?