Hello Chris,
To make better decision about how to include js, the Portlet Bridge try to
use MARKUP_HEAD_ELEMENT_SUPPORT if the portlet container supported it.
See PortletPageResponseRendererImpl for more details
Liferay support the optionnal MARKUP_HEAD_ELEMENT so tapestry is able to
add a js
I've never understood why you would want portlets in a tapestry app. Apart
from maybe integrating with legacy code.
What can a portlet give you that a tapestry component can not?
Hi Francois,
As I wrote option 1 isn't too bad - The thing that worries me about that
approach is the page specific initialization (pageinit.js) that is
triggered N times instead of 1, with different parameters. - Will that
always end up like expected and can we do anything to ensure that it
Hi,
I've been trying to get the tapestry5-portlet bridge up and running with
the newest T5.4 previews, just to learn a little about the technologies.
Basically each portlet corresponds to a page, so I see a lot of duplicate
javascript in the portal pages (a set of scripts per portlet).
The
