eBus / Bugs / #25 Abstract EMessage and EField message fields not supported.

#25 Abstract EMessage and EField message fields not supported.

Milestone: v1.0 (example)

Status: closed-fixed

Owner: Charles Rapp

Labels: None

Priority: 4

Updated: 2019-12-15

Created: 2017-06-13

Creator: Charles Rapp

Private: No

When an eBus message has a field of type EMessage or EField, then the field's type must be concrete. Abstract fields should be supported to allow for flexible message design. This means serializing the EMessage message key or the EField class prior to serializing the instance. This allows for the far-end to determine the message type prior to de-serializing.

Discussion

Charles Rapp - 2019-12-15

status: accepted --> closed-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Charles Rapp - 2019-12-15

Bug corrected in eBus release 5.2.2.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Abstract EMessage and EField message fields not supported.

Publish/Subscribe, Request/Reply Messaging API for Java.

Group

Searches

Help

#25 Abstract EMessage and EField message fields not supported.

Discussion