Re: ComponenentRequestHandler doesn't exist when testing using TestNG

2011-01-05 Thread abangkis
Hi donny, thanks. I will try this :) On Wed, Jan 5, 2011 at 11:08 PM, Donny Nadolny wrote: > You can contribute just the name of the file you want > ("quartz.properties"), > put it in the classpath, eg in src/main/resources, and then in the place > where you need to use it, load it from the class

Re: ComponenentRequestHandler doesn't exist when testing using TestNG

2011-01-05 Thread abangkis
Hi howard and Kalle, Thanks a lot for the advice :) Yes i was also looking at the PageTester, I think its very cool :) But the apps mainly consist of 2 page. A page with a link to start the process, and the page that will show the result of the process. All of the work will be executed on the servi

Re: ComponenentRequestHandler doesn't exist when testing using TestNG

2011-01-05 Thread Kalle Korhonen
... or HtmlUnit & Jetty, see below from a recent thread on Maven users list: subject Re: Fail a build if the web application fails to load in Jetty On Tue, Jan 4, 2011 at 11:10 AM, Nathan Wilhelmi wrote: > Hi - HtmlUnit is a simpler solution for what we are trying to test right > now. What I

Re: ComponenentRequestHandler doesn't exist when testing using TestNG

2011-01-05 Thread Howard Lewis Ship
... and this is why you either want to look at unit testing using mocks, or at integration testing using Selenium. In the half-ground you end up with a lot of complications since the code is designed to run inside a servlet container and you don't have one. PageTester exists to mock up the servle

Re: ComponenentRequestHandler doesn't exist when testing using TestNG

2011-01-05 Thread Donny Nadolny
You can contribute just the name of the file you want ("quartz.properties"), put it in the classpath, eg in src/main/resources, and then in the place where you need to use it, load it from the classloader as a resource: InputStream in = getClass().getResourceAsStream("quartz.properties"); But inste

Re: ComponenentRequestHandler doesn't exist when testing using TestNG

2011-01-05 Thread abangkis
Hi josh, thanks a lot. I follow your advice and tries to include all the module that i could think of. This is the modified initRegistry method : private void initRegistry() { RegistryBuilder builder = new RegistryBuilder(); builder.add(TapestryModule.class); builder.add(AppModule.class); b

Re: ComponenentRequestHandler doesn't exist when testing using TestNG

2011-01-05 Thread Josh Canfield
It doesn't look like you are including TapestryModule in your registry. Since you're building the registry you're in charge kit adding all the modules. Optionally you could add @SubModule(TapestryModule.class) to your AppModule to make the dependency explicit. On Jan 5, 2011 4:25 AM, "abangkis" w

ComponenentRequestHandler doesn't exist when testing using TestNG

2011-01-05 Thread abangkis
Hello, i have a tapestry app that consist of 1-2 pages, and lots of services. The apps is used to crawl another website. The apps uses hibernate module, quartz and some other contribution. Because of the nature of my apps, i want to test the services class using TestNG. I've created a simple test t