cannot render resource resourceWrapper ERROR during Form Submission

Thanks.

I have actually found out the exact issue with our forms post AEM 6.2 upgrade.

We have a custom form action developed on the same lines as "Create and Update Account" OOTB form action (/libs/foundation/components/account/actions/update) which uses 

com.day.cq.security.AccountManagerFactory for creation of new accounts.

Looks like we are not able to get a reference to this service any more due to which the class throws null pointer exception.

final AccountManagerFactory af = sling.getService(AccountManagerFactory.class);

I have tested the OOTB "Create and Update Account" form action and it has the same issue.

I saw this in the post.POST.jsp of this form action:

"This action is deprecated and should not be used anymore."

Just wanted to check with you if there's any way we can still make it work without having to change the implementation as these are on existing pages.

We are working on a new article that uses out of the box form components for users that are not using Adaptive forms and want to handle submit data.  

The best solution - and one where you will not encounter errors is to build a custom form action and then map that custom form action to a custom AEM service built as an OSGi service. When a user fills out the AEM form built with AEM form components - you can get the data to an OSGi service. Then you can build your service to process the submitted data to meet your business requirements. FOr example, store the data in a database, email it, etc. 

This solution does not requite you to modify any existing form JSP files or other overlays. 

http://scottsdigitalcommunity.blogspot.ca/2017/04/creating-custom-action-for-adobe.html

Hi,Did any one find a solution to this issue.We are facing the same after upgrade to AEM 6.2.The forms are on existing pages and so transitioning from OOTB form component to adaptive forms would not be easy.

Hey,

Did you ever find an answer on this one? I have the same problem 

Greetings

Roy

@smacdonald2008 We are not using adaptive form and the project is already live. So it would be very cumbersome to change the whole implementation now. Is there any other way we could solve this problem without using adaptive form.

Thanks  in advance.