Dear Janne, I have detected another issue, and I am not quite sure if it has to be with Wicket or LifeRay, as I see no exceptions, but I can see a little detail. I tell you:
I have the following View composition: Page > TabbedPanel > Panel[4] When testing this View in standalone WebPage impl it works perfect, but when testing it as a PortletPage in LifeRay (3.6.1 - requirement), suddenly the View changes to a standard LifeRay View (I guess), outputing the following message: ------------------------------------------------------- Portlet Expired The portlet you requested has expired. Return to home ------------------------------------------------------- This happens when I click on one of the 4 tabs I have in the View (TabbedPane links), and some other links I don't remember right now. Then, clicking to the "Return to home" link (above) it goes back to my Portlet Application Main Page. So, the portlet hasn't really desappeared, it just lost the View when clicked on whatever of the tabbedPane links (tabbedPane). Comparing the tab-links between both implementations I can see the following: WebPage impl > tabbedPane link = http://localhost:8080/nt/ntapplication?wicket:interface=:2:TabsConsulta:tabs:0:link:6:ILinkListener PortletPage impl > tabbedPane link = http://localhost/c/portal/layout?p_l_id=1&p_p_id=NTPortlet_WAR_es.tsystems.nt.web&p_p_action=1&p_p_state=normal&p_p_mode=view&p_p_col_order=w1&p_p_col_pos=2&p_p_col_count=3&_NTPortlet_WAR_es.tsystems.nt.web_wicket:path=107%3ATabsConsulta%3Atabs%3A0%3Alink&_NTPortlet_WAR_es.tsystems.nt.web_wicket:interface=ILinkListener&#p_NTPortlet_WAR_es.tsystems.nt.web If we check the Wicket portion of both links all this fragment ":2:TabsConsulta:tabs:0:link:6:" has desappeared in the PortletPage impl. May be this is because LifeRay Portal does supresses that fragment by some reason when parsing and filtering the outputs generated by my Portlet Application. But I understand that this fragment is unconditional necessary for the Wicket FW to work properly when tabbing... careless we are in a Portlet or not... I tried inserting that fragment at the URL of the Portlet in LifeRay, but didnt work, as "id"s may change... I guess. So, at the end, the TabbedPane links are not working properly in my PortletPage impl. Have any idea to solve it? I can remove the tabbedPane out the PortletPage, and multiply to 4 Views (simulating tabs), but this is not quite smart and does not face the problem directly. Thank you. Regards, M ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
