JBoss Tools SVN: r20484 - in trunk: struts/tests/org.jboss.tools.struts.vpe.struts.test and 2 other directories.
by jbosstools-commits@lists.jboss.org
Author: yradtsevich
Date: 2010-02-25 08:24:40 -0500 (Thu, 25 Feb 2010)
New Revision: 20484
Modified:
trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/ChangeMessageBundleTest_JBIDE5818.java
trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE2582Test.java
trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE2624Test.java
trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE3441Test.java
trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE3734Test.java
trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE4373Test.java
trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE788Test.java
trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/TestOpenOnForXhtmlFiles_JBIDE5577.java
trunk/struts/tests/org.jboss.tools.struts.vpe.struts.test/build.properties
trunk/struts/tests/org.jboss.tools.struts.vpe.struts.test/src/org/jboss/tools/struts/vpe/struts/test/StrutsHTMLComponentTest.java
trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/ProjectsLoader.java
trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/TestUtil.java
trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/VPETestPlugin.java
trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/VpeAllTests.java
trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/VpeTest.java
Log:
https://jira.jboss.org/jira/browse/JBIDE-5837
Make possible to run VPE JUnit tests one by one
- Fail-fast behavior has been implemented in the ProjectsLoader.
- plugin.xml of the org.jboss.tools.struts.vpe.struts.test has been added to source and binary builds (build.properties changed).
Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/ChangeMessageBundleTest_JBIDE5818.java
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/ChangeMessageBundleTest_JBIDE5818.java 2010-02-24 22:54:57 UTC (rev 20483)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/ChangeMessageBundleTest_JBIDE5818.java 2010-02-25 13:24:40 UTC (rev 20484)
@@ -10,6 +10,8 @@
******************************************************************************/
package org.jboss.tools.jsf.vpe.jsf.test.jbide;
+import java.io.IOException;
+
import org.eclipse.core.resources.IFile;
import org.eclipse.core.runtime.CoreException;
import org.eclipse.core.runtime.NullProgressMonitor;
@@ -71,7 +73,7 @@
* with {@code newContent} and saves it.
*/
private TextEditor replaceFileContent(final String path,
- final String newContent) throws CoreException {
+ final String newContent) throws CoreException, IOException {
IFile elementPageFile = (IFile) TestUtil.getResource(path, JsfAllTests.IMPORT_PROJECT_NAME);
IEditorInput input = new FileEditorInput(elementPageFile);
TextEditor editor = (TextEditor)
Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE2582Test.java
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE2582Test.java 2010-02-24 22:54:57 UTC (rev 20483)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE2582Test.java 2010-02-25 13:24:40 UTC (rev 20484)
@@ -13,6 +13,7 @@
package org.jboss.tools.jsf.vpe.jsf.test.jbide;
+import java.io.IOException;
import java.util.ArrayList;
import java.util.Collection;
import java.util.List;
@@ -119,9 +120,11 @@
* Test selection with resource string.
*
* @throws CoreException the core exception
+ * @throws IOException
*/
@SuppressWarnings("restriction")
- public void testSelectionWithResourceString() throws CoreException {
+ public void testSelectionWithResourceString()
+ throws CoreException, IOException {
IFile lfile = (IFile) TestUtil.getComponentPath(PAGE_2, getOpenProjectName());
IEditorInput input = new FileEditorInput(lfile);
// open and get editor
Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE2624Test.java
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE2624Test.java 2010-02-24 22:54:57 UTC (rev 20483)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE2624Test.java 2010-02-25 13:24:40 UTC (rev 20484)
@@ -14,6 +14,7 @@
import java.io.File;
+import java.io.IOException;
import java.util.ArrayList;
import java.util.List;
@@ -51,7 +52,7 @@
super(name);
}
- public void testJBide2624() throws CoreException {
+ public void testJBide2624() throws CoreException, IOException {
// get test page path
setException(null);
IFile file = (IFile) TestUtil.getComponentPath(TEST_PAGE_NAME, //$NON-NLS-1$
Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE3441Test.java
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE3441Test.java 2010-02-24 22:54:57 UTC (rev 20483)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE3441Test.java 2010-02-25 13:24:40 UTC (rev 20484)
@@ -10,6 +10,8 @@
******************************************************************************/
package org.jboss.tools.jsf.vpe.jsf.test.jbide;
+import java.io.IOException;
+
import junit.framework.Assert;
import org.eclipse.core.resources.IFile;
@@ -80,7 +82,7 @@
}
private VpeController openPageInVpe(final String pageName) throws CoreException,
- PartInitException {
+ PartInitException, IOException {
IFile elementPageFile = (IFile) TestUtil.getComponentPath(
pageName, JsfAllTests.IMPORT_PROJECT_NAME);
IEditorInput input = new FileEditorInput(elementPageFile);
Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE3734Test.java
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE3734Test.java 2010-02-24 22:54:57 UTC (rev 20483)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE3734Test.java 2010-02-25 13:24:40 UTC (rev 20484)
@@ -10,6 +10,8 @@
******************************************************************************/
package org.jboss.tools.jsf.vpe.jsf.test.jbide;
+import java.io.IOException;
+
import org.eclipse.core.resources.IFile;
import org.eclipse.core.runtime.CoreException;
import org.eclipse.ui.IEditorInput;
@@ -88,7 +90,7 @@
}
private VpeController openTestPage() throws CoreException,
- PartInitException {
+ PartInitException, IOException {
IFile ifile = (IFile) TestUtil.getComponentPath(TEST_FOLDER_PATH + TEST_FILE_NAME,
JsfAllTests.IMPORT_PROJECT_NAME);
IEditorInput input = new FileEditorInput(ifile);
Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE4373Test.java
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE4373Test.java 2010-02-24 22:54:57 UTC (rev 20483)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE4373Test.java 2010-02-25 13:24:40 UTC (rev 20484)
@@ -10,6 +10,8 @@
******************************************************************************/
package org.jboss.tools.jsf.vpe.jsf.test.jbide;
+import java.io.IOException;
+
import org.eclipse.core.runtime.CoreException;
import org.eclipse.jface.viewers.StructuredSelection;
import org.eclipse.ui.IEditorPart;
@@ -40,7 +42,7 @@
/**
* OpenOn test for Custom elements
*/
- public void testCorrectCustomElements() throws CoreException {
+ public void testCorrectCustomElements() throws CoreException, IOException {
VpeController vpeController = openInVpe(JsfAllTests.IMPORT_CUSTOM_FACELETS_PROJECT, "correctCustomTags.xhtml"); //$NON-NLS-1$
int position = TestUtil.getLinePositionOffcet(vpeController.getSourceEditor().getTextViewer(), 13, 8);
@@ -61,7 +63,8 @@
/**
* test openOn for undefined template
*/
- public void testIncorrectCustomElements() throws CoreException {
+ public void testIncorrectCustomElements()
+ throws CoreException, IOException {
VpeController vpeController = openInVpe(JsfAllTests.IMPORT_CUSTOM_FACELETS_PROJECT, "incorrectCustomTags.xhtml"); //$NON-NLS-1$
int position = TestUtil.getLinePositionOffcet(vpeController.getSourceEditor().getTextViewer(), 9, 6);
@@ -80,9 +83,11 @@
/**
* test open on for following case <h:outputText value="#{msg.greeting}" />
* @throws CoreException
+ * @throws IOException
*/
- public void testOpenOnForMessageBundlesInJSFElements() throws CoreException{
- VpeController vpeController = openInVpe(JsfAllTests.IMPORT_CUSTOM_FACELETS_PROJECT, "testOutputText.xhtml"); //$NON-NLS-1$
+ public void testOpenOnForMessageBundlesInJSFElements()
+ throws CoreException, IOException{
+ VpeController vpeController = openInVpe(JsfAllTests.IMPORT_CUSTOM_FACELETS_PROJECT, "testOutputText.xhtml"); //$NON-NLS-1$
int position = TestUtil.getLinePositionOffcet(vpeController.getSourceEditor().getTextViewer(), 13, 30);
Node sourceNode = SelectionUtil.getNodeBySourcePosition(vpeController.getSourceEditor(), position);
nsIDOMNode domNode = vpeController.getDomMapping().getNearVisualNode(sourceNode);
@@ -93,8 +98,10 @@
/**
* test open on for following case #{msg.prompt}
* @throws CoreException
+ * @throws IOException
*/
- public void testOpenOnForTextNodesMessageBundles() throws CoreException{
+ public void testOpenOnForTextNodesMessageBundles()
+ throws CoreException, IOException{
VpeController vpeController = openInVpe(JsfAllTests.IMPORT_CUSTOM_FACELETS_PROJECT, "testOutputText.xhtml"); //$NON-NLS-1$
int position = TestUtil.getLinePositionOffcet(vpeController.getSourceEditor().getTextViewer(), 12, 15);
Node sourceNode = SelectionUtil.getNodeBySourcePosition(vpeController.getSourceEditor(), position);
@@ -109,8 +116,9 @@
* in facelets' ui:composition template (VpeCompositionTemplate).
*
* @throws CoreException
+ * @throws IOException
*/
- public void testOpenOnforFacelets() throws CoreException {
+ public void testOpenOnforFacelets() throws CoreException, IOException {
VpeController vpeController = openInVpe(JsfAllTests.IMPORT_CUSTOM_FACELETS_PROJECT, "inputName.xhtml"); //$NON-NLS-1$
int position = TestUtil.getLinePositionOffcet(vpeController.getSourceEditor().getTextViewer(), 10, 38);
Node sourceNode = SelectionUtil.getNodeBySourcePosition(vpeController.getSourceEditor(), position);
@@ -125,8 +133,9 @@
* in facelets' ui:decorate template (VpeDecorateTemplate).
*
* @throws CoreException
+ * @throws IOException
*/
- public void testOpenOnForUiDecorate() throws CoreException {
+ public void testOpenOnForUiDecorate() throws CoreException, IOException {
VpeController vpeController = openInVpe(JsfAllTests.IMPORT_CUSTOM_FACELETS_PROJECT, "ui-decorate.xhtml"); //$NON-NLS-1$
int position = TestUtil.getLinePositionOffcet(vpeController.getSourceEditor().getTextViewer(), 11, 33);
Node sourceNode = SelectionUtil.getNodeBySourcePosition(vpeController.getSourceEditor(), position);
@@ -141,8 +150,9 @@
* in facelets' ui:define template (VpeDefineTemplate).
*
* @throws CoreException
+ * @throws IOException
*/
- public void testOpenOnForUiDefine() throws CoreException {
+ public void testOpenOnForUiDefine() throws CoreException, IOException {
VpeController vpeController = openInVpe(JsfAllTests.IMPORT_CUSTOM_FACELETS_PROJECT, "ui-define.xhtml"); //$NON-NLS-1$
int position = TestUtil.getLinePositionOffcet(vpeController.getSourceEditor().getTextViewer(), 6, 40);
Node sourceNode = SelectionUtil.getNodeBySourcePosition(vpeController.getSourceEditor(), position);
@@ -157,8 +167,9 @@
* in JSTL's c:import template (JstlImportTemplate).
*
* @throws CoreException
+ * @throws IOException
*/
- public void testOpenOnForCImport() throws CoreException {
+ public void testOpenOnForCImport() throws CoreException, IOException {
VpeController vpeController = openInVpe(JsfAllTests.IMPORT_CUSTOM_FACELETS_PROJECT, "c-import.xhtml"); //$NON-NLS-1$
int position = TestUtil.getLinePositionOffcet(vpeController.getSourceEditor().getTextViewer(), 12, 25);
Node sourceNode = SelectionUtil.getNodeBySourcePosition(vpeController.getSourceEditor(), position);
@@ -173,8 +184,9 @@
* in Seam's s:decorate template (SeamDecorateTemplate).
*
* @throws CoreException
+ * @throws IOException
*/
- public void testOpenOnForSDecorate() throws CoreException {
+ public void testOpenOnForSDecorate() throws CoreException, IOException {
VpeController vpeController = openInVpe(JsfAllTests.IMPORT_CUSTOM_FACELETS_PROJECT, "s-decorate.xhtml"); //$NON-NLS-1$
int position = TestUtil.getLinePositionOffcet(vpeController.getSourceEditor().getTextViewer(), 11, 33);
Node sourceNode = SelectionUtil.getNodeBySourcePosition(vpeController.getSourceEditor(), position);
@@ -188,8 +200,9 @@
* Test openOn mechanism for VpeIncludeTemplate in ajax4jsf a4j:include.
*
* @throws CoreException
+ * @throws IOException
*/
- public void testOpenOnForA4JInclude() throws CoreException {
+ public void testOpenOnForA4JInclude() throws CoreException, IOException {
VpeController vpeController = openInVpe(JsfAllTests.IMPORT_CUSTOM_FACELETS_PROJECT, "a4j-include.xhtml"); //$NON-NLS-1$
int position = TestUtil.getLinePositionOffcet(vpeController.getSourceEditor().getTextViewer(), 15, 55);
Node sourceNode = SelectionUtil.getNodeBySourcePosition(vpeController.getSourceEditor(), position);
@@ -203,8 +216,9 @@
* Test openOn mechanism for VpeIncludeTemplate in facelets' ui:include.
*
* @throws CoreException
+ * @throws IOException
*/
- public void testOpenOnForUiInclude() throws CoreException {
+ public void testOpenOnForUiInclude() throws CoreException, IOException {
VpeController vpeController = openInVpe(JsfAllTests.IMPORT_CUSTOM_FACELETS_PROJECT, "ui-include-relative.xhtml"); //$NON-NLS-1$
int position = TestUtil.getLinePositionOffcet(vpeController.getSourceEditor().getTextViewer(), 13, 27);
Node sourceNode = SelectionUtil.getNodeBySourcePosition(vpeController.getSourceEditor(), position);
@@ -218,8 +232,9 @@
* Test openOn mechanism for VpeIncludeTemplate in jsp's jsp:directive.include.
*
* @throws CoreException
+ * @throws IOException
*/
- public void testOpenOnForJspDirectiveInclude() throws CoreException {
+ public void testOpenOnForJspDirectiveInclude() throws CoreException, IOException {
VpeController vpeController = openInVpe(JsfAllTests.IMPORT_CUSTOM_FACELETS_PROJECT, "jsp-directive-include-relative.jsp"); //$NON-NLS-1$
int position = TestUtil.getLinePositionOffcet(vpeController.getSourceEditor().getTextViewer(), 13, 46);
Node sourceNode = SelectionUtil.getNodeBySourcePosition(vpeController.getSourceEditor(), position);
@@ -233,8 +248,9 @@
* Test openOn mechanism for VpeIncludeTemplate in jsp's jsp:include.
*
* @throws CoreException
+ * @throws IOException
*/
- public void testOpenOnForJspInclude() throws CoreException {
+ public void testOpenOnForJspInclude() throws CoreException, IOException {
VpeController vpeController = openInVpe(JsfAllTests.IMPORT_CUSTOM_FACELETS_PROJECT, "jsp-include-relative.jsp"); //$NON-NLS-1$
int position = TestUtil.getLinePositionOffcet(vpeController.getSourceEditor().getTextViewer(), 13, 36);
Node sourceNode = SelectionUtil.getNodeBySourcePosition(vpeController.getSourceEditor(), position);
@@ -252,7 +268,7 @@
* @author mareshkau
*/
- public void testOpenOnForHREF() throws CoreException {
+ public void testOpenOnForHREF() throws CoreException, IOException {
VpeController vpeController = openInVpe(JsfAllTests.IMPORT_PROJECT_NAME, "JBIDE/5183/a.html"); //$NON-NLS-1$
int position = TestUtil.getLinePositionOffcet(vpeController.getSourceEditor().getTextViewer(), 5, 41);
Node sourceNode = SelectionUtil.getNodeBySourcePosition(vpeController.getSourceEditor(), position);
Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE788Test.java
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE788Test.java 2010-02-24 22:54:57 UTC (rev 20483)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE788Test.java 2010-02-25 13:24:40 UTC (rev 20484)
@@ -10,6 +10,8 @@
******************************************************************************/
package org.jboss.tools.jsf.vpe.jsf.test.jbide;
+import java.io.IOException;
+
import org.eclipse.core.resources.IFile;
import org.eclipse.core.runtime.CoreException;
import org.eclipse.jface.text.contentassist.ICompletionProposal;
@@ -233,9 +235,11 @@
* @param linePosition
* @return
* @throws CoreException
+ * @throws IOException
*/
private ICompletionProposal[] checkOfCAByStartString(String caName, String testPagePath,
- String partOfString, int lineIndex, int linePosition) throws CoreException {
+ String partOfString, int lineIndex, int linePosition)
+ throws CoreException, IOException {
return this.checkOfCAByStartString(caName, testPagePath, partOfString, lineIndex, linePosition,true);
}
@@ -249,10 +253,11 @@
* @param isCheck
* @return
* @throws CoreException
+ * @throws IOException
*/
private ICompletionProposal[] checkOfCAByStartString(String caName, String testPagePath,
- String partOfString, int lineIndex, int linePosition,boolean isCheck) throws CoreException {
+ String partOfString, int lineIndex, int linePosition,boolean isCheck) throws CoreException, IOException {
// get test page path
IFile file = (IFile) TestUtil.getComponentPath(testPagePath,
JsfAllTests.IMPORT_PROJECT_NAME);
Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/TestOpenOnForXhtmlFiles_JBIDE5577.java
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/TestOpenOnForXhtmlFiles_JBIDE5577.java 2010-02-24 22:54:57 UTC (rev 20483)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/TestOpenOnForXhtmlFiles_JBIDE5577.java 2010-02-25 13:24:40 UTC (rev 20484)
@@ -10,6 +10,8 @@
******************************************************************************/
package org.jboss.tools.jsf.vpe.jsf.test.jbide;
+import java.io.IOException;
+
import org.eclipse.core.resources.IFile;
import org.eclipse.core.runtime.CoreException;
import org.eclipse.ui.IEditorInput;
@@ -36,7 +38,7 @@
super(name);
}
- public void testOpenOnForXhtmlFiles() throws CoreException {
+ public void testOpenOnForXhtmlFiles() throws CoreException, IOException {
/*
* Open index.html
*/
Modified: trunk/struts/tests/org.jboss.tools.struts.vpe.struts.test/build.properties
===================================================================
--- trunk/struts/tests/org.jboss.tools.struts.vpe.struts.test/build.properties 2010-02-24 22:54:57 UTC (rev 20483)
+++ trunk/struts/tests/org.jboss.tools.struts.vpe.struts.test/build.properties 2010-02-25 13:24:40 UTC (rev 20484)
@@ -1,11 +1,13 @@
bin.includes = META-INF/,\
resources/,\
struts-test.jar,\
- plugin.properties
+ plugin.properties,\
+ plugin.xml
jars.compile.order = struts-test.jar
src.includes = src/,\
resources/,\
META-INF/,\
- build.properties
+ build.properties,\
+ plugin.xml
source.struts-test.jar = src/
output.struts-test.jar = bin/
Modified: trunk/struts/tests/org.jboss.tools.struts.vpe.struts.test/src/org/jboss/tools/struts/vpe/struts/test/StrutsHTMLComponentTest.java
===================================================================
--- trunk/struts/tests/org.jboss.tools.struts.vpe.struts.test/src/org/jboss/tools/struts/vpe/struts/test/StrutsHTMLComponentTest.java 2010-02-24 22:54:57 UTC (rev 20483)
+++ trunk/struts/tests/org.jboss.tools.struts.vpe.struts.test/src/org/jboss/tools/struts/vpe/struts/test/StrutsHTMLComponentTest.java 2010-02-25 13:24:40 UTC (rev 20484)
@@ -10,12 +10,7 @@
******************************************************************************/
package org.jboss.tools.struts.vpe.struts.test;
-import java.util.HashMap;
-
import org.eclipse.core.resources.IFile;
-import org.eclipse.core.resources.IFolder;
-import org.eclipse.core.resources.IProject;
-import org.jboss.tools.vpe.ui.test.ProjectsLoader;
import org.jboss.tools.vpe.ui.test.TestUtil;
import org.jboss.tools.vpe.ui.test.VpeTest;
@@ -55,35 +50,7 @@
}
public void testImage() throws Throwable {
- /*
- * XXX temporary code is used to debug Struts tests on Hudson.
- * It must be removed when the problem with the failing tests is resolved.
- */
- StringBuilder debugInfo = new StringBuilder();
- debugInfo.append("projectNameToPath = ")
- .append(ProjectsLoader.getInstance().getProjectNameToPath())
- .append(";\n");
-
- IProject project = ProjectsLoader.getInstance().getProject(IMPORT_PROJECT_NAME);
- assertNotNull(debugInfo.toString(), project);
- debugInfo.append("project = ").append(project).append(";\n")
- .append("project.exists() = ").append(project.exists()).append(";\n")
- .append("project.isOpen() = ").append(project.isOpen()).append(";\n");
-
- IFolder folder = project.getFolder("WebContent/pages");
- assertNotNull(debugInfo.toString(), folder);
- debugInfo.append("folder = ").append(folder).append(";\n")
- .append("folder.exists() = ").append(folder.exists()).append(";\n");
-
- IFile testFile = (IFile) folder.findMember("components/html/image.jsp");
- assertNotNull(debugInfo.toString(), testFile);
- debugInfo.append("testFile = ").append(folder).append(";\n")
- .append("testFile.exists() = ").append(testFile.exists()).append(";\n");
-
- performTestForVpeComponent(testFile);
- fail(debugInfo.toString());
-
- // performTestForVpeComponent((IFile)TestUtil.getComponentPath("components/html/image.jsp", IMPORT_PROJECT_NAME)); //$NON-NLS-1$
+ performTestForVpeComponent((IFile)TestUtil.getComponentPath("components/html/image.jsp", IMPORT_PROJECT_NAME)); //$NON-NLS-1$
}
public void testImg() throws Throwable {
@@ -91,10 +58,6 @@
}
public void testLink() throws Throwable {
- // XXX wait is added just to check if the test will fail on Hudson.
- // Most probably it is not needed.
- TestUtil.waitForIdle();
-
performTestForVpeComponent((IFile)TestUtil.getComponentPath("components/html/link.jsp", IMPORT_PROJECT_NAME)); //$NON-NLS-1$
}
Modified: trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/ProjectsLoader.java
===================================================================
--- trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/ProjectsLoader.java 2010-02-24 22:54:57 UTC (rev 20483)
+++ trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/ProjectsLoader.java 2010-02-25 13:24:40 UTC (rev 20484)
@@ -10,9 +10,13 @@
******************************************************************************/
package org.jboss.tools.vpe.ui.test;
+import java.io.IOException;
+import java.net.URL;
import java.util.HashMap;
import java.util.Map;
+import junit.framework.Assert;
+
import org.eclipse.core.resources.IProject;
import org.eclipse.core.resources.IResource;
import org.eclipse.core.resources.ResourcesPlugin;
@@ -20,8 +24,6 @@
import org.eclipse.core.runtime.FileLocator;
import org.eclipse.core.runtime.IConfigurationElement;
import org.eclipse.core.runtime.IExtension;
-import org.eclipse.core.runtime.IExtensionPoint;
-import org.eclipse.core.runtime.IExtensionRegistry;
import org.eclipse.core.runtime.NullProgressMonitor;
import org.eclipse.core.runtime.Platform;
import org.jboss.tools.test.util.JobUtils;
@@ -38,11 +40,35 @@
private static final String TEST_PROJECT_ELEMENT = "testProject";
private static final String TEST_PROJECT_PATH_ATTRIBUTE = "path";
private static final String TEST_PROJECT_NAME_ATTRIBUTE = "name";
- private Map<String, String> projectNameToPath;
+ private Map<String, ProjectLocation> projectNameToLocation;
private static ProjectsLoader instance = null;
private ProjectsLoader() {
- loadProjectPaths();
+ /*
+ * Load project names and paths to them from the extensions of
+ * {@link VpeAllTests#VPE_TEST_EXTENTION_POINT_ID}. And store
+ * loaded data in {@link #projectNameToLocation}.
+ */
+ projectNameToLocation = new HashMap<String, ProjectLocation>();
+ IExtension[] extensions = VPETestPlugin.getDefault().getVpeTestExtensions();
+ for (IExtension extension : extensions) {
+ IConfigurationElement[] confElements = extension
+ .getConfigurationElements();
+ for (IConfigurationElement configurationElement : confElements) {
+ if (TEST_PROJECT_ELEMENT.equals(
+ configurationElement.getName())) {
+ Bundle bundle = Platform.getBundle(
+ configurationElement.getNamespaceIdentifier());
+ String name = configurationElement.getAttribute(
+ TEST_PROJECT_NAME_ATTRIBUTE);
+ String path = configurationElement.getAttribute(
+ TEST_PROJECT_PATH_ATTRIBUTE);
+
+ projectNameToLocation.put(name,
+ new ProjectLocation(bundle, path));
+ }
+ }
+ }
}
/**
@@ -60,17 +86,48 @@
* Returns instance of {@link IProject} by {@code projectName}.
* If the project does not exist in the workspace, imports it from the
* resources specified by extensions of {@code org.jboss.tools.vpe.ui.tests}
- * extension point. Returns {@code null} if the project is not declared in
- * the extensions.
+ * extension point.
+ * <p>
+ * This method has <i>fail-fast</i> behavior. It never returns {@code null}.
+ * It throws exceptions in the cases if the project is not defined,
+ * can not be opened, etc.
*/
- public IProject getProject(String projectName) {
+ public IProject getProject(String projectName) throws IOException {
IProject project = getExistingProject(projectName);
if (project == null) {
- String projectPath = projectNameToPath.get(projectName);
- if (projectPath != null) {
- project = ResourcesUtils.importProjectIntoWorkspace(
+ ProjectLocation location = projectNameToLocation.get(projectName);
+ if (location == null) {
+ throw new RuntimeException(
+ "Project '" + project + "' is not defined.");
+ }
+
+ Bundle bundle = location.getBundle();
+ if (bundle == null) {
+ throw new NullPointerException(
+ "Owning bundle of '" + project + "' is null.");
+ }
+
+ URL rootEntry = bundle.getEntry("/");
+ if (rootEntry == null) {
+ throw new NullPointerException(
+ "Root entry to the bundle with id='"
+ + bundle.getBundleId() + "' cannot be resolved.");
+ }
+
+ URL resolvedRootEntry = FileLocator.resolve(rootEntry);
+ String pluginRoot = resolvedRootEntry.getPath();
+ if (pluginRoot.equals("")) {
+ throw new RuntimeException("Path to '" + resolvedRootEntry
+ + "' does not exist.");
+ }
+
+ String projectPath = pluginRoot + location.getPath();
+ project = ResourcesUtils.importProjectIntoWorkspace(
projectPath, projectName);
+ if (project == null) {
+ throw new RuntimeException("Project by the path='" + projectPath
+ + "' cannot be imported.");
}
}
@@ -92,41 +149,6 @@
}
/**
- * Loads project names and paths to them from the extensions of
- * {@link VpeAllTests#VPE_TEST_EXTENTION_POINT_ID}. And stores
- * loaded data in {@link #projectNameToPath}.
- */
- private void loadProjectPaths() {
- projectNameToPath = new HashMap<String, String>();
- IExtensionRegistry extensionRepository = Platform
- .getExtensionRegistry();
-
- IExtensionPoint extensionPoint = extensionRepository
- .getExtensionPoint(VpeAllTests.VPE_TEST_EXTENTION_POINT_ID);
- IExtension[] extensions = extensionPoint.getExtensions();
- for (IExtension extension : extensions) {
- IConfigurationElement[] confElements = extension
- .getConfigurationElements();
- for (IConfigurationElement configurationElement : confElements) {
- if (TEST_PROJECT_ELEMENT.equals(configurationElement.getName())) {
- try {
- Bundle bundle = Platform.getBundle(configurationElement
- .getNamespaceIdentifier());
-
- String pluginRoot = FileLocator
- .resolve(bundle.getEntry("/")).getPath();
- String name = configurationElement.getAttribute(TEST_PROJECT_NAME_ATTRIBUTE);
- String path = configurationElement.getAttribute(TEST_PROJECT_PATH_ATTRIBUTE);
- projectNameToPath.put(name, pluginRoot + path);
- } catch (Exception e) {
- VPETestPlugin.getDefault().logError(e);
- }
- }
- }
- }
- }
-
- /**
* Removes the project with the {@code projectName} from the workspace.
*
* @param projectName the project name
@@ -168,13 +190,30 @@
removeProject(project);
}
}
-
- /*
- * XXX This temporary method is used to debug Struts tests on Hudson.
- * It must be removed when the problem with the failing tests is resolved.
+
+ /**
+ * Stores the {@code path} to a project and the owning {@code bundle}.
+ *
+ * @author Yahor Radtsevich (yradtsevich)
*/
- @Deprecated
- public Map<String, String> getProjectNameToPath() {
- return projectNameToPath;
+ private class ProjectLocation {
+ private Bundle bundle;
+ private String path;
+
+ public ProjectLocation(Bundle bundle, String path) {
+ this.bundle = bundle;
+ this.path = path;
+ }
+ public Bundle getBundle() {
+ return bundle;
+ }
+ public String getPath() {
+ return path;
+ }
+
+ public String toString() {
+ return String.format("(%s, %s)",
+ bundle == null ? null : bundle.getLocation(), path);
+ }
}
}
Modified: trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/TestUtil.java
===================================================================
--- trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/TestUtil.java 2010-02-24 22:54:57 UTC (rev 20483)
+++ trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/TestUtil.java 2010-02-25 13:24:40 UTC (rev 20484)
@@ -11,6 +11,7 @@
package org.jboss.tools.vpe.ui.test;
import java.io.File;
+import java.io.IOException;
import java.util.List;
import junit.framework.Assert;
@@ -66,20 +67,20 @@
* @return the component path
*
* @throws CoreException the core exception
+ * @throws IOException
*/
public static IResource getComponentPath(String componentPage,
- String projectName) throws CoreException {
+ String projectName) throws CoreException, IOException {
IProject project = ProjectsLoader.getInstance().getProject(projectName);
if (project != null) {
return project.getFolder(COMPONENTS_PATH).findMember(componentPage);
-
}
return null;
}
public static IResource getResource(String path,
- String projectName) throws CoreException {
+ String projectName) throws CoreException, IOException {
IProject project = ProjectsLoader.getInstance().getProject(projectName);
if (project != null) {
return project.findMember(path);
@@ -97,9 +98,10 @@
* @return the web content path
*
* @throws CoreException the core exception
+ * @throws IOException
*/
public static IResource getWebContentPath(String componentPage,
- String projectName) throws CoreException {
+ String projectName) throws CoreException, IOException {
IProject project = ProjectsLoader.getInstance().getProject(projectName);
if (project != null) {
return project.getFolder(WEBCONTENT_PATH).findMember(componentPage);
Modified: trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/VPETestPlugin.java
===================================================================
--- trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/VPETestPlugin.java 2010-02-24 22:54:57 UTC (rev 20483)
+++ trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/VPETestPlugin.java 2010-02-25 13:24:40 UTC (rev 20484)
@@ -10,12 +10,11 @@
******************************************************************************/
package org.jboss.tools.vpe.ui.test;
-import java.net.URL;
-
-import org.eclipse.core.runtime.FileLocator;
+import org.eclipse.core.runtime.IExtension;
+import org.eclipse.core.runtime.IExtensionPoint;
+import org.eclipse.core.runtime.IExtensionRegistry;
import org.eclipse.core.runtime.Platform;
import org.jboss.tools.common.log.BaseUIPlugin;
-import org.osgi.framework.Bundle;
import org.osgi.framework.BundleContext;
/**
@@ -25,6 +24,8 @@
// The plug-in ID
public static final String PLUGIN_ID = "org.jboss.tools.vpe.ui.test";
+
+ public static final String VPE_TEST_EXTENTION_POINT_ID = "org.jboss.tools.vpe.ui.tests"; //$NON-NLS-1$
// The shared instance
private static VPETestPlugin plugin;
@@ -62,15 +63,14 @@
return plugin;
}
- public static String getPluginResourcePath() {
- Bundle bundle = Platform.getBundle(PLUGIN_ID);
- URL url = null;
- try {
- url = bundle == null ? null : FileLocator.resolve(bundle
- .getEntry("/resources")); //$NON-NLS-1$
- } catch (Exception e) {
- url = bundle.getEntry("/resources"); //$NON-NLS-1$
- }
- return (url == null) ? null : url.getPath();
+ /**
+ * Returns all extensions of {@value #VPE_TEST_EXTENTION_POINT_ID}
+ */
+ public IExtension[] getVpeTestExtensions() {
+ IExtensionRegistry extensionRegistry = Platform.getExtensionRegistry();
+ IExtensionPoint extensionPoint = extensionRegistry
+ .getExtensionPoint(VPE_TEST_EXTENTION_POINT_ID);
+ IExtension[] extensions = extensionPoint.getExtensions();
+ return extensions;
}
-}
\ No newline at end of file
+}
Modified: trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/VpeAllTests.java
===================================================================
--- trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/VpeAllTests.java 2010-02-24 22:54:57 UTC (rev 20483)
+++ trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/VpeAllTests.java 2010-02-25 13:24:40 UTC (rev 20484)
@@ -17,8 +17,6 @@
import org.eclipse.core.runtime.IConfigurationElement;
import org.eclipse.core.runtime.IExtension;
-import org.eclipse.core.runtime.IExtensionPoint;
-import org.eclipse.core.runtime.IExtensionRegistry;
import org.eclipse.core.runtime.Platform;
import org.osgi.framework.Bundle;
@@ -30,7 +28,6 @@
public class VpeAllTests {
public static final String TESTS_ELEMENT = "tests";
- public static final String VPE_TEST_EXTENTION_POINT_ID = "org.jboss.tools.vpe.ui.tests"; //$NON-NLS-1$
public static final String TEST_SUITE_PARAM = "testSuite"; //$NON-NLS-1$
public static final String METHOD_SUITE_NAME = "suite"; //$NON-NLS-1$
public static final String VPE_TEST_PROJECT_NAME = "vpeTest"; //$NON-NLS-1$
@@ -38,12 +35,7 @@
public static Test suite() {
TestSuite result = new TestSuite();
- IExtensionRegistry extensionRepository = Platform
- .getExtensionRegistry();
-
- IExtensionPoint extensionPoint = extensionRepository
- .getExtensionPoint(VPE_TEST_EXTENTION_POINT_ID);
- IExtension[] extensions = extensionPoint.getExtensions();
+ IExtension[] extensions = VPETestPlugin.getDefault().getVpeTestExtensions();
for (IExtension extension : extensions) {
IConfigurationElement[] confElements = extension
.getConfigurationElements();
@@ -71,5 +63,4 @@
return result;
}
-
}
Modified: trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/VpeTest.java
===================================================================
--- trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/VpeTest.java 2010-02-24 22:54:57 UTC (rev 20483)
+++ trunk/vpe/tests/org.jboss.tools.vpe.ui.test/src/org/jboss/tools/vpe/ui/test/VpeTest.java 2010-02-25 13:24:40 UTC (rev 20484)
@@ -13,6 +13,7 @@
package org.jboss.tools.vpe.ui.test;
+import java.io.IOException;
import java.util.Collection;
import java.util.Map;
@@ -350,9 +351,10 @@
*
* @return VpeController
* @throws CoreException
+ * @throws IOException
*/
- protected VpeController openInVpe(String projectName, String fileName) throws CoreException
- {
+ protected VpeController openInVpe(String projectName, String fileName)
+ throws CoreException, IOException {
// get test page path
final IFile file =
(IFile) TestUtil.getComponentPath(fileName, projectName);
14 years, 2 months
JBoss Tools SVN: r20482 - trunk/documentation/guides/JBDS_3.0_Release_Notes/en-US.
by jbosstools-commits@lists.jboss.org
Author: irooskov(a)redhat.com
Date: 2010-02-24 17:52:17 -0500 (Wed, 24 Feb 2010)
New Revision: 20482
Modified:
trunk/documentation/guides/JBDS_3.0_Release_Notes/en-US/Fixed_Issues.xml
Log:
corrected spelling
Modified: trunk/documentation/guides/JBDS_3.0_Release_Notes/en-US/Fixed_Issues.xml
===================================================================
--- trunk/documentation/guides/JBDS_3.0_Release_Notes/en-US/Fixed_Issues.xml 2010-02-24 21:19:35 UTC (rev 20481)
+++ trunk/documentation/guides/JBDS_3.0_Release_Notes/en-US/Fixed_Issues.xml 2010-02-24 22:52:17 UTC (rev 20482)
@@ -35,13 +35,13 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5653">JBIDE-5653</ulink>: The <guilabel>ESB Content Based Router </guilabel> dialog box has been modified so that the <guilabel>CBR Alias</guilabel> field is now mondatory, allowing the value of it to determine what other fields are available. The <guilabel>Rule Set</guilabel> field is now not required when a <guilabel>CBR Alias</guilabel> of Regex or XPath is provided, since with these alias the rules can be specified inline and the <guilabel>Rule Language</guilabel> field is now set to apply only when the <guilabel>CBR Alias</guilabel> is Drools. The <guilabel>Rules Reload</guilabel> field will only apply when a <guilabel>Rule Set</guilabel> has been specified.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5653">JBIDE-5653</ulink>: The <guilabel>ESB Content Based Router </guilabel> dialog box has been modified so that the <guilabel>CBR Alias</guilabel> field is now mandatory, allowing the value of it to determine what other fields are available. The <guilabel>Rule Set</guilabel> field is now not required when a <guilabel>CBR Alias</guilabel> of Regex or XPath is provided, since with these alias the rules can be specified in-line and the <guilabel>Rule Language</guilabel> field is now set to apply only when the <guilabel>CBR Alias</guilabel> is Drools. The <guilabel>Rules Reload</guilabel> field will only apply when a <guilabel>Rule Set</guilabel> has been specified.
</para>
<para>
The table <guilabel>Route List</guilabel> found in the <guilabel>JBoss ESB Editor</guilabel> now lists the <emphasis>expression</emphasis> since this is a common undertaking by users.
</para>
<para>
- In the <guilabel> Add Route To</guilabel> dialog box, the <guilabel>Service Category</guilabel> field has been made mandatory. Other changes to this dialog box include the <guilabel>Desitination name</guilabel> only being required if the previous CBR action contained a <guilabel>Rule Set</guilabel> and if the CBR action did not contain a <guilabel>Rule Set</guilabel>, an <guilabel>Expression</guilabel> field is included.
+ In the <guilabel> Add Route To</guilabel> dialog box, the <guilabel>Service Category</guilabel> field has been made mandatory. Other changes to this dialog box include the <guilabel>Destination name</guilabel> only being required if the previous CBR action contained a <guilabel>Rule Set</guilabel> and if the CBR action did not contain a <guilabel>Rule Set</guilabel>, an <guilabel>Expression</guilabel> field is included.
</para>
</listitem>
<listitem>
@@ -71,12 +71,12 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5427">JBIDE-5427</ulink>: In the ESB Editor, the items that displayed when right clicking and going to <menuchoice><guimenuitem>Provider</guimenuitem><guimenuitem>New</guimenuitem></menuchoice> were presented in a different order to those of the <menuchoice><guimenuitem>Listner</guimenuitem><guimenuitem>New</guimenuitem></menuchoice> list. To ensure consistency the <guimenuitem>Provider</guimenuitem> list of items has been reordered to match the <guimenuitem>Listner</guimenuitem> menu.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5427">JBIDE-5427</ulink>: In the ESB Editor, the items that displayed when right clicking and going to <menuchoice><guimenuitem>Provider</guimenuitem><guimenuitem>New</guimenuitem></menuchoice> were presented in a different order to those of the <menuchoice><guimenuitem>Listener</guimenuitem><guimenuitem>New</guimenuitem></menuchoice> list. To ensure consistency the <guimenuitem>Provider</guimenuitem> list of items has been reordered to match the <guimenuitem>Listener</guimenuitem> menu.
</para>
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5229">JBIDE-5229</ulink>: ESB 4.7 that is contained within <application>JBoss SOA Platform 5.0</application> is now offically supported in this version of the <application>JBoss Developer Studio</application>.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5229">JBIDE-5229</ulink>: ESB 4.7 that is contained within <application>JBoss SOA Platform 5.0</application> is now officially supported in this version of the <application>JBoss Developer Studio</application>.
</para>
</listitem>
<listitem>
@@ -86,7 +86,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5108">JBIDE-5108</ulink>: The JBoss Runtime Manager was setup to search for ESB Runtime files from a specified location reguardless of how it was installed. This caused issue when the ESB Runtime was installed as a user defined runtime. The issue has been rectified by adding a <guilabel>Configuration</guilabel> field to the <guilabel>Preference</guilabel> page. If the user sets the <guilabel>Configuration</guilabel> field to the home location of the <application>JBoss Enterprise Application Platform</application> or <application>JBoss SOA Platform</application>, there configuration combination will list all available configurations. If the user selects a standalone ESB Runtime location, the configuration combination will be empty and the user should ignore the field. The ESB runtime classpath container now gathers configuration information from the selected server runtime and then selects JARs accordingly or the s!
tandalone ESB Runtime.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5108">JBIDE-5108</ulink>: The JBoss Runtime Manager was setup to search for ESB Runtime files from a specified location regardless of how it was installed. This caused issue when the ESB Runtime was installed as a user defined runtime. The issue has been rectified by adding a <guilabel>Configuration</guilabel> field to the <guilabel>Preference</guilabel> page. If the user sets the <guilabel>Configuration</guilabel> field to the home location of the <application>JBoss Enterprise Application Platform</application> or <application>JBoss SOA Platform</application>, there configuration combination will list all available configurations. If the user selects a standalone ESB Runtime location, the configuration combination will be empty and the user should ignore the field. The ESB runtime classpath container now gathers configuration information from the selected server runtime and then selects JARs accordingly or the st!
andalone ESB Runtime.
</para>
</listitem>
<listitem>
@@ -106,7 +106,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-2024">JBIDE-2024</ulink>: The <guilabel>Process</guilabel> field f the <guilabel>Action</guilabel> tab in the ESB now includes a <guibutton>Browse</guibutton> button that allows a user to select which method of the <classname>Action</classname> class should be used for the proces. The list in the dialog will show all public methods that has a <property>Message</property> parameter. Multiple methods can be selected if necessary.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-2024">JBIDE-2024</ulink>: The <guilabel>Process</guilabel> field f the <guilabel>Action</guilabel> tab in the ESB now includes a <guibutton>Browse</guibutton> button that allows a user to select which method of the <classname>Action</classname> class should be used for the process. The list in the dialog will show all public methods that has a <property>Message</property> parameter. Multiple methods can be selected if necessary.
</para>
</listitem>
<listitem>
@@ -133,7 +133,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5641">JBIDE-5641</ulink>: When specifying the persistence property: <property><property name="hibernate.ejb.cfgfile" value="hibernate.cfg.xml"/></property>, an error could display saying that the <filename>hibernate.cfg.xml</filename> file could not be found. This occured because the validator only considered full paths and not relative path naming. This has since been corrected through the modification of the <classname>HibernatePersistenceUnit</classname> class.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5641">JBIDE-5641</ulink>: When specifying the persistence property: <property><property name="hibernate.ejb.cfgfile" value="hibernate.cfg.xml"/></property>, an error could display saying that the <filename>hibernate.cfg.xml</filename> file could not be found. This occurred because the validator only considered full paths and not relative path naming. This has since been corrected through the modification of the <classname>HibernatePersistenceUnit</classname> class.
</para>
</listitem>
<listitem>
@@ -170,7 +170,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5222">JBIDE-5222</ulink>: A new feature as been added that allows for support of <guilabel>filter configurations in closed porjects</guilabel> for console configuration. This option is available through <menuchoice><guimenuitem>Preferences</guimenuitem><guimenuitem>Run/Debug</guimenuitem><guimenuitem>Launching</guimenuitem><guimenuitem>Launch Configurations</guimenuitem></menuchoice>.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5222">JBIDE-5222</ulink>: A new feature as been added that allows for support of <guilabel>filter configurations in closed projects</guilabel> for console configuration. This option is available through <menuchoice><guimenuitem>Preferences</guimenuitem><guimenuitem>Run/Debug</guimenuitem><guimenuitem>Launching</guimenuitem><guimenuitem>Launch Configurations</guimenuitem></menuchoice>.
</para>
</listitem>
<listitem>
@@ -215,12 +215,12 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4666">JBIDE-4662</ulink>: Annotations support has been added to Hibernate Tools. The addittion of annotations support allows for interaction with the Eclipse Dali Java Persistence Tools Project plug-in.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4666">JBIDE-4662</ulink>: Annotations support has been added to Hibernate Tools. The addition of annotations support allows for interaction with the Eclipse Dali Java Persistence Tools Project plug-in.
</para>
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4451">JBIDE-4451</ulink>: The option is now given to the user to enable the <guilabel>HQL Editor</guilabel> and <guilabel>Hibernate Criteria Editor</guilabel> to be dynamicly updated when opening a new query instead of opening an instance of each editor for each query. This can be achieved by clicking the button of a tack to the right of the <guilabel>Max resutls:</guilabel> drop-won box in the editor.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4451">JBIDE-4451</ulink>: The option is now given to the user to enable the <guilabel>HQL Editor</guilabel> and <guilabel>Hibernate Criteria Editor</guilabel> to be dynamically updated when opening a new query instead of opening an instance of each editor for each query. This can be achieved by clicking the button of a tack to the right of the <guilabel>Max results:</guilabel> drop-won box in the editor.
</para>
</listitem>
<listitem>
@@ -315,7 +315,7 @@
<ulink url="http://jira.jboss.com/jira/browse/JBIDE-816">JBIDE-816</ulink>: A bug existed within the JSF component of the <application>JBoss Developer Studio</application> where if a resource bundle is defined in a template page code completion for the bundle would not be available within the file that includes the template with the loadbundles. The workaround for this was to also define the resource bundle in this template client file, however that meant the same component was defined twice in the component tree.
</para>
<para>
- The bug has since been fixed by adding a schema for included page contexts. This schema enables the creation of contexts for all the pages included in the source and for the gathering of information on bundles delared in the included pages. The information collected is as follows:
+ The bug has since been fixed by adding a schema for included page contexts. This schema enables the creation of contexts for all the pages included in the source and for the gathering of information on bundles declared in the included pages. The information collected is as follows:
</para>
<itemizedlist>
<listitem>
@@ -325,7 +325,7 @@
</listitem>
<listitem>
<para>
- Tag labraries that are used
+ Tag libraries that are used
</para>
</listitem>
<listitem>
@@ -371,7 +371,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5221">JBIDE-5221</ulink>: The <guilabel>JBoss Server View</guilabel> has now been replaced with the <guilabel>Server View</guilabel> in the Seam perspective. This has occured out of the <guilabel>JBoss Server View</guilabel> being depricated.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5221">JBIDE-5221</ulink>: The <guilabel>JBoss Server View</guilabel> has now been replaced with the <guilabel>Server View</guilabel> in the Seam perspective. This has occurred out of the <guilabel>JBoss Server View</guilabel> being deprecated.
</para>
</listitem>
<listitem>
@@ -428,7 +428,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4136">JBIDE-4136</ulink>: Classloading issues were being faced by users of Seam Tools because the <application>JBoss Developer Studio</application> used the <filename>MANIFEST.MF</filename> file for creating an arifact classpath instead of using the EAR <filename>lib/</filename> directory that is recommended by Seam. Until now the <application>JBoss Developer Studio</application> has not been able to use the EAR <filename>lib/</filename> directory because this functionality has not been supported by Eclipse. With the introduction of Eclipse 3.5 in this release the use of the EAR <filename>lib/</filename> directory is now supported and the process of creating an artifact classpath has been updated.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4136">JBIDE-4136</ulink>: Classloading issues were being faced by users of Seam Tools because the <application>JBoss Developer Studio</application> used the <filename>MANIFEST.MF</filename> file for creating an artifact classpath instead of using the EAR <filename>lib/</filename> directory that is recommended by Seam. Until now the <application>JBoss Developer Studio</application> has not been able to use the EAR <filename>lib/</filename> directory because this functionality has not been supported by Eclipse. With the introduction of Eclipse 3.5 in this release the use of the EAR <filename>lib/</filename> directory is now supported and the process of creating an artifact classpath has been updated.
</para>
</listitem>
<listitem>
@@ -556,7 +556,7 @@
</listitem>
<listitem>
<para>
- The <methodname>createPartControl()</methodname> method in the <classname>MozillaEditor</classname> and <classname>MozillaPreview</classname> classes create <classname>XullRunnerEditor</classname> as an inner class. The issue was that the <classname>XullRunnerEditor</classname> class retained a reference to <classname>MozillaEditor(MozillaPreview)</classname> that caused it not to be released and instead retain references to WST and EMF classes. This has now been corrected so that <classname>MozillaEditor(MozillaPreview)</classname> is now released after use and referecnes are not retained.
+ The <methodname>createPartControl()</methodname> method in the <classname>MozillaEditor</classname> and <classname>MozillaPreview</classname> classes create <classname>XullRunnerEditor</classname> as an inner class. The issue was that the <classname>XullRunnerEditor</classname> class retained a reference to <classname>MozillaEditor(MozillaPreview)</classname> that caused it not to be released and instead retain references to WST and EMF classes. This has now been corrected so that <classname>MozillaEditor(MozillaPreview)</classname> is now released after use and references are not retained.
</para>
</listitem>
</itemizedlist>
@@ -583,7 +583,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4934">JBIDE-4934</ulink>: Facelets tag librarys support has been added to the <guilabel>Palette</guilabel> for the Visual Page Editor.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4934">JBIDE-4934</ulink>: Facelets tag library support has been added to the <guilabel>Palette</guilabel> for the Visual Page Editor.
</para>
</listitem>
<listitem>
@@ -665,12 +665,12 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-2571">JBIDE-2571</ulink>: Selection of the <property><h:selectOneMenu></property> did not function correctly. Instead of being selected with one mouse click, two clicks were necessary. A bug was also present that made the nested components <property><f:selectItem></property> and <property><f:selectItems></property> unable to be selected from within the Visual Page Editor. Correction of the two clicks necessary to select the <property><h:selectOneMenu></property> component has been completed by removing the check within <filename>VpeController.java</filename> that ensures the node is of type text. The issue that did not allow for the selection of the <property><f:selectItem></property> and <property><f:selectItems></property> components was found to be a bug in XULRunner. To correct this the XULRunner component has been updated to version 1.9, which corrects this error and provides!
numerious other small bug fixes (<ulink url="http://jira.jboss.com/jira/browse/JBIDE-2248">JBIDE-2248</ulink>.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-2571">JBIDE-2571</ulink>: Selection of the <property><h:selectOneMenu></property> did not function correctly. Instead of being selected with one mouse click, two clicks were necessary. A bug was also present that made the nested components <property><f:selectItem></property> and <property><f:selectItems></property> unable to be selected from within the Visual Page Editor. Correction of the two clicks necessary to select the <property><h:selectOneMenu></property> component has been completed by removing the check within <filename>VpeController.java</filename> that ensures the node is of type text. The issue that did not allow for the selection of the <property><f:selectItem></property> and <property><f:selectItems></property> components was found to be a bug in XULRunner. To correct this the XULRunner component has been updated to version 1.9, which corrects this error and provides!
numerous other small bug fixes (<ulink url="http://jira.jboss.com/jira/browse/JBIDE-2248">JBIDE-2248</ulink>.
</para>
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-2248">JBIDE-2248</ulink>: The XULRunner component has been upgraded to version 1.9. This new version of XULRunner adds support for the newest HTML and CSS features to the Visual Page Editor. Inlcuded in this is support for CSS3.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-2248">JBIDE-2248</ulink>: The XULRunner component has been upgraded to version 1.9. This new version of XULRunner adds support for the newest HTML and CSS features to the Visual Page Editor. Included in this is support for CSS3.
</para>
</listitem>
<listitem>
@@ -680,7 +680,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-527">JBIDE-527</ulink>: A bug existed within the Visual Page Editor that enhibited the <guibutton>Previous</guibutton> and <guibutton>Next</guibutton> buttons for detected occurances of searched annotations to not function correctly. The action of these buttons has now been corrected so that a user can navigate their way through all found occurances of a searched annotation. This functionality works in the Visual Page Editor as it would work in a text editor.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-527">JBIDE-527</ulink>: A bug existed within the Visual Page Editor that inhibited the <guibutton>Previous</guibutton> and <guibutton>Next</guibutton> buttons for detected occurrences of searched annotations to not function correctly. The action of these buttons has now been corrected so that a user can navigate their way through all found occurrences of a searched annotation. This functionality works in the Visual Page Editor as it would work in a text editor.
</para>
</listitem>
</itemizedlist>
@@ -726,7 +726,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5734">JBIDE-5734</ulink>: The shortcut keys for full pubilshing a project to the server and building a full archive have been combined under then shortcut key menu accessed with <keycombo><keycap>Alt</keycap><keycap>Shift</keycap><keycap>Y</keycap></keycombo>. From this menu press <keycap>F</keycap> to full pubilsh the project or <keycap>B</keycap> to build the full archive.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5734">JBIDE-5734</ulink>: The shortcut keys for full publishing a project to the server and building a full archive have been combined under then shortcut key menu accessed with <keycombo><keycap>Alt</keycap><keycap>Shift</keycap><keycap>Y</keycap></keycombo>. From this menu press <keycap>F</keycap> to full publish the project or <keycap>B</keycap> to build the full archive.
</para>
</listitem>
<listitem>
@@ -741,7 +741,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5743">JBIDE-5267</ulink>: The <application>JBoss Enterprise Application Platform</application> server would start correctly, however the <application>JBoss Developer Studio</application> would not acknowledge that it had started. To counteract this the <filename>JMXPoller.java</filename> timeout behaviour has been modified to always return that the server succeeded in starting instead of ignoring the timeout. This fix ensures that a user is not informed that the server did not start correctly when it did.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5743">JBIDE-5267</ulink>: The <application>JBoss Enterprise Application Platform</application> server would start correctly, however the <application>JBoss Developer Studio</application> would not acknowledge that it had started. To counteract this the <filename>JMXPoller.java</filename> timeout behavior has been modified to always return that the server succeeded in starting instead of ignoring the timeout. This fix ensures that a user is not informed that the server did not start correctly when it did.
</para>
</listitem>
<listitem>
@@ -788,7 +788,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5005">JBIDE-5005</ulink>: A new export wizard has been added to the <application>JBoss Developer Studio</application>. The new wizard allows the export operation to utilize IModule objects. This added feature reduces redundancy and inconsistancy for the export operation.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-5005">JBIDE-5005</ulink>: A new export wizard has been added to the <application>JBoss Developer Studio</application>. The new wizard allows the export operation to utilize IModule objects. This added feature reduces redundancy and inconsistency for the export operation.
</para>
</listitem>
<listitem>
@@ -796,7 +796,7 @@
<ulink url="http://jira.jboss.com/jira/browse/JBIDE-4976">JBIDE-4976</ulink>: The <guilabel>JBoss Tools Palette</guilabel> has been intergrated into the standard Eclipse GEF <guilabel>Palette</guilabel> view. The standard <guilabel>Palette</guilabel> view, accessible at <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Show View</guimenuitem><guimenuitem>Others</guimenuitem><guimenuitem>General</guimenuitem><guimenuitem>Palette</guimenuitem></menuchoice> is now shown in the right top part of the <guilabel>Web Development</guilabel> and <guilabel>Seam</guilabel> perspectives. The <guilabel>JBoss Tools Palette</guilabel> remains at <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Show View</guimenuitem><guimenuitem>Others</guimenuitem><guimenuitem>JBoss Tools Web</guimenuitem><guimenuitem>JBoss Tools Palette</guimenuitem></menuchoice>.
</para>
<para>
- The differences in behaviour between the paletts are:
+ The differences in behavior between the palettes are:
</para>
<itemizedlist>
<listitem>
@@ -811,7 +811,7 @@
</listitem>
</itemizedlist>
<para>
- Though the behaviour of the new palette is standard for Eclipse, for customers used to the globally set state of tabs and perfer to customize the palette before opening the <guilabel>Visual Page Editor</guilabel>, the old palette will remain accessible.
+ Though the behavior of the new palette is standard for Eclipse, for customers used to the globally set state of tabs and perfer to customize the palette before opening the <guilabel>Visual Page Editor</guilabel>, the old palette will remain accessible.
</para>
</listitem>
<listitem>
@@ -826,7 +826,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4888">JBIDE-4888</ulink>: The porlet facets configuration utility has been added for m2eclipse. This configuration utility allows for the following:
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4888">JBIDE-4888</ulink>: The portlet facets configuration utility has been added for m2eclipse. This configuration utility allows for the following:
</para>
<itemizedlist>
<listitem>
@@ -853,7 +853,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4850">JBIDE-4850</ulink>: A new feature has been added to the CSS Views with this release that allows a user to edit styles inside html and xhtm.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-4850">JBIDE-4850</ulink>: A new feature has been added to the CSS Views with this release that allows a user to edit styles inside HTML and xhtm.
</para>
</listitem>
<listitem>
@@ -936,7 +936,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-3563">JBIDE-3563</ulink>: Code assist has been added for classes that are defined in linked CSS. The schema for included page contexts has been added. This has occured as it is needed to create the contexts for all the pages included in the source. It allows for the gathering of information on bundles declared in included pages.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-3563">JBIDE-3563</ulink>: Code assist has been added for classes that are defined in linked CSS. The schema for included page contexts has been added. This has occurred as it is needed to create the contexts for all the pages included in the source. It allows for the gathering of information on bundles declared in included pages.
</para>
<para>
The included page contexts are created and the following information is collected within the included contexts:
@@ -949,7 +949,7 @@
</listitem>
<listitem>
<para>
- Tag labraries are used in the included pages
+ Tag libraries are used in the included pages
</para>
</listitem>
<listitem>
14 years, 2 months
JBoss Tools SVN: r20480 - trunk/struts/tests/org.jboss.tools.struts.vpe.struts.test/src/org/jboss/tools/struts/vpe/struts/test.
by jbosstools-commits@lists.jboss.org
Author: yradtsevich
Date: 2010-02-24 16:18:37 -0500 (Wed, 24 Feb 2010)
New Revision: 20480
Modified:
trunk/struts/tests/org.jboss.tools.struts.vpe.struts.test/src/org/jboss/tools/struts/vpe/struts/test/StrutsHTMLComponentTest.java
Log:
https://jira.jboss.org/jira/browse/JBIDE-5837
Make possible to run VPE JUnit tests one by one
- Struts VPE test are being failed on Hudson. waitForJobs has been added to check if it helps.
Modified: trunk/struts/tests/org.jboss.tools.struts.vpe.struts.test/src/org/jboss/tools/struts/vpe/struts/test/StrutsHTMLComponentTest.java
===================================================================
--- trunk/struts/tests/org.jboss.tools.struts.vpe.struts.test/src/org/jboss/tools/struts/vpe/struts/test/StrutsHTMLComponentTest.java 2010-02-24 19:50:11 UTC (rev 20479)
+++ trunk/struts/tests/org.jboss.tools.struts.vpe.struts.test/src/org/jboss/tools/struts/vpe/struts/test/StrutsHTMLComponentTest.java 2010-02-24 21:18:37 UTC (rev 20480)
@@ -91,6 +91,10 @@
}
public void testLink() throws Throwable {
+ // XXX wait is added just to check if the test will fail on Hudson.
+ // Most probably it is not needed.
+ TestUtil.waitForIdle();
+
performTestForVpeComponent((IFile)TestUtil.getComponentPath("components/html/link.jsp", IMPORT_PROJECT_NAME)); //$NON-NLS-1$
}
14 years, 2 months
JBoss Tools SVN: r20479 - branches/jbosstools-3.1.x/examples/plugins/org.jboss.tools.project.examples.
by jbosstools-commits@lists.jboss.org
Author: snjeza
Date: 2010-02-24 14:50:11 -0500 (Wed, 24 Feb 2010)
New Revision: 20479
Modified:
branches/jbosstools-3.1.x/examples/plugins/org.jboss.tools.project.examples/plugin.properties
branches/jbosstools-3.1.x/examples/plugins/org.jboss.tools.project.examples/plugin.xml
Log:
https://jira.jboss.org/jira/browse/JBIDE-5850 JBT Project Examples only includes SEAM & RESTEasy (& BPEL)
Modified: branches/jbosstools-3.1.x/examples/plugins/org.jboss.tools.project.examples/plugin.properties
===================================================================
--- branches/jbosstools-3.1.x/examples/plugins/org.jboss.tools.project.examples/plugin.properties 2010-02-24 19:25:12 UTC (rev 20478)
+++ branches/jbosstools-3.1.x/examples/plugins/org.jboss.tools.project.examples/plugin.properties 2010-02-24 19:50:11 UTC (rev 20479)
@@ -6,5 +6,3 @@
Project_Examples_command =Project Examples...
ProjectExamples=Project Examples file
Project_Examples = Project Examples
-JBoss_Developer_Studio_Examples = JBoss Developer Studio Examples
-JBoss_Developer_Studio30_Examples = JBoss Developer Studio 3.0 Examples
\ No newline at end of file
Modified: branches/jbosstools-3.1.x/examples/plugins/org.jboss.tools.project.examples/plugin.xml
===================================================================
--- branches/jbosstools-3.1.x/examples/plugins/org.jboss.tools.project.examples/plugin.xml 2010-02-24 19:25:12 UTC (rev 20478)
+++ branches/jbosstools-3.1.x/examples/plugins/org.jboss.tools.project.examples/plugin.xml 2010-02-24 19:50:11 UTC (rev 20479)
@@ -67,20 +67,5 @@
point="org.eclipse.core.runtime.preferences">
<initializer class="org.jboss.tools.project.examples.preferences.ProjectExamplesPreferencesInitializer"/>
</extension>
-
- <extension
- point="org.jboss.tools.project.examples.projectExamplesXml"
- name="%JBoss_Developer_Studio_Examples">
- <url>http://download.jboss.org/jbosstools/examples/project-examples-3.0.xml</url>
- <experimental>false</experimental>
- </extension>
-
- <extension
- point="org.jboss.tools.project.examples.projectExamplesXml"
- name="%JBoss_Developer_Studio30_Examples">
- <url>http://download.jboss.org/jbosstools/examples/project-examples-jbds30.xml</url>
- <experimental>false</experimental>
- </extension>
-
</plugin>
14 years, 2 months
JBoss Tools SVN: r20478 - workspace/examples.
by jbosstools-commits@lists.jboss.org
Author: snjeza
Date: 2010-02-24 14:25:12 -0500 (Wed, 24 Feb 2010)
New Revision: 20478
Modified:
workspace/examples/project-examples-3.1.xml
workspace/examples/project-examples-jbds30.xml
Log:
Modified: workspace/examples/project-examples-3.1.xml
===================================================================
--- workspace/examples/project-examples-3.1.xml 2010-02-24 19:24:43 UTC (rev 20477)
+++ workspace/examples/project-examples-3.1.xml 2010-02-24 19:25:12 UTC (rev 20478)
@@ -355,9 +355,574 @@
</fix>
<fix type="plugin">
<property name="id">org.maven.ide.eclipse.wtp</property>
- <property name="versions">0.9.9, 0.10.0</property>
+ <property name="versions">0.10.0</property>
<property name="description">This project example requires m2eclipse. You can install it using the following update sites: http://m2eclipse.sonatype.org/sites/m2e and http://m2eclipse.sonatype.org/sites/m2e-extras</property>
</fix>
</fixes>
</project>
+
+ <project>
+ <category>ESB for SOA-P 5.0</category>
+ <name>helloworld</name>
+ <shortDescription>JBoss ESB HelloWorld Example - ESB</shortDescription>
+ <description>NOTE: Before import this example, please make sure that there is a runtime named "jboss-soa-p.5.0 Runtime" in the workspace.
+ This example is to prove that the ESB is is properly configured and happy.
+As well as to demonstrate the needed minimal files to make a basic ESB component execute.</description>
+ <size>59000</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB for SOA-P 5.0</category>
+ <name>helloworld_testclient</name>
+ <shortDescription>JBoss ESB HelloWorld Example - Client</shortDescription>
+ <description>NOTE: Before import this example, please make sure that there is runtime named "jboss-soa-p.5.0 Runtime" in the workspace.
+ This example is to demonstrate how to invoke the deployed HelloWorld ESB. It requires the helloworld project.</description>
+ <size>1000000</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB for SOA-P 5.0</category>
+ <name>helloworld_action</name>
+ <shortDescription>JBoss ESB HelloWorld Action Example - ESB</shortDescription>
+ <description>NOTE: Before import this example, please make sure that there is runtime named "jboss-soa-p.5.0 Runtime" in the workspace.
+ This sample is to demonstrate the use of multiple action invocations from a single configuration. You can use
+ a single Action class and make multiple method calls or use multiple Action
+ classes.</description>
+ <size>7100</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB for SOA-P 5.0</category>
+ <name>helloworld_action_client</name>
+ <shortDescription>JBoss ESB HelloWorld Action Example - Client</shortDescription>
+ <description>NOTE: Before import this example, please make sure that there is runtime named "jboss-soa-p.5.0 Runtime" in the workspace.
+ This sample is to test the deployed helloworld_action ESB. It requires the helloworld_action project</description>
+ <size>18694</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB for SOA-P 5.0</category>
+ <name>helloworld_file_action</name>
+ <shortDescription>JBoss ESB HelloWorld File Action Example - ESB</shortDescription>
+ <description>NOTE: Before import this example, please make sure that there is runtime named "jboss-soa-p.5.0 Runtime" in the workspace.
+ This is a basic example of using the File gateway feature of the JBoss ESB.
+ Files that are found in a particular directory with a particular extension
+ are sent to a JMS queue with actions for processing. Before deploy the project, please change some properties according to the readme.txt file.</description>
+ <size>7920</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB for SOA-P 5.0</category>
+ <name>helloworld_file_action_client</name>
+ <shortDescription>JBoss ESB HelloWorld File Action Example - Client</shortDescription>
+ <description>NOTE: Before import this example, please make sure that there is runtime named "jboss-soa-p.5.0 Runtime" in the workspace.
+ This sample is to test the deployed helloworld_file_action ESB. It requires the helloworld_file_action project.</description>
+ <size>18694</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa...
+ </url>
+ </project>
+ <project>
+ <category>ESB for SOA-P 5.0</category>
+ <name>webservice_consumer1</name>
+ <shortDescription>JBoss ESB Web Service consumer1 Example</shortDescription>
+ <description>NOTE: Before import this example, please make sure that there is runtime named "jboss-soa-p.5.0 Runtime" in the workspace.
+ This example demonstrates how to consume a 181 Web Service in an ESB action.
+ This ESB will make a webservice request that requires a single "toWhom" string parameter.
+ The webservice will return a greeting response. The ESB simply dislays the response on the
+ console.</description>
+ <size>22500</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB for SOA-P 5.0</category>
+ <name>webservice_consumer1_client</name>
+ <shortDescription>JBoss ESB Web Service consumer1 Example - Client</shortDescription>
+ <description>NOTE: Before import this example, please make sure that there is runtime named "jboss-soa-p.5.0 Runtime" in the workspace.
+ This sample is to test the deployed a comsumer web service.It requires the webservice_consumer1 project.</description>
+ <size>1000000</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB for SOA-P 5.0</category>
+ <name>webservice_producer</name>
+ <shortDescription>JBoss ESB Web Service producer Example</shortDescription>
+ <description>NOTE: Before import this example, please make sure that there is runtime named "jboss-soa-p.5.0 Runtime" in the workspace.
+ This sample demonstrates how to deploy a JSR181 Webservice endpoint on
+ JBossESB using the SOAPProcessor action.</description>
+ <size>53000</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB for SOA-P 5.0</category>
+ <name>webservice_producer_client</name>
+ <shortDescription>JBoss ESB Web Service producer Example - Client</shortDescription>
+ <description>NOTE: Before import this example, please make sure that there is runtime named "jboss-soa-p.5.0 Runtime" in the workspace.
+ This sample is to test the deployed a web service endpoint.It requires the webservice_producer project.</description>
+ <size>14200</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB for SOA-P 5.0</category>
+ <name>transform_CSV2XML</name>
+ <shortDescription>JBoss ESB Smooks CSV->XML Example</shortDescription>
+ <description>NOTE: Before import this example, please make sure that there is runtime named "jboss-soa-p.5.0 Runtime" in the workspace.
+ This sample demonstrates how to transform a comma separated value (CSV) file to an xml.
+ The tranformation is done by configuring Smooks and performing two transformation, one
+ transformation from CSV to an intermediate xml format, and a second transformation from
+ the intermediate xml format to the target xml.</description>
+ <size>7200</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB for SOA-P 5.0</category>
+ <name>transform_CSV2XML_client</name>
+ <shortDescription>JBoss ESB Smooks CSV->XML Example - Client</shortDescription>
+ <description>NOTE: Before import this example, please make sure that there is runtime named "jboss-soa-p.5.0 Runtime" in the workspace.
+ This sample is to test the JBoss ESB smooks CSV->XML transformation.It requires the transform_CSV2XML project.</description>
+ <size>16600</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB for SOA-P 5.0</category>
+ <name>transform_XML2POJO</name>
+ <shortDescription>JBoss ESB Smooks XML->POJO Example</shortDescription>
+ <description>NOTE: Before import this example, please make sure that there is runtime named "jboss-soa-p.5.0 Runtime" in the workspace.
+ The purpose of the simple_transformation sample is to illustrate the
+use of Smooks performing a simple transformation by converting a XML file into
+Java POJOs.</description>
+ <size>26600</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB for SOA-P 5.0</category>
+ <name>transform_XML2POJO_client</name>
+ <shortDescription>JBoss ESB Smooks XML->POJO Example - Client</shortDescription>
+ <description>NOTE: Before import this example, please make sure that there is runtime named "jboss-soa-p.5.0 Runtime" in the workspace.
+ This sample is to test the JBoss ESB smooks XML->POJO transformation.It requires the transform_XML2POJO project.</description>
+ <size>22400</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB for SOA-P 5.0</category>
+ <name>transform_XML2XML_date_manipulation</name>
+ <shortDescription>JBoss ESB Smooks XML->XML date-manipulation Example</shortDescription>
+ <description>NOTE: Before import this example, please make sure that there is runtime named "jboss-soa-p.5.0 Runtime" in the workspace.
+ This is another simple sample of how to manually define and apply a Message
+ Transformation within JBoss ESB.
+
+ This sample is an extension of the "transformation_XML2XML_simple"
+ Quickstart, demonstrating how JBoss ESB Transformations can simplify your
+ XSLT transformations by combining the power of XSLT with Java. In this
+ Quickstart, we use Java to perform the ugly string manipulation on the
+ SampleOrder date field (see OrderDate.java) and use XSLT for what it's good at
+ i.e. Templating. Again, the transformed SampleOrder.xml message is just
+ printed to the Java console (message before and after).</description>
+ <size>13600</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB for SOA-P 5.0</category>
+ <name>transform_XML2XML_date_manipulation_client</name>
+ <shortDescription>JBoss ESB Smooks XML->XML date-manipulation Example - Client</shortDescription>
+ <description>NOTE: Before import this example, please make sure that there is runtime named "jboss-soa-p.5.0 Runtime" in the workspace.
+ This sample is to test the JBoss ESB XML->XML date-manipulation transformation.It requires the transform_XML2XML_date_manipulation project.</description>
+ <size>18600</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB for SOA-P 5.0</category>
+ <name>transform_XML2XML_simple</name>
+ <shortDescription>JBoss ESB Smooks XML->XML Example</shortDescription>
+ <description>NOTE: Before import this example, please make sure that there is runtime named "jboss-soa-p.5.0 Runtime" in the workspace.
+ This is a very basic sample of how to manually define and apply a Message
+ Transformation within JBoss ESB. It applies a very simple XSLT to a
+ SampleOrder.xml message and prints the before and after XML to the console.</description>
+ <size>6700</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB for SOA-P 5.0</category>
+ <name>transform_XML2XML_simple_client</name>
+ <shortDescription>JBoss ESB Smooks XML->XML Example - Client</shortDescription>
+ <description>NOTE: Before import this example, please make sure that there is runtime named "jboss-soa-p.5.0 Runtime" in the workspace.
+ This sample is to test the JBoss ESB XML->XML transformation.It requires the transform_XML2XML_simple project.</description>
+ <size>17800</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa...
+ </url>
+ </project>
+
+ <project>
+
+ <category>Portlet</category>
+ <name>testjavaportlet</name>
+ <shortDescription>JBoss Java Portlet Example</shortDescription>
+ <description>This example demonstrates the use of JBoss Java Portlet. It runs on JBoss EPP 4.3 or JBoss Portal 2.7.x.</description>
+ <size>10000</size>
+ <url>
+
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/portlet-exampl...
+ </url>
+ <welcome type="cheatsheets" url="/testjavaportlet/javaportletcs.xml"/>
+ <fixes>
+ <fix type="wtpruntime">
+ <property name="allowed-types">org.jboss.ide.eclipse.as.runtime.eap.43, org.jboss.ide.eclipse.as.runtime.42</property>
+ <property name="eclipse-projects">testjavaportlet</property>
+ <property name="description">This project example requires the JBoss EPP 4.3 or JBoss Portal 2.7.x</property>
+ </fix>
+
+ </fixes>
+ </project>
+
+ <project>
+ <category>Portlet</category>
+ <name>testjsfportlet</name>
+ <shortDescription>JBoss JSF Portlet Example</shortDescription>
+
+ <description>This example demonstrates the use of JBoss JSF Portlet. It runs on JBoss EPP 4.3 or JBoss Portal 2.7.x.</description>
+ <size>4000000</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/portlet-exampl...
+ </url>
+ <fixes>
+ <fix type="wtpruntime">
+ <property name="allowed-types">org.jboss.ide.eclipse.as.runtime.eap.43, org.jboss.ide.eclipse.as.runtime.42</property>
+ <property name="eclipse-projects">testjsfportlet</property>
+ <property name="description">This project example requires the JBoss EPP 4.3 or JBoss Portal 2.7.x</property>
+ </fix>
+
+ </fixes>
+ </project>
+
+ <project>
+ <category>Portlet</category>
+
+ <name>testseamportlet</name>
+ <shortDescription>JBoss Seam Portlet Example</shortDescription>
+ <description>This example demonstrates the use of JBoss Seam Portlet. It runs on JBoss EPP 4.3/JBoss Portal 2.7.x and Seam 2.0.</description>
+ <size>10000000</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/portlet-exampl...
+ </url>
+ <fixes>
+ <fix type="wtpruntime">
+ <property name="allowed-types">org.jboss.ide.eclipse.as.runtime.eap.43, org.jboss.ide.eclipse.as.runtime.42</property>
+ <property name="eclipse-projects">testseamportlet</property>
+ <property name="description">This project example requires the JBoss EPP 4.3 or JBoss Portal 2.7.x</property>
+ </fix>
+ <fix type="seam">
+ <property name="allowed-versions">2.0.0, 2.0.1, 2.0.2</property>
+ <property name="eclipse-projects">testseamportlet</property>
+ <property name="description">This project example requires Seam version 2.0</property>
+ </fix>
+ </fixes>
+ </project>
+
+ <project>
+ <category>ESB</category>
+ <name>helloworld</name>
+ <shortDescription>JBoss ESB HelloWorld Example - ESB</shortDescription>
+ <description>This example is to prove that the ESB is is properly configured and happy.
+As well as to demonstrate the needed minimal files to make a basic ESB component execute.</description>
+ <size>59000</size>
+
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example/hel...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB</category>
+ <name>helloworld_testclient</name>
+ <shortDescription>JBoss ESB HelloWorld Example - Client</shortDescription>
+
+ <description>This example is to demonstrate how to invoke the deployed HelloWorld ESB. It requires the helloworld project.</description>
+ <size>1000000</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example/hel...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB</category>
+
+ <name>helloworld_action</name>
+ <shortDescription>JBoss ESB HelloWorld Action Example - ESB</shortDescription>
+ <description>This example is to demonstrate the use of multiple action invocations from a single configuration. You can use a single Action class and make multiple method calls or use multiple Action
+ classes.</description>
+ <size>7100</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example/hel...
+ </url>
+
+ </project>
+
+ <project>
+ <category>ESB</category>
+ <name>helloworld_action_client</name>
+ <shortDescription>JBoss ESB HelloWorld Action Example - Client</shortDescription>
+ <description>This example is to test the deployed helloworld_action ESB. It requires the helloworld_action project.</description>
+ <size>18694</size>
+
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example/hel...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB</category>
+ <name>helloworld_file_action</name>
+ <shortDescription>JBoss ESB HelloWorld File Action Example - ESB</shortDescription>
+
+ <description>This is a basic example of using the File gateway feature of the JBoss ESB.
+ Files that are found in a particular directory with a particular extension
+ are sent to a JMS queue with actions for processing. Before deploy the project, please change some properties according to the readme.txt file.</description>
+ <size>7920</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example/hel...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB</category>
+
+ <name>helloworld_file_action_client</name>
+ <shortDescription>JBoss ESB HelloWorld File Action Example - Client</shortDescription>
+ <description>This example is to test the deployed helloworld_file_action ESB. It requires the helloworld_file_action project.</description>
+ <size>18694</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example/hel...
+ </url>
+
+ </project>
+ <project>
+ <category>ESB</category>
+ <name>webservice_consumer1</name>
+ <shortDescription>JBoss ESB Web Service consumer1 Example</shortDescription>
+ <description>This example demonstrates how to consume a 181 Web Service in an ESB action.
+ This ESB will make a webservice request that requires a single "toWhom" string parameter.
+ The webservice will return a greeting response. The ESB simply displays the response on the console.
+ </description>
+ <size>22500</size>
+
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/grid/esb-example/webs...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB</category>
+ <name>webservice_consumer1_client</name>
+ <shortDescription>JBoss ESB Web Service consumer1 Example - Client</shortDescription>
+
+ <description>This example is to test the deployed a consumer web service.It requires the webservice_consumer1 project.</description>
+ <size>1000000</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/grid/esb-example/webs...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB</category>
+
+ <name>webservice_producer</name>
+ <shortDescription>JBoss ESB Web Service producer Example</shortDescription>
+ <description>This sample demonstrates how to deploy a JSR181 Webservice endpoint on
+ JBossESB using the SOAPProcessor action.</description>
+ <size>53000</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/grid/esb-example/webs...
+ </url>
+
+ </project>
+
+ <project>
+ <category>ESB</category>
+ <name>webservice_producer_client</name>
+ <shortDescription>JBoss ESB Web Service producer Example - Client</shortDescription>
+ <description>This sample is to test the deployed a web service endpoint.It requires the webservice_producer project.</description>
+
+ <size>14200</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/grid/esb-example/webs...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB</category>
+ <name>transform_CSV2XML</name>
+
+ <shortDescription>JBoss ESB Smooks CSV->XML Example</shortDescription>
+ <description>This sample demonstrates how to transform a comma separated value (CSV) file to an xml.
+ The tranformation is done by configuring Smooks and performing two transformation, one transformation from CSV to an intermediate xml format, and a second transformation from the intermediate xml format to the target xml.</description>
+ <size>7200</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/grid/esb-example/tran...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB</category>
+ <name>transform_CSV2XML_client</name>
+ <shortDescription>JBoss ESB Smooks CSV->XML Example - Client</shortDescription>
+ <description>This sample is to test the JBoss ESB smooks CSV->XML transformation.It requires the transform_CSV2XML project.</description>
+ <size>16600</size>
+
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/grid/esb-example/tran...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB</category>
+ <name>transform_XML2POJO</name>
+ <shortDescription>JBoss ESB Smooks XML->POJO Example</shortDescription>
+
+ <description>The purpose of the simple_transformation sample is to illustrate the
+use of Smooks performing a simple transformation by converting a XML file into
+Java POJOs.</description>
+ <size>26600</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/grid/esb-example/tran...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB</category>
+
+ <name>transform_XML2POJO_client</name>
+ <shortDescription>JBoss ESB Smooks XML->POJO Example - Client</shortDescription>
+ <description>This sample is to test the JBoss ESB smooks XML->POJO transformation.It requires the transform_XML2POJO project.</description>
+ <size>22400</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/grid/esb-example/tran...
+ </url>
+
+ </project>
+
+ <project>
+ <category>ESB</category>
+ <name>transform_XML2XML_date_manipulation</name>
+ <shortDescription>JBoss ESB Smooks XML->XML date-manipulation Example</shortDescription>
+ <description>This is another simple sample of how to manually define and apply a Message
+ Transformation within JBoss ESB.
+
+ This sample is an extension of the "transformation_XML2XML_simple"
+ Quickstart, demonstrating how JBoss ESB Transformations can simplify your
+ XSLT transformations by combining the power of XSLT with Java. In this
+ Quickstart, we use Java to perform the ugly string manipulation on the
+ SampleOrder date field (see OrderDate.java) and use XSLT for what it's good at
+ i.e. Templating. Again, the transformed SampleOrder.xml message is just
+ printed to the Java console (message before and after).</description>
+
+ <size>13600</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/grid/esb-example/tran...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB</category>
+ <name>transform_XML2XML_date_manipulation_client</name>
+
+ <shortDescription>JBoss ESB Smooks XML->XML date-manipulation Example - Client</shortDescription>
+ <description>This sample is to test the JBoss ESB XML->XML date-manipulation transformation.It requires the transform_XML2XML_date_manipulation project.</description>
+ <size>18600</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/grid/esb-example/tran...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB</category>
+ <name>transform_XML2XML_simple</name>
+ <shortDescription>JBoss ESB Smooks XML->XML Example</shortDescription>
+ <description>This is a very basic sample of how to manually define and apply a Message
+ Transformation within JBoss ESB. It applies a very simple XSLT to a
+ SampleOrder.xml message and prints the before and after XML to the console.</description>
+ <size>6700</size>
+
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/grid/esb-example/tran...
+ </url>
+ </project>
+
+ <project>
+ <category>ESB</category>
+ <name>transform_XML2XML_simple_client</name>
+ <shortDescription>JBoss ESB Smooks XML->XML Example - Client</shortDescription>
+
+ <description>This sample is to test the JBoss ESB XML->XML transformation.It requires the transform_XML2XML_simple project.</description>
+ <size>17800</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/grid/esb-example/tran...
+ </url>
+ </project>
+ <project>
+ <category>RichFaces</category>
+ <name>RichFaces 3.2.2.SP1 Demo Application for JBoss AS 4.2.X</name>
+ <included-projects>richfaces-demo</included-projects>
+ <shortDescription>RichFaces 3.2.2.SP1 Demo Application - WAR</shortDescription>
+ <description>This example contains RichFaces 3.2.2.SP1 Demo Application. It requires JBoss EAP 4.3 or JBoss AS 4.2.x.</description>
+ <size>10640749</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/dgolovin/examples/rf/...
+ </url>
+ <fixes>
+ <fix type="wtpruntime">
+ <property name="allowed-types">org.jboss.ide.eclipse.as.runtime.eap.43, org.jboss.ide.eclipse.as.runtime.42</property>
+ <property name="description">This project example requires the JBoss EAP 4.3 or JBoss AS 4.2.x</property>
+ </fix>
+ </fixes>
+ </project>
+
</projects>
Modified: workspace/examples/project-examples-jbds30.xml
===================================================================
--- workspace/examples/project-examples-jbds30.xml 2010-02-24 19:24:43 UTC (rev 20477)
+++ workspace/examples/project-examples-jbds30.xml 2010-02-24 19:25:12 UTC (rev 20478)
@@ -238,5 +238,135 @@
http://anonsvn.jboss.org/repos/jbosstools/workspace/Denny/esb-example-soa...
</url>
</project>
+
+ <project>
+ <category>Seam</category>
+ <name>booking22</name>
+ <included-projects>
+ booking22,booking22-ear,booking22-ejb,booking22-test
+ </included-projects>
+ <shortDescription>Seam 2.2 Booking Example - EAR (including a tutorial)</shortDescription>
+ <description>This example demonstrates the use of Seam in a Java EE 5 environment.
+Transaction and persistence context management is handled by the EJB container.
+This example has been tested on JBoss EAP 5.0.
+It includes the booking22, booking22-ear,booking22-test and booking22-ejb projects.
+</description>
+ <size>38203392</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/seam-examples/...
+ </url>
+ <welcome type="cheatsheets" url="/booking22/cheatsheets/booking.xml"/>
+ <fixes>
+ <fix type="wtpruntime">
+ <property name="allowed-types">org.jboss.ide.eclipse.as.runtime.eap.50</property>
+ <property name="eclipse-projects">booking22,booking22-ejb,booking22-ear</property>
+ <property name="description">This project example requires the JBoss EAP 5.0</property>
+ </fix>
+
+ <fix type="seam">
+ <property name="allowed-versions">2.2.0</property>
+ <property name="eclipse-projects">booking22</property>
+ <property name="description">This project example requires Seam version 2.2.0</property>
+ </fix>
+ <fix type="plugin">
+ <property name="id">org.testng.eclipse</property>
+ <property name="versions">5.8.0, 5.9.0</property>
+ <property name="description">The TestNG plugin is required if you want to run Seam tests. You can install it using the following update site: http://beust.com/eclipse</property>
+ </fix>
+ </fixes>
+ </project>
+
+ <project>
+ <category>Seam</category>
+ <name>photoalbum</name>
+ <included-projects>
+ photoalbum,photoalbum-ear,photoalbum-ejb
+ </included-projects>
+ <shortDescription>PhotoAlbum - EAR (RichFaces 3.3.1.GA, Seam 2.2.0.GA)</shortDescription>
+ <description>This example demonstrates the use of RichFaces components. It includes the photoalbum,photoalbum-ear and photoalbum-ejb projects.
+The example requires Seam 2.2 and JBoss EAP 4.3/JBoss EAP 5.0/JBoss AS 4.2.x/JBoss AS 5.x.
+ </description>
+ <size>25833472</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/seam-examples/...
+ </url>
+ <fixes>
+ <fix type="wtpruntime">
+ <property name="allowed-types">org.jboss.ide.eclipse.as.runtime.eap.50, org.jboss.ide.eclipse.as.runtime.eap.43, org.jboss.ide.eclipse.as.runtime.51, org.jboss.ide.eclipse.as.runtime.50, org.jboss.ide.eclipse.as.runtime.42</property>
+ <property name="eclipse-projects">photoalbum,photoalbum-ear,photoalbum-ejb</property>
+ <property name="description">This project example requires JBoss EAP 4.3/JBoss EAP 5.0/JBoss AS 4.2.x/JBoss AS 5.x</property>
+ </fix>
+
+ <fix type="seam">
+ <property name="allowed-versions">2.2.0</property>
+ <property name="eclipse-projects">photoalbum</property>
+ <property name="description">This project example requires Seam version 2.2.0</property>
+ </fix>
+ </fixes>
+ </project>
+
+ <project>
+ <category>Seam</category>
+
+ <name>dvdstore22</name>
+ <included-projects>
+ dvdstore22,dvdstore22-ear,dvdstore22-ejb,dvdstore22-test
+ </included-projects>
+ <shortDescription>Seam 2.2 DVD Store Example - EAR (including a test project)</shortDescription>
+ <description>This example demonstrates the use of Seam with jBPM pageflow and business process management. It includes the dvdstore22,dvdstore22-ear,dvdstore22-test and dvdstore22-ejb projects.
+ </description>
+ <size>35225600</size>
+
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/seam-examples/...
+ </url>
+ <fixes>
+ <fix type="wtpruntime">
+ <property name="allowed-types">org.jboss.ide.eclipse.as.runtime.eap.50</property>
+ <property name="eclipse-projects">dvdstore22,dvdstore22-ejb,dvdstore22-ear</property>
+ <property name="description">This project example requires the JBoss EAP 5.0</property>
+ </fix>
+
+ <fix type="seam">
+ <property name="allowed-versions">2.2.0</property>
+ <property name="eclipse-projects">dvdstore22</property>
+ <property name="description">This project example requires Seam version 2.2.0</property>
+ </fix>
+ <fix type="plugin">
+ <property name="id">org.testng.eclipse</property>
+ <property name="versions">5.8.0, 5.9.0</property>
+ <property name="description">The TestNG plugin is required if you want to run Seam tests. You can install it using the following update site: http://beust.com/eclipse</property>
+ </fix>
+ </fixes>
+ </project>
+
+ <project>
+ <category>RESTEasy</category>
+ <name>simple</name>
+ <included-projects>
+ simple
+ </included-projects>
+
+ <shortDescription>RESTEasy Simple Example</shortDescription>
+ <description>This project is a simple example showing usage of @Path, @GET, PUT, POST, and @PathParam. It uses pure streaming output and includes the 'simple' project.
+Requires m2eclipse and JBoss EAP 4.3/JBoss EAP 5.0/JBoss AS 4.2.x/JBoss AS 5.x.
+ </description>
+ <size>16939</size>
+ <url>
+ http://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/resteasy-examp...
+ </url>
+ <fixes>
+ <fix type="wtpruntime">
+ <property name="allowed-types">org.jboss.ide.eclipse.as.runtime.eap.50, org.jboss.ide.eclipse.as.runtime.eap.43, org.jboss.ide.eclipse.as.runtime.51, org.jboss.ide.eclipse.as.runtime.50, org.jboss.ide.eclipse.as.runtime.42</property>
+ <property name="eclipse-projects">photoalbum,photoalbum-ear,photoalbum-ejb</property>
+ <property name="description">This project example requires JBoss EAP 4.3/JBoss EAP 5.0/JBoss AS 4.2.x/JBoss AS 5.x</property>
+ </fix>
+ <fix type="plugin">
+ <property name="id">org.maven.ide.eclipse.wtp</property>
+ <property name="versions"> 0.10.0</property>
+ <property name="description">This project example requires m2eclipse. You can install it using the following update sites: http://m2eclipse.sonatype.org/sites/m2e and http://m2eclipse.sonatype.org/sites/m2e-extras</property>
+ </fix>
+ </fixes>
+ </project>
</projects>
14 years, 2 months
JBoss Tools SVN: r20477 - trunk/examples/plugins/org.jboss.tools.project.examples.
by jbosstools-commits@lists.jboss.org
Author: snjeza
Date: 2010-02-24 14:24:43 -0500 (Wed, 24 Feb 2010)
New Revision: 20477
Modified:
trunk/examples/plugins/org.jboss.tools.project.examples/plugin.properties
trunk/examples/plugins/org.jboss.tools.project.examples/plugin.xml
Log:
https://jira.jboss.org/jira/browse/JBIDE-5850 JBT Project Examples only includes SEAM & RESTEasy (& BPEL)
Modified: trunk/examples/plugins/org.jboss.tools.project.examples/plugin.properties
===================================================================
--- trunk/examples/plugins/org.jboss.tools.project.examples/plugin.properties 2010-02-24 17:22:24 UTC (rev 20476)
+++ trunk/examples/plugins/org.jboss.tools.project.examples/plugin.properties 2010-02-24 19:24:43 UTC (rev 20477)
@@ -5,6 +5,4 @@
Project_Examples_wizard = Project Examples
Project_Examples_command =Project Examples...
ProjectExamples=Project Examples file
-Project_Examples = Project Examples
-JBoss_Developer_Studio_Examples = JBoss Developer Studio Examples
-JBoss_Developer_Studio30_Examples = JBoss Developer Studio 3.0 Examples
\ No newline at end of file
+Project_Examples = Project Examples
\ No newline at end of file
Modified: trunk/examples/plugins/org.jboss.tools.project.examples/plugin.xml
===================================================================
--- trunk/examples/plugins/org.jboss.tools.project.examples/plugin.xml 2010-02-24 17:22:24 UTC (rev 20476)
+++ trunk/examples/plugins/org.jboss.tools.project.examples/plugin.xml 2010-02-24 19:24:43 UTC (rev 20477)
@@ -68,17 +68,4 @@
<initializer class="org.jboss.tools.project.examples.preferences.ProjectExamplesPreferencesInitializer"/>
</extension>
- <extension
- point="org.jboss.tools.project.examples.projectExamplesXml"
- name="%JBoss_Developer_Studio_Examples">
- <url>http://download.jboss.org/jbosstools/examples/project-examples-3.0.xml</url>
- <experimental>false</experimental>
- </extension>
-
- <extension
- point="org.jboss.tools.project.examples.projectExamplesXml"
- name="%JBoss_Developer_Studio30_Examples">
- <url>http://download.jboss.org/jbosstools/examples/project-examples-jbds30.xml</url>
- <experimental>false</experimental>
- </extension>
</plugin>
14 years, 2 months
JBoss Tools SVN: r20476 - trunk/as/docs/reference/en/modules.
by jbosstools-commits@lists.jboss.org
Author: ochikvina
Date: 2010-02-24 12:22:24 -0500 (Wed, 24 Feb 2010)
New Revision: 20476
Modified:
trunk/as/docs/reference/en/modules/perspective.xml
Log:
<html><head><meta name="qrichtext" content="1" /></head><body style="font-size:9pt;font-family:Sans Serif">
<p>https://jira.jboss.org/jira/browse/JBDS-925 - added info about cascade archive updates. </p>
</body></html>
Modified: trunk/as/docs/reference/en/modules/perspective.xml
===================================================================
--- trunk/as/docs/reference/en/modules/perspective.xml 2010-02-24 16:24:28 UTC (rev 20475)
+++ trunk/as/docs/reference/en/modules/perspective.xml 2010-02-24 17:22:24 UTC (rev 20476)
@@ -1192,6 +1192,11 @@
</tbody>
</tgroup>
</table>
+
+ <note>
+ <title>Note:</title>
+ <para>When editing an archive, it is also updated in all folders and other archives where it is nested.</para>
+ </note>
</section>
<section id="PublishToServer">
14 years, 2 months
JBoss Tools SVN: r20475 - in trunk/jsf/docs/userguide/en: modules and 1 other directory.
by jbosstools-commits@lists.jboss.org
Author: ochikvina
Date: 2010-02-24 11:24:28 -0500 (Wed, 24 Feb 2010)
New Revision: 20475
Added:
trunk/jsf/docs/userguide/en/images/visual_page/message.png
Modified:
trunk/jsf/docs/userguide/en/modules/editors.xml
Log:
<html><head><meta name="qrichtext" content="1" /></head><body style="font-size:9pt;font-family:Sans Serif">
<p>https://jira.jboss.org/jira/browse/JBDS-1012 - Added new info about changes in adding code assist to custom components to Doc - VisualWebTools. </p>
</body></html>
Added: trunk/jsf/docs/userguide/en/images/visual_page/message.png
===================================================================
(Binary files differ)
Property changes on: trunk/jsf/docs/userguide/en/images/visual_page/message.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Modified: trunk/jsf/docs/userguide/en/modules/editors.xml
===================================================================
--- trunk/jsf/docs/userguide/en/modules/editors.xml 2010-02-24 15:02:58 UTC (rev 20474)
+++ trunk/jsf/docs/userguide/en/modules/editors.xml 2010-02-24 16:24:28 UTC (rev 20475)
@@ -767,7 +767,7 @@
<title>Adding dynamic code assist to custom components that were added to JBoss
Tools Palette</title>
<para>Here is what you need to do to add project based code assist to a custom
- component added in <property>JBoss Developer Studio</property>:</para>
+ component added in <property>JBoss Developer Studio 2.X</property>:</para>
<orderedlist>
<listitem>
<para>Create a new xml file in <emphasis>
@@ -854,7 +854,24 @@
component.</para>
</listitem>
</orderedlist>
-
+ <para>From <emphasis>JBoss Developer Studio 3.0.0.M1</emphasis> you should not do any of the steps described
+ before,dynamic code assist to custom components is added automatically.</para>
+ <para>If you open projects that were created in older studio versions such message could appear:</para>
+ <figure>
+ <title>Missing Natures Message</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/visual_page/message.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>It shows that some features of content assist including this one probably will not work.
+ To fix this problem and turn off the message box execute the following steps:</para>
+ <itemizedlist>
+ <listitem><para>Right click the project in Package Explorer.</para></listitem>
+ <listitem><para>Select <property>Configure -> Add JSF Capabilities</property> from the context menu.</para></listitem>
+ <listitem><para>Configure your project using Add JSF Capabilities wizard and press <property>Finish</property></para></listitem>
+ </itemizedlist>
</section>
</section>
<section id="FullControlOverSourceFiles-SynchronizedSourcAndVisualEditing74">
14 years, 2 months