Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
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"

User Story #233 (closed)

Opened 18 years ago

Closed 18 years ago

Read/write separation is not clean enough

Reported by: jamoore Owned by: jamoore
Priority: minor Milestone: 3.0-M3
Component: ORM Keywords: spring,hibernate,flush,interceptor,read,write, iteration4
Cc: Story Points: n.a.
Sprint: n.a. Importance: n.a.
Total Remaining Time: n.a. Estimated Remaining Time: n.a.

Description

All service methods are marked as read or write, however there are times when "write-like" actions take place which can cause difficulties. An example is in PojosImpl where we'd like to re-arrange results before returning them to the user.

Read calls should be protected from accidental writes to the db through AOP/interceptor magic. Currently, the Spring wrappers around Hibernate sessions tend to want to guarantee flushes.

We need a flag to guarantee non-flush.

Change History (2)

comment:1 Changed 18 years ago by jmoore

Depends on #236

comment:2 Changed 18 years ago by jmoore

  • Keywords iteration4 added
  • Milestone changed from Unscheduled to 3.0-M3
  • Resolution set to duplicate
  • Status changed from new to closed

Later ticket #323 subsumes this one. Closing.

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.63509 sec.)

We're Hiring!