Timeline for Difference between returning null and ApexPages.currentPage()
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 28, 2015 at 5:05 | comment | added | highfive | Oh God! You'll never know how much helpful this for me!!! | |
| Apr 16, 2013 at 0:24 | vote | accept | ipavlic | ||
| Apr 12, 2013 at 19:16 | history | edited | Mohith Shrivastava | CC BY-SA 3.0 |
added 278 characters in body
|
| Apr 12, 2013 at 19:13 | comment | added | Mohith Shrivastava | Thanks i just verified for both scenario using return null and also using return ApexPages.currentPage().You are Perfect!!!Constructors wont run unless we have setredirect set to true .I will include your points too in answer and modify my answer .Using ApexPages.CurrentPage we will have an option to run the constructor everytime .Thanks again for removing the myth i had on this concept | |
| Apr 12, 2013 at 14:20 | comment | added | Bob Buzzard | Returning the current page won't run the constructors unless the setRedirect flag is set to true though. From the docs "If the postback request indicates a page redirect and the redirect is to a page that uses the same controller and a proper subset of controller extensions of the originating page, a postback request is executed for that page." In this case, the same controller would be in use as its the same page. | |
| Apr 12, 2013 at 10:28 | history | answered | Mohith Shrivastava | CC BY-SA 3.0 |