to minimaze our portlets we put all jsf jars (jsf-ibm, jsf-impl-messages, jsf-portletbridge, odc-jsf, odc-jsf-portlet) in shared library.
After that our portlets works fine, except we have problem with tabbed panel and section panel (many section panels are inside one or more tabs).
After postback all opened section closes and first tab allways become active (no matter which tab is currently active).
This never happend when we pack all JWL jars into WEB-INF/lib directory.
We use WebSphere Portal 6.1 and JWL version is 3.1.14.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
1 reply Latest Post - 2012-12-27T06:35:43Z by SystemAdmin
Pinned topic Problem with shared JSF libraries
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-12-27T06:35:43Z at 2012-12-27T06:35:43Z by SystemAdmin
SystemAdmin 110000D4XK6420 PostsACCEPTED ANSWER
Re: Problem with shared JSF libraries2012-12-27T06:35:43Z in response to svarturHello,
while I cannot speak for WS, the tendency is towards creating complete web applications instead of web applications depending on shared resources. Tomcat 6 documentation states explicitly about the shared library directory that "Normally, application classes should NOT be placed here".
I believe the drive towards not using shared jars comes from the Servlet spec and therefore it is not a "Tomcat thing" but should apply to WS as well. Hence, placing jars to WEB-INF/lib directory both solves your problem and is also the right thing to do.