> But in this case, technically, the way the viewStatistics code works is to > expose information of the current JVM and ticket registry.
Ah, I see. You envision the management app being deployed on a different running JVM from the CAS server itself, which I recall we've discussed in the past and the value is self-evident as well. > That's why I wanted to stick these statistics with the CAS server.... It's a > bit like the /status url. Agreed they're similar and it makes sense, though there may be value yet in a separate optional webapp module to contain them. But that's down the road if ever. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
