On Fri, Aug 26, 2011 at 5:17 PM, Martin Grigorov <[email protected]>wrote:
> Hi, > > Can you paste a stacktrace which is not understandable by you ? > Yes, of course that I understand how to read a stack trace (not need to be a troll, ok). > I don't understand what do you mean by "/mypage is implemented by > com.myapp.bla.MyPage" > I guess you have MyPage mounted at /mypage but I don't understand what > kind of problems are hard to find the cause. Is not for a particular kind of problem, but when you have to fix a bug in a big web application, sometimes you don't know who is processing the page that is displayed. So you have to start searching where the URL is mounted, etc. That takes time, specially if you are not the original developer. I usually end doing a simple thing: just look into the page source, then search in code for some string in the page source (sometimes that works). Compare that to the easy Seaside.st halos (look at http://seaside.st/about/examples/halos), I don't want something advanced as the Seaside halos (which I think is not possible in Wicket). But I want something more friendly and fast than trying to get the information from the RequestLogger. A special servlet could be enabled in development/qa (or even in production under some security constraint) and could be useful also for QA people to report bugs in a page. > > I've the information of the pages > > where the error occurs and I've to find which Page/Component implements > that > > page. > I suppose you are not sure which page is being processed when the > problem occurs. You can you Wicket's RequestLogger to log which page > is going to be processed or web container's access log to see what URL > is requested and then map it to a page. > > > On Fri, Aug 26, 2011 at 10:49 PM, Diego Fernandez <[email protected]> > wrote: > > Hi wicket devs, usually when I'm trying to fix a bug in a Wicket > application > > (or other Java servlet applications), I've the information of the pages > > where the error occurs and I've to find which Page/Component implements > that > > page. > > When the application gets bigger, finding where the logic for a page is > > implemented requires a lot of search in different parts of the > application. > > > > I was wondering if exists a wicket servlet/filter that could give > > information about: > > - Which class implements the page > > - Which components are rendered for a page > > > > Something like: > > http://localhost:8080/wicketinfo?page=/mypage > > > > /mypage is implemented by com.myapp.bla.MyPage > > And is composed by: > > - com.myapp.bla.components.XComponent > > ... > > > > Is there something like this in Wicket? > > > > I'm asking in the dev list, because if there is nothing like this I think > > that could be good to develop it, at least it will save me a lot of > search > > during bugfixing. > > Any clues on where to look to develop something like this? > > > > Thanks, > > Diego > > > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com >
