Community
Participate
Working Groups
In Kepler, for a collections with items that contain an attribute that for some of the items is undefined, xselect always returns an empty set when comparing on the attribute value: coll->xselect(item.attribute = aValue)->size() = 0 In Juno, this statement returns all items that match the expression. In Kepler and Juno, coll->selectOne(item.attribute = aValue) return one item (if the expression matches). The semantics of xselect and selectOne should be the same (modulo one item vs. a list of items)
"undefined" was a vagueness in OCL 2.0 that was clarified to "null" or "invalid" in OCL 2.3. So your report about "undefined" is also vague. Please provide a test case that demonstrates your concern.
Can't reproduce on the following example. There are classes with and without a package in my test model. As expected, xselect returns only those with a package. var classes : Set(EClass) = source.objects()[EClass]; var selection : Collection(EClass) = classes->xselect(c | c.ePackage != null );
(In reply to comment #2) > Can't reproduce on the following example. The original report distinguished Juno/Kepler, but referred to 'undefined' values. Presumably 'null' values since collections containing invalid are invalid. The classic OCL functionality re-used by QVTo has been very stable but not 100%. There are a few corner cases where the functionality was clearly wrong and easily fixed and so it has been corrected. This sounds like it could be one of them. You might also want to see whether the setting of the "Implement lax null handling .." option has any effect.
