If you used the quickstart to get your project going, you have a file called Start.java. From your IDE, just run Start.java in debug mode and you will get automatic class reloading, etc. If you didn't use the quickstart, then create a quickstart and copy that file out of it. Modify it to fit your needs and use it.
I prefer Eclipse. But anytime you ask about preferred IDE, you are bound to get a variety of answers. -- Jeremy Thomerson http://www.wickettraining.com On Wed, Aug 5, 2009 at 7:06 PM, arungupta<arun.gu...@gmail.com> wrote: > > Then I'm not understanding your original point. Is jetty:run not the embedded > Jetty ? > > How do I use the Start class ? > > I agree about the debugging part. Which IDE is preferred by the Wicket > community ? > > -Arun > > > igor.vaynberg wrote: >> >> i dont think jetty:run will get you class reloading - which means any >> time you modify a java file it has to restart the app - annoying. >> >> besides, how do you use a debugger? >> >> much easier to just right click Start and select "debug as a java >> application" >> >> my two cents >> >> -igor >> >> On Wed, Aug 5, 2009 at 4:07 PM, arungupta<arun.gu...@gmail.com> wrote: >>> >>> Thanks for the tip! >>> >>> I'm indeed using jetty:run and that surely speeds up the cycle. It's good >>> to >>> know that markup/property files are reloaded live as well, should've >>> thought >>> about it :) >>> >>> -Arun >>> >>> >>> igor.vaynberg wrote: >>>> >>>> also your learning point: # Edit/Save/Deploy/Refresh cycle is time >>>> consuming is completely wrong. >>>> >>>> if you wouldve used the quickstart you wouldve gotten the Start class. >>>> you can use this to launch your app with an embedded jetty container. >>>> as long as wicket is in development mode you get markup and property >>>> file reloading on a live application. if you run the start class in >>>> the debug mode you will also get hotswap - class reloading in the live >>>> application. >>>> >>>> there is no edit/save/deploy/refresh cycle. there is edit - possibly >>>> restart jetty if you made a change hotswap cant handle - refresh >>>> cycle. >>>> >>>> -igor >>>> >>>> On Wed, Aug 5, 2009 at 2:41 PM, arungupta<arun.gu...@gmail.com> wrote: >>>>> >>>>> Some background ... >>>>> >>>>> I'm trying to build a sample application using different Web frameworks >>>>> and >>>>> Wicket is one of them. More details at: >>>>> http://kenai.com/projects/runner/pages/Home >>>>> >>>>> Regarding pure Servlet approach, I agree and that's what I'm going to >>>>> do >>>>> when I built my sample application using a pure Java EE application. >>>>> >>>>> This time, I'm trying to see if this can be done purely in Wicket >>>>> though. >>>>> Or >>>>> even with Wicket I need to fall back to Servlets ? >>>>> >>>>> -Arun >>>>> >>>>> >>>>> Alexandru Objelean wrote: >>>>>> >>>>>> Why would you use wicket for this? The simplest approach is a plain >>>>>> servlet.. >>>>>> >>>>>> Alex Objelean >>>>>> >>>>>> >>>>>> arungupta wrote: >>>>>>> >>>>>>> I need to define couple of URLs in my app that return JSON data on >>>>>>> GET >>>>>>> request and are not tied to any view. Planning to use >>>>>>> QueryStringUrlCodingStrategy and append the URL as >>>>>>> "type=runlogs&chart=barchart". Then in the WebPage, extract the query >>>>>>> string and process them. >>>>>>> >>>>>>> How do I ensure that JSON data is returned for GET requests to those >>>>>>> URLs >>>>>>> ? >>>>>>> >>>>>>> Thanks, >>>>>>> -Arun >>>>>>> >>>>>>> -- >>>>>>> Need Application Server ? - Download glassfish.org >>>>>>> Blog: http://blogs.sun.com/arungupta >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>>>>>> For additional commands, e-mail: users-h...@wicket.apache.org >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> -- >>>>> View this message in context: >>>>> http://www.nabble.com/Processing-GET-requests-tp24836398p24836690.html >>>>> Sent from the Wicket - User mailing list archive at Nabble.com. >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>>>> For additional commands, e-mail: users-h...@wicket.apache.org >>>>> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>>> For additional commands, e-mail: users-h...@wicket.apache.org >>>> >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Processing-GET-requests-tp24836398p24837780.html >>> Sent from the Wicket - User mailing list archive at Nabble.com. >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> >> > > -- > View this message in context: > http://www.nabble.com/Processing-GET-requests-tp24836398p24838282.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
