[
https://issues.jboss.org/browse/BAM-26?page=com.atlassian.jira.plugin.sys...
]
Gary Brown updated BAM-26:
--------------------------
Fix Version/s: 1.0.0.M4
(was: 1.0.0.M5)
Investigate deserialising custom activity types
-----------------------------------------------
Key: BAM-26
URL:
https://issues.jboss.org/browse/BAM-26
Project: Business Activity Monitoring
Issue Type: Task
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.M4
Currently the JSON deserialization uses a type field to determine the ActivityType.
However this is only possible because the types have been registered against the
ActivityType class using the Jackson JsonSubTypes annotation.
The benefit of the type field approach is that it is language independent (whereas @class
is Java specific) and the amount of information in the json encoding is smaller (i.e. no
package name).
However this approach means it is not easy for users to add new ActivityType derived
classes, as the class would need to be added to the JsonSubTypes derived in the
annotations for ActivityType class.
Another approach would be to have own type registry that custom activity type classes
could also be registered with.
Need to investigate the possibilities and how the user's custom classes would be
added to the AS7 installation easily. May need to update the org.overlord.bam module?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira