I know it's borked... I'm just not sure why, how, or in what specific departments. Does anybody know the details on what Apple did to the JVM in Leopard? It works, but it seems to perform quite differently, at least in my case. 

Basically, it feels quick once it's got all the necessary classes loaded, but is _very_ slow loading new classes. The first time I run my app, it's much slower than in Tiger. Then, if I leave it open, repeated use seems to be nice a speedy (this is a particular analysis routine, which I run on a midi file, so it easy to get a subjective idea of how fast it's running). Anybody know what this is all about, and whether I might be able to fix it with any specific optimizations, or JVM settings?

I know it's borked... I'm just not sure why, how, or in what specific departments. Does anybody know the details on what Apple did to the JVM in Leopard? It works, but it seems to perform quite differently, at least in my case. 
Basically, it feels quick once it's got all the necessary classes loaded, but is _very_ slow loading new classes. The first time I run my app, it's much slower than in Tiger. Then, if I leave it open, repeated use seems to be nice a speedy (this is a particular analysis routine, which I run on a midi file, so it easy to get a subjective idea of how fast it's running). Anybody know what this is all about, and whether I might be able to fix it with any specific optimizations, or JVM settings?

just-how-borked-is-java-1-5-in-leopard

Well, it seems like some classloader thing. I specified my directory, but it still does a nice little hang when instantiating new classes for the first time. Very odd.

It's not that big a deal, since things move along just fine after the necessary classes have been loaded at least once, but it's a bit annoying.

Am I the only one having this problem? Or am I just the only one silly enough to be doing mxj development in 10.5 already?

Just how borked is Java 1.5 in Leopard?