Just to be sure, we should also check whether this occurs in generated mode too.
--
Istvan RATH, PhD
Research fellow Budapest University of Technology and Economics
Fault Tolerant Systems Research Group
On Thursday, October 24, 2013 at 10:23 AM, Tamas Szabo wrote:
No, I meant the Library.name. Have you
updated the example project? I am talking about
library.domain.base.
If I define the mostPopularBookCategory in the Library class
(which doesn't use eval) then I frequently see that the feature
has no value.
Hi,
I assume you mean Writer.name, since Library.name is not a
QBF. I can see that eval is used in that query, which is the
first occasion that such combination is used.
The space-time continuum is breached when a single value
QBF has multiple values (i.e. there is a match appearance
_before_ the previous match disappears) or when a multi value
QBF loses a match that has not appeared before.
I recommend you add breakpoints to the two
places where such error is logged (if it occurs for
multi-value QBFs as well) and look at the source and
target/removed values and the contents of the refMemories.
It is possible, that eval has some weird
issue that that causes multiple matches transiently. You could
try the name query without the eval (say the name is always
the lastName), if that behaves correctly, then my bet is on
eval, though debugging may reveal a problem in the QBF
implementation.
@Abel: When can such a thing happen with the
Single/MultiValueQueryBasedFeature?
Can you take a look at the library.domain.base example?
If you play around with the dynamic instance model you can see
some
really weird values for the Library.name feature.
Sometimes it doesn't have a value, sometimes it has a wrong
value...