You'll need to cache this stuff yourself. I really recommend avoiding
reflection though for any performance critical things -- even if there is no
time required for the class/methods lookup, you will still tend to spam a
lot of temporary objects. If you are going to use reflection, plan to spend
Hi all,
Doing profiling I discovered that Class.getMethods() is taking a lot
of time, and results are not cached internally - from J2EE world I'm
used that such caching is available, and must be switched off
explicitly. Is there reason for this? (I'm sure there is a good one,
but can not find
it)
2 matches
Mail list logo
