Hi Eduard!
It's something custom. We have implemented some solutions (e.g. notifications system) using the feature you mentioned in the past but we always ended up creating new classes to handle the complexity we needed.
Anyway are still experimenting with this one :)
Hi Tirthankar,
You probably need to set up the Object Gateway classpath correctly.
I've just got it working as follows:
- Get the proper .jar files
I've copied them from the jgw container:
docker cp jgw:/jgw/FirstDemo.jar shared/
docker cp jgw:/jgw/gson-2.8.5.jar shared/
docker cp jgw:/jgw/intersystems-gateway-3.1.0.jar shared/
docker cp jgw:/jgw/intersystems-jdbc-3.1.0.jar shared/
docker cp jgw:/jgw/intersystems-utils-3.1.0.jar shared/
You can also generate your .jar files, just make sure it contains all the required dependencies.
- Set up your local Object Gateway:
- IP address:
127.0.0.1 - Port:
4444 - ClassPath:
/shared/FirstDemo.jar:/shared/gson-2.8.5.jar:/shared/intersystems-utils-3.1.0.jar
After that, start your Object Gateway, you should see something like:
Executing O.S. command: java -Xrs -classpath /shared/FirstDemo.jar:/shared/gson-2.8.5.jar:/shared/intersystems-utils-3.1.0.jar:/usr/irissys/dev/java/lib/JDK18/intersystems-gateway-3.1.0.jar:/usr/irissys/dev/java/lib/JDK18/intersystems-jdbc-3.1.0.jar com.intersystems.gateway.JavaGateway 4444 "" "" 127.0.0.1 ""
- Modify some of the PEX components in the production, e.g.
FirstOperation:
- Gateway Host:
localhost - Gateway Port:
4444
That should work.
It simply calls the subscriber endpoint via
$classmethodand passing the message payload as parameter :)It could be improved adding way more types of endpoints such as remote HTTP endpoints (REST), etc.