Details
-
Bug
-
Resolution: Solved By
-
Major
-
None
-
3.5
-
Unknown
-
N/A
-
N/A
-
Description
In event stream, jerome have implemented "named parameters", which was a good feature (XWIKI-6839).
However, for performance reasons, it have been reverted (XWIKI-7520).
So it means that we have, in the Activity Stream, custom parameters called "param1", "param2", "param3", "param4" and "param5" that we cannot use in Event Stream.
The correct way to fix this issue is XWIKI-7554, but until we find how to make it without performance issue, we could also simply add "param1", "param2", "param3", "param4" and "param5" to the Event Stream module, even if it looks a bit ugly.
Unless ActivityStream had never used them, it means now we have some data store in the wiki that Event Stream is not able to load...
Attachments
Issue Links
- blocks
-
XWIKI-14010 Create a Notification system
- Closed
- depends on
-
XWIKI-17040 Allow to use a custom LegacyEventConverter
- Closed
- relates to
-
XWIKI-7520 Activity Stream performance regression
- Closed
-
XWIKI-6839 Support for named parameters in eventstream events
- Closed
-
XWIKI-7554 Add again support for Named Parameters in the Event Stream
- Closed