Tuesday, October 04, 2005

 

Archaeology and contracting

Ever had that feeling you wish you knew more about archaeological techniques when trying to sort out a clients problem?

Fighting with a jboss installation today. There are two jars with the same name: one in action, one in deploy. In this jar is supposed to be a class with a static method which takes three parameters. Now in the oldest jar, the class is not there, in the newest jar the class is there but the method only takes 2 parameters (I decompiled to check). So it must be somewhere else. A bruteforce search doesn't find it, and getting the jsp to tell me where the class is: URL whereItIs = getClass().getClassLoader().getResource( ); just tells me the name of the jar, which I already know. So the jar is obviously in another jar, and may be nested further.

Now an archaeologist might start first by "field walking", i.e. just wandering around on the site to see if there is anything just laying on the surface, and then go on to a geophysical survey.

Hmm, geophysical survey: I think I need to write a tool that acts like a radar to find where this class might be hiding.

Comments: Post a Comment



Links to this post:

Create a Link



<< Home

This page is powered by Blogger. Isn't yours?

Subscribe to Posts [Atom]