[#GALAXY-322] Activity logging should be built on event API

Galaxy

Activity logging should be built on event API

Created: 27/Jun/08 10:25 AM Updated: 31/Aug/08 08:53 AM

Component/s:

Core

Affects Version/s:

None

Fix Version/s:

1.5-RC

Time Tracking:

Not Specified

Issue Links:

Block

This issue is blocked by:

~~GALAXY-321~~ Create Event API

Labels:
User impact:	Medium

All

Comments

Work Log

Change History

Transitions

FishEye

Sort Order:

[ Permlink | « Hide ]

Andrew Perepelytsya added a comment - 20/Jul/08 03:51 PM

Most of the activity logging has been migrated to use event api and enhanced where applicable. This is for info-type messages, errors have not yet been ported.

[ Permlink | « Hide ]

Andrew Perepelytsya added a comment - 22/Jul/08 12:53 PM

Now that we have async support, practically every activity logging listener can be implemented as an async one

[ Permlink | « Hide ]

Dan Diephouse added a comment - 13/Aug/08 10:25 PM

Just looking to see if I could close this - seems the only thing that isn't implemented as an event is a property change.

[ Permlink | « Hide ]

Andrew Perepelytsya added a comment - 14/Aug/08 07:45 AM

It was, though now needs minor fixes after artifact/entry refactoring (check the log text). After that we can close the issue, keeping in mind that error logging needs to be thought through in the future, currently it writes to the log directly when needed.