On Jun 9, 2012, at 10:05 AM, dsh wrote:
Hi,
today I learned about the Metrics Java library and felt you may find
it useful. They already have a Jetty instrumentation module so I
suppose the concept could be applied to TomEE too:
- http://metrics.codahale.com/
Awesome stuff.
Regards,
I learned about by watching this InfoQ talk:
http://www.infoq.com/presentations/Using-Monitoring-and-Metrics-to-Learn-in-Development
On Sun, Jun 10, 2012 at 5:08 PM, Alan D. Cabrera l...@toolazydogs.com wrote:
On Jun 9, 2012, at 10:05 AM, dsh wrote:
Hi,
today I learned about the Metrics
Hi,
it is interesting but we (tomcat + our integration) already provide some
figues through JMX. Then the question is should it be at app server level
or user level?
If you take jetty, the user builds its server and it is here that the lib
is.
any thought?
- Romain
2012/6/10 dsh
Thank you Romain! I didn't notice that.
What about using /* and then excluding the /ejb/*
Something like...
!-- Everything is secured... --
security-constraint
web-resource-collection
web-resource-nameApplication/web-resource-name
url-pattern/*/url-pattern
Not sure if it work, try it ;). A good test is to run arquillian tomee
remote tests.
Romain
Le 10 juin 2012 20:36, Thiago Veronezi thi...@veronezi.org a écrit :
Thank you Romain! I didn't notice that.
What about using /* and then excluding the /ejb/*
Something like...
!-- Everything is
