Following a previous posting and another in 2009 about Page Push/Following.
http://ofbiz.135035.n4.nabble.com/Page-Push-Following-Push-URL-Follow-session-td3903077.html http://ofbiz.135035.n4.nabble.com/Page-Push-Following-td163975.html The page in question can be found at https://demo-trunk.ofbiz.apache.org/partymgr/control/visitdetail?visitId=15869. Focusing on component://party/widget/partymgr/VisitScreens.xml#visitdetail, this screen uses, component://party/webapp/partymgr/visit/visitdetail.ftl, which in turn declares 2 <form> tags. These forms generate a GET request to the controller: component:/party/webapp/partymgr/WEB-INF/controller.xml, request=pushPage component:/party/webapp/partymgr/WEB-INF/controller.xml, request=setAppletFollower These requests result in the below java methods being used: CommonEvents.setAppletFollower() CommonEvents.setFollowerPage() They are partially implemented and it seems that no one could comment on how they are supposed to be used and what issue they are there to solve. My proposal would be to remove the 2 <form> tags defined in component://party/webapp/partymgr/visit/visitdetail.ftl, that prompt the user to give input for this functionality which end up doing not much. One can keep the code in CommonEvents.java for posterity, but just remove the UI related portion that deals with it. This would reduce the confusion that led to this posting and that of 2009. Thanks -- View this message in context: http://ofbiz.135035.n4.nabble.com/Page-Push-Following-Push-URL-Follow-session-tp3910177p3910177.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
