Ticket #827 (closed Defect: fixed)

Opened 9 years ago

Last modified 9 years ago

AccessControl assignToWorkspace() seems not to work with Associations

Reported by: Malte Owned by: jri
Priority: Major Milestone: Release 4.7
Component: DeepaMehta Standard Distribution Version: 4.6.1
Keywords: Cc: jri
Complexity: 3 Area:


.. can you confirm this?


// 5) ### associate association to "system" workspace too
AccessControl.assignToWorkspace(assoc, acCore.getSystemWorkspaceId());

I get some neo4j error like "Expecting node, found edge" - sorry, but i have no access to full stack trace atm and getting it is too far away from me now (different setup).

Background is
Associations introduced in a migration cannot be edited/deleted by "admin" later but if i could assign them to the "System" workspace they will be.

Change History

comment:1 Changed 9 years ago by jri

  • Status changed from new to accepted
  • Owner set to jri

Thanks for reporting!

comment:2 Changed 9 years ago by Jörg Richter <jri@…>

In dc191f468f86ab84951b8cea8a3cb2245a5e258a/deepamehta:

Fix Core AccessControl?: assignToWorkspace (#827).

Core AccessControl?'s assignToWorkspace() method works also for associations.

Thank you, Malte, for reporting!

See #827.

comment:3 Changed 9 years ago by jri

  • Status changed from accepted to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.