openwebbeans-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gurkan Erdogdu (JIRA)" <j...@apache.org>
Subject [jira] Closed: (OWB-77) exception when running OpenWebBeans + MyFaces apps in tomcat
Date Sun, 11 Oct 2009 14:08:31 GMT

     [ https://issues.apache.org/jira/browse/OWB-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gurkan Erdogdu closed OWB-77.
-----------------------------

    Resolution: Fixed

This is not related to OWB.

> exception when running OpenWebBeans + MyFaces apps in tomcat
> ------------------------------------------------------------
>
>                 Key: OWB-77
>                 URL: https://issues.apache.org/jira/browse/OWB-77
>             Project: OpenWebBeans
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: M1
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>
> This is only for documenting a partly known bug!
> MyFaces has a workaround for a tomcat bug with initialising the default JspFactory.
> This results in the following exception:
> java.lang.IllegalStateException: No Factories configured for this Application. This happens
if the faces-initialization does not work at all - make sure that you properly include all
configuration settings necessary for a basic faces application and that all the necessary
libs are included. Also check the logging output of your web application and your container
for any exceptions!
> If you did that and find nothing, the mistake might be due to the fact that you use some
special web-containers which do not support registering context-listeners via TLD files and
a context listener is not setup in your web.xml.
> A typical config looks like this;
> <listener>
>   <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
> </listener>
> 	javax.faces.FactoryFinder.getFactory(FactoryFinder.java:106)
> 	javax.faces.webapp.FacesServlet.init(FacesServlet.java:105)
> 	org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> 	org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
> 	org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
> 	org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
> 	org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> 	java.lang.Thread.run(Thread.java:619)
> The workaround is to include jasper.jar and jasper-el.jar in the webapp.
> But this is imho really dirty - so anyone knows another trick?
> The war has been built with
> $> mvn -Pjetty clean package and deployed into tomcat via manual upload

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message