Discovery Problems

[Ja...@exigengroup.lv]

Hi!

My jar which includes all necessary for axis is trying to discover 
different BeanInfo, _Helper, Handler and .propertie files
which does not exist in reality.
This forces BIG additional traffic for each Class.forName() invocation!
How can I avoid this? Is there possibility to tell the system to live with 
only thinkgs it can get and do not ask for non existing one :(
I understand, that way to check if they exists is to try them load and get 
exception, but in real life, thats a bad idea as it makes
huge traffic :(
For now I changed the axis code to not try load stupid _Helper classes, 
but I am still stucked with BeanInfo and .properties files!
_______________________________________________________
Living things are systems that tend to respond to changes in their 
environment, 
and inside themselves, in such a way as to promote their own continuation.

Janis Olekss
Exigen Latvia System Analyst
(Office) +371 7072900
(Cell) +371 9136267