Skip to main content

Missing: JavaOne Conference CFP

Posted by daniel on December 13, 2004 at 6:36 AM PST

Has anyone seen the Call for Papers?

The year is shaped by regular events. One of them, for many Java developers, is the annual JavaOne call for papers. Now this shape has been thrown off in the past in those years when the conference was held in March instead of June. But, for the most part, here's how I remember the annual ritual for years in which the conference is held in June - feel free to post your corrections.

Sometime in October or November there would be a call for papers with guidelines to the major topics for this year's show and descriptions of what constitutes a BoF or a Session. The deadline would be sometime around now - usually Friday night at midnight. Some time around 10 pm that night the servers would be flooded by those of us finally submitting our half a dozen session proposals. We'd be told that we would hear back from the referees some time in January. About a week after that published deadline we'd get email with a new deadline for notification.

As of this morning the JavaOne Call for Papers page still advises that you "check back later this Fall for specifics on the Call for Papers process and deadlines. We will be looking for submissions on technical sessions on Java technology. Now is the time to begin thinking about the technical solutions you would like to share with this exclusive audience."

Eduardo Pelegri-Llopart points out changes in licensing that mean JAX-RPC and JAXB now under the new JDL in today's Weblogs.
He writes, "The version of the JDL that we are using in JAXB and in JAX-RPC includes the right to access the TCKs for these technologies. These TCKs are now also at Java.Net and can be used, free of cost, on the Reference Implementations and on artifacts derived from them to help test their compatibility."

Malcolm Davis points to an article on The top 20 IT mistakes to avoid. Malcolm adds his thoughts on his hot button issue: the management of software development and writes that he "was informed by a software veteran of 30 years, that the biggest change they had noticed was the ratio of junior programmers to senior developers. When they first started, there was one junior to several senior developers. By the time they had left the profession, there were 4 or 5 junior to every 1 senior developer."

Eric Freeman weighs in on Java, Coolness, Human Scale, and Creative Environments. Eric makes the point that "The good news is that this analogy is directed more at the Java API than the core language. With the APIs one doesn't have to look far to see "uncoolness," at least from a design sense (J2EE, Swing, Calendar to name a few), but these are APIs (or higher level platforms) and so we don't have to be stuck with them."

In Also in Java Today , Tim Bray reports from the recent Sun summit on Dynamic languages on the Java platform. As Tim notes, "the fact that Java is a three-legged stool (language, JVM, libraries) kind of gets lost under the enveloping carpet of the one-word name 'Java'." Among other lessons from the gathering, "it might be worthwhile to add a new bytecode to the JVM to help with at least some of this choreography and housekeeping; especially since it doesn’t look like that bytecode would be very expensive to add."

Depending on the implementation, Java Messaging Service can be either hub-and-spoke or peer-to-peer. Traditionally, all JMS traffic will go through a single "broker", which is obvious as a possible bottleneck. In Distributed Messaging with MantaRay, Amir Shevat shows an alternative approach to JMS: "MantaRay provides a much higher level of robustness, better performance, and faster implementation by eliminating the need for a broker and bringing all functionality to the edges. MantaRay eliminates the single point of congestion and single point of failure of traditional models by using a peer-to-peer, serverless architecture."

In Projects and
, the Java Desktop home page asks "Do you need a production-quality, open-source windowing and docking framework? The creators of the FlexDock project need volunteers to continue FlexDoc development. If you can help, please contact Scott Delap at scott AT"

You'll find the Mnemos in the JavaTools community is a Lightweight Object Oriented Persistence System (LOOPS) based upon Java Object Serialization which aims to provide a system that requires a minimal amount of set up in order to make objects persistent.

, Peter Kessler responds to a request to add an === operator, "I'm certainly not anything like an official position from Sun on this issue, but I can try to convince the folks who are to take a look at it. I don't do language design, but historically we've had enough confusion between "=" and "==" that introducing a third variant "===" seems misguided"

Dalibor asks about the builds, Is there some reason why you don't just use autotools on all platforms?

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 feed.

Current and upcoming href=""> Java Events :

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 site.

Archives and Subscriptions: This blog is delivered
weekdays as the href="">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="">

Has anyone seen the Call for Papers?