[ https://jira.jboss.org/browse/JBAS-8521?page=com.atlassian.jira.plugin.sy... ] Lincoln Baxter III updated JBAS-8521: ------------------------------------- Attachment: prettyfaces-test.tar test-application -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8521?page=com.atlassian.jira.plugin.sy... ] Shelly McGowan commented on JBAS-8521: -------------------------------------- On jbossas/trunk, there are a few things. Looks like the filter does get initialized: 19:53:57,328 INFO [javax.enterprise.resource.webcontainer.jsf.config] Initializing Mojarra 2.0.3 (SNAPSHOT 20100726) for context '/mateo' 19:53:59,679 INFO [org.jboss.resteasy.cdi.CdiInjectorFactory] Found BeanManager in ServletContext 19:53:59,696 INFO [STDOUT] [mateo] INFO [Thread-2] PrettyFilter.init(278) | PrettyFilter starting up... 19:53:59,727 INFO [STDOUT] [mateo] DEBUG [Thread-2] PackageFilter.<init>(37) | No package filter specified! 19:53:59,755 INFO [STDOUT] [mateo] DEBUG [Thread-2] FacesConfigBeanNameResolver.init(99) | Found 0 bean names in faces configuration. 19:53:59,757 INFO [STDOUT] [mateo] DEBUG [Thread-2] SpringBeanNameResolver.init(65) | WebApplicationContext not found in ServletContext. Resolver has been disabled. 19:53:59,758 INFO [STDOUT] [mateo] DEBUG [Thread-2] SeamBeanNameResolver.init(75) | Seam class has not been found. Seam resolver will be disabled. 19:53:59,764 INFO [STDOUT] [mateo] DEBUG [Thread-2] CDIBeanNameResolver.init(140) | CDI environment detected. Enabling bean name resolving via BeanManager. 19:53:59,796 INFO [STDOUT] [mateo] INFO [Thread-2] PrettyFilter.init(285) | PrettyFilter initialized. Then, fails with this: 19:53:59,877 INFO [org.jboss.ejb3.session.SessionSpecContainer] Starting jboss.j2ee:jar=mateo.war,name=InicializaAplicacion,service=EJB3 19:53:59,879 INFO [org.jboss.ejb3.EJBContainer] STARTED EJB: mx.edu.um.mateo.bootstrap.InicializaAplicacion ejbName: InicializaAplicacion 19:53:59,931 WARN [org.jboss.kernel.plugins.dependency.AbstractKernelController] Broken callback: ClassSingleCallbackItem@178374c9{name=interface org.jboss.ejb3.container.spi.EJBContainer whenRequired=ControllerState@5fb08cf3{Installed} dependentState=ControllerState@5fb08cf3{Installed} attributeName=onInstall owner=AbstractKernelControllerContext@42c31c7d{ metadata=AbstractBeanMetaData@6d4b473{name=StartupSingletonInitiator bean=org.jboss.ejb3.singleton.deployer.StartupSingletonInitiator properties= classLoader=BeanMetaDataDeployer$DeploymentClassLoaderMetaData@780c94eb{classloader=null} constructor=null autowireCandidate=true installCallbacks=[method=onInstall]}name=StartupSingletonInitiator target=org.jboss.ejb3.singleton.deployer.StartupSingletonInitiator@3d98c28c state=Installed depends=AbstractDependencyInfo@2050de0{}} signature=org.jboss.ejb3.container.spi.EJBContainer}: java.lang.RuntimeException: Could not invoke PostConstruct on the newly created bean instance at org.jboss.ejb3.singleton.impl.container.SingletonEJBInstanceManagerImpl.create(SingletonEJBInstanceManagerImpl.java:136) [:1.0.0-alpha-14] at org.jboss.ejb3.singleton.deployer.StartupSingletonInitiator.onInstall(StartupSingletonInitiator.java:67) [:1.0.0-alpha-14] And, also ran into this: http://seamframework.org/Community/JBoss600SNAPSHOTNPEUponDeploymentIfWel... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8521?page=com.atlassian.jira.plugin.sy... ] Lincoln Baxter III commented on JBAS-8521: ------------------------------------------ Silly me. I sent the wrong test application! Unfortunately, I can't say if this is a regression issue or not, because I've never really been able to use a milestone release of JBoss AS successfully with JSF; however, I do believe that this is new in M5, because I've never experienced this specific issue before. Please see the new attached test case that definitely reproduces this Just access: http://localhost:8080/pretty-prime-test/ You should see content from the index page (through PrettyFaces pretty-config.xml) but receive 404 instead. Also, if you view this page it is clear that PrettyFilter is never invoked because the Config, which is normally set on filter boot, is null. http://localhost:8080/pretty-prime-test/faces/index.xhtml This is my successful startup log: 09:01:59,230 INFO [AbstractJBossASServerBase] Server Configuration: JBOSS_HOME URL: file:/home/lb3/Development/jboss6/ Bootstrap: $JBOSS_HOME/server/default/conf/bootstrap.xml Common Base: $JBOSS_HOME/common/ Common Library: $JBOSS_HOME/common/lib/ Server Name: default Server Base: $JBOSS_HOME/server/ Server Library: $JBOSS_HOME/server/default/lib/ Server Config: $JBOSS_HOME/server/default/conf/ Server Home: $JBOSS_HOME/server/default/ Server Data: $JBOSS_HOME/server/default/data/ Server Log: $JBOSS_HOME/server/default/log/ Server Temp: $JBOSS_HOME/server/default/tmp/ 09:01:59,237 INFO [AbstractServer] Starting: JBossAS [6.0.0.20100911-M5 "Neo"] 09:02:02,478 INFO [ServerInfo] Java version: 1.6.0_20,Sun Microsystems Inc. 09:02:02,478 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_20-b02) 09:02:02,478 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 16.3-b01,Sun Microsystems Inc. 09:02:02,478 INFO [ServerInfo] OS-System: Linux 2.6.35-22-generic,i386 09:02:02,479 INFO [ServerInfo] VM arguments: -Dprogram.name=JBossTools: JBoss 6 -Xms256m -Xmx768m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.endorsed.dirs=/home/lb3/Development/jboss6/lib/endorsed -Djava.endorsed.dirs=/home/lb3/Development/jboss6/lib/endorsed -Djava.library.path=/home/lb3/Development/jboss6/bin/native: -Dfile.encoding=UTF-8 09:02:02,549 INFO [JMXKernel] Legacy JMX core initialized 09:02:09,146 INFO [AbstractServerConfig] JBoss Web Services - Stack CXF Server 3.4.0.Beta2 09:02:09,563 INFO [JSFImplManagementDeployer] Initialized 2 JSF configurations: [Mojarra-1.2, Mojarra-2.0] 09:02:12,489 WARNING [FileConfigurationParser] AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal 09:02:15,666 WARNING [FileConfigurationParser] AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal 09:02:15,921 INFO [JMXConnector] starting JMXConnector on host localhost:1090 09:02:16,624 INFO [MailService] Mail Service bound to java:/Mail 09:02:17,524 INFO [HornetQServerImpl] live server is starting.. 09:02:17,638 INFO [JournalStorageManager] Using NIO Journal 09:02:17,668 WARNING [HornetQServerImpl] Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default. Please see the HornetQ user guide, cluster chapter, for instructions on how to do this. 09:02:18,685 INFO [NettyAcceptor] Started Netty Acceptor version 3.2.1.Final-r2319 localhost:5445 for CORE protocol 09:02:18,690 INFO [NettyAcceptor] Started Netty Acceptor version 3.2.1.Final-r2319 localhost:5455 for CORE protocol 09:02:18,694 INFO [HornetQServerImpl] HornetQ Server version 2.1.2.Final (Colmeia, 120) started 09:02:18,771 INFO [WebService] Using RMI server codebase: http://localhost:8083/ 09:02:19,885 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /home/lb3/Development/jboss6/bin/native: 09:02:20,082 INFO [ModClusterService] Initializing mod_cluster 1.1.0.CR3 09:02:20,099 INFO [TomcatDeployment] deploy, ctxPath=/invoker 09:02:20,940 INFO [RARDeployment] Required license terms exist, view vfs:/home/lb3/Development/jboss6/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml 09:02:20,950 INFO [RARDeployment] Required license terms exist, view vfs:/home/lb3/Development/jboss6/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml 09:02:20,957 INFO [RARDeployment] Required license terms exist, view vfs:/home/lb3/Development/jboss6/server/default/deploy/jms-ra.rar/META-INF/ra.xml 09:02:20,971 INFO [HornetQResourceAdapter] HornetQ resource adaptor started 09:02:20,978 INFO [RARDeployment] Required license terms exist, view vfs:/home/lb3/Development/jboss6/server/default/deploy/mail-ra.rar/META-INF/ra.xml 09:02:20,989 INFO [RARDeployment] Required license terms exist, view vfs:/home/lb3/Development/jboss6/server/default/deploy/quartz-ra.rar/META-INF/ra.xml 09:02:21,081 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: Thread-2 09:02:21,143 INFO [SchedulerSignalerImpl] Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl 09:02:21,144 INFO [QuartzScheduler] Quartz Scheduler v.1.8.0 created. 09:02:21,148 INFO [RAMJobStore] RAMJobStore initialized. 09:02:21,151 INFO [QuartzScheduler] Scheduler meta-data: Quartz Scheduler (v1.8.0) 'JBossQuartzScheduler' with instanceId 'NON_CLUSTERED' Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally. NOT STARTED. Currently in standby mode. Number of jobs executed: 0 Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads. Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered. 09:02:21,151 INFO [StdSchedulerFactory] Quartz scheduler 'JBossQuartzScheduler' initialized from an externally opened InputStream. 09:02:21,152 INFO [StdSchedulerFactory] Quartz scheduler version: 1.8.0 09:02:21,152 INFO [QuartzScheduler] Scheduler JBossQuartzScheduler_$_NON_CLUSTERED started. 09:02:21,706 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS' 09:02:22,010 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA' 09:02:22,086 INFO [xnio] XNIO Version 2.1.0.CR2 09:02:22,097 INFO [nio] XNIO NIO Implementation Version 2.1.0.CR2 09:02:22,261 INFO [remoting] JBoss Remoting version 3.1.0.Beta2 09:02:22,385 INFO [TomcatDeployment] deploy, ctxPath=/ 09:02:22,527 INFO [service] Removing bootstrap log handlers 09:02:22,608 INFO [org.apache.coyote.http11.Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080 09:02:22,646 INFO [org.apache.coyote.ajp.AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009 09:02:22,646 INFO [org.jboss.bootstrap.impl.base.server.AbstractServer] JBossAS [6.0.0.20100911-M5 "Neo"] Started in 23s:382ms 09:02:30,258 INFO [org.jboss.weld.Version] WELD-000900 1.1.0 (Beta1) 09:02:31,257 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] deploy, ctxPath=/pretty-prime-test 09:02:31,300 INFO [org.apache.catalina.core.StandardContext] The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored. 09:02:31,455 INFO [javax.enterprise.resource.webcontainer.jsf.config] Initializing Mojarra 2.0.4 (SNAPSHOT 20100826) for context '/pretty-prime-test' 09:02:33,718 INFO [javax.enterprise.resource.webcontainer.jsf.config] Monitoring jndi:/localhost/pretty-prime-test/WEB-INF/faces-config.xml for modifications 09:02:33,769 INFO [org.jboss.resteasy.cdi.CdiInjectorFactory] Found BeanManager at java:comp/BeanManager -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8521?page=com.atlassian.jira.plugin.sy... ] Lincoln Baxter III commented on JBAS-8521: ------------------------------------------ PS- This is tested on the M5 release, not on trunk. So if it works for you there, excellent, but it does not with what people are trying out right now (I have been getting messages on my user forums.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8521?page=com.atlassian.jira.plugin.sy... ] Shelly McGowan commented on JBAS-8521: -------------------------------------- I noted that this was filed against M5 but thought I'd try on the latest to see where we're at. One thing I did note from your logs is: 09:02:31,455 INFO [javax.enterprise.resource.webcontainer.jsf.config] Initializing Mojarra 2.0.4 (SNAPSHOT 20100826) for context '/pretty-prime-test' 6.0.0.M5 had Mojarra 2.0.2-FCS 19:53:57,328 INFO [javax.enterprise.resource.webcontainer.jsf.config] Initializing Mojarra 2.0.3 (SNAPSHOT 20100726) for context '/mateo' Stan will look into this further. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8521?page=com.atlassian.jira.plugin.sy... ] Lincoln Baxter III commented on JBAS-8521: ------------------------------------------ Not sure why your web context root is different, but I verified the results on trunk as well and see everything working. Thanks Stan. This looks like it's fixed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8521?page=com.atlassian.jira.plugin.sy... ] susnet commented on JBAS-8521: ------------------------------ It is the same problem with tuckey.org urlrewritefilter on JBoss 6 M5. But it works if you have a web app without CDI/JSF2. When I run a simple servlet web app it works fine. So there must be some problem regarding CDI/JSF2 in combination with filter loading that causes this problem. It is really good if you have already fixed this. I guess I now only have to wait until 15th november when JBoss 6.0.0 CR1 is planned to be released or is there some nightly builds I can download in the meantime? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira