On 1/13/06, Garner, Shawn <[EMAIL PROTECTED]> wrote: > > Which TLD inside with JAR? Sometimes JRun can be quirky with jars being in > which lib directory, especially when I deploy directory for development > instead of a war. > > I'd be inclined to bug them if I know which J2EE 1.3 functionality to tell > them directly isn't working?
If you're using MyFaces 1.1.1, for example, you can do a "jar tvf" on the myfaces-all.jar file and see the four TLD files in the META-INF directory. One of those has a <listener> element to registers the listener that configures MyFaces. Craig Maybe I'll try to run an updater on JRun. They might have added that > support after the original version was released. > > > Shawn > > -----Original Message----- > From: [EMAIL PROTECTED] > To: Struts Users Mailing List > Sent: 1/13/2006 12:38 AM > Subject: Re: [shale] starting server errors > > On 1/12/06, Garner, Shawn <[EMAIL PROTECTED]> wrote: > > > > Googled and couldn't find anything and not sure what to try and still > have > > this error: > > > > 01/12 16:16:18 error Error loading class for Filter shale: Filter is > > disabled. > > java.lang.IllegalStateException: No Factories configured for this > > Application - typically this is because a context listener is not > setup in > > your web.xml. > > A typical config looks like this; > > <listener> > > > > > <listener-class>org.apache.myfaces.webapp.StartupServletContextListener > > </lis > > tener-class> > > </listener> > > > > at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:84) > > > > Any help? > > > Sounds like JRun is not obeying the spec requirements about recognizing > a > <listener> element inside a TLD that is inside a JAR file. Both the JSF > RI > and MyFaces implementations rely on this to implicitly register their > servlet context listener implementations that do the configuration step. > > Temporary workaround is to declare the appropriate listener class in > your > web.xml. > > Permanent solution is to bug the JRun guys to obey the specs. > > Craig > > > **************************************************************************** > This email may contain confidential material. > If you were not an intended recipient, > Please notify the sender and delete all copies. > We may monitor email to and from our network. > > **************************************************************************** >
