RIA News Desk

Subscribe to RIA News Desk: eMailAlertsEmail Alerts
Get RIA News Desk via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn

Related Topics: RIA Developer's Journal, JBoss Enterprise Middleware, Apache Web Server Journal, AJAX World RIA Conference

RIA & Ajax: Article

JBoss Finally Releases Developer Studio of AJAX Tools

Since its non-acquisition of Exadel's RichFaces AJAX tooling, Red Hat's JBoss has been promising us a platform

Since its non-acquisition of Exadel's RichFaces Ajax tooling last March, Red Hat's JBoss has been promising us a full technology platform that reaches all the way from Web 2.0 front end back to the middle tier and, since this is Red Hat, the Linux OS as well. JBoss has also promised us that the tooling would be fully Eclipse-compliant, but only through its own developer portal rather than Eclipse.org.

JBoss has now issued the 1.0 release after months of previews. Of course, this being the world of open source, there are few surprises as to what's in the released 1.0 stack. It includes Exadel's front end development tools that include Studio Pro, a web application development toolset which supports JSF, Struts, Hibernate, and Spring; RichFaces which provides visual components; and Ajax4jsf, which provides a way for using JSF components to generate Ajax-style rich clients.

Like many other enterprise Ajax tools, JBoss Developer Studio helps minimize raw coding of JavaScript; in this case, it does so by relying on JSF, which provides a way of generating web pages from Java components.

The JBoss technology stack walks the fine line between open source and what might otherwise be considered proprietary technology. The entire stack is all open source, meaning you can play with the guts of the technology and do anything with it, and only pay for support. But it's hardly vendor neutral. In this case, JBoss Developer Studio is optimized for supporting other JBoss technologies, such as SEAM, which the company claims is more than just another model-view-controller (MVC) pattern because of its JSF support. And there is native integration with JBoss' BPM and Rules Management tooling.

This is an excellent example of what developers commonly refer to as "captive open source", where the guts of the technology are fully open, but the open source project is controlled by the vendor. The approach is similar with Eclipse: JBoss is a member of the board, its development stack is available as Eclipse plug-ins, but JBoss, not Eclipse, hosts the JBoss tool projects. JBoss reasons that it's because its licensing is different: the "purer" GPL versus the more vendor-friendly Apache license endorsed by the Eclipse foundation. In other words, it doesn't want vendors who license their offerings under conventional proprietary terms to make money by embedding JBoss.

More Stories By RIA News Desk

Ever since Google popularized a smarter, more responsive and interactive Web experience by using AJAX (Asynchronous JavaScript + XML) for its Google Maps & Gmail applications, SYS-CON's RIA News Desk has been covering every aspect of Rich Internet Applications and those creating and deploying them. If you have breaking RIA news, please send it to RIA@sys-con.com to share your product and company news coverage with AJAXWorld readers.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.