Community
Participate
Working Groups
A binding of constraints no longer finds client contexts defined by other plug-ins (it's a matter of luck) since the resolution of bug 137213. The result is occurrences of "Client context <other plug-in's context id> does not exist in constraint binding defined by plug-in <my plug-in id>" errors. The problem is, that now each extension is processed separately, parsing first context definitions and then bindings. However, previously, *all* context definitions were processed before *all* bindings, cutting across extensions. Probably, late resolution of client context IDs will be required (descriptors, anyone?)
Committed a fix to ensure that constraint-bindings can reference a client-context ID that has not yet been initialized. If the client-context does not yet exist when binding is parsed from an extension, then a stub is created, to be filled in when its declaration is parsed. In the event that no such declaration is found by the time validation requires it, the problem will be logged at that time and the bindings disabled. Also committed a reorganization of the extensions in the JUnit test plug-in to reproduce the problem and test the solution.
Fix available in HEAD: 1.3.0.I200811021725.
Restore original target after milestones were deranged.
