Hello Michael,
No that doesn't work either. In fact switching to this I get an error on the Class.forName(className) line where as previously I could create the Class object (but not instantiate it). When I debug using Eclipse, the method does get executed, but when I step over the line of code, it throws the exception without going into the try/catch block. Most frustrating as I can't even determine what the problem is!
Could you show us the whole code of where you use Class.forName with the try-catch block around it?
Does the code work stand-alone (without Axis)?
I'm guessing I would need to load the properties before hand and pass them to the common jar. You'll have to forgive my lack of knowledge when it comes to Java; I've been using .NET for the last 3 years so I haven't had to worry about classpaths. Is passing the properties when you load the common jar (through say the constructor) the common way to handle this sort of issue?
I think you are trying to apply some OO and have the common jar have interface or factory class through which you access it. Depending on how common you want that code to be, there are various ways to do this. If the properties are not vital to make the initial instance, using one or more setters would come to mind. If you want the jar to depend on a property file, you could also just pass the path to it.
You could try discussing it in a Java developing related mailing list. Regards, Dies --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
