Is it possible to have a Java Callout that directly references a jar at the org or env level?

Google Cloud Apigee
1

I have a Java jar (apigee-logger.jar) which I would like to reference in many different proxies. In trying to avoid uploading it to each of the proxies, I have uploaded it to the Organization/Environment (I have tried both levels). I get the following error when attempting to save:

messaging.config.beans.InvalidBundle. Errors:[Entity : policy-Logger, Resource Not Found: apigee-logger.jar;].

If I upload the jar to the proxy directly it saves/deploys/runs just fine. The jar does not have any dependencies as at the moment it just sets a variable on the message context.

Is this method of accessing resources not supported or am I missing something?

2

Java callout can be at the org or env level. However, if the JAR is referenced directly by the Java callout policy, the UI won’t let you deploy if the Jar doesn’t exist locally in the proxy.

The workaround is: add the Jar locally. Download the bundle. Delete the JAR and upload the proxy again. It should deploy.

1 Like