Again. I cannot locate the screen that you are referring to:
component://party/widget/partymgr/VisitScreens.xml#FindVisits
Could this be your personal screen definition? It does not exist in ofbiz
branch 9.04 nor the trunk. The one that comes from the branch and trunk has
"only" 2 screens defined:
component://party/widget/partymgr/VisitScreens.xml#showvisits
component://party/widget/partymgr/VisitScreens.xml#visitdetail
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. It is these forms that generate a new GET request
below:
component:/party/webapp/partymgr/WEB-INF/controller.xml, request=pushPage
component:/party/webapp/partymgr/WEB-INF/controller.xml,
request=setAppletFollower
These request results in the below java methods being used:
CommonEvents.setAppletFollower()
CommonEvents.setFollowerPage()
I'm referring to these methods. They are partially implemented and it seems
no one knows 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-tp3903077p3909909.html
Sent from the OFBiz - User mailing list archive at Nabble.com.
