|How validation constraints may have been disabled [message #538011]
||Fri, 04 June 2010 13:46
| Adam Neal
Registered: July 2009
I'm investigating why in our tool validation constraints contributed by a
lower component have been removed. Specifically UML validations. I found
that when I disable our plugins, the validation constraints are loaded and
executed (i.e. it all works). However, something we've done in our code
base has caused these validation rules to no longer be loaded for batch
validations. I'm wondering if anyone can provide ideas on what we may have
done to do this?
I don't see any registrations of the same id in our .xml files. I do see
that we have our own validation client contex which extends the context that
actually plugs in the validations. But I tried commenting this out in the
plugin.xml and it didn't fix it.... Could it be something related to client
When debugging the non-working case, I see it read in the validation
constraint ( and it seems to be added the same way as in the working case,
that its added to the targetsMap, and its set as not-explict ), but when it
comes time to actually execute the batch constraints, it doesn't exist in
the list anymore ( getConstraints() returns only 10 constraints, where as in
the working case there are 23). I can't seem to pin-point where/why its
being dropped :(
I've been looking in the ConstraintCache class, and this is where I see it
get 'loaded'. Any hints on how we could have disabled the UML validations?
Again, UML defines the validations, our base tool registers them, and then
we are somehow disabling them.
I am not seeing any errors/warnings in the log about disabling constraints.
Thanks in advance!
Powered by FUDForum
. Page generated in 0.09463 seconds