Re: [Rife-users] RifeFilter Not Found
the web.xml file looks fine to me can you post the command u r using to start jetty? most of the classpath problems i've had with it had to do with not setting the rife.webapp.path parameter. ie. -Drife.webapp.path=... hth cheers, Emmanuel On 10/6/06, Jeremy Whitlock [EMAIL PROTECTED] wrote: Hi All, I have ran RIFE before and now that I'm back in the game, I've followed previous RIFE packaging steps for my new app. The web app has the rife jar in the lib directory and the structure is that the same as before (rep, site, templates and elements are in the web-app's classes directory). Below is the stack trace and my web.xml: STACKTRACE - org.apache.maven.lifecycle.LifecycleExecutionException: Failure at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments (DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke (Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode (Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Failure at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty (AbstractJettyMojo.java:422) at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:356) at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:172) at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:167) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:534) ... 16 more Caused by: java.lang.ClassNotFoundException: com.uwyn.rife.servlet.RifeFilter at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at org.codehaus.classworlds.RealmClassLoader.loadClassDirect (RealmClassLoader.java:195) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:274) at org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass (WebAppClassLoader.java:344) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:306) at org.mortbay.util.Loader.loadClass(Loader.java:92) at org.mortbay.util.Loader.loadClass (Loader.java:72) at org.mortbay.jetty.servlet.Holder.doStart(Holder.java:51) at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:64) at org.mortbay.component.AbstractLifeCycle.start (AbstractLifeCycle.java:38) at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:542) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1000) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:365) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:373) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java :38) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:159) at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:118) at
Re: [Rife-users] RifeFilter Not Found
Hey Jeremy, it really looks to me like the RIFE classes simply can't be found. Are you sure that the jars are in the correct directory and that it's accessible? Is it the main RIFE jar (http://rifers.org/download/90/ rife-1.5.1-jdk15.jar - 2.58MB)? When you look at the contents of the jar, do you see the com.uwyn.rife.servlet.RifeFilter class? Best regards, Geert On 06 Oct 2006, at 18:48, Jeremy Whitlock wrote: Hi All, I have ran RIFE before and now that I'm back in the game, I've followed previous RIFE packaging steps for my new app. The web app has the rife jar in the lib directory and the structure is that the same as before (rep, site, templates and elements are in the web- app's classes directory). Below is the stack trace and my web.xml: STACKTRACE -- --- org.apache.maven.lifecycle.LifecycleExecutionException: Failure at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneG oal(DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand leFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment s (DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java: 115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke (Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced (Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode (Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Failure at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty (AbstractJettyMojo.java:422) at org.mortbay.jetty.plugin.AbstractJettyMojo.execute (AbstractJettyMojo.java:356) at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute (AbstractJettyRunMojo.java:172) at org.mortbay.jetty.plugin.Jetty6RunMojo.execute (Jetty6RunMojo.java:167) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:534) ... 16 more Caused by: java.lang.ClassNotFoundException: com.uwyn.rife.servlet.RifeFilter at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at org.codehaus.classworlds.RealmClassLoader.loadClassDirect (RealmClassLoader.java:195) at org.codehaus.classworlds.DefaultClassRealm.loadClass (DefaultClassRealm.java:255) at org.codehaus.classworlds.DefaultClassRealm.loadClass (DefaultClassRealm.java:274) at org.codehaus.classworlds.RealmClassLoader.loadClass (RealmClassLoader.java:214) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass (WebAppClassLoader.java:344) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass (WebAppClassLoader.java:306) at org.mortbay.util.Loader.loadClass(Loader.java:92) at org.mortbay.util.Loader.loadClass (Loader.java:72) at org.mortbay.jetty.servlet.Holder.doStart(Holder.java:51) at org.mortbay.jetty.servlet.FilterHolder.doStart (FilterHolder.java:64) at org.mortbay.component.AbstractLifeCycle.start (AbstractLifeCycle.java:38) at org.mortbay.jetty.servlet.ServletHandler.initialize (ServletHandler.java:542) at org.mortbay.jetty.webapp.WebAppContext.startContext (WebAppContext.java:1000) at org.mortbay.jetty.handler.ContextHandler.doStart (ContextHandler.java:365) at org.mortbay.jetty.webapp.WebAppContext.doStart (WebAppContext.java:373) at org.mortbay.component.AbstractLifeCycle.start (AbstractLifeCycle.java :38) at
Re: [Rife-users] RifeFilter Not Found
Geert, I did download the proper file and the RifeFilter is listed in the contents.Frederic, That appears to be a typo as the contents on disk have no extra space.Emmanuel, I'm using Maven 2 so I'm running mvn jetty6:run. This will build a staging directory and will run Jetty aware of this staging directory. I am not passing the rife.webapp.path. It shouldn't matter since the web app is being found and it is up to the servlet container to load RIFE and to the servlet container, everything is setup properly.Take care,Jeremy On 10/6/06, Geert Bevin [EMAIL PROTECTED] wrote: Hey Jeremy,it really looks to me like the RIFE classes simply can't be found.Are you sure that the jars are in the correct directory and that it'saccessible? Is it the main RIFE jar ( http://rifers.org/download/90/rife-1.5.1-jdk15.jar - 2.58MB)? When you look at the contents of thejar, do you see the com.uwyn.rife.servlet.RifeFilter class?Best regards,GeertOn 06 Oct 2006, at 18:48, Jeremy Whitlock wrote: Hi All, I have ran RIFE before and now that I'm back in the game, I've followed previous RIFE packaging steps for my new app.The web app has the rife jar in the lib directory and the structure is that the same as before (rep, site, templates and elements are in the web- app's classes directory).Below is the stack trace and my web.xml: STACKTRACE -- --- org.apache.maven.lifecycle.LifecycleExecutionException: Failure at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java :559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneG oal(DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand leFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment s (DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLifecycleExecutor.java :140) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java: 115) at org.apache.maven.cli.MavenCli.main (MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke (Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced (Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode (Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Failure at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty (AbstractJettyMojo.java :422) at org.mortbay.jetty.plugin.AbstractJettyMojo.execute (AbstractJettyMojo.java:356) at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute (AbstractJettyRunMojo.java:172) at org.mortbay.jetty.plugin.Jetty6RunMojo.execute (Jetty6RunMojo.java:167) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:534) ... 16 more Caused by: java.lang.ClassNotFoundException: com.uwyn.rife.servlet.RifeFilter at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java :188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at org.codehaus.classworlds.RealmClassLoader.loadClassDirect (RealmClassLoader.java:195) at org.codehaus.classworlds.DefaultClassRealm.loadClass (DefaultClassRealm.java:255) at org.codehaus.classworlds.DefaultClassRealm.loadClass (DefaultClassRealm.java:274) at org.codehaus.classworlds.RealmClassLoader.loadClass (RealmClassLoader.java:214) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass (WebAppClassLoader.java:344) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass (WebAppClassLoader.java:306) at org.mortbay.util.Loader.loadClass(Loader.java:92) at org.mortbay.util.Loader.loadClass (Loader.java :72) at org.mortbay.jetty.servlet.Holder.doStart(Holder.java:51) at org.mortbay.jetty.servlet.FilterHolder.doStart (FilterHolder.java:64) at org.mortbay.component.AbstractLifeCycle.start (AbstractLifeCycle.java:38) at org.mortbay.jetty.servlet.ServletHandler.initialize (ServletHandler.java:542) at org.mortbay.jetty.webapp.WebAppContext.startContext ( WebAppContext.java:1000) at org.mortbay.jetty.handler.ContextHandler.doStart (ContextHandler.java:365) at
Re: [Rife-users] RifeFilter Not Found
Geert, I agree but while RIFE is having a problem, HSQLDB is not and I've done this before when developing web apps with Maven. I'll try to verify this myself by taking Maven out of the picture and I will get back to you. Take care,JeremyOn 10/6/06, Geert Bevin [EMAIL PROTECTED] wrote: Hi Jeremy,are you sure that the RIFE jar is copied also to the staging directory? Ireally think that this is a very simple case of the jar not being part ofthe classpath, you just have to eliminate all the possible culprits. Take care,GeertJeremy Whitlock wrote: This will build a staging directory and will run Jetty aware of this staging directory.I am not passing the rife.webapp.path .It shouldn't matter since the web app is being found and it is up to the servlet container to load RIFE and to the servlet container, everything is setup properly.--View this message in context: http://www.nabble.com/RifeFilter-Not-Found-tf2396742.html#a6688309Sent from the RIFE - users mailing list archive at Nabble.com.___Rife-users mailing listRife-users@uwyn.com http://lists.uwyn.com/mailman/listinfo/rife-users ___ Rife-users mailing list Rife-users@uwyn.com http://lists.uwyn.com/mailman/listinfo/rife-users
Re: [Rife-users] RifeFilter Not Found
Hi All, I found the problem and it wasn't RIFE, Maven or Jetty's fault. I install the rife jar into my Maven repository wrongly...Take care,JeremyP.S. - What do you expect when it is 2:00 a.m.. .On 10/6/06, Geert Bevin [EMAIL PROTECTED] wrote: Hi Jeremy,are you sure that the RIFE jar is copied also to the staging directory? Ireally think that this is a very simple case of the jar not being part ofthe classpath, you just have to eliminate all the possible culprits. Take care,GeertJeremy Whitlock wrote: This will build a staging directory and will run Jetty aware of this staging directory.I am not passing the rife.webapp.path .It shouldn't matter since the web app is being found and it is up to the servlet container to load RIFE and to the servlet container, everything is setup properly.--View this message in context: http://www.nabble.com/RifeFilter-Not-Found-tf2396742.html#a6688309Sent from the RIFE - users mailing list archive at Nabble.com.___Rife-users mailing listRife-users@uwyn.com http://lists.uwyn.com/mailman/listinfo/rife-users ___ Rife-users mailing list Rife-users@uwyn.com http://lists.uwyn.com/mailman/listinfo/rife-users