We are attempting to connect to AEM 6.5 from a legacy system that was connected to AEM6.4. After updating the AEM to 6.5 and upgrading the proxy jars we are getting the following error when we try to call the Formservice over SOAP.
Error calling:
formsService.renderPDFForm(templatePath, inputBLOB, pdfFormRenderSpec, uriValues, null,
outRenderPDFFormResultDoc, longHolder, stringHolder, formsResult);
Error:
Caused by: java.lang.NoSuchMethodFoundError: com.adobe.idp.services.forms.FormsService.renderPDFForm(Ljava/lang/String;Lcom/adobe/idp/services/forms/BLOB;Lcom/adobe/idp/services/forms/PDFFormRenderSpec;Lcom/adobe/idp/services/forms/URLSpec;Lorg/apache/xml/xml_soap/Map;Ljavax/xml/ws/Holder;Ljavax/xml/ws/Holder;Ljavax/xml/ws/Holder;Ljavax/xml/ws/Holder;)V
We are running on WebLogic 10.3.6 using java 1.7 and AEM 6.5 is on jboss 7.1.4.GA -redHat
Thanks
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
The issue was with the proxy creation. The adobe documentation are not accurate. When you create the proxies using WS Import the packages got created correctly and resolved the issue.Thanks all for checking.
Please post this query in AEM forms section: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-forms/ct-p/adobe-experienc...
Thanks!!
Please post this query in AEM forms section: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-forms/ct-p/adobe-experienc...
Thanks!!
Hi,
I assume this is AEM Forms JEE 6.5 and you have rebuilt your WL application with the latest adobe client jars and whatever else is given in the SDK section of the 6.5 installation.
The first thing I am not sure about is if Java 1.7 will still work with this, AEM Forms runs under Java 8 or 11 and all jars are compiled for 1.8 and 11.
But what puzzles me is your formsService API call. The 6.4 Javadoc shows the following interface:
Your API call contains much more parameters not documented. The error we see in your post looks consistent if I have not misinterpreted your information.
Views
Replies
Total Likes
The issue was with the proxy creation. The adobe documentation are not accurate. When you create the proxies using WS Import the packages got created correctly and resolved the issue.Thanks all for checking.