This is not straightforward. WlssContainerAdapter should allow this without issue; however IBMContainerAdapter uses the AsynchronousWorkAPI, which restricts return values to be Serializable. JavaToEChartsMachine currently is not Serializable.
The issue is that JavaToEChartsMachine contains a FeatureBox, which is not Serializable. The FeatureBox is used for putEvent(). A workaround would be to make the FeatureBox transient, and restore it if needed to putEvent(). JavaToEChartsMachine knows its SipApplicationSession ID, so it could retrieve the FeatureBox from the SipApplicationSession.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is not straightforward. WlssContainerAdapter should allow this without issue; however IBMContainerAdapter uses the AsynchronousWorkAPI, which restricts return values to be Serializable. JavaToEChartsMachine currently is not Serializable.
The issue is that JavaToEChartsMachine contains a FeatureBox, which is not Serializable. The FeatureBox is used for putEvent(). A workaround would be to make the FeatureBox transient, and restore it if needed to putEvent(). JavaToEChartsMachine knows its SipApplicationSession ID, so it could retrieve the FeatureBox from the SipApplicationSession.