Thread: JBPatch
View Single Post
Old 07-26-2012, 05:39 PM   #335
ixtab
(offline)
ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.
 
ixtab's Avatar
 
Posts: 2,907
Karma: 6736092
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
Quote:
Originally Posted by qlob View Post
Does this work for kindle 3? in the OP, i saw that 100% of the java framework can be patched, but don't know if this is still the case.
Why shouldn't that be the case anymore?

The general approach works for every Java VM - after all, it's pure Java. So yes, of course, the method works on the K3. The only thing that requires some research effort is how to get the patcher bootstrapped. On the K5, this is achieved by registering with the framework as the very first OSGi bundle, and immediately intercepting and hooking into the classloader chain, so that all subsequent class load events come through the PatchingClassLoader.

Of course there are a few K5-specifics in the distribution (most notably the UI), but again: the core will work on everything that runs Java, be it a Kindle, a mobile phone or a PC.

Just give it a try!
ixtab is offline   Reply With Quote