limitations of java code in a Java Callout policy in Apigee

[kairuppala_pras]

Hi,

I have successfully tried Java callout policy having simple Java codes .

Now i am trying to incorporate a complex java code like - which calls a different URL and fetches the data,

but I am getting flow execution error.

I am not able to use a service callout policy as the backend url has a different authentication mechanism.

Any limitations on the complexity of the code that can be incorporated in the Java callout policy?

Thanks in advance!

K.Prashanthi.

UPDATE to this above query: To enable the NTLM authentication to Microsoft SharePoint from APIGEE On-Prem, we are trying this Java Callout Policy. In this Java code we are using Apache HTTPClient Libraries as jars(totally 7 jars).

Inside the Java code, we are calling the on-prem API Proxy of the SharePoint Backend Service. In this case, API Proxy which has this Java Callout and the API Proxy we are calling inside the Java Code are same.

Please provide some idea for the betterment. Thanks!