Revision history [back]

click to hide/show revision 1
initial version

answered 2013-03-22 15:42:48 +0800

gganassin gravatar image gganassin flag of Luxembourg

http://www.hybris.com/

There are thousand of ways to achieve this, probably the last recommendable one is a cookie. Assuming that by a security point of view there is no issue or you managed it, app A just need to expose a dedicated servlet or even just a callback.zul file:

<window>
<zscript><![CDATA[
    String id = execution.getParameter("id");
]]></zscript>
<label value="${id}"/>

</window>

so when in app B the user push the "select" button you have just to redirect to callback.zul?id=123. In callback.zul you are back to your app A and with the selected ID you can do what you have to do.

I repeat: the cookie was the last option... this is just a possible (stupid) other way to manage your scenario.

There are thousand thousand of ways to achieve this, probably the last recommendable one is a cookie. A stupid straight forward one? Assuming that by a security point of view there is no issue or you managed it, app A just need to expose a dedicated servlet or even just a callback.zul file:

<window>
<zscript><![CDATA[
    String id = execution.getParameter("id");
]]></zscript>
<label value="${id}"/>

</window>

so when in app B the user push the "select" button you have just to redirect to callback.zul?id=123. In callback.zul you are back to your app A and with the selected ID you can do what you have to do.

I repeat: the cookie was the last option... this is just a possible (stupid) other way to manage your scenario.

There are thousand of ways to achieve this, probably the last recommendable one is a cookie. cookie.

A stupid straight forward one?

Assuming that by a security point of view there is no issue or you managed it, app A just need to expose a dedicated servlet or even just a callback.zul file:

<window>
<zscript><![CDATA[
    String id = execution.getParameter("id");
]]></zscript>
<label value="${id}"/>

</window>

so when in app B the user push the "select" button you have just to redirect to callback.zul?id=123. In callback.zul you are back to your app A and with the selected ID you can do what you have to do.

I repeat: the cookie was the last option... this is just a possible (stupid) other way to manage your scenario.

Support Options
  • Email Support
  • Training
  • Consulting
  • Outsourcing
Learn More