Consuming Object Messages

For the connector to process object messages, it requires access to the classes that define the object payloads.

Assuming that your payload classes are in their own projects, and are packaged into their own JAR files, place these JAR files and their dependencies (if any) onto the connector’s CLASSPATH; see Adding External Libraries.

  • We recommend that these JAR files contain only the relevant payload classes to prevent any unexpected behavior.

  • In the JAR files, your class files must be archived in the same directory/classpath as the application that publishes them. For example, if the source application is publishing a message with payload type, MySerializablePayload, defined under classpath com.sample.payload, then when packaging the payload jar for the connector, the MySerializablePayload class must still be accessible under the com.sample.payload classpath.

    Typically, build tools such as Maven or Gradle handle this archival process when they package the JAR files.