Portlet instances could not be created -------------------------------------- Key: JBPORTAL-1232 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1232 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Alpha1, 2.6.Alpha2 Environment: AS 4.0.5 JBoss Portal 2.6Alpha1 and Alpha2 Reporter: Ryszard Kozmik Assigned To: Julien Viet Fix For: 2.6.Beta1 Below is part of AS starting log while deploying JBoss Portal 2.6Alpha2. 01:05:48,173 WARN [InstanceMetaData] The instance PolicyConfiguratorPortletInstance will not be created because the component referenced is outside of the same web app portal.PolicyConfiguratorPortlet 01:05:48,173 WARN [InstanceMetaData] The instance DefaultCMSPortletInstance will not be created because the component referenced is outside of the same web app portal.CMSPortlet 01:05:48,173 WARN [InstanceMetaData] The instance CMSAdminPortletInstance will not be created because the component referenced is outside of the same web app portal.CMSAdminPortlet 01:05:48,173 WARN [InstanceMetaData] The instance ManagementPortletInstance will not be created because the component referenced is outside of the same web app portal.ManagementPortlet 01:05:48,173 WARN [InstanceMetaData] The instance NavigationPortletInstance will not be created because the component referenced is outside of the same web app portal.NavigationPortlet 01:05:48,173 WARN [InstanceMetaData] The instance UserPortletInstance will not be created because the component referenced is outside of the same web app portal.UserPortlet 01:05:48,173 WARN [InstanceMetaData] The instance RolePortletInstance will not be created because the component referenced is outside of the same web app portal.RolePortlet 01:05:48,173 WARN [InstanceMetaData] The instance CatalogPortletInstance will not be created because the component referenced is outside of the same web app portal.CatalogPortlet 01:05:48,173 WARN [InstanceMetaData] The instance ThemePortletInstance will not be created because the component referenced is outside of the same web app portal.ThemeManager 01:05:48,173 WARN [InstanceMetaData] The instance ThemeSelectorInstance will not be created because the component referenced is outside of the same web app portal.ThemeSelectorPortlet 01:05:48,184 ERROR [PortletAppDeployment] Error when creating instances java.lang.ClassCastException: org.jboss.portal.core.deployment.jboss.PortletAppDeployment$InstanceMetaDataContext at org.jboss.portal.core.deployment.jboss.PortletAppDeployment.buildInstances(PortletAppDeployment.java:244) at org.jboss.portal.core.deployment.jboss.PortletAppDeployment.start(PortletAppDeployment.java:99) at org.jboss.portal.server.deployment.jboss.DeploymentContext.start(DeploymentContext.java:99) at org.jboss.portal.server.deployment.jboss.PortalDeploymentInfoContext.start(PortalDeploymentInfoContext.java:210) at org.jboss.portal.server.deployment.jboss.ServerDeployer.start(ServerDeployer.java:217) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy156.deploy(Lorg.jboss.deployment.DeploymentInfo;)V(Unknown Source) at org.jboss.portal.server.deployment.jboss.ServerDeployer.deploy(ServerDeployer.java:259) at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) All you have to do to achieve such an impressive failure of instances is place in your AS deployment directory an app with some old default-object.xml(in my case it was like that) in WEB-INF directory. I had default-object.xml there by mistake but still whatever I had in my ear I shouldn't be able to cause Portal's portlet instances to fail. After looking into sources I noticed that in line 445 "extends InstanceMetaData" is missing. When I ran AS with this change code moved a bit further but still there are problems: 01:29:41,074 ERROR [PortletAppDeployment] Error when creating instances java.lang.NullPointerException at org.apache.xml.serializer.TreeWalker.dispatachChars(TreeWalker.java:244) at org.apache.xml.serializer.TreeWalker.startNode(TreeWalker.java:414) at org.apache.xml.serializer.TreeWalker.traverse(TreeWalker.java:143) at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:389) at org.jboss.portal.common.util.XML.toString(XML.java:173) at org.jboss.portal.common.util.XML.toString(XML.java:137) at org.jboss.portal.core.deployment.jboss.PortletAppDeployment.buildInstances(PortletAppDeployment.java:252) at org.jboss.portal.core.deployment.jboss.PortletAppDeployment.start(PortletAppDeployment.java:99) at org.jboss.portal.server.deployment.jboss.DeploymentContext.start(DeploymentContext.java:99) at org.jboss.portal.server.deployment.jboss.PortalDeploymentInfoContext.start(PortalDeploymentInfoContext.java:210) at org.jboss.portal.server.deployment.jboss.ServerDeployer.start(ServerDeployer.java:217) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy156.deploy(Lorg.jboss.deployment.DeploymentInfo;)V(Unknown Source) at org.jboss.portal.server.deployment.jboss.ServerDeployer.deploy(ServerDeployer.java:259) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira