Red Hat

In Relation To JBoss Tools

In Relation To JBoss Tools

JBoss Tools 2.0 GA goes final

Posted by    |       |    Tagged as JBoss Tools

We are releasing JBoss Tools 2.0.0.GA today! Downloads available here.

This is the first GA standalone release of our plugins that integrates the Eclipse plugins from what was formerly known as JBossIDE and Exadel Studio into one.

The combined works gives you first-class support for JBoss related technology and an unprecedented development environment for JSF and Seam. All the tooling is well integrated with JBoss technologies but we are not limited to that. All the functionality will work standalone and with other application servers.

Main feature highlights are:

  • First-class support for JBoss Seam 1.2 and 2.0
  • Visual Page editor for rich editing of (X)HTML, JSP, JSF and Facelets pages
  • Unique JSF and Facelets support
  • JBoss AS server integration
  • Project Archives
  • Hibernate 3 Support
  • JBPM support

...and more! All available for Linux, Windows and Mac

Getting started

The reference documentation are available at docs.jboss.org

What's New and Noteworthy plus some screen casts are also avaible on the Seam and Project archives features.

Upgrade from previous versions

If you are an JBossIDE user then you should be able to easily upgrade.

If you used JBossIDE Packaging you can either continue to just run the /packaging-build.xml/ directly or to migrate the related projects to JBoss Tools archiving. We have provided a migration script here and you can read more about the JBoss Tools archiving in a previous blog entry.

If you are an Exadel Studio user then you will find an migration guide here.

What is the difference between JBoss Developer Studio and JBoss Tools

This release of JBoss Tools is what went into our JBoss Developer Studio which provides an easy-to-install Eclipse based IDE fully configured and ready to run with the bundled JBoss Enterprise Application Platform.

In short JBoss Tools are just a set of Eclipse plugins and JBoss Developer Studio adds:

  • An installer
  • Eclipse and Web Tools preconfigured
  • JBoss EAP with JBoss AS and Seam preconfigured
  • 3rd party plugins bundled and configured
  • Access to RHEL and Red Hat Network
  • Access to the JBoss/Red Hat supported software

It is available for existing support customers or under a 99$ subscription which you can read more about here.

Feedback

As always your feedback and questions are very welcome in our forum and if you have found an issue or feature request then please report that in our jira.

Enjoy and Merry Christmas ;)

JBoss Developer Studio 1.0 released

Posted by    |       |    Tagged as JBoss Tools

I'm proud to report that we released JBoss Developer Studio 1.0 (formerly known as Red Hat Developer Studio) earlier today.

The feature highlights of the Developer Studio are:

  • Out-of-the-box configuration of Eclipse Web Tools, JBoss EAP incl. Seam
  • JBoss Tools 2.0.GA included
  • Visual Page editor for rich editing of (X)HTML/JSP/JSF/Facelets pages
  • JSF support
  • First-class support for JBoss Seam 1.2 and 2.0
  • Hibernate 3 Support
  • JBoss AS server integration
  • Exploded deployment for fast turnaround times during development
  • Start/Stop/Run/Debug of JBoss AS 3.2 to 4.2
  • Project Archives
  • Easy and fast incremental packaging of your project layout and deployment (not bound to WTP nor JBoss)
  • JBPM support
  • Spring IDE included
  • TestNG plugin included
  • Available for Linux and Windows

...and more!

JBoss Developer Studio (JBDS) is JBoss and Red Hat's Java developer offering where you for 99$ gets access to an easy-to-install Eclipse based IDE fully configured and ready to run with the bundled JBoss Enterprise Application Platform 4.2.

The advantage is that you get access to the fully supported JBoss binaries and that you after the download get a no-fuzz installation and everything is ready to run out-of-the-box.

Furthermore you get entitlements to Red Hat Enterprise Linux (RHEL) and other Red Hat software. Please note that Developer Studio is cross-platform and is available for Windows and Linux today and we plan to have a Mac OS X available in the new year.

Read the details about the offering here.

p.s. I'll be back later this week with details about JBoss Tools 2 GA (currently under the mercy of the JavaPolis network gods :)

Fast and incremental packaging in JBoss Tools

Posted by    |       |    Tagged as JBoss Tools

One of my favorite feature in JBoss Tools is the Project Archives which provides automatic and incremental archiving of arbitrary directories into a zipped archive (jar,zip,war,etc) or into an exploded directory. Usable for any development that wants hot and/or exploded deployment.

A screen cast is available at docs.jboss.org, but if you want the details read the following...

Project Archives View

To start using it you open the Project archives view, select a project and right click in the view to add the type of jar you want (each project can have multiple archives defined).

In the dialog that comes up you specify what the name of the archive should be, where it should be located and whether the folder should be archived/compressed or exploded.

The tools will dependent on the archive type and project files give a best-guess on which files you would like to include in the archive. You can of course customize this freely afterwards.

When you have pressed Ok, you will be able to see the resulting archive or folder in Eclipse or if you configured it to go the file system use your favorite file browser to see the result.

Automatic Incremental packaging

When first defined through the Project archives view JBoss Tools will automatically monitor changes and keep the archive or folder in sync. Since the changes and archiving is done incrementally there are no need to wait for Ant or Maven to collect the various artifacts and do a full archiving.

I suggest watching the screen cast to get a sense of how easy and fast this works.

Exploded jars

The exploded archive support allows you to use this with any server that supports what is called exploded deployment (commonly used with many Java and non-java servers) - thus this is in no way limited to JBoss servers or even Java technology; any technology that needs to copy a set of files to a directory or archive will be able to benefit from this feature.

What about JBossIDE packaging ?

JBossIDE 1.x had a similar feature which relied on generating an ant script and execute Ant to do the actual packaging.

The advantages of the new Project Archives is that it does not wait for a launch of Ant and instead of doing a full build/repackaging of a compressed archive every time, we can now do it incrementally and with the option of exploded form.

To migrate from JBossIDE packaging to JBoss Tools archiving you can use the conversion tool which we made available at download.jboss.org.

The conversion is as simple as:

java -jar packaging-converter.jar /path/to/.packaging

Ant and Maven

To avoid specifying how packaging works twice, once in JBoss Tools and once in your favorite build system we added an ant task to allow you to use it externally from Eclipse.

The following is an example of how that is used:

<property name="studio.home" location="${eclipse.home}/../studio/eclipse"/>

 <path id="generate-archives-classpath">
  <fileset dir="${eclipse.home}/plugins">
   <include name="org.eclipse.equinox.common_*.jar"/>                                    
  </fileset>
  <fileset dir="${studio.home}">
   <include name="plugins/org.jboss.ide.eclipse.archives.core**/archivescore.jar"/>
   <include name="plugins/org.jboss.ide.eclipse.archives.core**/lib/*.jar"/>         
  </fileset>
</path>
                 
 <taskdef name="generate-archives" classpathref="generate-archives-classpath"       
classname="org.jboss.ide.eclipse.archives.core.ant.GenerateArchivesTask"/>
         
<target name="run-packaging">
 <!-- each project needs to have their root dir defined when running outside eclipse -->
 <property name="pojp.dir" value="C:/Users/max/workspace/pojp"/>
 <generate-archives projectPath="C:/Users/max/workspace/pojp"/>
</target>

Final words

Thanks goes out to Rob for showing me how the Ant task works and for Marshall to get the conversion script ready. We hope to integrate that more directly into JBoss Tools in an upcoming release.

If you want to see this in live action look me up at JavaPolis next week (in the JBoss/Red Hat booth).

JBoss Tools Screenshots

Posted by    |       |    Tagged as Java EE JBoss Tools Seam

To celebrate the new release of JBoss Tools, I'm going to walk through some of the features of JBoss Tools that are interesting to Seam developers.

There are two perspectives that are of interest for people using Seam: the Seam perspective and the Hibernate perspective:

The Seam perspective features some very useful wizards in the New menu:

The first thing you'll want to do is create a Seam Web Project, by following the wizard:

Next, create a Seam Action:

All Seam components are easily accessible from the Seam Component View:

Even better, they're autocompleted whenever you start typing an EL expression:

Even property names are autocompleted (JBoss Tools is even smart enough to understand generic types!):

We can run our application from the Run menu, or from the Servers View. JBoss Tools automatically deploys changes incrementally, a /big/ improvement over the Ant-based solution used in seam-gen:

The most impressive feature of JBoss Tools is the visual page editor, which does a great job of previewing complex Facelets pages with RichFaces controls, standard JSF controls and even Facelets templating:

Of course, autocomplete and hyperlink/F3 navigation to Seam components and Seam component properties also works in the visual editor:

There is a visual editor for web.xml:

And one for components.xml:

Autocomplete and hyperlinking/F3 work here too:

If we use Seam Generate Entities, we can reverse engineer an application from a database schema, or from existing entities:

And, switching to the Hibernate Perspective, we can browse the entities via a treeview:

Or via a full visualization of the mapping:

back to top