◀️ Running Bundles in Container 🔗 Understanding PadoGrid Pods ▶️

The PadoGrid distribution includes addon jar files for the supported data grid products. These jar files are found in the respective product lib directory as follows:

cd $PADOGRID_HOME
tree -L 2 */lib

Output:

geode/lib
└── geode-addon-core-0.9.25.jar
hazelcast/lib
├── hazelcast-addon-common-0.9.25.jar
├── v3
│   ├── hazelcast-addon-core-3-0.9.25.jar
│   └── hazelcast-addon-jet-demo-3-0.9.25.jar
├── v4
│   ├── hazelcast-addon-core-4-0.9.25.jar
│   ├── hazelcast-addon-jet-core-4-0.9.25.jar
│   └── hazelcast-addon-jet-demo-4-0.9.25.jar
└── v5
    └── hazelcast-addon-core-5-0.9.25.jar
kafka/lib
└── kafka-addon-core-0.9.25.jar
mosquitto/lib
└── padogrid-mqtt-0.9.25.jar
redis/lib
└── redisson-addon-core-0.9.25.jar
snappydata/lib
└── snappydata-addon-core-0.9.25.jar

To use the addon jar files in your apps, the following padogrid jar files are required.

cd $PADOGRID_HOME
tree -P padogrid* lib/

Output:

lib/
├── padogrid-common-0.9.25.jar
└── padogrid-tools-0.9.25.jar

❗️ Note that if you are running client apps outside the workspaces and they depend on PadoGrid addon services, then you must explicitly include these jar files in the client's class path. This explicit class path setting is not necessary for the apps running inside the workspaces, however, since PadoGrid automatically includes the addon jar files in their class path.

◀️ Running Bundles in Container 🔗 Understanding PadoGrid Pods ▶️