Weblogs |
 |
Getting rid of that pesky MalformedObjectNameException
You can't construct a JMX ObjectName without handling
MalformedObjectNameException, which is a checked exception. Here's
why that is a pain, how to relieve that pain, and what we're doing
to make it less painful in the next version. —
Eamonn McManus
GlassFish @ JavaMUG - Trip Report
Presented on GlassFish
at Java
MUG last week. The event is hosted at Sun's North Dallas Office.
It was impressive to know that local Sun team is hosting 4 User Groups (MySQL, Solaris, and OpenSolaris
other than the JUG) in a month. —
Arun Gupta
Building Rich Internet Applications Using Pivot and JavaScript
Pivot now allows developers to write their application logic using their scripting language of choice, using the features provided by the javax.script package available in Java 6 and above. —
Greg Brown
Forums |
 |
Re: Tracking Java Versions using Google Analytics
So it seems fair to say that ~70% of web users have Java installed, but for those of us interested in Applets or Desktop Applications I guess we are only interested in the top 56% or even 4%... Is that good enough? I guess it depends on whether you see the glass half-full of or half-empty. I am actually quite surprised that 56% of web users have Java 1.6 installed. That's actually much better than I expected! —
Re: Text anti-aliasing settings/Changing LAF
In my opinion, the whole thing about exposing API to set the text rasterization hints is unnecessary. Java2D should use the native rasterizer on *all* platforms for all text rasterization APIs. This is partially done in 6u10 on Windows when the awt.font.desktophints property is used as mentioned in the original links. Hopefully, JDK 7 will remove the bundled rasterizer(s), deprecate the existing rendering hints (in addition to the desktop property) and make them no-ops and start using native text rasterization exclusively based on the current settings of the user desktop environment. —
Java Web Start as Rich Internet Application technology
I work for a large company that has created a web start application that is now being used by thousands of users. The application uses web start for deployment but has all business logic on the server using web services. Our marketing group wanted to know how to define our application, and I told them they should use the term Rich Internet Application. Because that is, in my belief exactly what it is. There are some in the company that don't believe in Java on the Client technology and therefore are pitching hard that this technology not be considered RIA, even though they are willing to call flash, flex, air, and silverlight RIA. How does the Java Desktop community come down on this question. I think it is important because much of Java on the Desktop issues really come down to marketing not technology. —
java.net RSS Feeds
