[
https://issues.jboss.org/browse/WFLY-2594?page=com.atlassian.jira.plugin....
]
Stan Silvert reassigned WFLY-2594:
----------------------------------
Assignee: Farah Juma (was: Stan Silvert)
Farah, can you look at this?
Undeploy of JSF application is throwing SEVERE messages, when there
were deployed more JSF apps
-----------------------------------------------------------------------------------------------
Key: WFLY-2594
URL:
https://issues.jboss.org/browse/WFLY-2594
Project: WildFly
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: JSF
Environment: WildFly Beta2-SNAPSHOT from 2013-12-02
Reporter: Tomas Remes
Assignee: Farah Juma
When you deploy more than one JSF application and then you undeploy one of them,
you'll face following message in server log:
{noformat}
SEVERE [javax.faces] (MSC service thread 1-2) Unable to obtain InjectionProvider from
init time FacesContext. Does this container implement the Mojarra Injection SPI?
SEVERE [javax.faces] (MSC service thread 1-2) Unable to call @PreDestroy annotated
methods because no InjectionProvider can be found. Does this container implement the
Mojarra Injection SPI?
{noformat}
I think
javax.faces.FactoryFinder.FactoryManagerCache.getApplicationFactoryManager(ClassLoader)
shouldn't try to create new instance of FactoryManager in this case. I am not really
sure, what is special initialization case, but it seems to me that this should evaluate to
true in this case (btw Does this
javax.faces.FactoryFinder.FactoryManagerCache.detectSpecialInitializationCase(FacesContext)
ever evaluate as true?).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira