I have a couple of portlets deployed in a war package. If I deploy the war file
after the application server is started the portlets start and work as
expected. However if I restart the application server I have to redeploy my war
file before the portlets work. There are no errors in the log
Did not touch the deployment order (would not even know how to change that ;-))
It's a Seam / MyFaces application. In the web.xml the initialization for Seam
and MyFaces is done. Nothing special in the portlet.xml and
portlet-instances.xml.
The application does have a dependency on some EJB
In principle I do not need page global conversations. PortletA contains a
couple of links that are invoked on PortletB which runs in a long running
conversation. The side-effect of this is that PortletA creates a new long
running conversation for each click. If I could only cancel or discard
Both PortletA and B render a page that contain command links:
| h:commandLink action=#{controller.showContent}
| #{portal_messages['clickme']}
| /h:commandLink
|
Because of IPC all actions of PortletA and B are invoked on PortletB (the
listening portlet). IPC is
I'm also working on IPC using JSF and experience the same behavior as you
mentioned: the target portlet shows the source view instead of the destination
view. Changing the STATE SAVING to client makes it work in Fire Fox but then
Internet Explorer 7 does not accept the URL anymore... When I
