Task #356 (closed)
Opened 18 years ago
Closed 9 years ago
CreatePojosFixture needs further improvements for being client & server-side compatible.
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | major | Milestone: | Unscheduled |
| Component: | General | Version: | 3.0-M1 |
| Keywords: | n.a. | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
r934 "fixed" CreatePojosFixture for the server-side, but didn't go far enough. The user/group values are left null. Either:
- These should be hidden behind getters which throw UnsupportedOperationExceptions or
- The Fixture should be updated to use the new SecSystem functionality (#328) for getting current user.
Change History (5)
comment:1 Changed 18 years ago by jmoore
- Resolution set to fixed
- Status changed from new to closed
comment:2 Changed 18 years ago by jmoore
- Priority changed from minor to major
- Resolution fixed deleted
- Status changed from closed to reopened
The previous fix is not enough. On the server-side (without Login) all objects are being given to the same user. CreatePojosFixture? may not be able to work server-side. Or, there will need to be a server-side ServiceFactory which takes a Login and calls securitySystem.login(name) before every call.
comment:3 Changed 18 years ago by jmoore
- Keywords iteration5 removed
- Milestone changed from 3.0-M3 to 3.0-M4
comment:4 Changed 17 years ago by jmoore
- Milestone changed from 3.0-Beta2 to Unscheduled
comment:5 Changed 9 years ago by jburel
- Resolution set to invalid
- Status changed from reopened to closed
More tests have been added and structure expanded.
Closing this ticket.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Fixed by r957. See #328 for more.