WSRP portlets

[jean-francois.lamy (Jean-François Lamy)]

The instructions to the WSRP add-on include the following

Widgetset must be deployed to the consumer portal so the user can load the widgetset using the standard /html/VAADIN/widgsetset/ url. The widgetset must include the WSRP add-on and any other add-ons that are used.

Does this not defeat the very purpose of using WSRP? I don’t know as much as I should about portlets, but is this standard practice ? Outside the specific constraints of GWT, does any JavaScript library used by a portlet require being served statically from the portlet container ?

In trusted environments, is there a way to get the producer to provide the widgetset (I guess not, as the method override appears to yield a path relative to the container)

[jean-francois.lamy (Jean-François Lamy)]

Looking at Liferay specifically, given the
FriendlyURLMapper
can we imagine hacking something such that the portlet itself would return references to the widgetset i.e. using something like …/-/VAADIN/ and implementing a hook inside the portlet to locate the widgetset in the war). Or am I barking up the wrong tree entirely ?

[Tom118 (Tom Cat)]

Hi Jean, did you find a solution yet?