Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

where to get the most recent JAR libraries for Java Callout?

Hi there,

For reasons that I cannot challenge (at the moment) we are required to perform AES decryption on Apigee, as such and given the Javascript crypto object is limited we have built a Java Callout which is working as we speak.

However, we had few challenges to get the dependent libraries to be downloaded.

At the moment, the latest message-flow 1.0.0 was obtained successfully from https://repository.apigee.com/repository/public-repo/

But expressions 1.0.0 is not available on the same repository.

The way we manage to get this working was to use expressions from the api-platform-samples-master, but it contains an old version of the binaries which were built for JDK 6.  Which makes us a bit sceptical of getting this compiled code live knowing this is not ideal.

Also after bit more digging we found these JAR files would also reside on the installed environment, however although it is an OPDK installation we don't have permissions to access the filesystem in order to download the JAR files.

What is weird is that message-flow is available on apigee maven repositories but not expressions. What are we missing here? Can someone help please?

 

 

 

 

Solved Solved
0 8 588
2 ACCEPTED SOLUTIONS

Thanks for that

I must have a pre-populated .m2 cache. 

 

Let me raise a bug.  internal ref: b/370985586

View solution in original post

Can you try something for me? 

Can you try removing the specific directory for com.apigee in your .m2 local cache, and then re-try that operation?  I just tried it here and it seems to work fine.  

rm -fr ~/.m2/repository/com/apigee

mvn dependency:get -Dartifact=com.apigee.infra.libraries:expressions:1.0.0 \
   -DremoteRepositories=https://us-maven.pkg.dev/apigee-release/apigee-java-callout-dependencies/

mvn dependency:get -Dartifact=com.apigee.gateway.libraries:message-flow:1.0.0 \
    -DremoteRepositories=https://us-maven.pkg.dev/apigee-release/apigee-java-callout-dependencies/

This worked for me.  I searched around and found this suggestion on Stackoverflow .

I guess it's possible there was something that changed between when I tried this originally and now.  

View solution in original post

8 REPLIES 8