Re: wicketstuff-jamon
Started tracing where the null monitor is being created. For my Wicket application, the null target values are associated with Wicket packaged resources such as images and JavaScript files. -- View this message in context: http://www.nabble.com/wicketstuff-jamon-tp16125597p22501465.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
Re: wicketstuff-jamon
I started it and left it in a very basic state, mainly because of my lack of css skills. It is funcationally usable and checked in. See the JamonAdminPage. Lars On Fri, Mar 13, 2009 at 2:42 PM, shetc wrote: > > Thanks, Lars. I also have seen a null monitor as well, and was going to > look > into that -- I'll let > you know how I get on. Did you finish Wicketising the Admin pages? > -- > View this message in context: > http://www.nabble.com/wicketstuff-jamon-tp16125597p22496658.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 > >
Re: wicketstuff-jamon
Thanks, Lars. I also have seen a null monitor as well, and was going to look into that -- I'll let you know how I get on. Did you finish Wicketising the Admin pages? -- View this message in context: http://www.nabble.com/wicketstuff-jamon-tp16125597p22496658.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
Re: wicketstuff-jamon
Hi Steve, I haven't worked on the code for a while, so feel free to commit, change or adjust it the way you like. I have used in in production code without problems. It is pretty monkey proof, so even if it fails it wont intervene with the normal process. The only thing that can "break" is the monitoring itself, I have seen Monitors with the name null from time to time but have never figured out what caused that. Regards, Lars 2009/3/12 shetc > > Hi Lars, > > Your Jamon implementation looks very good and I was able to easily > integrate > it with my Wicket > project. Please tell me what the current status of this code is, and will > it > be okay to add it to > a production application? > > Thanks, > Steve > -- > View this message in context: > http://www.nabble.com/wicketstuff-jamon-tp16125597p22476908.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 > >
Re: wicketstuff-jamon
Hi Lars, Your Jamon implementation looks very good and I was able to easily integrate it with my Wicket project. Please tell me what the current status of this code is, and will it be okay to add it to a production application? Thanks, Steve -- View this message in context: http://www.nabble.com/wicketstuff-jamon-tp16125597p22481260.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
Re: wicketstuff-jamon
Hi Lars, Your Jamon implementation looks very good and I was able to easily integrate it with my Wicket project. Please tell me what the current status of this code is, and will it be okay to add it to a production application? Thanks, Steve -- View this message in context: http://www.nabble.com/wicketstuff-jamon-tp16125597p22481222.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
Re: wicketstuff-jamon
Hi Lars, Your Jamon implementation looks very good and I was able to easily integrate it with my Wicket project. Please tell me what the current status of this code is, and will it be okay to add it to a production application? Thanks, Steve -- View this message in context: http://www.nabble.com/wicketstuff-jamon-tp16125597p22476908.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
Re: wicketstuff-jamon
Please beware that it's still in development (just started few weeks ago). The labels are added to JAmon, but for the admin functionality you still need to use the provided JAMon admin functionality (jsps). I am currently Wicketising (new verb?) the admin interface now, but that is far from finished. You should override the newRequestCycle to return the JamonMonitoredWebRequestCycle and the newRequestCycleProcessor to return the JamonAwareWebRequestCycleProcessor Cheers, Lars On Tue, Mar 18, 2008 at 6:03 PM, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > I was browsing the sources for wicketstuff-jamon and I was wondering > > how to actually "hook it up" into my app? How do you use the custom > > web request cycle instead of the default one provided by wicket? > > By overriding newRequestCycle in your application class. > > Eelco > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: wicketstuff-jamon
> I was browsing the sources for wicketstuff-jamon and I was wondering > how to actually "hook it up" into my app? How do you use the custom > web request cycle instead of the default one provided by wicket? By overriding newRequestCycle in your application class. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
wicketstuff-jamon
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-contrib-jamon/src/main/java/org/wicketstuff/jamon/ I was browsing the sources for wicketstuff-jamon and I was wondering how to actually "hook it up" into my app? How do you use the custom web request cycle instead of the default one provided by wicket? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
