With so many Java developers enjoying their Mac OS X machines, JBoss Developer Studio is now available for Mac OS X. Product Manager Bryan Che writes:
… now you can get all the benefits of fantastic certified tools and an integrated JBoss Enterprise Application Platform with native Mac support. Many JBoss developers use Macs, and we know that many in our community use Macs, so we’re excited to make this available. And, of course, if you’re a Windows or Linux user, JBoss Developer Studio has been available for those platforms as well.
Bryan also explains why this release only supports Mac OS X Tiger 10.4.x until the next update:
… due to an issue in Eclipse, we are only supporting JBoss Developer Studio on Mac OS Tiger 10.4.x and earlier right now. There is a workaround available for Leopard, but this isn’t a supported configuration. We’ll add formal Leopard support in our next update.
RichFaces 3.2.0.GA is out, requiring JSF 1.2 and JDK 5.0 or above. A demo of new components is available, and the announcement includes a list of the new components, including Combo Box, Progress Bar, File Upload, and Pick List. Enhancements include DataTable Sorting, DataTable Filter, and standard component skinning.
The candidate release 2 of the JBoss Portlet Container project is available. This completes the first milestone for JBoss Portal 2.7, as Project Lead Julien Viet details. Following this, the 2.7 work is focused on integrating the controller module of the JBoss Portlet Container and providing a “JSR 286 Portlet runtime meta data overview through the administration portlet.” The project’s main JIRA page has a roadmap for 2.7.
In reference to the Portlet CR2, Julien writes:
Since the candidate release 1 we added an administration portlet that can manage the life cycle of the deployed applications and containers.
We have also added a very useful event debugger that can help developers to understand the event flow distributed among the different portlets during the interactions an event phase.
Mark Proctor at JBoss World on video talking about how Drools/JBoss Rules fits in to the SOA infrastructure handling business logic. While covering a lot of basics and ground, Mark provides a vision of a fully integrated and tooled platform that includes authoring, service side management, deployment, and a runtime:
Download this video: [Ogg Theora]
(Updated to include more details about the JBoss Portal 2.7 status.)
The post “Free of lock-in and open source — features that matter” presented information about why certain open source licenses were chosen for JBoss Developer Studio and that those licenses did not restrict the usage of the bundled Eclipse plugins by other Eclipse vendors.
Following that, I was contacted by JBoss Developer Studio project lead Max Rydahl Andersen, who corrected the post on licensing details.
His point is that the licenses chosen are more and varied than I posted, and were chosen specifically to allow maximum freedom. No licenses prevent their usage or forking by others, including other commercial versions.
From that discussion, here is a clearer picture of the mix of licenses:
JBoss Developer Studio is released under the GPL as a distribution, but that is not the license of all components. This is similar to Red Hat Enterprise Linux, which is overall under the GPL and many components within are different open source licenses.
The parts inside of JBoss Developer Studio are a mix of (mostly) EPL, LGPL, and ASL.. In specific:
The result is a 100% open source, vendor supported Java developer IDE without lock-in.
When JBoss Developer Studio was released, Darryl Taft, who writes an application development blog for eWeek.com, wondered, “Red Hat claims first place in the Eclipse open-source IDE stakes and I want to know why that makes a difference.” In the article, Darryl raises some difficult to understand points, such as equating the GPL to a lock-in license while misunderstanding the licensing of the plugins open sourced by Red Hat.
In trying to understand Darryl’s logic, I have read and re-read his short article. It leaves me with the question, does Darryl understand what open source is compared to closed source/proprietary software?
Almost as if in response to criticism that JBoss Developer Studio doesn’t matter, JBoss CTO and iconoclast Sacha Labourey spoke to JBoss.org to answer, Why JBoss Developer Studio, and why you should care.
While you can freely get all of these open Source plugins, what we have also done is released all of them in an easy-to-consume package that we sell as part of a subscription for $99. For that price, you not only get access to JBDS, but you also get access to our Enterprise Application Platform (EAP) as well as Red Hat Enterprise Linux. Essentially, for that price, you get everything you need to develop enterprise-grade applications, from the OS to a full EE-certified Application Server and complete tooling suite – we do not provide a laptop though
(Post updated with correct URL to the eWeek article.)
The long awaited JBoss Developer Studio was released:
We’re pleased to announce today the general availability of JBoss Developer Studio 1.0 for Windows and Linux. JBoss Developer Studio provides a certified open source development environment that includes and integrates:
- Eclipse
- Eclipse Tooling
- JBoss Enterprise Application Platform
Developer Studio provides a host of powerful features, such as Seam tools, powerful Ajax capabilities, a Visual Page Editor with WYSIWYG editing of JSF pages and RichFaces Ajax components, robust Hibernate capabilities and much more.
As Bryan put it in his version of that post, We’re not going to release Red Hat Developer Studio anymore. Introducing JBoss Developer Studio 1.0!. This product was originally called “Red Hat Developer Studio”, but “(d)uring the beta process, we found that it would be advantageous to leverage the powerful JBoss developer brand more clearly.”
Here’s what your $99 subscription gets you:
Our best news this week is the availability of a release candidate for Red Hat Developer Studio (RC1) (for Linux and for Windows). It is also the release candidate for JBoss Tools 2.
As with other parts of the Red Hat universe, these technologies are being developed neck-to-neck in the community before Red Hat/JBoss peels off a codebase to support for subscribers. At this moment, the codebases are the same. Here from the JBoss Tools announcement:
The major news in this release are Seam 2 and Mac OS X support plus a long list of bugfixes and enhancements. You can read more about the specific enhancements in the New and noteworthy pages.
Next step is GA
This release brings JBoss Tools very close to a final release, but to get there we are going to need help from the community to test out the release. If you haven’t already done so, please try out JBoss Tools and if you find any issues bring them up in the forum or open issues in JIRA.
As a bonus, Max’s blog entry has a demo movie showing the functionality of JBoss Tools/Red Hat Developer Studio.
By Jacob Orshalick
The concept of conversations has been popularized recently by a rush of frameworks providing more fine-grained control over state management. The age old issue of maintaining state throughout web interactions with a user has been a constant difficulty for developers. While the HTTP Session provides a manner of maintaining state between requests for a specific user, it is shared throughout the user’s interaction with the application. This can lead to hard to debug situations as data is shared between potentially unrelated sections of the application and is a constant source of memory leaks. Conversations offer an alternative to this approach that allows state to be scoped to a unit of work and automatically handles memory cleanup when a conversation is no longer in use.
Catching up on blogs from our various friends, we note Max’s post about the beta release of Red Hat Developer Studio:
http://www.redhat.com/developers/rhds/
This beta features all components, including installer, Eclipse 3.3, Eclipse Web Tools Platform 3.3, JBoss Enterprise Application Platform 4.2, and JBoss Tools beta 3. It is available for Linux and Microsoft Windows.
This interview is edited and republished from the original source.
A Dev Fu Interview with Andrew Overholt and Bryan Che
On 30 August 2006, Red Hat released version 3 of it’s Eclipse-based Red Hat Developer Suite of developer tools, the latest in a line of Red Hat Eclipse-based IDEs that goes back for several years. To find out more about the developer suite, what it does, how to get it, and why you’d want to we talked to Andrew Overholt, a Senior Software Engineer on The Eclipse Team, and Bryan Che, Product Manager for Developers at Red Hat. Here’s what they had to say.
This tip article has been edited and republished from its original location.
by Jeff Johnston
|
The Autotools plug-in is a Red Hat initiative to allow existing open source C/C++ projects to be maintained using the Eclipse CDT (C/C++ Development Tooling). The plug-in is previewed in the Red Hat Developer Suite (RHDS) 3 product. It extends the Eclipse CDT and adds features needed by C/C++ projects that use Autotools and have a configuration step. |
