search

eclipse-ocl / org.eclipse.ocl

Eclipse Public License 2.0
0 stars 0 forks source link

Regression Complete OCL doesn't complement #2185

Closed eclipse-ocl-bot closed 2 weeks ago

eclipse-ocl-bot commented 2 weeks ago

| --- | --- | | Bugzilla Link | 574041 | | Status | RESOLVED FIXED | | Importance | P3 major | | Reported | Jun 05, 2021 09:35 EDT | | Modified | Feb 17, 2024 03:30 EDT | | Depends on | 571721 | | See also | 582947, 582722 | | Reporter | Ed Willink |

Description

Pursuing the Complete OCL tutorial and the complements are ignored.

Probably an EnviromentFactory per-thread issue.

But why no JUnit test failure for this important UX?

eclipse-ocl-bot commented 2 weeks ago

By Ed Willink on Jun 06, 2021 04:12

(In reply to Ed Willink from comment #0)

Probably an EnviromentFactory per-thread issue.

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=571721#c7

eclipse-ocl-bot commented 2 weeks ago

By Ed Willink on Oct 14, 2021 06:16

Resolved in 2021-06

eclipse-ocl-bot commented 2 weeks ago

By Ed Willink on Feb 17, 2024 03:30

(In reply to Ed Willink from comment #0)

Probably an EnviromentFactory per-thread issue.

Problem re-created while over-avoiding EnvironmentFactory lifecycle as part of Bug 582947.

When an EMF editor application does OCL->Load Document, the OCL-blind EMF application must acquire a discoverable EnvironmentFactory whose lifetime perists until the EMF application terminates. This can now be achieved by associating the EnvironmentFactory with the relevant per-part main Thread manged by the ThreadLocalExecutorUI.

(Limiting the life-cycle to the LoadCompleteOCLResourceHandler.ResourceDialog causes unload proxying of the load resources.)