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 <excludes> 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 >>>> >>>> >>> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
