when u "run" the jar it creates a new jar, runs that jar which is the installer for the blue prints solutions. I'm not sure what the XOR is all about. it seems to have some sort of a signature in the file that it verifies against it may have somethin to do with it. I can post all of the source as it was decomiled by dj java decompiler.
So i was being nosy today and cracked open the jar file for the java blue prints catalolg installer (bpcatalog-1.0.1_01-installer.jar). I see a meta-inf directory and a manifest file inside that. I also see a bpcatalog.class file at the root of the jar. Standard stuff right? Except for fact that the class file is a bit plump, 3.73 MB to exact. That made me go "huh?". So I decomile the class and see some code that looks like this:
looks like the class extracts an installer jar out of itself and then executes it
So I thought this was kind of neat was wondering if anyone has seen this before. Makes me wonder how I would go about stuffing a jar into a class my self.