Task #254 (closed)
Opened 18 years ago
Closed 18 years ago
EventContext like CurrentDetails should be completely encapsulated by SecuritySystem
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | 3.0-M3 |
| Component: | Security | Version: | 3.0-M3 |
| Keywords: | refactor, encapsulation, iteration5 | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by jmoore)
Currently EventContext rears its head only in AbstractBean. That too should stop. When so, fix the tiki docs at security system and getting started
Change History (5)
comment:1 Changed 18 years ago by jmoore
- Description modified (diff)
comment:2 Changed 18 years ago by jmoore
- Keywords iteration4 added
- Priority changed from trivial to minor
comment:3 Changed 18 years ago by jmoore
comment:4 Changed 18 years ago by jmoore
- Keywords iteration5 added; iteration4 removed
Dependent on #328. Moving to iteration5
comment:5 Changed 18 years ago by jmoore
- Resolution set to fixed
- Status changed from new to closed
Have taken another turn. Now fully using EventContext and even making it remotable. See #328 for details.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
r891 adds login and logout to the SecuritySystem interface and changes all /server code to use that rather than accessing EventContext directly. r892 does the same for /ejb.
These changes don't, however, lower the visibility of ome.system.*EventContext. They should probably just be removed or moved to ome.security.