Korosh Afshar wrote: >Ok thanks for that. > >I tried your suggestion and gotten to at least load the classes. Now I >get InvocationTargetException on the ThirdPartyLauncher. > >I talked to the thirdparty support guy and he said there is a way to >force their ThirdPartyLauncher classloader to not load my classes by >providing mypackage prefix on the command line argument to jvm (really >bad in my oponion). > >Guess what, I tried their suggestion NOT using avalon framework and got >the InvocationTargetException. > >I also tried it, WITHOUT your suggested changes outside of avalon >framework, providing the command line argument they suggested, and got >ClassNotFoundException. > >So now I am thinking that their class loader must be doing something >funky and unexpected. They assured me that if their class loader can't >find my classes, then it would delegate to the parent classloader which >should be the default system classloader(CLASSPATH). This doesn't seem >to be the case as I am certain that my build directory which contains my >classes(non jar format) is in the CLASSPATH. > > running with -verbose will tell you where the classes are loading from... this might help you track down the problem.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
