Performance issue while connecting with the webservices

I would use CFX - as shown in the article - to consume the 3rd party WSDL. Use CFX to produce the Java proxy classes.

Then use these classes to invoke the WSDL.

Do this:

1 - Use CFX to create the Java proxy classes. Next, get it working inside of Eclipse. That is, add the Java proxy classes to an eclipse project. Write the Java app logic to invoke the WSDL (this is dependant om the WSDL). Its better to use the strongly typed Java proxy API to consume the web service. 

2 - Once you get that working - then you know your Java proxy classes work. Bundle them into a JAR and then add that JAR into an OSGi bundle as shown in the article. 

3 - Deploy the OSGi to AEM. Invoke via a JSP as shown in the article.  

We figured out that it gives an exception while passing the csrf tokens in between multiple modal windows.

To describe it in detail,if we sign-up 'granite.csrf.standalone' loads fine from global.jsp where we have configured it,it will passon to the next popup window,and the one after that has contact information,while saving this contact information it would give following error - Is this an existing error with CSRF that we know of ? or is there something we can change at the site configuration level so as to avoid this error with multiple modal windows - 

09.10.2015 08:21:10.356 *INFO* [10.170.214.77 [1444400470356] POST /services/contactInfo HTTP/1.1] com.adobe.granite.csrf.impl.CSRFFilter isValidRequest: not well formed CSRF token - rejecting

09.10.2015 08:21:10.356 *INFO* [10.170.214.77 [1444400470356] POST /services/Info HTTP/1.1] com.adobe.granite.csrf.impl.CSRFFilter doFilter: the provided CSRF token is invalid

09.10.2015 08:21:10.359 *WARN* [10.170.214.77 [1444400470356] POST /services/Info HTTP/1.1] com.day.cq.wcm.core.impl.components.ComponentCacheImpl No component node found at /services/contactInfo.servlet

09.10.2015 08:21:10.375 *ERROR* [10.170.214.77 [1444400470356] POST /services/Info HTTP/1.1] org.apache.sling.servlets.post.impl.operations.ModifyOperation Exception during response processing.

javax.jcr.RepositoryException: org.apache.sling.api.resource.PersistenceException: Resource at '/404.html' is not modifiable.

        at org.apache.sling.servlets.post.impl.operations.ModifyOperation.doRun(ModifyOperation.java:113)

Yes you are right! That was the initial guess.But this looks something related only the CSRF issue and tokens not getting passed as expected.We have opened a Adobe ticket for this.Thanks for your help so far! :)