caclark has An opinion on deliverables..... mainly the rhino implementation in today's Forums. "I was concerned that the latest Rhino release was not fully realized because it involved certain features that a poster (A. Sundararajan's Weblog) said was not to be included.... 'Although Mustang includes Rhino 1.6R1 (and probably will change to Rhino 1.6R2 before FCS), we are not including E4X (ECMAScript for XML) support in it. We had removed this feature primarily because of footprint consideration. Note that E4X Rhino implementation uses Apache XMLBeans (xbean.jar).' ... please explain to me how this is a good scenario regarding scripting implementation in the next version of the java platform. E4X is the only reason I personally would move to using Java 1.6 scripting (as it seems to currently be based on rhino)."

coxcu has been working through a Swing performance glitch that pegs his CPU and reveals What finally led me to the problem: "I'm looking at a similar problem now, so I decided to write up how I solved the last one. Hopefully it will either help someone else out of a similar spot or spur someone to show me a better way. To recap, I had a Swing application that consumed 100% CPU while just sitting there. Trying to find the bottleneck with java -agentlib:hprof didn't produce anything that seemed like good data. I posted to this forum, and got some nice suggestions, but nothing worked. Since this wasn't really interfering with development, I put the problem out of my mind and hoped that it would go away. Later, I had someone run the software on a laptop that was much slower than my development machine. While the software was still useable, the problem was much worse. I could no longer ignore the problem."