[JBoss Portal] - Re: org.jboss.portal.faces.loader.FacesLoaderServlet Null Po
by dpegram
Thanks Wesley! I overlooked the Ajax4Jsf namespace in the facelet files. Removing them fixed those IllegalArgumentExceptions.
Unfortunately, I'm getting a different one now.
Seems like I've wired something wrong, missing a library, or have the an incompatible version.
Any suggestions are greatly appreciated!
- David
10:24:30,671 ERROR [MyFacesGenericPortlet] Error initializing MyFacesGenericPortlet
java.lang.IllegalArgumentException: Class com.sun.facelets.FaceletPortletViewHandler is no javax.faces.application.ViewHandler
at org.apache.myfaces.config.FacesConfigurator.getApplicationObject(FacesConfigurator.java:665)
at org.apache.myfaces.config.FacesConfigurator.configureApplication(FacesConfigurator.java:602)
at org.apache.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:148)
at org.apache.myfaces.portlet.MyFacesGenericPortlet.initMyFaces(MyFacesGenericPortlet.java:210)
at org.apache.myfaces.portlet.MyFacesGenericPortlet.init(MyFacesGenericPortlet.java:128)
at javax.portlet.GenericPortlet.init(GenericPortlet.java:270)
at org.jboss.portal.faces.loader.FacesPortlet.init(FacesPortlet.java:61)
at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.initPortlet(PortletContainerImpl.java:359)
at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.start(PortletContainerImpl.java:233)
at org.jboss.portal.portlet.impl.container.PortletApplicationContextImpl.startPortletApplication(PortletApplicationContextImpl.java:130)
at org.jboss.portal.portlet.deployment.jboss.PortletAppDeployment.start(PortletAppDeployment.java:150)
at org.jboss.portal.core.deployment.jboss.PortletAppDeployment.start(PortletAppDeployment.java:95)
at org.jboss.portal.server.deployment.jboss.DeploymentContext.start(DeploymentContext.java:99)
at org.jboss.portal.server.deployment.jboss.PortalDeploymentInfoContext.start(PortalDeploymentInfoContext.java:211)
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 sun.reflect.GeneratedMethodAccessor224.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(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 $Proxy227.deploy(Unknown Source)
at org.jboss.portal.server.deployment.jboss.ServerDeployer.deploy(ServerDeployer.java:259)
at org.jboss.portal.server.deployment.WebAppAdapter.deploy(WebAppAdapter.java:53)
at org.jboss.portal.server.deployment.WebAppIntercepter.handleNotification(WebAppIntercepter.java:160)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:153)
at $Proxy233.handleNotification(Unknown Source)
at org.jboss.mx.util.JBossNotificationBroadcasterSupport.handleNotification(JBossNotificationBroadcasterSupport.java:127)
at org.jboss.mx.util.JBossNotificationBroadcasterSupport.sendNotification(JBossNotificationBroadcasterSupport.java:108)
at org.jboss.deployment.SubDeployerSupport.emitNotification(SubDeployerSupport.java:340)
at org.jboss.deployment.SubDeployerSupport.start(SubDeployerSupport.java:308)
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:482)
at sun.reflect.GeneratedMethodAccessor126.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(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.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:93)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
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 $Proxy214.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(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 $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100680#4100680
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100680
18Â years, 5Â months
[Beginners Corner] - Application Specific Log4J configuration
by ejb3workshop
I would like to consolidate all log messages from several nodes into a central database. At first I tried using the JMSAppender, but quickly ran into problems during startup. As the Appender is initiallised pretty early on in the startup sequence the Topic has not yet been created which result in nothing being logged.
Since I am only really interested in the log messages originating from my application I though about packaging log4j together with my application. I tried added the log4j.jar file to the ear and modify the manifest of the EAR as well as the JAR.
In the end I could not get this working either. It seems to me that I would have to implement my own buffered appender to store messages until a connection to the database (or the topic) is available. This feels a bit like re-inventing the wheel. Please let me know if there is a better (more generic) solution.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100679#4100679
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100679
18Â years, 5Â months
[Installation, Configuration & DEPLOYMENT] - Application Specific Log4J configuration
by ejb3workshop
I would like to consolidate all log messages from several nodes into a central database. At first I tried using the JMSAppender, but quickly ran into problems during startup. As the Appender is initiallised pretty early on in the startup sequence the Topic has not yet been created which result in nothing being logged.
Since I am only really interested in the log messages originating from my application I though about packaging log4j together with my application. I tried added the log4j.jar file to the ear and modify the manifest of the EAR as well as the JAR.
In the end I could not get this working either. It seems to me that I would have to implement my own buffered appender to store messages until a connection to the database (or the topic) is available. This feels a bit like re-inventing the wheel. Please let me know if there is a better (more generic) solution.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100677#4100677
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100677
18Â years, 5Â months
[Clustering/JBoss] - Clustered Logging using Log4J
by ejb3workshop
I would like to consolidate all log messages from several nodes into a central database. At first I tried using the JMSAppender, but quickly ran into problems during startup. As the Appender is initiallised pretty early on in the startup sequence the Topic has not yet been created which result in nothing being logged.
Since I am only really interested in the log messages originating from my application I though about packaging log4j together with my application. I tried added the log4j.jar file to the ear and modify the manifest of the EAR as well as the JAR.
In the end I could not get this working either. It seems to me that I would have to implement my own buffered appender to store messages until a connection to the database (or the topic) is available. This feels a bit like re-inventing the wheel. Please let me know if there is a better (more generic) solution.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100675#4100675
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100675
18Â years, 5Â months