Hi Erik, yes, the framework calls the auditing service within the transaction.
The implementation of the auditing service is pluggable however, and in fact the framework did not itself provide an out-of-the-box implementation. I presume you are therefore referring to the Isis Addons implementation, which behaves as you say. But it is very easy to provide your own implementation. That could use Activemq, for example, to decouple the persisting of the audit records from the original request. I mention Activemq because there is the publisher in Isis Add-ons for the rather similar publishing service SPI Hope that helps Dan On 14 Mar 2016 08:20, "Erik de Hair" <[email protected]> wrote: > Hi, > > It looks like the audit logging is executed before an action is fully > completed. (Is that correct?) Is it possible to do the audit logging > asynchronously, so after the action itself was fully completed and all > changes committed to the database? For larger data structures the audit > logging takes a relatively large amount of time because of all the separate > inserts per property. > > This way we missed some asynchronously sent response messages from our > suppliers. We should fix this in a different way, but I thought it might be > something that could improve responsiveness of the application. > > Met vriendelijke groet, > > > *Erik de Hair* > > Software Engineer | Pocos bv > > Pocos gaat verhuizen! Vanaf 29 maart is ons adres: Beemdstraat 1b, 5653 MA > Eindhoven. > > [image: Pocos bv] [image: Telecom Inspirience awards - Best VaMo Project] > > T: 088-0100713 | [email protected] | Partner ondersteuning: > [email protected] <[email protected]> | Service: [email protected] > > www.pocos.nl | Croy 9c, 5653 LC Eindhoven | Kamer van Koophandel 17097024 > | [image: btn_in_20x15] > <https://www.linkedin.com/company/pocos?trk=prof-following-company-logo> > [image: > twitter] <https://twitter.com/Pocosbv> > >
