Bugs: Browse | Download .csv | Monitor

[#4119] [OCL] Annoying behavior with pathmap:// resources

Date: 2012-04-17 16:49	Priority: 3
State: Closed
Submitted by: Pierre Gaufillet (gaufille)	Assigned to: Pierre Gaufillet (gaufille)
Category: OCL tools	Resolution: Fixed
Platform: Linux / Gtk+	Detected in version: 5.2.0
Target version: 5.3.0
Summary: [OCL] Annoying behavior with pathmap:// resources
Detailed description when checking UML / SysML files, exceptions are raised each time a marker needs to be placed on a pathmap:// resource. Those exceptions are of no use, as pathmap:// are usually not modified by users. Moreover, it impacts the performances. It should be modified so that exceptions are raised only if a workspace resource can not be accessed. Beyond this issue with exceptions, users are most of the time not interested in checking pathmapped resources. They should therefore be removed from the OCLextentMap. The consequence is that context and allInstance() will only map to objects contained in workspace resources.

Followup Message Date: 2012-04-19 14:42 Sender: Pierre Gaufillet committed for 5.3.0. Remarks are welcome. Linked to [#3219]. This behavior may be a preference for each rule.

Related Tasks: No Related Tasks

Attached Files: No Files Currently Attached

No commits have been made.

Changes: Field Old Value Date By status_id Open 2012-11-14 10:38 gaufille close_date None 2012-11-14 10:38 gaufille details when checking UML / SysML files, exceptions are raised each time a marker needs to be placed on a pathmap:// resource. Those exceptions are of no use, as pathmap:// are usually not modified by users. Moreover, it impacts the performances. It should be modified so that exceptions are raised only if a workspace resource can not be accessed. 2012-04-19 14:42 gaufille summary [OCL] Annoying Exceptions on pathmap:// resources 2012-04-19 14:42 gaufille Resolution Accepted 2012-04-17 17:00 gaufille