I think you have jetspeed-api or jetspeed-common in your portlet
application WEB-INF/lib
portlet application will use these libraries from shared lib
Vivek
brunp wrote:
The issue that is preventing my Portlets from starting seems to be related to
this function in JetspeedContainerServlet:
private boolean attemptStart(ServletContext context, String contextName,
String contextPath, String paDir, ClassLoader paClassLoader)
{
try
{
context.log(TRY_START_MSG + contextPath);
PortletServices services =
JetspeedPortletServices.getSingleton();
if (services != null)
{
PortletApplicationManagement pam =
(PortletApplicationManagement)services.getService("PAM");
if (pam != null && pam.isStarted())
{
DirectoryHelper paDirHelper = new DirectoryHelper(new
File(paDir));
pam.startPortletApplication(contextName, contextPath,
paDirHelper, paClassLoader);
started = true;
psm =
(PortalSessionsManager)services.getService(PortalSessionsManager.SERVICE_NAME);
context.log(STARTED_MSG + contextPath);
return true;
}
}
}
catch (Exception e)
{
context.log(INIT_FAILED_MSG + contextPath, e);
return true; // don't try again
}
return false;
}
I get the TRY_START_MSG message, but the call to get the "Services"
singleton must is "Null" or the
PortletApplicationManagement is getting "null". Is there an easy way to
trace this down?
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
