Re: Does Tapestry and Tomcat work together?
Hi George Christman, yes, i have followed the tapestry quickstart getting started guide, but it does not work. I tried to run it from maven over 'mvn jetty:run' and also from netbeans, but the it run the selenium test and the selenium test goes wrong. At the time I tried it, there was no Tapestry 5.4-beta 9 option. Thanks for the information Regards Jeremias On Fri 06 Jun 2014 10:20:59 PM CEST, George Christman wrote: > Have you considered trying the Tapestry quickstart project? I haven't used > eclipse in a while, but I think you could just create a new maven project > in eclipse and use the following criteria. > > > groupId - org.apache.tapestry > artifactId - quickstart > version - 5.4-beta-9 > repository - https://repository.apache.org/content/groups/staging/ > > > > On Fri, Jun 6, 2014 at 11:42 AM, jeremias.epp...@web.de < > jeremias.epp...@web.de> wrote: > >> Hi Daniel, >> >> thanks for the nice comment! >> >> After all the trouble tapestry works :-). >> Only in combination with Eclipse, but this is not really a problem. I >> have used eclipse before. >> >> You ask about how i can put all the jars in one war file. >> For that i have used a stackoverflow response ( >> http://stackoverflow.com/questions/17868232/how-to-use-tomcat-8-in-eclipse >> ). If you now add some libraries to your "dynamic web page" project. >> Eclipse show you a hint, that the library is not in the classpath, if >> you do an right click you get a window with two options. Select the >> second option add jar to buildpath, it is called something like that. >> After that you can export your project as war archive or start tomcat >> and every library, you added before to the build path, is in your war >> archive. >> >> Maven is nice and I would use it in the future, it sounds really cool a >> package management system for java. >> >> Don't worry, my written and spoken English is bad, but reading English >> isn't that hard. >> >> Regards >> Jeremias >> >> On Fri 06 Jun 2014 03:23:29 PM CEST, Daniel Jue wrote: >>> Hi Jeremias, >>> >>> I'm sorry about the difficulties you're having. It seems to me the real >>> issue is dependency resolution, and then making sure those dependencies >> get >>> seen by Tomcat. Neither of those are a Tapestry problem -- it's just a >>> task inherent in all Maven or Gradle based projects. Tapestry, along >> with >>> thousands of other libraries, is meant to be used with dependency >>> resolution tools like Maven or Gradle or Ant+Ivy. You essentially MUST >> use >>> Maven or Gradle to avoid the pain of downloading all those jars manually. >>> >>> I'm also sorry that you felt you needed to switch your IDE to Eclipse. I >>> love Eclipse, but I didn't mean to say you couldn't use your favorite >> IDE! >>> All the popular IDEs have some level of Maven support, and even if it >> did >>> not, there is always the command line. Maven (or Gradle) is the key to >>> making Tapestry projects work. If Eclipse makes you uncomfortable, you >>> should be able to use the IDE of your choice. Do you have Maven >> installed? >>> >>> Don't get too frustrated over this, please have faith that plenty of us >> are >>> using Tapestry with Tomcat--I've been doing so for over 8 years now. >>> Please know that it was a challenge for me as well--My first Tapestry >>> project was the first experience with Maven, and I had to learn a little >>> bit of Maven to get started. I was overwhelmed on that first day (some 8 >>> years ago) but I bit the bullet and learned a little about how and why >>> Maven works. Let me tell you--it's a great thing to grow into a Maven >>> expert over time--I use it in all my projects, now that I've paid my dues >>> and I can wield it with some power. :-) Gradle is great too, and is >>> often recognized as the successor to Maven. However Maven is still very >>> widely used and supported. >>> >>> What it comes down to is A depends on B, B depends on C, C depends on D >> and >>> E, etc. For Maven, in your pom you just specify that you need A, and >> Maven >>> will seek out appropriate versions of B, C,D,E, etc. >>> >>> In addition to the Jars Tapestry needs for a web application, it is my >>> experience that there are almost the same number of jars that are used >> for >>> the testing phase! So not all the jars Maven uses end up in your .war >> file. >>> >>> By the way, are you packaging your application into a war file? If so, >> how? >>> >>> If you use Maven or Gradle to also build your war file (recommended), >> Maven >>> will stick the jars you need in the appropriate place in the war file, >> and >>> then Tomcat will get everything it needs in the war file. Just make sure >>> that something you include doesn't also include a *servlet*.jar, because >>> that will cause Tomcat to not load your app. (That's where my first >> email >>> applies, using the tag in your Maven pom to remove conflicting >>> jars) >>> >>> >>> Sometimes problems like this come about because you
Re: Does Tapestry and Tomcat work together?
Have you considered trying the Tapestry quickstart project? I haven't used eclipse in a while, but I think you could just create a new maven project in eclipse and use the following criteria. groupId - org.apache.tapestry artifactId - quickstart version - 5.4-beta-9 repository - https://repository.apache.org/content/groups/staging/ On Fri, Jun 6, 2014 at 11:42 AM, jeremias.epp...@web.de < jeremias.epp...@web.de> wrote: > Hi Daniel, > > thanks for the nice comment! > > After all the trouble tapestry works :-). > Only in combination with Eclipse, but this is not really a problem. I > have used eclipse before. > > You ask about how i can put all the jars in one war file. > For that i have used a stackoverflow response ( > http://stackoverflow.com/questions/17868232/how-to-use-tomcat-8-in-eclipse > ). If you now add some libraries to your "dynamic web page" project. > Eclipse show you a hint, that the library is not in the classpath, if > you do an right click you get a window with two options. Select the > second option add jar to buildpath, it is called something like that. > After that you can export your project as war archive or start tomcat > and every library, you added before to the build path, is in your war > archive. > > Maven is nice and I would use it in the future, it sounds really cool a > package management system for java. > > Don't worry, my written and spoken English is bad, but reading English > isn't that hard. > > Regards > Jeremias > > On Fri 06 Jun 2014 03:23:29 PM CEST, Daniel Jue wrote: > > Hi Jeremias, > > > > I'm sorry about the difficulties you're having. It seems to me the real > > issue is dependency resolution, and then making sure those dependencies > get > > seen by Tomcat. Neither of those are a Tapestry problem -- it's just a > > task inherent in all Maven or Gradle based projects. Tapestry, along > with > > thousands of other libraries, is meant to be used with dependency > > resolution tools like Maven or Gradle or Ant+Ivy. You essentially MUST > use > > Maven or Gradle to avoid the pain of downloading all those jars manually. > > > > I'm also sorry that you felt you needed to switch your IDE to Eclipse. I > > love Eclipse, but I didn't mean to say you couldn't use your favorite > IDE! > > All the popular IDEs have some level of Maven support, and even if it > did > > not, there is always the command line. Maven (or Gradle) is the key to > > making Tapestry projects work. If Eclipse makes you uncomfortable, you > > should be able to use the IDE of your choice. Do you have Maven > installed? > > > > Don't get too frustrated over this, please have faith that plenty of us > are > > using Tapestry with Tomcat--I've been doing so for over 8 years now. > > Please know that it was a challenge for me as well--My first Tapestry > > project was the first experience with Maven, and I had to learn a little > > bit of Maven to get started. I was overwhelmed on that first day (some 8 > > years ago) but I bit the bullet and learned a little about how and why > > Maven works. Let me tell you--it's a great thing to grow into a Maven > > expert over time--I use it in all my projects, now that I've paid my dues > > and I can wield it with some power. :-) Gradle is great too, and is > > often recognized as the successor to Maven. However Maven is still very > > widely used and supported. > > > > What it comes down to is A depends on B, B depends on C, C depends on D > and > > E, etc. For Maven, in your pom you just specify that you need A, and > Maven > > will seek out appropriate versions of B, C,D,E, etc. > > > > In addition to the Jars Tapestry needs for a web application, it is my > > experience that there are almost the same number of jars that are used > for > > the testing phase! So not all the jars Maven uses end up in your .war > file. > > > > By the way, are you packaging your application into a war file? If so, > how? > > > > If you use Maven or Gradle to also build your war file (recommended), > Maven > > will stick the jars you need in the appropriate place in the war file, > and > > then Tomcat will get everything it needs in the war file. Just make sure > > that something you include doesn't also include a *servlet*.jar, because > > that will cause Tomcat to not load your app. (That's where my first > email > > applies, using the tag in your Maven pom to remove conflicting > > jars) > > > > > > Sometimes problems like this come about because you are at a point in > life > > where you are able to grow and overcome the obstacles. Once you overcome > > this problem you will gain intuition that will really help later on. > Just > > face it with the right attitude: there is a solution to the problem and > > it's within your abilities to figure it out. :-) > > > > I hope you were able to understand my message here -- I'm trying to use > > terms that would translate easily. > > > > I wish you success. > > > > Dan > > > > > > On Fri, Jun 6
Re: Does Tapestry and Tomcat work together?
Hi Daniel, thanks for the nice comment! After all the trouble tapestry works :-). Only in combination with Eclipse, but this is not really a problem. I have used eclipse before. You ask about how i can put all the jars in one war file. For that i have used a stackoverflow response ( http://stackoverflow.com/questions/17868232/how-to-use-tomcat-8-in-eclipse ). If you now add some libraries to your "dynamic web page" project. Eclipse show you a hint, that the library is not in the classpath, if you do an right click you get a window with two options. Select the second option add jar to buildpath, it is called something like that. After that you can export your project as war archive or start tomcat and every library, you added before to the build path, is in your war archive. Maven is nice and I would use it in the future, it sounds really cool a package management system for java. Don't worry, my written and spoken English is bad, but reading English isn't that hard. Regards Jeremias On Fri 06 Jun 2014 03:23:29 PM CEST, Daniel Jue wrote: > Hi Jeremias, > > I'm sorry about the difficulties you're having. It seems to me the real > issue is dependency resolution, and then making sure those dependencies get > seen by Tomcat. Neither of those are a Tapestry problem -- it's just a > task inherent in all Maven or Gradle based projects. Tapestry, along with > thousands of other libraries, is meant to be used with dependency > resolution tools like Maven or Gradle or Ant+Ivy. You essentially MUST use > Maven or Gradle to avoid the pain of downloading all those jars manually. > > I'm also sorry that you felt you needed to switch your IDE to Eclipse. I > love Eclipse, but I didn't mean to say you couldn't use your favorite IDE! > All the popular IDEs have some level of Maven support, and even if it did > not, there is always the command line. Maven (or Gradle) is the key to > making Tapestry projects work. If Eclipse makes you uncomfortable, you > should be able to use the IDE of your choice. Do you have Maven installed? > > Don't get too frustrated over this, please have faith that plenty of us are > using Tapestry with Tomcat--I've been doing so for over 8 years now. > Please know that it was a challenge for me as well--My first Tapestry > project was the first experience with Maven, and I had to learn a little > bit of Maven to get started. I was overwhelmed on that first day (some 8 > years ago) but I bit the bullet and learned a little about how and why > Maven works. Let me tell you--it's a great thing to grow into a Maven > expert over time--I use it in all my projects, now that I've paid my dues > and I can wield it with some power. :-) Gradle is great too, and is > often recognized as the successor to Maven. However Maven is still very > widely used and supported. > > What it comes down to is A depends on B, B depends on C, C depends on D and > E, etc. For Maven, in your pom you just specify that you need A, and Maven > will seek out appropriate versions of B, C,D,E, etc. > > In addition to the Jars Tapestry needs for a web application, it is my > experience that there are almost the same number of jars that are used for > the testing phase! So not all the jars Maven uses end up in your .war file. > > By the way, are you packaging your application into a war file? If so, how? > > If you use Maven or Gradle to also build your war file (recommended), Maven > will stick the jars you need in the appropriate place in the war file, and > then Tomcat will get everything it needs in the war file. Just make sure > that something you include doesn't also include a *servlet*.jar, because > that will cause Tomcat to not load your app. (That's where my first email > applies, using the tag in your Maven pom to remove conflicting > jars) > > > Sometimes problems like this come about because you are at a point in life > where you are able to grow and overcome the obstacles. Once you overcome > this problem you will gain intuition that will really help later on. Just > face it with the right attitude: there is a solution to the problem and > it's within your abilities to figure it out. :-) > > I hope you were able to understand my message here -- I'm trying to use > terms that would translate easily. > > I wish you success. > > Dan > > > On Fri, Jun 6, 2014 at 8:05 AM, Thiago H de Paula Figueiredo < > thiag...@gmail.com> wrote: > >> On Fri, 06 Jun 2014 05:51:08 -0300, jeremias.epp...@web.de < >> jeremias.epp...@web.de> wrote: >> >>java.lang.ClassNotFoundException: org.apache.tapestry5.TapestryFilter >>> >>> That error Message is absolutly bullshit, it totally missleading me. >>> The real problem is that tapestry depends on a lot of jars and some of >>> jars from tapestry have dependencies to some other libraries like >>> hibernate, mongodb and spring and are not needed for the helloworld >>> example. >>> >> >> I'm sorry, but you're the one saying BS here. :P The error message, w
Re: Does Tapestry and Tomcat work together?
Hi Jeremias, I'm sorry about the difficulties you're having. It seems to me the real issue is dependency resolution, and then making sure those dependencies get seen by Tomcat. Neither of those are a Tapestry problem -- it's just a task inherent in all Maven or Gradle based projects. Tapestry, along with thousands of other libraries, is meant to be used with dependency resolution tools like Maven or Gradle or Ant+Ivy. You essentially MUST use Maven or Gradle to avoid the pain of downloading all those jars manually. I'm also sorry that you felt you needed to switch your IDE to Eclipse. I love Eclipse, but I didn't mean to say you couldn't use your favorite IDE! All the popular IDEs have some level of Maven support, and even if it did not, there is always the command line. Maven (or Gradle) is the key to making Tapestry projects work. If Eclipse makes you uncomfortable, you should be able to use the IDE of your choice. Do you have Maven installed? Don't get too frustrated over this, please have faith that plenty of us are using Tapestry with Tomcat--I've been doing so for over 8 years now. Please know that it was a challenge for me as well--My first Tapestry project was the first experience with Maven, and I had to learn a little bit of Maven to get started. I was overwhelmed on that first day (some 8 years ago) but I bit the bullet and learned a little about how and why Maven works. Let me tell you--it's a great thing to grow into a Maven expert over time--I use it in all my projects, now that I've paid my dues and I can wield it with some power. :-) Gradle is great too, and is often recognized as the successor to Maven. However Maven is still very widely used and supported. What it comes down to is A depends on B, B depends on C, C depends on D and E, etc. For Maven, in your pom you just specify that you need A, and Maven will seek out appropriate versions of B, C,D,E, etc. In addition to the Jars Tapestry needs for a web application, it is my experience that there are almost the same number of jars that are used for the testing phase! So not all the jars Maven uses end up in your .war file. By the way, are you packaging your application into a war file? If so, how? If you use Maven or Gradle to also build your war file (recommended), Maven will stick the jars you need in the appropriate place in the war file, and then Tomcat will get everything it needs in the war file. Just make sure that something you include doesn't also include a *servlet*.jar, because that will cause Tomcat to not load your app. (That's where my first email applies, using the tag in your Maven pom to remove conflicting jars) Sometimes problems like this come about because you are at a point in life where you are able to grow and overcome the obstacles. Once you overcome this problem you will gain intuition that will really help later on. Just face it with the right attitude: there is a solution to the problem and it's within your abilities to figure it out. :-) I hope you were able to understand my message here -- I'm trying to use terms that would translate easily. I wish you success. Dan On Fri, Jun 6, 2014 at 8:05 AM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Fri, 06 Jun 2014 05:51:08 -0300, jeremias.epp...@web.de < > jeremias.epp...@web.de> wrote: > >java.lang.ClassNotFoundException: org.apache.tapestry5.TapestryFilter >> >> That error Message is absolutly bullshit, it totally missleading me. >> The real problem is that tapestry depends on a lot of jars and some of >> jars from tapestry have dependencies to some other libraries like >> hibernate, mongodb and spring and are not needed for the helloworld >> example. >> > > I'm sorry, but you're the one saying BS here. :P The error message, which > isn't from Tapestry, but from Tomcat, is absolutely clear: you mentioned a > class in your web.xml which isn't in the webapp classpath. Tapestry-core > (the web framework) doesn't not depend on Hibernate, MongoDB nor Spring. > Some optional stuff do. tapestry-core has exactly 5 runtime dependencies, > including transitive ones which don't come from the Tapestry project > itself: commons-codec, Antlr, SLF4J (which is also used by an awful lot of > other libraries), javax.inject (a Java SSR), Servlet API (which will > actually be provided by your servlet container). > > You were having a dependency problem and that's exactly why you should > some tool to handle it. Maven and Gradle are quite good for that and have > support from IDEs. Just use one of them. > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
Re: Does Tapestry and Tomcat work together?
On Fri, 06 Jun 2014 05:51:08 -0300, jeremias.epp...@web.de wrote: java.lang.ClassNotFoundException: org.apache.tapestry5.TapestryFilter That error Message is absolutly bullshit, it totally missleading me. The real problem is that tapestry depends on a lot of jars and some of jars from tapestry have dependencies to some other libraries like hibernate, mongodb and spring and are not needed for the helloworld example. I'm sorry, but you're the one saying BS here. :P The error message, which isn't from Tapestry, but from Tomcat, is absolutely clear: you mentioned a class in your web.xml which isn't in the webapp classpath. Tapestry-core (the web framework) doesn't not depend on Hibernate, MongoDB nor Spring. Some optional stuff do. tapestry-core has exactly 5 runtime dependencies, including transitive ones which don't come from the Tapestry project itself: commons-codec, Antlr, SLF4J (which is also used by an awful lot of other libraries), javax.inject (a Java SSR), Servlet API (which will actually be provided by your servlet container). You were having a dependency problem and that's exactly why you should some tool to handle it. Maven and Gradle are quite good for that and have support from IDEs. Just use one of them. -- Thiago H. de Paula Figueiredo Tapestry, Java and Hibernate consultant and developer http://machina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Does Tapestry and Tomcat work together?
Thanks Daniel and Kalle, your solution helps me to resolve the problem. Previously I work with Netbeans and setup the tapestry Framwork their. I downloaded the Tapestry 5.4 archive and use the HelloWorldExplained Example from jumpstart and try to run the application with different java environments (Java 7 & 8 ) and webcontainer (Glassfish 4, Apache Tomcat 8.0.3 and 8.0.8). But allways I get the error message: org.apache.catalina.core.StandardContext.filterStart Exception starting filter app java.lang.ClassNotFoundException: org.apache.tapestry5.TapestryFilter That error Message is absolutly bullshit, it totally missleading me. The real problem is that tapestry depends on a lot of jars and some of jars from tapestry have dependencies to some other libraries like hibernate, mongodb and spring and are not needed for the helloworld example. So to get Tapestry work I have done following: - changed from netbeans 8 to eclipse kepler ide - added all tapestry jars to the project library - added the apache tomcat 8.0.8 server to my project run configuration - created the three tapestry files from the HelloWorldExplained jumpstart example - run the server after that I get an error message that a jar is missing, I have searched for the jar downloaded it an added the jar to my project. I have repeated that action several times. Missing jars: - JPA - apache commons fileupload - apache commons io - mozilla rhino - validation api (validation-api-1.0.0.GA.jar) - less4j - clojoure (http://dl.google.com/closure-compiler/compiler-latest.zip) - compiler-latest But the important thing was, that apache tomcat in combination with eclipse gave me better error messages. After that, I could load the helloworld example. I think this was the most difficult helloworld example I have ever done ;-) Sorry, for my bad English. Regards Jeremias On Fri 06 Jun 2014 06:19:10 AM CEST, Daniel Jue wrote: > Kalle is right, and this can be a stumbling block to those who are new to > web application development in general. It really has nothing to do with > Tapestry in and of itself, but little problems can cause newcomers to be > discouraged, for the wrong reasons. > > Assuming you are using Maven: > > If you are using Maven as your build tool, it can help to use an IDE that > supports Maven (I use Eclipse Kepler EE version) Using the IDE it is > easier to find out what other dependencies are causing the extra servlet > jar to seen by Tomcat. By opening your pom.xml in Eclipse and looking at > the dependency hierarchy tab, you can type in the word 'servlet' to see any > jars with that String in it. Then you'll want to exclude those extra > servlet jars in your pom, using the tag in the appropriate > dependency. I hope this helps. > > A similar problem occurs when your 3rd party dependencies includes extra > SLF4J/Log4J implementations, or when you have Log4J and something else > include Logback. Fixing these kinds of dependency issues is just part of > the job, and it's not bad once you expect to have to do it. :-) > > > > > > On Thu, Jun 5, 2014 at 10:08 PM, Kalle Korhonen > wrote: > >> Yes, Tapestry most certainly works well with Tomcat. Very likely, you have >> an additional servlet-api in your classpath, remove it and it should work. >> >> Kalle >> >> >> On Thu, Jun 5, 2014 at 4:49 PM, jeremias.epp...@web.de < >> jeremias.epp...@web.de> wrote: >> >>> Hi, >>> >>> does Tapestry and Tomcat work together? >>> Because I get that error message: >>> >>> rg.apache.catalina.core.StandardContext.filterStart Exception starting >>> filter app >>> java.lang.ClassNotFoundException: org.apache.tapestry5.TapestryFilter >>> at >>> >>> >> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1333) >>> at >>> >>> >> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1180) >>> at >>> >>> >> org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:549) >>> at >>> >>> >> org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:530) >>> at >>> >>> >> org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:150) >>> at >>> >>> >> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:258) >>> at >>> >>> >> org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:105) >>>
Re: Does Tapestry and Tomcat work together?
Kalle is right, and this can be a stumbling block to those who are new to web application development in general. It really has nothing to do with Tapestry in and of itself, but little problems can cause newcomers to be discouraged, for the wrong reasons. Assuming you are using Maven: If you are using Maven as your build tool, it can help to use an IDE that supports Maven (I use Eclipse Kepler EE version) Using the IDE it is easier to find out what other dependencies are causing the extra servlet jar to seen by Tomcat. By opening your pom.xml in Eclipse and looking at the dependency hierarchy tab, you can type in the word 'servlet' to see any jars with that String in it. Then you'll want to exclude those extra servlet jars in your pom, using the tag in the appropriate dependency. I hope this helps. A similar problem occurs when your 3rd party dependencies includes extra SLF4J/Log4J implementations, or when you have Log4J and something else include Logback. Fixing these kinds of dependency issues is just part of the job, and it's not bad once you expect to have to do it. :-) On Thu, Jun 5, 2014 at 10:08 PM, Kalle Korhonen wrote: > Yes, Tapestry most certainly works well with Tomcat. Very likely, you have > an additional servlet-api in your classpath, remove it and it should work. > > Kalle > > > On Thu, Jun 5, 2014 at 4:49 PM, jeremias.epp...@web.de < > jeremias.epp...@web.de> wrote: > > > Hi, > > > > does Tapestry and Tomcat work together? > > Because I get that error message: > > > > rg.apache.catalina.core.StandardContext.filterStart Exception starting > > filter app > > java.lang.ClassNotFoundException: org.apache.tapestry5.TapestryFilter > > at > > > > > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1333) > > at > > > > > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1180) > > at > > > > > org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:549) > > at > > > > > org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:530) > > at > > > > > org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:150) > > at > > > > > org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:258) > > at > > > > > org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:105) > > at > > > > > org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4586) > > at > > > > > org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5196) > > at > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > > at > > > > > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:724) > > at > > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:700) > > at > > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:697) > > at > > > > > org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:581) > > at > > org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:455) > > at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1496) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > > > > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > > at > > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at java.lang.reflect.Method.invoke(Method.java:483) > > at > > > > > org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300) > > at > > > > > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) > > at > > com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) > > at > > > org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:1437) > > at > > > org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:884) > > at > > org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:335) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:618) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:725) > > at > > > > > org.apache.catalina.core.ApplicationFilter
Re: Does Tapestry and Tomcat work together?
Yes, Tapestry most certainly works well with Tomcat. Very likely, you have an additional servlet-api in your classpath, remove it and it should work. Kalle On Thu, Jun 5, 2014 at 4:49 PM, jeremias.epp...@web.de < jeremias.epp...@web.de> wrote: > Hi, > > does Tapestry and Tomcat work together? > Because I get that error message: > > rg.apache.catalina.core.StandardContext.filterStart Exception starting > filter app > java.lang.ClassNotFoundException: org.apache.tapestry5.TapestryFilter > at > > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1333) > at > > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1180) > at > > org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:549) > at > > org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:530) > at > > org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:150) > at > > org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:258) > at > > org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:105) > at > > org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4586) > at > > org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5196) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > at > > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:724) > at > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:700) > at > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:697) > at > > org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:581) > at > org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:455) > at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1496) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at > > org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300) > at > > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) > at > com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) > at > org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:1437) > at > org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:884) > at > org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:335) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:618) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:725) > at > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:301) > at > > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) > at > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) > at > > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > > org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:393) > at > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) > at > > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > > org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108) > at > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) > at > > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219) > at > > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106) > at > > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:615) > at > > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:136) > at > > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportVa
Does Tapestry and Tomcat work together?
Hi, does Tapestry and Tomcat work together? Because I get that error message: rg.apache.catalina.core.StandardContext.filterStart Exception starting filter app java.lang.ClassNotFoundException: org.apache.tapestry5.TapestryFilter at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1333) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1180) at org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:549) at org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:530) at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:150) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:258) at org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:105) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4586) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5196) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:724) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:700) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:697) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:581) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:455) at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1496) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) at org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:1437) at org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:884) at org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:335) at javax.servlet.http.HttpServlet.service(HttpServlet.java:618) at javax.servlet.http.HttpServlet.service(HttpServlet.java:725) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:301) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:393) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:615) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:136) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:78) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:610) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:526) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1033) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:652) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:222) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1566) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1523) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at
