Page Push/Following...Push URL...Follow session

[Wai]

Hello All,

This question is related to a previous post of a few years ago.

http://ofbiz.135035.n4.nabble.com/Page-Push-Following-td163975.html

I would like to know what is the purpose of feature "Page Push/Following"..."Push URL"..."Follow session".  The functionality is not used in Ofbiz.  I'm not sure what is the purpose of this functionality.  What kind of problem is it trying to solve and how exactly is it supposed to be used.

Having looked at the code, CommonEvents.java, there is not much in there that answers my question.  I think it is missing some important functionality.

Thanks,
Wai

[BJ Freeman]

this was 9.04 or earlier.(Aug 10, 2009)
The thread refereed to the party visit screen which in found the the
widgets folder
(component://party/widget/partymgr/VisitScreens.xml#FindVisits)

however the rest you refer to ins not in ofbiz.

Wai sent the following on 10/13/2011 2:57 PM:

> Hello All,
>
> This question is related to a previous post of a few years ago.
>
> http://ofbiz.135035.n4.nabble.com/Page-Push-Following-td163975.html
>
> I would like to know what is the purpose of feature "Page
> Push/Following"..."Push URL"..."Follow session".  The functionality is not
> used in Ofbiz.  I'm not sure what is the purpose of this functionality.
> What kind of problem is it trying to solve and how exactly is it supposed to
> be used.
>
> Having looked at the code, CommonEvents.java, there is not much in there
> that answers my question.  I think it is missing some important
> functionality.
>
> Thanks,
> Wai
>
> --
> View this message in context: http://ofbiz.135035.n4.nabble.com/Page-Push-Following-Push-URL-Follow-session-tp3903077p3903077.html
> Sent from the OFBiz - User mailing list archive at Nabble.com.
>

[Wai]

The screen you referred to, component://party/widget/partymgr/VisitScreens.xml#FindVisits, does not exist.
From what I see, 9.04 and the trunk as it relates to "Page Push/Following" functionality have not changed.  It is still partially implemented.

As mentioned, the ofbiz trunk still allows a user to specify input for this functionality.  Even though it doesn't do much.

I would suggest removing the "Page Push/Following" prompts from the UI.  If there's no objections, I'll create an issue in jira to have it removed from the UI.

As a reference, that page is accessed via https://localhost:8443/partymgr/control/visitdetail?visitId=11111.

Thanks

[BJ Freeman]

i took component://party/widget/partymgr/VisitScreens.xml#FindVisits, is
the view source of the URL partymgr/control/visitdetail?visitId=11111
it is the second line.
Page Push/Following is only in a label file as far as I can see. I
searched for the property key PartyPagePushFollowing and could not find
it.  So I guess you asking if you cabn remove PartyPagePushFollowing
from the label file. That would be best ask on the Dev list.
I was confused when you stated it was partially implemented, that means
to me there is some code.

Wai sent the following on 10/15/2011 9:10 PM:

> The screen you referred to,
> component://party/widget/partymgr/VisitScreens.xml#FindVisits, does not
> exist.
>>From what I see, 9.04 and the trunk as it relates to "Page Push/Following"
> functionality have not changed.  It is still partially implemented.
>
> As mentioned, the ofbiz trunk still allows a user to specify input for this
> functionality.  Even though it doesn't do much.
>
> I would suggest removing the "Page Push/Following" prompts from the UI.  If
> there's no objections, I'll create an issue in jira to have it removed from
> the UI.
>
> As a reference, that page is accessed via
> https://localhost:8443/partymgr/control/visitdetail?visitId=11111.
>
> Thanks
>
>
> --
> View this message in context: http://ofbiz.135035.n4.nabble.com/Page-Push-Following-Push-URL-Follow-session-tp3903077p3908795.html
> Sent from the OFBiz - User mailing list archive at Nabble.com.
>

[Wai]

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

[BJ Freeman]

see inline

Wai sent the following on 10/16/2011 9:53 AM:
> 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:
It is in the current demo-trunk but apparently I am not communicating well

>
>     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

This functionality looks like a way to do a crawl. I don't see a need to
remove the uri from the controller. Maybe someone will decided to take
this one and complete it.

Now you have more detail suggest you ask on the dev list.
>
>
>
>
>
> --
> 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.
>

[Wai]

Hello, BJ

component://party/widget/partymgr/VisitScreens.xml#FindVisits  does exist in the trunk.  It was my mistake.  I didn't do a timely update of my checked out version.

I've continued the posting in the dev list.

Thanks