Extending a seeded controller

Question

Hi,
There is a submit button ("Save for Later") that saves any changed data on the application, and then redirects to a different page. Our requirement is to prevent the system from automatically redirecting to the second page.
I have used JAD to decompile the seeded controller, and am planning to use the same (processFormRequest) code in the custom controller, except for the line which redirects to the second page.
However, when I am unable to compile the seeded controller (decompile version):
aserializable[0] = s;
aserializable[1] = "CASE";
Class aclass[] = {java/lang/String, java/lang/String}; <<<< ERROR
String s8 = (String)pageContext.getApplicationModule(webBean).invokeMethod("SubmitForRefresh", aserializable, aclass);
What should be the correct representation for aclass? Apologize for my ignorance of Java.
Thanks,
Ashish

Answer 1

Hi Pratap,
Thanks for your response. Please help me understand the proposed solution.
The standard page has a "Save for Later" button (FndSaveButtonSubmit). Standard functionality is when a user clicks on this button the changes are saved, and automatically re-directed to a different page.
We want to retain the existing functionality, except instead of re-directing to the different page, we want to remain on the same page. The code snippet is:
Serializable aserializable2[] = {
s13, s9
Class aclass2[] = {java/lang/String, java/lang/String};
pageContext.getApplicationModule(webBean).invokeMethod("SaveCaseFolder", aserializable2, aclass2);
HashMap hashmap3 = new HashMap();
hashmap3.put("Status", s13);
hashmap3.put("CaseFolderNumber", (String)row1.getAttribute("CaseFolderNumber"));
pageContext.setForwardURL("ARCMANALYSISSEARCHPAGE", (byte)4, "ARCMMENUAPPLICATION", hashmap3, false, "N", (byte)0);
I don't want the line line in my custom controller. For this, I tried to decompile the standard controller, and comment out the redirect code.
But not sure how to replace: Class aclass2[] = {java/lang/String, java/lang/String};
In the below solution, did you mean that in my custom controller, I should simply re-direct to the current page (no other code/processing)? Also, the standard page has quite a few parameters in it. Is there a way to capture the exact URL and then redirect to the same?
Appreciate your help.
Ashish