-
1. Re: Spurious waring :-)
weston.price May 29, 2006 10:45 AM (in response to adrian.brock)We could the JNDI name as part of the XSLT. If it is this important, it might make sense to tie the attribute across all the MBeans that get generated at deployment time.
-
2. Re: Spurious waring :-)
weston.price May 29, 2006 10:47 AM (in response to adrian.brock)And actually, quite a bit of the old code does the log.error("error: some message"); sutff. I will remove it where I see it and clean this stuff up.
-
3. Re: Spurious waring :-)
weston.price May 29, 2006 11:18 AM (in response to adrian.brock)The other thing, on top of the prefill pool stuff I wanted to get into this release is the refactoring of the pool 'stuff' into it's own package and getting it out of the JBossManagedConnectionPool MBean. Static inner classes are fine, but this is ridiculous. I have this on a local build and was planning on checking it in later.
As always, I am going to assume silence is a 'go' ;-) -
4. Re: Spurious waring :-)
weston.price May 29, 2006 11:19 AM (in response to adrian.brock)And...IMHO, there is far too much of the inner class stuff in this code base for my comfort.