Skip to main content

The Bleeding Heart Show

Posted by editor on October 25, 2006 at 7:16 AM PDT

"Surprising and vigorous" reactions to JSR-277

JSR-277, the Java Module System, has been in public draft review for just two weeks and is already attracting profound attention. Not just that a lot of people are commenting on it, but they're doing so in significant depth. This is a tremendously important thing of course, as the JSR attempts to resolve a number of issues -- versioning, dependency management, etc. -- that have long nagged Java developers, and that the existing JAR format has proven incapable of managing in its current form.

It's a hot topic on this week's Java Posse podcast, which picks up on a debate in their forums over the proposal. Some of the posters there have pointed out the work done by OSGi in this space, most typified by Peter Kriens' JSR 277 Review, which we featured on the site on Monday. Posse member Dick Wall sees the discussion turning into another "Spring versus Java EE 5" thing, with some accusing Sun of having a "not invented here mindset" and ignoring a similar, possibly superior, and already-available standard established outside of the heliosphere. Wall's reply is that 277 has been developed through the JCP, a more open process than you typically (if ever) find for successful products the size of Java, and criticizes some of the anti-277 rhetoric:

What I've been reading is things like, "well, JSR 277"... there's a lot of kitschy or cliquey terms being bandied around like... "JSR 277 is OSGi without the eight years of experience that we've got." And my response to that would be, well, you know, you could bring that experience and help out the JSR if you wanted to. That experience, I'm sure, would be welcomed. But at the same time, I don't see that just because you got there first, you can dictate terms. This is going to affect a lot of people in the Java space, and I think they should all have their voices heard. I don't think it should be forced into being from one company's viewpoint or one organization's viewpoint.

Of course, it's still fair game to consider JSR-277 on its merits, or lack thereof, as blogger Patrik Beno does in his JSR 277 Review. He writes: "This document is an attempt to review and comment work of the expert group presented in the initial early draft of the specification published on October 11, 2005 [...] My impressions are three-fold: There is some great stuff in this JSR, some stuff is missing, and finally, I see some design flaws, some of them real hard showstoppers. Now if you're ready, read on."

Also in today's Weblogs, Jody Garnett has an update on OOPSLA Part I:
"The only real reason to attend a mad scene like OOPSLA is for that wack to the side of the head that shakes lose some of your preconceptions, and hopefully allows you some room for those ideas that seem to gravitate to such occasions."

Richard Bair has some help to offer with
SSL and Self Signed Certs:
"Connecting to web servers over https that have self signed certificates has always been a hassle in Swing applications. Hopefully, with some recently added code and API in the SwingX-WS project this is no longer the case."

In today's Forums,
gcsaba2 asks
How can an unsigned applet certify itself?:
"I have a graphics design applet which is not signed. With this applet the user can draw lines, circles etc. and may add regular images. There's a set of pre-made images, so the chances that the user will use his own are low. However, there is an option for this, so if the user wants to insert his own images, an open dialog must show up and allow the user to select a file from his computer. Unfortunately, to use an open dialog the applet must be signed, otherwise a security exception will be thrown. Because in most cases the user will not use his own images, it is stupid for me to sign the entire applet, and have the certificate window appear each time. The confirmation window should only appear when the user clicks on the Open button, in which case the applet should use the keystore which I'd provide and it should "sign itself", ie. certify itself with the browser's security manager. How can I do this?"

mcacker has some class resolution problems in
Shared client package:
"hi, i have a scenario where i have a web service with multiple endpoints (SEIs). using client customizations, i can put the client bindings in separate packages, which works fine. however, i have some shared classes that are used by all the SEIs, and client bindings for these shared classes are created in each of the packages for the same classes, thus there are duplicate classes in each package. this becomes a problem when sharing instances of these classes, as on the client they are not instances of the same classes, and the code will not compile"

In Java Today,

NetBeans 6.0 Milestone 4 is now available, and the Milestone 4 report details some of its new features: Java EE 5 support from NetBeans 5.5 was merged into 6.0, Mobility Pack made its firsst milestone release, and Profiler added 'a bunch of features". This Milestone build is available from the Trunk Milestones Index.

Emil Sit, a graduate student in parallel computing at MIT recently began working with the Sun Grid. In his blog post First steps with the SunGrid, he describes the concepts and organization of the grid, shares his experience working with it, and offers some suggestions for possible improvements.

The incubated Java Desktop project JIL (Java Islamic Library) is a project to provide a plethora of useful Islamic tools and applications as well as a comprehensive feature-full Islam-centric library. The JIL project includes Hijri date, Muslim prayer times, and Qibla etc.

In today's
News Headlines

Registered users can submit news items for the href=""> News Page using our
news submission
. All submissions go through an editorial review before being
posted to the site. You can also subscribe to the href=""> News RSS

Current and upcoming Java

Registered users can submit event listings for the href=""> Events Page using our href="">events submission form.
All submissions go through an editorial review before being posted to the

Archives and Subscriptions: This blog is delivered weekdays as
the Java
Today RSS feed
. Also, once this page is no longer featured as the
front page of it will be
archived along with other past issues in the href=""> Archive.

"Surprising and vigorous" reactions to JSR-277