You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@isis.apache.org by David Tildesley <da...@yahoo.co.nz> on 2013/11/06 21:57:06 UTC
Publish and Audit service questions
Hi All,
Audit service is missing one important item of information - the name of the attribute for the value that changed.
Publishing service doesn't provide the "previous value" and so this doesn't provide an alternative to address the point above.
Apart from framework changes (happy to raise a Jira) , what else can we do in the meantime to override either Audit or Publishing service behavior?
Thanks,
David.
Re: Publish and Audit service questions
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
You're welcome.
Geeking out at Oredev in Malmo [1], on free beer, so was online anyway.
Very chilled out here.
[1]
http://oredev.org/2013/wed-fri-conference/rrraddd-ridiculously-rapid-domain-driven-and-restful-apps-with-apache-isis
On 6 November 2013 22:22, David Tildesley <da...@yahoo.co.nz> wrote:
> Hi Dan,
>
> Magic. Thanks very much for your quick reply. :)
>
> Regards,
> David.
>
>
>
>
> On Thursday, 7 November 2013 10:19 AM, Dan Haywood <
> dan@haywood-associates.co.uk> wrote:
>
> Hi David,
> I noticed this (quite) recently also.
>
> The AuditService2 interface adds in the missing attribute. If the audit
> service implements AuditService2 rather than the original AuditService,
> then the overloaded version of audit(...) will be called that provides the
> missing parameter.
>
> All of the above was in the recent v1.3.0 release.
>
> Let me know if that doesn't work for you.
>
> Cheers
> Dan
>
>
>
>
> On 6 November 2013 21:57, David Tildesley <da...@yahoo.co.nz> wrote:
>
> > Hi All,
> >
> > Audit service is missing one important item of information - the name of
> > the attribute for the value that changed.
> >
> > Publishing service doesn't provide the "previous value" and so this
> > doesn't provide an alternative to address the point above.
> >
> > Apart from framework changes (happy to raise a Jira) , what else can we
> do
> > in the meantime to override either Audit or Publishing service behavior?
> >
> > Thanks,
> > David.
> >
>
Re: Publish and Audit service questions
Posted by David Tildesley <da...@yahoo.co.nz>.
Hi Dan,
Magic. Thanks very much for your quick reply. :)
Regards,
David.
On Thursday, 7 November 2013 10:19 AM, Dan Haywood <da...@haywood-associates.co.uk> wrote:
Hi David,
I noticed this (quite) recently also.
The AuditService2 interface adds in the missing attribute. If the audit
service implements AuditService2 rather than the original AuditService,
then the overloaded version of audit(...) will be called that provides the
missing parameter.
All of the above was in the recent v1.3.0 release.
Let me know if that doesn't work for you.
Cheers
Dan
On 6 November 2013 21:57, David Tildesley <da...@yahoo.co.nz> wrote:
> Hi All,
>
> Audit service is missing one important item of information - the name of
> the attribute for the value that changed.
>
> Publishing service doesn't provide the "previous value" and so this
> doesn't provide an alternative to address the point above.
>
> Apart from framework changes (happy to raise a Jira) , what else can we do
> in the meantime to override either Audit or Publishing service behavior?
>
> Thanks,
> David.
>
Re: Publish and Audit service questions
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
Hi David,
I noticed this (quite) recently also.
The AuditService2 interface adds in the missing attribute. If the audit
service implements AuditService2 rather than the original AuditService,
then the overloaded version of audit(...) will be called that provides the
missing parameter.
All of the above was in the recent v1.3.0 release.
Let me know if that doesn't work for you.
Cheers
Dan
On 6 November 2013 21:57, David Tildesley <da...@yahoo.co.nz> wrote:
> Hi All,
>
> Audit service is missing one important item of information - the name of
> the attribute for the value that changed.
>
> Publishing service doesn't provide the "previous value" and so this
> doesn't provide an alternative to address the point above.
>
> Apart from framework changes (happy to raise a Jira) , what else can we do
> in the meantime to override either Audit or Publishing service behavior?
>
> Thanks,
> David.
>