v6.161

Changes in this release:

• Add SystemSchema.hasChannel() helper method.

v6.160

Changes in this release:

• Flush the Websocket after writing to it, to ensure data gets transmitted to the client.

v6.159

Changes in this release:

• Gracefully handle non-contiguous Channel ids in server code.

v6.158

Changes in this release:

• Gracefully handle non-contiguous Channel ids.

v6.157

Changes in this release:

• If an exec or subscription request is submitted within an Arez transaction then we delay the triggering of the replicant scheduler until the transaction completes by queuing an action.

v6.156

Changes in this release:

• Patch ReplicationInterceptor so that it does not remove the ServerConstants.REQUEST_RESPONSE_KEY from the context on completion so that the value van be propagated back to the caller.

v6.155

Changes in this release:

v6.154

Changes in this release:

• Replace Glassfish dependency with jackson when building project to avoid unanticipated issues with Eclipselink annotation processors.
• Backport ReplicantEntityChangeListener from downstream applications.

v6.153

Changes in this release:

• Introduce ReplicantSessionContext on the serverside that abstract the application capabilities required to implement the SessionManager.
• Convert the ReplicantSessionManagerImpl into a concrete class that uses the newly introduced ReplicantSessionContext so that downstream applications do not need to extend it.
• Convert the ReplicantMessageBrokerImpl into a concrete class so that downstream applications do not need to extend it.
• Backport ReplicantChangeRecorder from downstream applications.
• Begin refactoring ChannelLink so that it can carry the filter for the target graph that is linked to.
• Update ReplicantSessionContext.propagateSubscriptionFilterUpdate() to start using the new ChannelLink capabilities.

v6.152

Changes in this release:

• Migrate server code from the org.realityforge.replicant.server package to the replicant.server package.
• Rename SystemMetaData to SchemaMetaData and all supported infrastructure to use the new name (i.e. systemId becomes schemaId). This is to achieve consistency between the client and server as well as domgen generated code and hand-crafted code.
• Rename ChannelAddress.id to ChannelAddress.rootId on the client and rename ChannelAddress.subChannelId to ChannelAddress.rootId on the server. This is done to gain consistency across client, server, and generated code.
• Start to use records in the server code to reduce verbosity.
• Pass JsonValue as the response object rather than converting JsonValue to a string and then deserializing back into a JsonValue in server code.
• Change ChannelMetaData to use more explicit mechanisms for decoding strings into JsonValue objects in java Object rather than reliance on implicit jackson presence.