While everyone else is having fun at JavaOne we uploaded the candidate release of JBoss Tools 2.1.0 at sourceforge and via the development update site.

This release is mainly 100+ bugfixes/enhancements based on QA and feedback from the last release.

A few new features did make it into 2.1.x and you can see those at new and noteworthy.

To upgrade safely to this release please read the following.

Existing Seam projects

Existing Seam projects will work fine in this new release, except EAR projects with an application.xml should be updated to have something like the following modules:




..and nothing else. The <java> elements we generated previously are unnecessary and breaks WTP 2.0.2. The details about why that is are in the following.

Less rigid WTP 2.0.2

We are now targeting WTP 2.0.2+Patches to get some of its important bugfixes.

Unfortunately WTP 2.0.2 introduced a bad regression bug concerning deployment and another bug which makes WTP 2.0.2 very rigid about deploying jar's listed in application.xml via <java> or <ejb> tags unless they have xml descriptors (which is not required in JEE 5).

This affects Seam 1.2 projects and any other projects using binary jars with EJB's in them and projects that uses <java> or <ejb> in application.xml for jars without descriptors which is the case for projects created with previous version of JBoss Tools

To get around these various bugs/features of WTP 2.0.2 we had to do two things:

  1. application.xml in new Seam projects no longer lists jar's in <java> elements to work with WTP 2.0.2. Besides being more correct and standard compliant it also makes the application.xml much smaller so in overall this is a Good thing. Unfortunately existing JBoss Seam projects that uses <java> in application.xml can run into files not being deployed thus we added a EAR validator that will put warnings/errors on offending elements we know can cause problems and with instructions on how to fix it.
  2. We provide a cumulative feature patch to WTP 2.0.2 which removes the rigidness in WTP with respect to JEE jars without descriptors. It is a hack, but it at least allows JEE 5 compliant jars to work instead of causing a exception stacktraces and random behavior in Eclipse.

We had hoped this rigidness could be removed in an update to WTP 2.x, but that does not seem to happen within a decent time frame so we decided to release the patch on our own. Note: WTP 2.0.2+WTP provided patches will work for most users, but we do recommend running with our patch to avoid publishing issues.


We plan on going GA within the next few weeks so we encourage you to provide feedback on our forum and jira in case you find something bad or good ;).

p.s. This version of JBoss Tools (sans the experimental parts) will be available in a JBoss Developer Studio 1.1.0.CR1 for JBDS customers soon.

07. May 2008, 09:52 CET | Link

did you manage to get the tools (seam) to work with MyEclipse? I reported this as a problem last release. I will try this set of tools again and see.

07. May 2008, 13:02 CET | Link

If MyEclipse works with Eclipse WTP 2.0.2 it should work.

Otherwise there is not much I can do since I do not have access to MyEclipse source code to see what is going on. Contributions are welcome to fix any such issue.



07. May 2008, 18:41 CET | Link

Hi, I installed a new dl of x86.64.


Then I updated with the given development update site link. Then I added the patches.

Bundle org.mozilla.xulrunner.gtk.linux.x86_64 is not found.


Mozilla XPCOM For Java is there (I don't know if this is the Xulrunner)

thanks a lot.

some plugins: (2.1.0.CR1) "ADF support for JBoss Visual Page Editor Plug-in" [Resolved] (2.1.0.CR1) "Ajax4jsf VPE Plug-in" [Starting] (2.1.0.CR1) "Facelets Plug-in" [Starting] (2.1.0.CR1) "JSF support for JBoss Visual Page Editor Plug-in" [Starting] (2.1.0.CR1) "MyFaces support for JBoss Visual Page Editor Plug-in" [Starting] (2.1.0.CR1) "Richfaces VPE Support Plug-in" [Starting] (2.1.0.CR1) "Seam VPE support Plug-in" [Starting] (2.1.0.CR1) "Tomahawk VPE Support Plug-in" [Starting] (2.1.0.CR1) "JBoss AS Initialization Plug-in" [Active] (2.1.0.CR1) "Jsp Editor Plug-in" [Active] (2.1.0.CR1) "Jetty Generic Server Definition Plug-in" [Starting] (2.1.0.CR1) "JRun Generic Server Definition Plug-in" [Starting] (2.1.0.CR1) "Resin Generic Server Definition Plug-in" [Starting] (2.1.0.CR1) "Web" [Active] (2.1.0.CR1) "Web Debug" [Starting] (2.1.0.CR1) "Web Debug UI" [Starting] (2.1.0.CR1) "Web Tiles" [Active] (2.1.0.CR1) "JBoss Tools Tiles" [Starting] (2.1.0.CR1) "Web UI" [Active] (2.1.0.CR1) "WEB Verification" [Active] (2.1.0.CR1) "Seam Core Plug-in" [Active] (2.1.0.CR1) "Seam Text Editors Extensions" [Starting] (2.1.0.CR1) "Seam GUI Tools" [Active] (2.1.0.CR1) "JBoss Tools Seam XML" [Active] (2.1.0.CR1) "Seam XML" [Starting] (2.0.0) "" [Active] (2.1.0.CR1) "Red Hat Struts Debugger" [Starting] (2.1.0.CR1) "Struts Text Editors Extensions" [Starting] (2.1.0.CR1) "JBoss Tools Struts UI" [Active] (2.1.0.CR1) "JBoss Tools Struts Validator" [Starting] (2.1.0.CR1) "Struts Verification" [Active] (2.1.0.CR1) "Struts support for JBoss Visual Page Editor Plug-in" [Resolved] (2.1.0.CR1) "Visual Page Editor" [Active] (2.1.0.CR1) "HTML support for JBoss Visual Page Editor Plug-in" [Starting] (2.1.0.CR1) "JSP support for JBoss Visual Page Editor Plug-in" [Starting] (2.1.0.CR1) "JBoss Tools Palette" [Starting] (2.1.0.CR1) "Browser (XULRunner) Plug-in" [Active] (3.1.3.CR1) "JBoss jBPM JPDL Designer Plug-in" [Starting] org.junit (3.8.2.v200706111738) "JUnit Testing Framework" [Resolved] org.junit4 (4.3.1) "JUnit Testing Framework Version 4" [Resolved] org.mortbay.jetty (5.1.11.v200706111724) "Jetty WebServer" [Resolved] org.mozilla.xpcom ( "Mozilla XPCOM For Java" [Resolved] org.uddi4j (2.0.5.v200706111329) "UDDI4J" [Resolved]

In addition to this: a) you don't allow underscores as in x86xx64 in text? b) could you make this box bigger? its tiny.

07. May 2008, 19:07 CET | Link

I forgot to add that I have already followed the advice on the wiki page.


best wishes.

07. May 2008, 21:11 CET | Link

please use the user forum or jira for this. thanks.



11. May 2008, 16:34 CET | Link

I found these lines should also be removed.

12. May 2008, 00:45 CET | Link
GapLo wrote on May 11, 2008 10:34:
I found these lines should also be removed.

huh ? That is exactly the lines that has to be in there.

Why do you find that they should be removed ?



03. Jun 2008, 05:57 CET | Link
Siarhei Dudzin

Just FYI, Seam 2.0.0 in maven repo doesn't have the descriptors, which probably could have caused some confusion. Seam starting only from 2.0.1.GA in maven repo does have the descriptors.

22. Jul 2008, 03:57 CET | Link

How about providing the patch as an update site instead of a zip? It would be much easier for everyone to install that way.

22. Jul 2008, 15:10 CET | Link
How about providing the patch as an update site instead of a zip? It would be much easier for everyone to install that way.

Not sure we could do that without messing up Eclipse update manager logic. Anyhow Eclipse will be incorporating this patch soon in Eclipse 3.3.x fixes.