I can only guess as to what the problem might be.
If I were you I would try these things:
- set the debug property on the callout to true - you may get a stack trace that way which may help you better understand what is failing.
- if that does not work, explicitly provide all the dependencies as Java resources in your Apigee Edge environment.
Regarding the latter, In some cases when I publish a Java callout, I assume the dependencies, like BouncyCastle or slf4j, are available in Apigee. You can see that in the pom.xml file of that callout , which has this snip in the ant plugin used during the package phase:
<!-- exclude files we can count on. -->
<exclude name="lib/slf4j-api-${slf4j.version}.jar"/>
<exclude name="lib/bc*-jdk15on-*.jar"/>
In the case of this particular callout, the required jars are:
bcutil-jdk15on-1.70.jar
slf4j-api-1.7.14.jar
bcpkix-jdk15on-1.70.jar
bcprov-jdk15on-1.70.jar
Strictly speaking , excluding dependencies like this from the packaging phase is risky. Apigee doesn't make any guarantees that it supplies a set of "common" or "popular" Java JARs for use by callouts. Apigee of course is built on Java and uses many JARs itself, and at least up until now, the JARs Apigee packages for itself could also be used by callouts. But there has been no guarantee.
The Apigee documentation has always said that you must explicitly provide all dependencies for any JARs you use in JavaCallouts. It is possible that Apigee Edge is not "implicitly" providing one or more of those require JARs.
If this is the problem , then the solution is one of these things:
- manually obtain the Bouncy castle jars and slf4j jars
- comment-out those two lines from the pom.xml file, and rebuild the callout jar. This will assemble all the JARs necessary for this callout, and place them into the bundle/apiproxy/resources/java directory.
...and THEN, you must supply those jars as resources in your environment, or (probably less wise) as resources for this particular proxy.
LinkedIn
Twitter
