"The Cloud" is many things to many people, but in the example he is showing off how to use JBoss Tools server adapter together with the new Delta Cloud tooling to deploy to a server running on Amazon EC2. blogs
I've embedded the video he did into this blog posting, but Andre's blog contains more details on how you can do this your self - such as configuring the right ports on Amazon EC2 and example image names/id's to try this out with.
This screencast primarily shows off the current integration between Delta Cloud + JBoss Tools Server adapter + EC2 Images made by Marek Goldmann; images which anyone can use or create on their own as outlined in the screencast - and when they are done its like deploying against your own local server in the cloud.
We will be posting a demo showing off some of the other improvements that have been made in the latest JBoss Tools 3.2 release allowing for even more flexible deployments to a server (JBoss and others).
Next month at EclipseCon I'll be continuing the saga of the Graph Editor. This story actually starts back in 2005, when I was working on the very first graphical editor for jBPM 3. I was using the Eclipse Graphical Editing Framework (GEF) and became very frustrated with the lack of good documentation. So for my own records, I kept notes as to how the application was put together. The result served as the base for a number of talks and tutorials on GEF at the EclipseWorld (2005, 2006 and 2007) and EclipseCon (2006, 2007 and 2008) conferences. Should you be interested, I have attached the last version of this tutorial that I presented at EclipseCon 2008.
In the meantime, two other frameworks have emerged in the Eclipse realm that can be used to create such rich graphical editors. The Graphical Modeling Framework (GMF) has been around for a very long time even and is well matured. It builds on top of GEF and the Eclipse Modeling Framework (EMF). It also has a powerful tools suite that can be used to quickly model and generate your application. Graphiti is a bit more recent and is currently in incubation at Eclipse. Graphiti also builds on top of GEF and uses EMF to store its graphical details. EMF is also the preferred way to serialize the semantic model.
During the previous year, I have been using GMF intensively while forging a prototype BPMN2 editor for jBPM 5. Later that same year I was asked to investigate Graphiti as a candidate technology for a BPMN2 editor. Just like 6 years ago, I have kept notes on the use of both of these technologies. It was only a small step to turn these notes into a presentation comparing both technologies. So I am happy to have been accepted to share this experience at the upcoming EclipseCon conference.
If you expected to see the results of the comparison in this post, I'll have to disappoint you. I will probably write up an article later on but in the meantime I'll leave the scoop to the EclipseCon attendees. The advice is to register for EclipseCon and attend my session on Tuesday March 22nd at 2:30 pm. I hope I will see a lot of you!
I'm very happy to be able to announce that we pushed out JBoss Tools 3.2 to the servers shortly before the weekend.
Existing Eclipse Workspaces used with JBoss Tools 3.1 will work with JBoss Tools 3.2, but do take a backup of your workspace to be on the safe side.
As per tradition the updatesite is now moved over to a stable location
To "upgrade" from JBoss Tools 3.1 to JBoss Tools 3.2 you need to install Eclipse 3.6 and add the updatesite. Updating Eclipse major versions via updatesite does sometime work, but we do recommend a clean install to make it all a bit cleaner.
If you don't like messing with updatesites you can also install JBoss Tools 3.2 via Eclipse Marketplace - simply use Help > Eclipse Marketplace directly from Eclipse and find JBoss Tools 3.2 (Helios) via the Search facility.
The following paragraphs outlines the highlights from the JBoss Tools 3.2 release, but I recommend reading the complete
What's New lists if you want to see all the noticable changes and improvements that have been made since JBoss Tools 3.1.
The Visual Page Editor and our XHTML structured editors now supports JSF 2; especially the notion of composite components which is a new feature of JSF 2 allowing users to much easier define reusable components for their application or framework.
JSF 2 also provides a new standardized approach to load up resources via the classpath and web archives; these are all supported by JBoss Tools making the visual page editor render even more realistically the layout of the page but also code completion, navigation and even quickfixes now benefit from this additional information to make it easy to fix issues and navigate to the linked resources instantly.
The CDI tooling have received a lot of updates, especially in context of providing validations of all the error handling cases covered by the CDI TCK test suite and a few other hints provided by the Weld CDI Team.
There is also a good set of wizards, code navigations and quickfixes added in this release and I recommend you go read Alexey Kazakov's blog about this feature set.
Besides supporting JSF 2 better in this release various other improvements were done to the Visual Page Editor.
The biggest new feature for the Application Server integration in JBoss Tools 3.2 is the introduction of Remote Deployment.
Remote Deployment works (more or less) just like the Local deployment except instead of using local file copies we now relay the file transfer to the Eclipse Remote System Explorer API; this then allows you to deploy to systems via SSH, FTP, etc.
This Remote Deployment not only works for the JBoss Application Server adapters but is also provided via the "Deploy Only" server meaning you can use it to deploy any project to any application server or system which supports hotdeployment by scanning their local file system for changes.
We've also improved support for "non-WTP" style projects by enabling you to right click Folders and mark them as Deployable. These deployable folders can then be deployed to any of the Server adapters provided by JBoss Tools, including the Deploy Only server.
The JBoss Server Adapter now also supports the new JBoss 6 and updated versions of JBoss Enterprise Application Platform based servers.
One of the big hassles of any IDE configuration is to identify and configure your various runtimes, such as JBoss Application Server, Seam, jbpm, ESB, Drools, JDK's etc.
We've contributed the installer logic from our JBoss Developer Studio 4 product into the actual JBoss Tools plugins and enhanced it so it can be configured to scan one or more directories at startup for new runtimes; if it detects a new runtime it will ask if it should add it and JBoss Tools will do a default installation of the runtime - freeing you from having to go through the various runtime user interfaces.
This feature is available under Eclipse Preferences in JBoss Tools > JBoss Tools Runtime Detection
In the future we plan to add more runtime detections, not just JBoss based ones.
Google's Eclipse plugin for GWT does not provide seamless integration with Eclipse WTP based projects; thus we made an Eclipse Facet that allows you to easily enable Google GWT on your WTP project and not having to use custom wizards and special projects to get started with the Eclipse GWT tooling.
Please note that since Google are not providing stable named features from their updatesite to have Eclipse updatesites work together, it is necessary to install Google GWT plugin manually before trying to use our Google GWT facet.
See Andre's article on how to use this Google GWT feature.
The tooling for Delta Cloud provides a perspective and a few views to easily interact with systems such as SteamCannon that provide a DeltaCloud API.
This gives you the ability to browse, start & stop virtual machines hosted by cloud service providers such as EC2 and Rackspace.
You can try it out by using https://try.steamcannon.org/deltacloud/api as the URL for a Delta Cloud connection.
Note, DeltaCloud tooling is marked experimental while the DeltaCloud API and implementations are stabilizing. If needed we will provide an update to support the latest/stable DeltaCoud servers.
We've continued to expand the support for Maven projects by extending m2eclipse tooling to automatically configure projects based on the dependencies of your project.
Thus now if you import or configure a Maven based project and it uses a standard dependency for either Seam, CDI, JSF, Hibernate or GateIn/Portal the features for these frameworks will now be enabled and configured automagically.
You can control this per framework under Eclipse Preferences via JBoss Tools > JBoss Maven Integration
To see an example of this applied, look at Snjezana's blog where she illustrate how via Project Examples you can easily get started with the CDI and JSF tooling. This blog works because of the Maven Integration provided here.
Modeshape provides a JCR based view on many different datasources such as file systems, databases, other JCR repositories and even your own services and applications.
The Modeshape tooling provided in JBoss Tools 3.2 gives you a way to easily connect to a Modeshape server, browse it content and checkin/checkout content from and to the Eclipse workspace.
The Teiid Designer that is used to visualize model your datamodel and transformations as supported by the Teiid runtime is now included into JBoss Tools.
The Teiid Designer plugins also provides a testbed for testing and exploring your Teiid configured dataservices.
You can read more about Teiid Designer on its community page.
The BPEL tooling is based on the Eclipse BPEL project but provides a set of bugfixes and features that have not yet made it back to the Eclipse BPEL project, especially in context of supporting deployment to other systems than Tomcat based systems such as Apache ODE. We support the Riftsaw JBoss based BPEL system.
If you want to read about the BPEL feature set and its future (its fixes are being contributed back to Eclipse.org) you can read Bob Brodt's blog about this.
We've added some much simpler wizards for creating JAX-RS or even JAX-WS webservices to the tooling; but even more interesting is the new Webservice Tester UI which gives you a view to easily query a SOAP or REST based webservice and introspect its result.
When you install a JBoss Tools plugin, on the first startup of Eclipse a dialog will ask if you wish to send anonymous usage data to us. We use that information to see which OS's, system configurations and plugins you are running plus we get to see how fast (or slow) new versions of spreads over the world.
The above highlights are just a subset of the over 1600 issues fixed and implemented over the last many months thus the best way to get to know it all is to try it out
Let us know how it goes and above all,
JBoss Tools includes the JBoss Maven Integration and Weld feature that enable you to quickly and easily start developing Weld applications.
The best way to install JBoss Tools including the JBoss Maven integration is to start with Eclipse Java EE IDE for Web Developers.
What you then need to do is download appropriate archive for your OS, unpack it and start Eclipse.
Call Help>Install New Software..., click the Add button and enter the following update site:
Choose All JBoss Tools 3.2.0 and Maven Support
Click the Next button, accept the license terms and click the Finish button.
Click the OK button on the Security Warning dialog.
and the Restart Now button on the Software Updates dialog.
You have installed JBoss Tools, the JBoss Maven Integration and all required dependencies.
You can perform the following steps to install the JBoss AS 6.0 Server:
Download JBoss AS 6.0.0.Final and unpack the archive to some directory.
Call Window>Preferences>JBoss Tools>JBoss Tools Runtime Detection
Click the Add button and point to the directory where you unpacked the JBoss AS 6.0.0.Final.
Click the OK button.
The JBoss AS 6.0 Server is created.
In order to install this example you need to call Help>Project Examples
Select Weld JSF login example and click the Finish button.
You will then get the weld-jsf-login application in your workspace.
If you are interested in more info on this example, see Weld 1.1.0 Reference - Chapter 3. JSF web application example
The following procedure demonstrates how to deploy and start this application:
As a result, the weld-jsf-login application will be deployed and executed on the JBoss AS 6.0 server.
The application includes the JBoss CDI and WTP JSF feature.
The following examples can be created in a similar way:
We're getting ready to merge the JBoss fork of the BPEL Designer code back into the eclipse.org repository. This will include many bug fixes and a few enhancements. The merge should be complete by the end of this month, so stay tuned.
Some new things are in the works for the BPEL Designer at eclipse.org. Vincent Zurczak, one of our committers, has been thinking about how to improve the user experience. Please have a look and let us know what you think.
I've seen two major releases of JBoss Tools in my year and a half at JBoss/Red Hat. In that time, the many talented folks we have working on tooling have developed new tools and updated existing ones. Functionality has been added just about anywhere you look in the tooling.
As such, I want to call out just a few of the areas we've made progress in for JBoss Tools 3.2...
First, the ESB Editor gained support for new ESB 4.9 functionality including BPELInvoke, new methods for creating ESB actions via annotations, and Camel ESB integration. And the team also added a first cut at better validation of ESB configurations to help make sure files will will work before they're deployed.
Next, there's the great BPEL Editor work that Bob has already mentioned here
Beyond that, I have to say that I'm happy with the work we've done on the Web Service Tester that's been added. I know Bob uses it for testing web services used in BPEL processes and Lukas has used it extensively in QE. More feedback would be great, but I'm happy with where we are for a first release! You can read more about the WS Tester here.
And I'm also happy with some of the new Web Service wizards we've introduced for bottom-up WS development in this release. Though the WTP Web Service wizard works, it's not the most user friendly beast in the world and it's also not the easiest framework to extend. As such, we reused a few chunks that we'd written and found ways to present a simpler approach for developing web service artifacts for existing annotated classes.
We integrate with JBossWS and JAX-WS annotated classes and we even integrate with RESTful services if you have RESTEasy installed. So hopefully these will help you get work done a bit faster than before. You can read more about these new wizards here.
So there you have a few of the areas we've worked on for this release. As always with JBoss Tools, this is just the tip of the iceberg so be sure to keep an eye out for posts celebrating functionality in other areas!