Java Today |
 |
JNA brings native code to JRuby
The JDK community's incubated Java Native Access (JNA) project gets a starring role in extending JRuby's reach to POSIX support and native extension support. InfoQ points out how in JNA brings native code to JRuby. "The (not so) secret ingredient here is the Java Native Access (JNA) library, not to be confused with Java's JNI. While JNI provides access to native C code, it requires extra effort and glue code, such as JNI header definitions that need to be compiled, to access it." JNA, by contrast, provides an automatic mapping from a Java interface to a native function.
Java Mobility Podcast 18: Learn new UI techniques with phoneME UI Labs and Java ME
The latest Java Mobility Podcast is Episode 18: Learn new UI techniques with phoneME UI Labs and Java ME. "phoneME UI Labs is the one stop resource for developers to learn about the advanced UI technologies in Java ME platform. Aastha Bhardwaj talks about scalable vector graphics (SVG) in JSR 226 and JSR 287 and the demos that developers can find in UI Labs."
NetBeans.tv Speaks with Rich Unger
In their latest video interview, NetBeans.tv Speaks with Rich Unger. Rich used to work for Nuance Communications, where he added quite a bit to the NetBeans platform early on. These days, he's taking a year-long dream sabbatical with his fiancee - seeing the world and dropping in on NetBeans users along the way. See what he has to say about the forthcoming 6.0 release, the GPL announcement and flying kites in Patagonia!
Weblogs |
 |
Smooth Sailing in the NetBeans Mobile; Wicket AJAX basics
After an initial mechanical hiccup, the NetBeans Mobile is purring along nicely. Photos from today are available . It looks like I'll be visiting with members of the Salt Lake City, Utah Java Users' Group on Friday, the Milwaukee, Wisconsin JUG on Monday and the Madison, Wisconsin JUG on Tuesday. If you're along my route, drop me a line! —
Tim Boudreau
Web Services Addressing 1.0 - Metadata is now a W3C Recommendation.
Web Services Addressing 1.0 - Metadata specification is now a W3C Recommendation. It defines how to express abstract properties defined in the Addressing 1.0 core specification and uses WS-Policy 1.5 to express conformance to Web Services Addressing 1.0 specification. —
Rama Pulavarthi
Learn to REST using Jersey
Jersey is the open source JAX-RS (JSR 311) Reference Implementation for building RESTful Web services. Paul announced the availability of 0.2.1. This blog entry describe the steps to get started with Jersey and provide useful pointers for further exploration. —
Arun Gupta
Forums |
 |
Poll: Topic for phoneME Advanced Web seminar
I'm taking a poll to see what topic would be good for a future phoneME Advanced Web seminar (tentatively Thu. 27Sep2007 @ 0800 AM, US/Pacific
Time). Please log in and vote at: https://forums.java.net/jive/poll.jspa?pollID=4. Thanks. —
Request for feedback: implementing Swing-based drawers
I've inherited some code to which I need to add a 'dresser drawer' like functionality. Click on a logical 'open' button and the drawer opens, revealing, or displaying as the case may be, a JPanel with more stuff in it. Click on a logical 'close' button and the drawer closes, leaving its container in the visual state in which it started. A familiar example of this effect might be something like the Mac Dock in 'auto hide' mode, where the Dock moves in and out of sight and addressability with some pointer action. The Dock is always 'there', but sometimes just not visible. So it would be with the drawer. I am wondering if a solution would be based loosely on theDrawer.setVisible(), or whether something that sets the drawer's component width or height to 0 for-hide would be more likely. Can anyone offer guidance on how to approach this using standard Swing techniques? —
Push via messaging vs pull via polling..
I'm starting to consider how I'm going to design a portion of my application. I guess the best way to describe it would be "a queue shared between multiple application clients / users." I can think of two ways to do this... 1. Use the messaging system to publish changes relevant to the queue to subscribed application clients. 2. Have each application client poll the server (refresh) at regular intervals. I'd like to know if anyone has any thoughts / comments relating to either strategy. I have a preference, but would like to see what other people think before I start. —
