Skip navigation
1 2 3 4 5 Previous Next

JBoss Tools

71 Posts authored by: maxandersen

http://community.jboss.org/servlet/JiveServlet/showImage/38-2030-10503/earlyaccess.pngThose interested in trying out our milestone builds of JBoss Developer Studio 5 can now do so from our Early Access Site.

 

JBoss Developer Studio 5 is the next version of our Eclipse based IDE targeted for development on JBoss supported platforms.

This version of Developer Studio is based on JBoss Tools 3.3. We've not included every plugin from JBoss Tools but the plugins we found ready to bundle into Developer Studio. As we go towards the final version we will evaluate which plugins will make it in based on our own QE and your feedback.

 

This milestone, we've focused on migrating to Eclipse 3.7, JBoss AS 7/EAP 6 support and separated out the SOA tooling so JBoss Developer Studio 5 will not include Teiid, jbpm, drools, ESB and Smooks by default - these are planned to be available from our Extra's updatesite going forward.

Installation

As last time there are two versions available, one with JBoss Enterprise Application Platform for developer use bundled and one without.

 

Please note that currently we bundle JBoss Enterprise Application Platform 5.1, but we will be moving to bundle JBoss  Enterprise Application Platform 6 when that becomes available.

 

The bundled version, requires registration via this form, but the unbundled version of JBoss Developer Studio 5 is available for free download.

 

Once you have downloaded the jar installer, you simply run it by double-clicking the jar (if your setup supports it) or run the following from the commandline:

 

java -jar <devstudio-installer-path>.jar

 

Then the installer will ask you a few basic questions and it will install JBoss Developer Studio 5 from which you will be able to start developing instantly.

Feedback

Instructions on how and where to give us private feedback for this early access is available here and otherwise we are listening in our public forums too

jbosstools_as7_logo.png

3.3 M2 (Rabbit Chaser)

[Download] [Update Site] [What's New] [Forums] [JIRA] [Twitter]

 

We've worked around the speed bumps I talked about last time, and can now announce the release of JBoss Tools 3.3 M2, the first milestone that will work with Eclipse 3.7 "Indigo" and the just released JBoss "White Rabbit" AS 7 CR 1.

 

Note: Since this blog was written, AS 7 Final was released and is now available and works with JBoss Tools 3.3 M2 and higher!

 

JBoss Tools is a set of plugins for Eclipse that complements, enhances and goes beyond the support that exist for JBoss and related technologies in the default Eclipse distribution, in this release we are especially moving the AS 7 and CDI/Solder integration forward.

Installation

 

First off, go download & Install Eclipse 3.7 (Indigo) JEE bundle - you can use some of the other bundles too, but with the JEE bundle you save bandwidth and you'll have less problems getting the right dependencies.

 

Once you have installed Eclipse, you use our update site directly.

 

The updatesite URL to use from Help > Install New Software... is:

 

http://download.jboss.org/jbosstools/updates/development/indigo/

 

Important: If you are running on recent released Linux distributions or 64-bit distributions you might be bumping into an Eclipse 3.7 regression bug that prevents the visual page editor to load and result in a hard crash of the visual VM. To avoid this problem you can run eclipse with a property to disable the visual page editor.

 

eclipse -vmargs -Dorg.jboss.tools.vpe.loadxulrunner=false

 

Alternatively you can try using 

http://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/swt.xulrunner.patch

as updatesite to install temporary SWT patch that works similar to the planned Eclipse 3.7.1 patch.

 

Where are my SOA Tools ?

We are working on splitting out the SOA functionality (Teiid, Modeshape, Drools and jbpm) from the core distribution since the SOA tooling historically are not following the same release cycle of the core and thus at times it is beneficial that they can release their final version a bit delayed from the core. That means that for this milestone the main updatesite does not contain SOA tools but will for now be on a separate updatesite.

 

JBoss Tools - SOA Tooling updatesite:

 

http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooling/

 

The final layout and distribution mechanisms might change as we collect feedback, but for now SOA is separate from the core.

 

JBoss Application Server 7

This morning JBoss AS 7 CR1 was released and JBoss Tools are ready to support it. The best way I can imagine showing what this means is by giving you this very short screencast showing how easy and fast AS 7 is and how easy it is to use when using from JBoss Tools.

 

 

 

Another additional new feature for this release is the option named "Do not exectue startup or shutdown commands".

 

dont-execute-start-command.png

This option allows you to start and stop your server outside of Eclipse but still be able to use the deployment, debugger and Run As.. features.

Ideal for when you want to run your own custom startup scripts and maybe even more interesting for remote servers where the server might be started/stopped by service scripts instad.

 

JAX-RS

Xavier Coulon contributed JAX-RS standard tooling to JBoss Tools shortly after M1 and I'm now very proud to include it in this milestone.

Xavier will be blogging about this shortly but in short it provides a explorer to navigate your JAX-RS resources and it comes with basic validation and code completion related to JAX-RS.

 

jaxrs_explorer.png

 

The tooling will evolve more over the upcoming milestones/betas; if you have input/questions we are very interested in hearing about it.

Context & Dependency Injection (CDI)

For this release the Seam Solder support is more complete by adding support for @Generic beans which is used by most Seam 3 and many CDI extensions out there to customize their framework CDI integration. This allows JBoss Tools to be more precise in its validation but also to provide better and improved content assist and navigation for CDI components.

 

Other extensions like Seam Config also got improvements and we now provide better validation of the Java backed schemas in the XML file format for CDI.

 

seam_config_validation.png

Maven & AS 7 Quick Starts

With the release of Maven Integration For WTP (org.maven.ide.eclipse.wtp) 0.13 a few days ago Maven works even better now together with Eclipse WTP projects - in particular, there are fixes concerning having manifest and other descriptors generated by Maven according to pom.xml and  much better handling of classpath which make this a huge improvement over previous versions.

 

On top of these enhancements we've added further automatic configuration of your projects based on your pom.xml and its dependencies making it super easy to import existing Maven projects using technologies like JSF, CDI and Hibernate.

 

This all is coming together with the AS 7 CR 1 release which comes with a set of Quickstarts and archetypes.

Both the quickstarts and archetypes will automatically get configured when you import them to have all the JBoss Tools enhancements ready for you to use.

 

Give them a try.

 

And more...

There are a bunch of other improvements in this release and you can see descriptions and screenshots in What's New

 

Over the next few days/weeks we will be blogging more about the new features and usecases this release of JBoss Tools and AS 7 enables.

 

Feedback

As always we crave for any feedback you can give, especially if you have a project that causes performance issues or wrong validations. We've done a lot of work testing but we are sure we haven't covered all possible combinations - if you find something we missed let us know!

 

Thanks, and now go chase that White Rabbit! with JBoss Tools!

 

Have fun!

Update: JBoss Tools 3.3 M2 have been released that targets/supports Eclipse 3.7 making this blog out-of-date!

In about 24 hours or so Eclipse Indigo are going to push out their Indigo release train and its many users will bring all the Eclipse mirrors to a halt for the coming days.

 

The yearly release of Eclipse always generates alot of questions concerning if JBoss Tools will run on the latest and greatest version just released and i'm writing this blog so those that go look will have an answer.

 

The short answer is that you can use JBoss Tools 3.3.0.M1 release with Eclipse 3.7M6, last minute API changes makes it so you will see errors

if you try run M1 on Eclipse 3.7 final. If you really really want to to use Eclipse 3.7 final you can use our nightly build updatesite on your own risk but I do recommend you wait until we have JBoss Tools 3.3.0.M2.

 

We were planning on releasing on the same date as Indigo, but we have hit a few speedbumps on the last weeks of release lockdown making it so we will miss the Indigo release train.

 

The speed bumps is the release of JBoss AS 7 release candidate to be sure our new AS 7 Server adapter integration will work smoothly and we needed to implement a workaround for a hard-to-track regression issue with Eclipse SWT and XulRunner which causes crashes on newer Linux distributions.

 

We expect to have these fixed this week and expect to release JBoss Tools 3.3.0.M2 shortly there after.

 

I'll update this blog when release details becomes available.

 

Have fun!

Eclipse 3.7 is coming out soon and we are happy to deliver the first milestone of JBoss Tools targeting the upcoming Eclipse Indigo release.

 

http://in.relation.to/service/File/10824

3.3.0.M1 (Forge On!)

[Download] [Update Site]  [What's New] [Movies] [Documentation (not updated yet)]  [Forums]  [JIRA] [Twitter]

 

This is a development release in its true form which requires Eclipse 3.7 M6 to run.

 

If you use Eclipse 3.7 M7 things will install, but there have been API changes between M6 and M7 so please follow the installation instructions below very carefully to avoid problems.

Installation

Read this very carefully - if you don't follow this you *will* have problems running this milestone since Eclipse 3.7 M7 is not compatible with Eclipse 3.7 M6.

 

  1. Download & Install Eclipse 3.7 M6a (Indigo) JEE bundle.
  2. Run and add this URL to Eclipse's list of available update sites:
    http://download.jboss.org/jbosstools/updates/development/indigo
  3. Disable all other URL's except that URL and this
    http://download.jboss.org/jbosstools/updates/indigo/M6/
  4. Now go and install the JBoss Tools components you want from the JBoss Tools updatesite

 

Step #3 is the important one - this prevents P2 from overriding your M6 installation with M7 updates.

 

This Jira explains the details for this with screenshots if the above text is causing problems.

 

New & Noteworthy

The biggest change is for this release is definitely the Eclipse 3.7 compatiblity but besides that and a bunch of bugfixes and minor improvements we have more than a few exciting new features in this release.

 

JBoss AS 7

 

This release introduces a server adapter which allows you to start/stop/debug and deploy applications to JBoss AS 7 via the file system.

 

If you haven't tried out JBoss AS 7 now is the time - it starts a in approximate 3 seconds; it's like night and day compared to previous AS versions.

 

CDI/Seam Solder

The CDI tools have added additional features and bugfixes, but most importantly we now support components based of Seam Solder allowing us to pickup and identify CDI and Seam 3 components that uses the Seam Solder extensions. i.e. we will now honor the Seam Solder annotation @Veto to ignore otherwise valid CDI components.  The full list of supported annotations from Seam Solder so far is:

 

  • @Veto
@Requires
@Exact
@MessageLogger
@MessageBundle
@DefaultBean
@Unwraps
@ServiceHandlerType
@FullyQualified
@Resource

 

In addition to support Seam Solder annotations we also support components defined in Seam Config providng an Seam Config aware XML editor and pickup components defined and configured via XML in additon to annotations.

 

Forge Tools

Our Forge Tools which are integrating Seam Forge into the Eclipse IDE is now bundled in JBoss Tools and allows you to use Seam Forge out of the box from inside Eclipse.

 

Seam Forge is core framework for rapid-application development in a standards-based environment; it provides a command line style shell for rapid scaffolding style development. The special thing about Seam Forge is that the motivation behind it is to support standards such as Java EE, CDI and JPA in addition to common defacto technologies such as git and maven.

 

In its current release it allows you to easily create CDI based applications based on scaffolding principles as known

from tools like seam-gen, ruby-on-rails, grails etc.

 

This first release of Forge Tools are focusing on bringing the command shell experience directly available in Eclipse as a console so you can

interact directly with Forge meaning you can execute and run Forge commands directly from IDE and as an extra nice bonus it imports and open projects you have created via the shell. It allows you to use the power of command line shell's together with the visual and integrated developer environment.

 

Koen made a very nice video of all this in play which I've embedded here below. You can see the details of what is shown in the

demo on his blog.

 

 

Maven

 

What you might not notice in this demo is that it is using m2e/wtp and the JBoss Tools specific m2e configurators behind the scenes to

automatically have the related plugins for the project automatically configured based on the Maven metadata instead of you having to manually configure and setup the tools.

 

In upcoming releases of JBoss Tools you will see even tighter integration with Seam Forge and with Maven to make you even more productive in working with JEE 6 based technologies.

...and more

The new and noteworthy provides a short overview with screenshots of the various improvements made in JBoss Tools extensive plugin set.

Next Steps

This release is mostly to get feedback on any issues found in Eclipse 3.7, and to introduce some of work that we are doing to provide a faster and more developer friendly developer environment than ever before - this includes Forge Tools and AS 7 for now but we will also focus on making tools such as Maven easier and faster to use.

 

We've already contributed several patches to m2e which makes it up to 5 times faster in importing and updating project configuration - these improvements will be available soon from our nightly build site if you can't wait

 

JBoss Tools 3.3 will also continue to make it easier to configure and install JBoss and other runtimes and frameworks to allow you as developer to focus on the code instead of the configuration - at least upfront.

 

We also have a few other ideas, but we'll save that for some future blogs

 

Do remember though that we really appreciate feedback on wether the functionallity is helping you, if it is going in the right direction and if you have ideas for improvements or even patches.

 

We are listing and reacting in both forums, jira, twitter and irc.

 

Enjoy this milestone - remember to read the installation instructions careful! and...

 

Have Fun!

JBoss AS 7 is still being developed on but lately file based deployment is now in place and I thought it would be a good thing to tell you how you can use JBoss AS 7 from our tools even before there is an optimized and fully supported server adapter for it.

 

It's not optimal, but at least it lets you get started.

 

For this blog I used JBoss AS 7 Beta 2 and JBoss Developer Studio 4; you can use a newer version of AS 7 (beta 3 is coming out soon) or if you have JBoss Tools 3.2.0 installed all this works fine too from there.

 

Read more below.

Start/Stop of AS 7

For now the best way to start/stop AS 7 when working from Eclipse is to simply start and stop it from a command line.

 

Start:

$JBOSS_HOME/bin/standalone

 

Stop:

Press Ctrl+C in your terminal/command prompt

 

You can start AS 7 via Eclipse External Tools support but Stopping won't work since it will only stop the shell script not the actual running AS 7 instance. Thus for now - use the command line.

Deployment to AS 7

If you have a standard Eclipse Web Tools Project style project then the simplest is to use the Deploy Only server, if you have a free-form project you can also use Deploy Only server but maybe Project Archives gives you a better workflow. I'll outline the "Web Tools" and Project Archives approach below:

 

Create a Deploy Only Server

The "Deploy Only" server is available in JBoss Tools & Developer Studio and provides a server adapter that has no special knowledge about the server it is deploying to beyond a directory location. Thus this is perfect for using with servers that does not yet have direct support from within Eclipse.

 

To create one you simply hit Ctrl+N or use File > New > Other from the menu and find the Server wizard.

 

define_new_server.png

Within the Server wizard you need to find and select the "Deploy Only" server:

newserver_deployonly.png

Press "Next", and then give your server a name and specify the directory location for deployments.

 

deployonly_deploydirectory.png

For AS 7 standalone deployments goes to $JBOSS_HOME/standalone/deployments.

 

Press "Finish" and you should now have your "AS 7" server available in the servers view:

 

as7_serverview.png

Now you have a "Server" which you can deploy standard Web tools projects to; you simply drag'n'drop deployable resources to the server or use the "Add and Remove" available in the context menu.

 

Enable Compressed Archives

There is one "gotcha" with this setup and that is that with AS 7 for exploded deployments it now requires a .dodeploy marker to explicitly trigger a (re)deployment of an exploded directory.

 

The simplest way to avoid having to set this up is to enable "Compressed Archives" from within the tools since AS 7 will automatically deploy such archives once they are complete.

 

To enable this, double click the Server and it's server editor should show up.

 

enable_compressed_archives.png

In this editor, switch to the Deployment tab and make sure there is a checkmark for "Deploy projects as compressed archives".

 

With this done you can now easily add any war/jar/ear project to the server and deploy it.

as7_helloworld.png

Above I've added a project called "helloworld".

 

To deploy or redeploy this simply right click the server and choose "Publish" (you can also use the keyboard shortcut shown in the menu for easier access).

 

publish.png

 

Exploded and Explicit Deployments

If you really want to use exploded deployments then there is a trick you can do to simulate the .dodeploy marker with JBoss Tools.

 

 

Simply create a text file in your project called "foo.war.dodeploy" where foo.war should the name of your deployment. In my case that is "helloworld.war.dodeploy".

dodeploy_file.png

Then right click this file and choose "Mark as Deployable"

 

markasdeployable.png

This should then automatically get deployed to your sever (if you have multiple there will be a dialog asking you which server to deploy to)

dodeploy_in_serverview.png

If you don't know what a "dodeploy marker" is look in the README.txt in $JBOSS_HOME/standalone/deployments for an explanation.

 

Please note that Deploy Only server currently does not support automatic publishing thus you have explicit invoke Publish when you are ready.

 

This will be fixed in upcoming release of JBoss Tools 3.2.

Deploy using Project Archives

Project Archives is mostly relevant for those not using Web Tools style projects, but is also usable for deploying to AS 7 - the feature is already documented and even with a screencast in a previous blog

 

Please, Make this easier!

We are working on it and the first steps of an AS 7 adapter is already in JBoss Tools trunk which will be JBoss Tools 3.3 and target Eclipse 3.7.

If you are interested in that work ask on the forums where we will keep you updated with the progress, i.e. when there will be an updatesite to install and use from

Note: JBoss Developer Studio 5 is now available, see https://community.jboss.org/en/tools/blog/2012/06/21/jboss-tools-33-and-developer-studio-50-final-release

 

JBoss Developer Studio 4 is now avaliable for free (registration required) from http://devstudio.jboss.com/download/

 

If you are an existing Red Hat Support Portal user/customer then you already should have access to JBoss Developer Studio via the Downloads section, but if you are a new user the only thing you need to do is to signup and you will be granted access to the free download of JBoss Developer Studio.

 

The direct link to the download no matter if you are existing or new user of Red Hat Support Portal is: https://www.redhat.com/wapps/eval/index.html?evaluation_id=1015

What is JBoss Developer Studio 4 ?

JBoss Developer Studio 4 comes as a full easy to install Eclipse installation that bundles Eclipse WTP, TestNG, Spring IDE and the latest updated release of the supported plugins from JBoss Tools 3.2.

 

This latest release highlights are that it is now based on Eclipse 3.6 (Helios), updates the JSF 2 tooling, adds remote deployment for JBoss server adapters, easier setup of existing runtimes, provides tech preview of improved CDI functionallity and it includes updates for the SOA-P related features such as Guvnor, Drools, jBPM 3, Teiid Designer and Modeshape plugins.

 

Free vs For Pay ?

The free version of JBoss Developer Studio is the standalone version which can be used with both community and productized versions of JBoss Application Server and related frameworks such as Hibernate, Seam, Drools, jbpm, etc. The difference between this distribution and JBoss Tools boils down to ease-of-installation and future updates.

 

The product called JBoss Developer Studio Portfolio Edition is also available from http://devstudio.jboss.com/download/ for 99$ and in addition to the standalone version of JBoss Developer Studio it gives access to a bundle with JBoss Enterprise Application Platform 5 and additional downloads for development purposes of JBoss and Red Hat runtime distributions - including but not limited to JBoss Enterprise SOA Platform and Red Hat Enterprise Linux. You can read more about this offering at http://www.jboss.com/products/devstudio/

 

Thus if you already have access to the runtimes you would like to target for development the free version of JBoss Developer Studio is for you, but if you want access to the full range of JBoss and Red Hat runtime products (+ updates) for developement then the Portfolio Edition is what you are looking for.

 

Have fun!

"The Cloud" is many things to many people, but in the example Andre Dietisheim blogs 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.

 

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.

 

Next steps

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).

 

Have fun!


http://in.relation.to/service/File/10824

3.2.0

[Download] [Update Site] [Market Place] [What's New] [Documentation] [Forums] [JIRA] [Twitter]

 

I'm very happy to be able to announce that we pushed out JBoss Tools 3.2 to the servers shortly before the weekend.

Installation/Upgrade

 

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 

http://download.jboss.org/jbosstools/updates/stable/helios/

 

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.

 

New Features

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.

 

JSF 2

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.

Context & Dependency Injection (CDI)

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.

 

Visual Page Editor

Besides supporting JSF 2 better in this release various other improvements were done to the Visual Page Editor.

 

  • Templates for jBPM, Spring and Richfaces 4 were added/improved
  • DocBook support were made more complete and is now a separately named editor
  • A generic "Split-Editor" functionallity were added (can be used with any Eclipse editor)
  • The UI were cleaned up to fit better into the Eclipse IDE

Servers, Packaging & Remote Deployment

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.

 

Automatic Runtime Detection

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 GWT (Experimental)

 

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.

 

DeltaCloud (Experimental)

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.

 

Maven

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

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.

 

Teiid Designer

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.

 

BPEL

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.

WebServices

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.

 

Brian Fitzpatrick wrote a couple of blogs about it, giving you an overview of the new improvements for the WebServices support.

 

Usage Reporting

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.

 

...and much more...

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,

 

Have fun!

http://community.jboss.org/servlet/JiveServlet/downloadImage/38-2030-10503/449-54/earlyaccess.png

The Early Access site for JBoss Developer Studio now contains CR1 free for download and if you want the JBoss Enterprise Application platform bundled you just need to and sign up for the early access program here.

Improvements

This release contains a few improvements over the last couple of betas that are worth mentioning.

 

Most of these stems from the change we made from using the horrible dropin feature of Eclipse to have a proper

P2 enabled Eclipse product build. This should make things like installation, startup and updates much smoother, simpler and in some cases faster.

New Directory Layout

There is no longer a seperate "eclipse" directory; everything related to JBoss Developer Studio is now in the "studio" folder and

instead of using raw eclipse to start you now uses the jbdevstudio, jbdevstudio.exe or the JBoss Developer Studio.app dependent on your

platform to launch.

 

If you have installed the EAP bundle jboss-eap still lives in <install>/jboss-eap.

Runtime Detection/Setup

You can still use the "Server" page in the installer to setup JBoss server runtimes, but all this that was previously isolated in the installer is now also available from inside JBoss Tools under the Preferences for "JBoss Tools Runtime Detection". Here you can configure directories to scan for runtimes and it supports not only Server runtimes, but also standalone framework runtimes like Seam and Drools.

Welcome Screen

You will also now be greeted with a new shiny Welcome Screen:

 

jbds4_welcomescreen.png

 

...and of course the latest stable fixes and features from JBoss Tools 3.2.

 

Have fun!


http://in.relation.to/service/File/10824

3.2.0.CR1

[Download] [Update Site] [Market Place] [What's New] [Documentation] [Forums] [JIRA] [Twitter]

 

Note: Downloads are now being served from download.jboss.org while we wait for Sourceforge getting their issue fixed.

 

This release is squashing 400+ issues thus if you use JBoss Tools milestones it is time to upgrade and if you find remaining issues report them as soon as possible.

 

What's New covers the usability fixes there have been added, and a few new additions/improvements.

 

Top 6 on Eclipse Marketplace

Even though we haven't been on Eclipse Marketplace for long we are already the 6th most downloaded Eclipse plugin within 30 days on Eclipse Marketplace; and in 9th place of all time.

 

Thank you for the interest and usage - if you don't know Eclipse Marketplace, you can see how to use it here.

 

For those already using it, I encourage you to go and give us your star or even a review at our Eclipse Market Place page

 

Automatic Runtime Detection

First of all this release finally enables one of my favorite new features "Automatic Runtime Detection". It's been possible for a while now to use the "Search" button under JBoss Tools to find JBoss runtimes and have them configured and setup in the IDE for direct usage without having to set up all the individual parts.

 

In this release we have gone a bit further and allowed you to configure a set (one or many) of directories that JBoss Tools will scan on new workspaces or if you enable it at every startup; if anything new is found it will show the new items and you can then say if you want the runtimes to be installed or not.

 

This means when you install a new version of JBoss AS, Seam, Drools, EAP, SOA-P, etc. you can simply put in this "watched" directory and JBoss Tools will configure them for you in the IDE. In the future we will add more types of runtime distribution detection such as Java JDK's.

 

This feature is available under Eclipse Preferences in JBoss Tools > JBoss Tools Runtime Detection

CDI Improvements

For Context Dependency Injection (CDI) we've added a few quick fixes against some of the more common issues our validator finds.

This allows you to use Ctrl+1 on warnings and fix issues. For example fixing @Produces annotations on non-static methods in a Session Bean by making the method static.

 

We've also added support for the Maven integration to enable CDI automatically if/when your pom.xml file referenes the CDI api jars. Making it simple to import a Maven based CDI project and have all features enabled.

 

 

Feedback

 

There is more shown in What's New, take a look, try the release and let us know how it goes! If nothing major is found we'll be releasing the final version within the next couple of weeks.

 

Have fun!

With JBoss Tools 3.2 Beta 2 it is simple to start using CDI (Context Dependency Injection).

 

All you need is the following:

 

 

Here it is as a video walk through:

 

 

...and here are the steps in Screenshot form:

 

Step 1: Install/Configure the Server runtime

The simplest way to setup JBoss runtimes is to use the "JBoss Runtimes" preference page which are available

via the Preferences or by simply pressing Ctrl+3 and type in "JBoss runtimes".

 

hellocdi_ctrl3runtimes.png

When pressing enter you should see the following Preferences page:

 

hellocdi_preferencepageruntimes.png

Click the "Search..." button and point it to a directory with your JBoss runtimes; in this case I got a few.

 

hellocdi_selectruntimefolder.png

When you have selected the directory JBoss Tools will scan for runtimes it knows about and show

you what it found:

 

hellocdi_foundruntimes.png

In this dialog you can then remove the checkmarks for runtimes you do not want configured or simply press OK and JBoss Tools will make all selected runtimes available from within the IDE.

 

For the Server parts it is now availabe in the server view:

 

cdihelloworld_servers.png

From here you can start the server (in this case JBoss 6) by clicking the Debug or Run icon. If you start via Debug icon the server will wait at any breakpoints you have set in your code and allow you to inspect the current state.

 

In any case when the server starts up it sends the output of the console to the Console View:

 

helloworld_cdi_console.png

Step 2: Create the Project

Now use the File > New > Dynamic Web Project or simply press Ctrl+N and find the "Dynamic Web Project" wizard

 

dynamic_web_project.png

On the Wizard page, type in a project name (i.e. "cditest") and Click the "Modify" button under Configuration.

 

webprojectwizard.png

The Modify Configuration is where you can enable/disable what Eclipse calls project facets.

In this case we simply want to enable the Context Dependency Injection facet.

 

cdifacet.png

Now Click Ok and press Finish on the Wizard and a basic WAR project will be created for you.

cdiproject.png

Step 3: Create the code

The code we will create are the minimal for printing out Hello World via a servlet.

 

We will need to add the following files:

 

  • WebContent/WEB-INF/beans.xml to enable CDI fully for the project (in next revision of JBoss Tools this file will be created for you)
  • src/org/cditest/HelloWorld.java the bean for giving the "Hello World" greeting.
  • src/org/cditest/HelloServlet.java the servlet for rendering the greeting in its response method.

 

To create the bean.xml simply use Ctrl+N and type in "XML File" and choose the WebContent/WEB-INF folder and give it the name: beans.xml

 

beans.png

The default file is empty, but we need to add the following content to make it work:

 

<beans/>

 

that will suffice for this blog; remember the beans.xml file is simply just

a marker file to inform the CDI container that the War archive should be scanned for beans.

 

Next on comes the HelloWorld and Servlet class - for this I will just paste the simplest code

which you can paste into two .java files or use Eclipse's excellent wizards for it. If you want to see the full steps for this you can watch the video above.

 

HelloWorld.java:

 

package org.cditest;

public class HelloWorld {
    public String getGreeting() {
        return "Hello World!";
    }
}

 

HelloServlet.java:

 

package org.cditest;

import java.io.IOException;
import javax.inject.Inject;
import javax.servlet.*;
import javax.servlet.annotation.WebServlet;
import javax.servlet.http.*;

@WebServlet("/HelloServlet")
public class HelloServlet extends HttpServlet {
    @Inject private HelloWorld hello;
       
    public HelloServlet() {
        super();
    }

    protected void doGet(HttpServletRequest request, HttpServletResponse response) 
        throws ServletException, IOException {
        response.getOutputStream().println("<html><h1>" + hello.getGreeting() + "</h1></html>");
    }
}

 

If you look at the code of the HelloServlet you can see it simply a class with a @WebServlet annotation to specify the context/url name, an @Inject annotated field called Hello and a doGet() method which prints out the value of hello.getGreeting().

 

In short, the simplest example of @Inject annotation on a servlet.

 

Step 4: Run the Servlet


From within Eclipse you can use the Run As... or Debug As... toolbar menu to run what is the current selection and the tools will try and guess what kind of "Run" that means. i.e. for an XHTML page named home.xhtml it might be to open up a browser at http://localhost:8080/home.seam or in this case for a Servlet to open up the browser at the @WebServlet specified location relative to the deployment name, i.e. http://localhost:8080/cditest/HelloServlet.

 

runonserver.png

For new projects like this example Eclipse will ask you what Server you wish to run on:

 

selectserver.png

In this case I got several servers available, so I will choose the JBoss 6 server and

choose "Always use this server when running this project" so I will not have to answer

this question again on future Run's.

 

When the server is selected JBoss Tools will deploy the application and show the relevant page

in a browser:

 

browserhelloworld.png

 

Step 5: Have fun!

That is it - and there is of course more functionallity in the CDI tooling such as validations, quick fixes and code completions but I thought it would be good to just show the simplest application imaginable.

 

But with the steps described above you now know how to setup any JBoss runtime, create any kind of project and enable the Eclipse facets you want on them.

 

If you want to see how easy it is to debug your applications then watch the video above, it has a little more details.

 

Hope you enjoyed it

 

p.s. the exact same steps can be used to run against Glassfish or other CDI enabled servers that has Eclipse WTP server adapters.

http://community.jboss.org/servlet/JiveServlet/downloadImage/38-2030-10503/449-54/earlyaccess.png

In addition to releasing JBoss Tools 3.2 Beta 2 we've also released the second Beta of JBoss Developer Studio 4 to our early access site which incorporates the updated plugins from the JBoss Tools release.

 

You can download the full Eclipse based IDE from the early access site  for free,  and if you want to have the no-fuzz-single-click-install  experience  with JBoss Enterprise Application platform bundled you just  need to go  and sign up for the early access program here.

 

Have fun!

Here is a freshly cut Beta 2 of JBoss Tools 3.2 for you to enjoy this season.

 

http://in.relation.to/service/File/10824

3.2.0.Beta2

[Download] [Update Site] [What's New]  [Movies]  [Documentation] [Forums] [JIRA] [Twitter]

 

The end is near!

This is the last beta planned before we do a planned CR1 and then Final next month.

 

If you are on Eclipse 3.6 (Helios) we definitely recommend you to upgrade to this version. It has never been better.

 

We are hungry for feedback!

A few last improvements

For this last beta we've squeezed in some improvements within the almost 500 issues fixed in this round.

Simplified Download and installation

The simplest way to install the most commonly downloaded JBoss Tools 3.2.x plugins is now to use Eclipse Marketplace.

Eclipse Marketplace is available from the Help > Eclipse Marketplace menu in Eclipse.

 

When you install JBoss Tools via Eclipse Marketplace you get the "Web 2.0" plugins in one click - if you want additional or the complete plugin set you can use the complete Update Site.

 

Finally we also provide a zipped version of the Update sites from our Download page, which this time is also reduced to just the most popular download options instead of listing all 60+ sub-components individually.

 

Let us know what you think about this simplified installation!

More Platforms

You can now install all of JBoss Tools on any Eclipse compatible OS and in particular Windows and OS X 64-bit. Previously we limited the installation to those where the Visual Page Editor can run which unfortunately excluded some OS's. That restriction has now been lifted which means all can now get advantage of the complete tooling, except for the visual part of the editor which still only will be available on platforms were there exists working XULRunner/SWT bindings.

Cloud & Remote deployment

There have been done a lot in the area of the JBoss Server adapter Remote System support and for the Delta Cloud tooling but most importantly is that the SteamCannon team is now hosting a DeltaCloud server you can try and use together with JBoss Tools without having to setup your own DeltaCloud server.

 

The url for this is http://try.steamcannon.org/deltacloud/ and can be used as the URL for a Cloud Connection in the Cloud Wizard in JBoss Tools.

 

Note: Please beaware that this URL is still driven by experimental code and can at any time stop working - so try it while you can

Performance!

Beta 2 delivers 10 X performance improvements over M2 in the HTML and JSF validation - making this release the fastest ever!

JBoss 6 and CDI

The latest JBoss 6 release provides a full-fledged CDI environment and JBoss Tools now provide full set of code completion, validation, refactoring and quick fixes for CDI. If you are into trying out CDI using JBoss Tools with JBoss 6 gets you started very easily.

...and more!

Hibernate, Seam, Drools, BPEL, ESB, GWT and Modeshape also received a good set of fixes and improvements - you can see more about these in the What's New

 

Now go Get It and Have Fun!

earlyaccess.png

We've pushed our first Beta of JBoss Developer Studio 4 to our early access site.

 

You can download the full Eclipse based IDE from the early access site  for free, and if you want to have the no-fuzz-single-click-install  experience with JBoss Enterprise Application platform bundled you just  need to go and sign up for the early access program here.

 

This release incorporates the changes and improvements done in JBoss Tools 3.2 Beta1.

 

Have fun!

jbosseclipsemarketplace.png

We've added JBoss Tools 3.1 and 3.2 to Eclipse Marketplace.

 

What does that mean for users ?

 

It means you can now from your own Eclipse Help menu choose "Eclipse Marketplace"

 

helpMarketplace.png

...and if you type in "jboss" into the search field you will find JBoss Tools there and click "Install" for the version that is relevant for you.

i.e. 3.1 is for Galileo and 3.2 is for Helios (if in doubt, see the description text in the Marketplace).

jbosstoolsmarketplace.png

The screenshot also shows how easy it is to Update or Uninstall the installation you already have (in this case I got JBoss Tools 3.2 already installed).

 

We hope this makes it even easier to install and use JBoss Tools and if you like what you see please go and favorite us (click the Star) or comment on our Eclipse Marketplace page.

1 2 3 4 5 Previous Next

Filter Blog

By date:
By tag: