Foros de discusión

What is a "portlet bag"?

thumbnail
Rune Hellem, modificado hace 15 años.

What is a "portlet bag"?

New Member Mensajes: 5 Fecha de incorporación: 28/01/09 Mensajes recientes
I've created a portlet application which I have been testing on Liferay for a while now. Earlier this week I did some updates of my application, added some methods in the abstract portlet class, added a config-param in web.xml and some minor changes in the actual portlets. Because of this I now get the following errors when trying to deploy my portlet app:


[http-8080-4] () ERROR com.liferay.portlet.PortletContextFactory - Portlet IntellisearchPortlet_WAR_intellisearch has a null portlet bag
[http-8080-4] () ERROR com.liferay.portlet.PortletContextFactory - Portlet IntellisearchPortlet_WAR_intellisearch has a null portlet bag
[http-8080-4] () ERROR portal-web.docroot.html.portal.status.jsp - org.apache.jasper.JasperException: java.lang.NullPointerException
org.apache.jasper.JasperException: java.lang.NullPointerException


It runs perfectly well on WebSphere Portal, so the erorr is not that obvious to me...but for at starter it would have helped a lot if I could have figured out what a "portlet bag" is...desperatly tried various searches without much success.

R.
thumbnail
Amos Fong, modificado hace 15 años.

RE: What is a "portlet bag"?

Liferay Legend Mensajes: 2047 Fecha de incorporación: 7/10/08 Mensajes recientes
Hey Rune,

A portlet bag is a collection of information on that portlet including name, portlet instance, listeners, etc.

See the portletbag.java class.
thumbnail
Rune Hellem, modificado hace 14 años.

RE: What is a "portlet bag"?

New Member Mensajes: 5 Fecha de incorporación: 28/01/09 Mensajes recientes
As easy as it was hard. I came across this posting related to "SEVERE: Error listenerStart"-message I found in the log. By installing the Tomcat Plugin to Eclipse I was all of a sudden able to view the detailed message

SEVERE: Exception sending context initialized event to listener instance of class com.liferay.portal.kernel.servlet.PortletContextListener
java.lang.NoClassDefFoundError: com.ibm.portal.um.Principal


so...very easy when I got hold of the needed information. Maybe I could have tweaked some logging properties. Anyhow, the tomcat plugin helped me out.

R.
thumbnail
Ranga Rao Bobbili, modificado hace 10 años.

RE: What is a "portlet bag"?

Regular Member Mensajes: 152 Fecha de incorporación: 20/07/07 Mensajes recientes
Rune Hellem:
I've created a portlet application which I have been testing on Liferay for a while now. Earlier this week I did some updates of my application, added some methods in the abstract portlet class, added a config-param in web.xml and some minor changes in the actual portlets. Because of this I now get the following errors when trying to deploy my portlet app:


[http-8080-4] () ERROR com.liferay.portlet.PortletContextFactory - Portlet IntellisearchPortlet_WAR_intellisearch has a null portlet bag
[http-8080-4] () ERROR com.liferay.portlet.PortletContextFactory - Portlet IntellisearchPortlet_WAR_intellisearch has a null portlet bag
[http-8080-4] () ERROR portal-web.docroot.html.portal.status.jsp - org.apache.jasper.JasperException: java.lang.NullPointerException
org.apache.jasper.JasperException: java.lang.NullPointerException


It runs perfectly well on WebSphere Portal, so the erorr is not that obvious to me...but for at starter it would have helped a lot if I could have figured out what a "portlet bag" is...desperatly tried various searches without much success.

R.


I also faced above issue so many times due to wrong ordered elements in liferay-portlet.xml or portlet.xml. Most of the times above error is because of schema validation errors in these two files

Thanks,
Ranga Rao
Kat Polyz, modificado hace 8 años.

RE: What is a "portlet bag"?

New Member Mensaje: 1 Fecha de incorporación: 18/09/15 Mensajes recientes
Same as Ranga, i had a "null portlet bag" exception because the ordering was wrong in liferay-portlet.xml .
I used Eclipse and had Validations in Preferences tab disabled so i couldn't see the xml errors before the Server was deployed.