History | Log In     View a printable version of the current page. Get help!  
Issue Details [XML]

Key: SES-290
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Arjohn Kampman
Reporter: Arjohn Kampman
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Sesame

AdminListener.transactionStart()/End() only called in server context when adding data

Created: 07/Aug/06 09:42 AM   Updated: 07/Aug/06 09:43 AM
Component/s: Admin (add/remove statements)
Affects Version/s: 1.2.5, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.2, 1.2-RC2, 1.2-RC1, 1.1.3, 1.1.2, 1.1.1, 1.1, 1.1-RC2, 1.1-RC1, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0
Fix Version/s: 1.2.6


 Description   
When data is uploaded to a Sesame server, the transactionStart() and transactionEnd() methods defined in interface AdminListener are being called by the servlets while the rest of the methods are being called by the RDF Admin module. As a result, the first two methods do not get called when data is added to a local repository. To fix this, these method calls should be moved from the servlets to the RDF Admin module. The RDF Admin module already correctly calls these methods when statements are removed or when a repository is cleared.

 All   Comments   Change History      Sort Order:
Comment by Arjohn Kampman [07/Aug/06 09:43 AM]
The calls to AdminListener.transactionStart() and transactionEnd() have been moved to the RDF Admin module. Further, the code for adding data that was in class SesameUpload has been merged into class RdfAdmin, which already contained the code for removing statements and clearing repositories.