Community
Participate
Working Groups
In RAP 1.2.2, I have just found the following bug: #316443 Firefox 3.6: NumberFormatException on ToolItem click https://bugs.eclipse.org/bugs/show_bug.cgi?id=316443 Given that it did not happen to me on Eclipse, but only when running the WAR under Tomcat, this led me to question my WAR deployment procedure. Doing so raised questions about what the proper WAR deployment procedure would be for the 1.2.2 release, which although considered the latest stable, is several months behind HEAD. It seems to me that the procedure in the Eclipse Help article "WAR Deployment" is out of date, even with the help file provided by the latest (1.3 RC3) tooling. Specifically, the servletbridge project org.eclipse.equinox.servletbridge.extensionbundle is not mentioned in the article - it is not present in the bundle included in the help article: http://127.0.0.1:49165/help/topic/org.eclipse.rap.help/help/html/advanced/servletbridge-anon.psf nor is it in feature.xml from HEAD in org.eclipse.rap.demo.feature. However, sources such as the following lead me to believe that it is required. http://wiki.eclipse.org/RAP/FAQ#Exported_WAR_file_does_not_work #293020 War-deployment fails with equinox bridgeservlet from HEAD https://bugs.eclipse.org/bugs/show_bug.cgi?id=293020 If it is required, is there anything I need to do other than check out the project and include it in feature.xml before I run the webAppBuilder script? Is there anything else required that is not mentioned in the Help article? Since the WAR deployment procedure involves compiling the servletbridge, the question arises, what version of the servletbridge projects should I have in my workspace when running the webAppBuilder script? I have tried both the latest from HEAD (incl. the extensionbundle project) and the CVS source as of 27/01/2010 (the day after the 1.2.2 release). I understand that the WAR deployment procedure is likely in flux as the 1.3 release approaches, and that you are also working towards a more automated procedure (https://bugs.eclipse.org/bugs/show_bug.cgi?id=279743). However, I am trying to work with the latest stable, 1.2.2, rather than 1.3 exactly because it is more stable than 1.3.
The org.eclipse.equinox.servletbridge.extensionbundle fragment will be generated automatically at runtime by the Equinox Servlet Bridge. The only thing you need to do is to add it to the config.ini so OSGi can attach it. Is there anything special you're missing in the tutorial? We reviewed it for Helios and the deployment works as expected for 1.2 and 1.3. The only thing we missed is to update the screenshot (see bug 318317 ). I'd suggest to close this bug as WORKSFORME because the tutorial works as is. Ryan, I'd love to improve the documentation but I need concrete ideas what problem you have.
I will close it as WORKSFORME, like Benny suggested. Ryan, please reopen if you still have a deployment problems.
