This may be a stupidly simple question, but it's often the obvious that eludes us.

Did you add an instance of the portlet to the target page (in your case the demos page) ?

tony ennis wrote:
I installed jetspeed and got the main portal demo page working.

Then I created a portlet using 'mvn archetype:generate', made a .war out of
it with 'mvn package', then copied it to
<jetspeed-2.2.0>/webapps/jetspeed/WEB-INF/deploy.  According to the logs,
the war file was consumed by jetspeed, compiled, and loaded.

When I refresh the portlet demos page, nothing changes.  It is as if I
didn't deploy anything.  Did I miss a step?

localhost.log:
Sep 2, 2009 4:29:29 PM org.apache.catalina.core.ApplicationContext log
INFO: JetspeedContainerServlet: starting initialization of Portlet
Application at: mps5-1.0
Sep 2, 2009 4:29:29 PM org.apache.catalina.core.ApplicationContext log
INFO: JetspeedContainerServlet: Could not yet start portlet application at:
mps5-1.0. Starting back ground thread to start when the portal comes online.
Sep 2, 2009 4:29:29 PM org.apache.catalina.core.ApplicationContext log
INFO: JetspeedContainerServlet: initialization done for Portlet Application
at: mps5-1.0
Sep 2, 2009 4:29:29 PM org.apache.catalina.core.ApplicationContext log
INFO: JetspeedContainerServlet: attemping to start Portlet Application at:
/mps5-1.0
Sep 2, 2009 4:29:29 PM org.apache.catalina.core.ApplicationContext log
INFO: JetspeedContainerServlet: started Portlet Application at: /mps5-1.0

catalina.log:
Sep 2, 2009 4:29:29 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive mps5-1.0.war

I have no idea what to try next. Any ideas?

------------------------------------------------------------------------


No virus found in this incoming message.
Checked by AVG - www.avg.com Version: 8.5.409 / Virus Database: 270.13.75/2341 - Release Date: 09/02/09 05:50:00



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to