change email webservice whould initiate only one transaction. At this time it is initiating as many transactions as there are number of SorRecords for a person. For example, if some one has SorPerson records for RIAS and SRDB, there will be two transactions initiated.
This issue only popped up after resolving OR-384. It is quite related, but of lower priority for the time being.
Environment
None
Activity
Show:
Naveed Hussain
June 6, 2012 at 8:01 PM
Resolved the issue by adding a method (saveOrCreateEmailForAllSorPersons)in service layer (DefaultEmailService). This is the method from where a single transaction will start.
change email webservice whould initiate only one transaction. At this time it is initiating as many transactions as there are number of SorRecords for a person. For example, if some one has SorPerson records for RIAS and SRDB, there will be two transactions initiated.
This issue only popped up after resolving OR-384. It is quite related, but of lower priority for the time being.