Skip to main content

The Best Of What's Around

Posted by editor on September 26, 2007 at 8:42 AM PDT


Two years in the making, jMaki 1.0 hits the street

Continuing what's been a busy month of 1.0 releases, jMaki has just announced its first full-version release.

jMaki is one of those things where the name may be better known than the particulars of the project (hint: think "Ajax made easy"). Fortunately, the project is pulling together a guide to the many docs and blogs that explain what it is and how it works. A good place to start for absolute beginner information is the Why Use jMaki? document, which makes the case for jMaki's simplifications, standardizations, and flexibility.

Recently on the O'Reilly editor's list, we had a discussion trying to track where the Ajax market is going. There's a sense that a lot of developers have built DIY Ajax systems with hand-rolled JavaScript on the client and their choice of server-side frameworks... and have come away from the experience saying "I'm never doing that again." And as a result, there's now a great interest in getting a handle on all the various Ajax frameworks out there... do you want DWR or GWT or jMaki or something else entirely?

jMaki's in a busy part of the webapp world right now, and it will be interesting to see what kind of a niche it can carve out for itself.


Also in Java Today,

Javalobby has just posted an Interview with Tom Ball, openjfx compiler lead. After briefly discussing Project Jackpot, he talks about his new role on openjfx, the differences between JavaFX and JavaFX Mobile, the challenges of living up to community demands, the schedule for delivering JavaFX, the role of the open-source community in JavaFX's development, and more.

A pair of entries on The Aquarium portray the history and future of GlassFish in graphic form. First, in How Did We Get Here? GlassFish v2 History, Part I, Eduardo Pelegri-Llopart writes, "Rich has written a nice Historical Recap going through NetDynamics, KivaSoft, Netscape, iPlanet, Forte SynerJ, SunOne, Sun Java System Application Server, and then, GlassFish. He captured it all in this picture." Then the entry Branches, Branches... GlassFish Branches... looks ahead: "Nice post from Abhijit where he captures graphically, and in more detail, the Future GlassFish Releases. Abhijit covers GFv2 UR1, GFv2.1 (tentative name) and GFv3. Read his Detailed Entry or go directly to the Diagram."


In today's Forums,
hat27533
offers a tip of the hat to the jMaki project on the occasion of the 1.0 release, writing in
Re: Well Done The JMAKI team,
"I have just completed a RIA framework investigation at my company. JMAKI fits with our constaints: 1) Java based, 2) No new language for developers to learn, 3) Future proof, 4) Must be pure thin client with no client side runtimes. I have recommended that we use JMAKI going forward for all our web application needs."

eduardomartins announces further help for Mobicents users in
Mobicents Quick Start Guide wiki page updated.
"I know people are having some hard times with the current issue of having versions for JBoss 3.x and 4.x, so I've updated the main wiki page to make things easier. Let me know if the instructions doesn't work for you. Note, the problem with the src packages on sourceforge with the jain-slee-tck-1.0 folder empty is not fixed yet. Please use the CVS."

Finally, in
@Webservice and JMS @Resource, markshure writes:
"Hey all, I'm trying to create a webservice that uses the in-built embedded message queue. Everything works except when using the @Resource annotation with a JNDI reference to the queue and connection factory, both of them are null. Can this kind of resource injection be used within a web service or do I need to use a service locator? Note that when I use the @Resource with a test client application (appclient -client) it works fine. I'm using Sun App. Server 9.0 Update 1."


Kelly