Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #230 (closed)

Opened 13 years ago

Closed 12 years ago

Unify "Global" types with SystemTypes.

Reported by: jamoore Owned by: jamoore
Priority: major Milestone: 3.0-Beta3
Component: Security Version: 3.0-M3
Keywords: dsl, types, event Cc:
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description

Currently, only Experimenter and Event are "Global" types (as defined in the DSL). This means they have no owner/group/event to prevent weird cyclical dependencies. First, Permissions should also be added to this based on how the filter issue is solved (see #117), so that Experimenter and Event always have null details.

And in general, global types should disappear and be replaced by properly configured (i.e. umasks #179 etc.) system types.

Change History (6)

comment:1 Changed 13 years ago by jmoore

#239 has some discussion on this as well.

comment:2 Changed 13 years ago by jmoore

The easiest way to simplify/unify global and system types may to handle the mapping manually. I.e. meta.ome.xml would no longer need to exist or only in stub form (once all are global, see #239), and the actual *.hbm.xml files would override the code generated ones. Then it would be possible in that ome/model/meta package to define a static utility class for do the isSystemType(Class) checks. Useable also then on the client-side to know when an object is not doing to have owner/group/permissions/etc.

This would make the system types (which really should be under ome.model.sys(tem)) the boot strap types, and the only ones which should be referenced with the core classes.

comment:3 Changed 13 years ago by jmoore

  • Keywords iteration6 added

comment:4 Changed 13 years ago by jmoore

  • Keywords iteration6 removed
  • Milestone changed from 3.0-M3 to 3.0-M4

#239 is marked duplicate. See for more context. Will also have to wait at least until M4 because of database changes (See #373.)

comment:5 Changed 13 years ago by jmoore

  • Milestone changed from 3.0-Beta2 to 3.0-Beta3

comment:6 Changed 12 years ago by jmoore

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.158388 sec.)

We're Hiring!