[
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...
Filters not registered when applications start up
-------------------------------------------------
Key: JBAS-8521
URL:
https://jira.jboss.org/browse/JBAS-8521
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Java EE APIs
Affects Versions: 6.0.0.M5
Environment: JBoss AS M5 - Ubuntu 10.10
Reporter: Lincoln Baxter III
Assignee: Shelly McGowan
Attachments: prettyfaces-test.tar
It seems like custom filters are not being booted when JBoss starts applications - place
a breakpoint in PrettyFilter.init(ServletContext context) and it will never fire. Nor is
the filter ever invoked on web-requests.
The attached application can be used to reproduce this on M5. This works on Glassfish.
--
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