Sorry Diego, I didn't mean to be rude or a troll.
Honestly, what you want might be an excellent tool to be added to Wicket
Stuff. Something like:
if (developmentMode) {
mountPage("/_wicket_info", WicketInfoDashboard.class);
// ugly URL to not be confused with something else
}
And that page be able to provide a lot of information on something like a
URL, a WebPage or a component.
Ask for GitHub access and start a project at WicketStuff. Sure there will be
others willing to help. Not just troll... :-) I'm one of them.
*Bruno Borges*
(21) 7672-7099
*www.brunoborges.com*
On Fri, Aug 26, 2011 at 6:02 PM, Diego Fernandez <[email protected]> wrote:
> Well I think that is not a matter of knowing how to read the logs.
> Testability and usability (for the developer) are quality attributes that
> could be improved by the feature that I'm trying to explain: easy for QA to
> report bug details, easy for the dev to look in the right place.
>
> Ok, I'll try to implement the feature and publish it in github it when is
> ready, I was expecting a more friendly response from you guys.
>
> Thanks,
> Diego
>
>
> On Fri, Aug 26, 2011 at 5:43 PM, Bruno Borges <[email protected]
> >wrote:
>
> > This is more related to knowing on how to read logs rather a lack of
> > feature
> > in Wicket.
> >
> > *Bruno Borges*
> > (21) 7672-7099
> > *www.brunoborges.com*
> >
> >
> >
> > 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 ?
> > >
> > > 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.
> > >
> > > > 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
> > >
> >
>
