JBoss Tools SVN: r20824 - trunk/struts/docs/struts_tools_tutorial/en-US.
by jbosstools-commits＠lists.jboss.org
Author: abogachuk
Date: 2010-03-15 10:55:40 -0400 (Mon, 15 Mar 2010)
New Revision: 20824
Modified:
trunk/struts/docs/struts_tools_tutorial/en-US/relevant_resources.xml
Log:
https://jira.jboss.org/jira/browse/JBDS-1152 - Corrected the misspelled word.
Modified: trunk/struts/docs/struts_tools_tutorial/en-US/relevant_resources.xml
===================================================================
--- trunk/struts/docs/struts_tools_tutorial/en-US/relevant_resources.xml 2010-03-15 13:11:02 UTC (rev 20823)
+++ trunk/struts/docs/struts_tools_tutorial/en-US/relevant_resources.xml 2010-03-15 14:55:40 UTC (rev 20824)
@@ -22,7 +22,7 @@
<para>Download: <ulink url="http://struts.apache.org/download.cgi#struts206">Release of Apache
Struts</ulink></para>
- <para>Thus, this tutorial should help you to execute the hole development circle for building a
+ <para>Thus, this tutorial should help you to execute the whole development circle for building a
sample Struts-based Web application using <property>JBoss Tools</property> bundle of Eclipse
plugins starting from organizing a new Struts project and ending with the running and
deploying it onto the <property>JBoss Server</property>.</para>
14 years, 3 months
JBoss Tools SVN: r20823 - in trunk: jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/jsf2test/WebContent/pages/JBIDE/5985 and 4 other directories.
by jbosstools-commits＠lists.jboss.org
Author: mareshkau
Date: 2010-03-15 09:11:02 -0400 (Mon, 15 Mar 2010)
New Revision: 20823
Added:
trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/jsf2test/WebContent/pages/JBIDE/5985/
trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/jsf2test/WebContent/pages/JBIDE/5985/testFacesContextResolution.jsp
trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/jsf2test/WebContent/pages/JBIDE/5985/testFacesContextResolution.jsp.xml
trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/TestContextPathResolution.java
Modified:
trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java
trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/template/expression/VpeFunctionHref.java
trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/template/expression/VpeFunctionSrc.java
trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/util/ElService.java
trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/util/Jsf2ResourceUtil.java
Log:
https://jira.jboss.org/jira/browse/JBIDE-5985
Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/jsf2test/WebContent/pages/JBIDE/5985/testFacesContextResolution.jsp
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/jsf2test/WebContent/pages/JBIDE/5985/testFacesContextResolution.jsp (rev 0)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/jsf2test/WebContent/pages/JBIDE/5985/testFacesContextResolution.jsp 2010-03-15 13:11:02 UTC (rev 20823)
@@ -0,0 +1,16 @@
+<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
+<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
+
+<f:loadBundle var="Message" basename="demo.Messages"/>
+
+<html>
+ <head>
+ <title>Input User Name Page</title>
+ </head>
+ <body>
+ <f:view id="jbide-5985">
+ <h:graphicImage value="#{facesContext.externalContext.requestContextPath}/resources/img/img.gif"></h:graphicImage>
+ <img src="#{facesContext.externalContext.requestContextPath}/resources/img/img.gif"/>
+ </f:view>
+ </body>
+</html>
Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/jsf2test/WebContent/pages/JBIDE/5985/testFacesContextResolution.jsp.xml
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/jsf2test/WebContent/pages/JBIDE/5985/testFacesContextResolution.jsp.xml (rev 0)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/jsf2test/WebContent/pages/JBIDE/5985/testFacesContextResolution.jsp.xml 2010-03-15 13:11:02 UTC (rev 20823)
@@ -0,0 +1,14 @@
+<tests>
+<test id="jbide-5985">
+<TABLE STYLE="border: 1px dotted rgb(255, 102, 0); padding: 5px; width: 100%;">
+<TR>
+<TD>
+<DIV>
+<IMG SRC="/.*jsf2test/WebContent/resources/img/img.gif/" STYLE="-moz-user-modify: read-write;"/>
+<IMG SRC="/.*jsf2test/WebContent/resources/img/img.gif/"/>
+</DIV>
+</TD>
+</TR>
+</TABLE>
+</test>
+</tests>
Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java 2010-03-15 04:46:19 UTC (rev 20822)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java 2010-03-15 13:11:02 UTC (rev 20823)
@@ -91,6 +91,7 @@
import org.jboss.tools.jsf.vpe.jsf.test.jbide.SelectAllAndCut_JBIDE4853;
import org.jboss.tools.jsf.vpe.jsf.test.jbide.SelectWholeElement_JBIDE4713;
import org.jboss.tools.jsf.vpe.jsf.test.jbide.TaglibXMLUnformatedDTD_JBIDE5642;
+import org.jboss.tools.jsf.vpe.jsf.test.jbide.TestContextPathResolution;
import org.jboss.tools.jsf.vpe.jsf.test.jbide.TestFViewLocaleAttribute_JBIDE5218;
import org.jboss.tools.jsf.vpe.jsf.test.jbide.TestForUsingComponentsLibrariesWithDefaultNamespace;
import org.jboss.tools.jsf.vpe.jsf.test.jbide.TestOpenOnForXhtmlFiles_JBIDE5577;
@@ -121,6 +122,7 @@
TestSuite suite = new TestSuite("Tests for Vpe Jsf components"); //$NON-NLS-1$
// $JUnit-BEGIN$
+ suite.addTestSuite(TestContextPathResolution.class);
suite.addTestSuite(JBIDE5920Test.class);
suite.addTestSuite(RenderFacetAndInsertChildrenTest.class);
suite.addTestSuite(EditFontFamilyTest_JBIDE5872.class);
Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/TestContextPathResolution.java
===================================================================
--- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/TestContextPathResolution.java (rev 0)
+++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/TestContextPathResolution.java 2010-03-15 13:11:02 UTC (rev 20823)
@@ -0,0 +1,36 @@
+/*******************************************************************************
+ * Copyright (c) 2007-2010 Red Hat, Inc.
+ * Distributed under license by Red Hat, Inc. All rights reserved.
+ * This program is made available under the terms of the
+ * Eclipse Public License v1.0 which accompanies this distribution,
+ * and is available at http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributor:
+ * Red Hat, Inc. - initial API and implementation
+ ******************************************************************************/
+package org.jboss.tools.jsf.vpe.jsf.test.jbide;
+
+import org.jboss.tools.jsf.vpe.jsf.test.JsfAllTests;
+import org.jboss.tools.vpe.ui.test.ComponentContentTest;
+
+/**
+ * https://jira.jboss.org/jira/browse/JBIDE-5985
+ *
+ * @author mareshkau
+ *
+ */
+public class TestContextPathResolution extends ComponentContentTest{
+
+ public TestContextPathResolution(String name) {
+ super(name);
+ }
+
+ public void testContextPathResolution() throws Throwable{
+ performContentTest("JBIDE/5985/testFacesContextResolution.jsp"); //$NON-NLS-1$
+ }
+
+ @Override
+ protected String getTestProjectName() {
+ return JsfAllTests.IMPORT_JSF_20_PROJECT_NAME;
+ }
+}
Modified: trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/template/expression/VpeFunctionHref.java
===================================================================
--- trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/template/expression/VpeFunctionHref.java 2010-03-15 04:46:19 UTC (rev 20822)
+++ trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/template/expression/VpeFunctionHref.java 2010-03-15 13:11:02 UTC (rev 20823)
@@ -36,7 +36,7 @@
public VpeValue exec(VpePageContext pageContext, Node sourceNode) throws VpeExpressionException {
String tagValue = getParameter(0).exec(pageContext, sourceNode).stringValue();
- tagValue = resolveEL(pageContext,tagValue);
+ //tagValue = resolveEL(pageContext,tagValue);
IPath tagPath = new Path(tagValue);
if (tagPath.isEmpty()) {
Modified: trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/template/expression/VpeFunctionSrc.java
===================================================================
--- trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/template/expression/VpeFunctionSrc.java 2010-03-15 04:46:19 UTC (rev 20822)
+++ trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/template/expression/VpeFunctionSrc.java 2010-03-15 13:11:02 UTC (rev 20823)
@@ -52,7 +52,7 @@
public VpeValue exec(VpePageContext pageContext, Node sourceNode) throws VpeExpressionException {
String tagValue = getParameter(0).exec(pageContext, sourceNode)
.stringValue();
- tagValue = resolveEL(pageContext,tagValue);
+// tagValue = resolveEL(pageContext,tagValue);
IFile iFile = VpeCreatorUtil.getFile(tagValue, pageContext);
if (iFile != null) {
@@ -251,24 +251,24 @@
* temporary solution to solve #{facesContext.externalContext.requestContextPath}
* JBIDE-1410
*/
- protected String resolveEL(VpePageContext pageContext, String value) {
- String resolvedValue = value.replaceFirst("^\\s*(\\#|\\$)\\{facesContext.externalContext.requestContextPath\\}", ""); //$NON-NLS-1$ //$NON-NLS-2$
-
- //fix for JBIDE-2550, author Maksim Areshkau
- if(Jsf2ResourceUtil.isJSF2ResourceString(resolvedValue)){
- resolvedValue = Jsf2ResourceUtil.processCustomJSFAttributes(pageContext, resolvedValue);
- }
-
- //Fix for JBIDE-3030
- if(pageContext.getVisualBuilder().getCurrentIncludeInfo()==null
- || !(pageContext.getVisualBuilder().getCurrentIncludeInfo() instanceof IFile)){
- return resolvedValue;
- }
- final IFile file = (IFile) pageContext.getVisualBuilder().getCurrentIncludeInfo().getStorage();
-
- resolvedValue = ElService.getInstance().replaceEl(file, resolvedValue);
- return resolvedValue;
- }
+// protected String resolveEL(VpePageContext pageContext, String value) {
+// String resolvedValue = value.replaceFirst("^\\s*(\\#|\\$)\\{facesContext.externalContext.requestContextPath\\}", ""); //$NON-NLS-1$ //$NON-NLS-2$
+//
+// //fix for JBIDE-2550, author Maksim Areshkau
+// if(Jsf2ResourceUtil.isJSF2ResourceString(resolvedValue)){
+// resolvedValue = Jsf2ResourceUtil.processCustomJSFAttributes(pageContext, resolvedValue);
+// }
+//
+// //Fix for JBIDE-3030
+// if(pageContext.getVisualBuilder().getCurrentIncludeInfo()==null
+// || !(pageContext.getVisualBuilder().getCurrentIncludeInfo() instanceof IFile)){
+// return resolvedValue;
+// }
+// final IFile file = (IFile) pageContext.getVisualBuilder().getCurrentIncludeInfo().getStorage();
+//
+// resolvedValue = ElService.getInstance().replaceEl(file, resolvedValue);
+// return resolvedValue;
+// }
public static String getAbsoluteResourcePath(String resourcePathInPlugin) {
String pluginPath = VpePlugin.getPluginResourcePath();
Modified: trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/util/ElService.java
===================================================================
--- trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/util/ElService.java 2010-03-15 04:46:19 UTC (rev 20822)
+++ trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/util/ElService.java 2010-03-15 13:11:02 UTC (rev 20823)
@@ -186,7 +186,9 @@
if (((this.isAvailable(file) && this.isAvailableForNode(sourceNode, file)))
|| isInResourcesBundle(pageContext, sourceNode)){
rst = true;
- }else if(Jsf2ResourceUtil.isContainJSF2ResourceAttributes(sourceNode)) {
+ }else if(Jsf2ResourceUtil.isContainJSFExternalContextPath(sourceNode)){
+ rst = true;
+ }if(Jsf2ResourceUtil.isContainJSF2ResourceAttributes(sourceNode)) {
//added by Maksim Areshkau, see JBIDE-4812
rst = true;
}
@@ -386,6 +388,10 @@
//replace custom attributes
rst = replaceCustomAttributes(pageContext,rst);
+ if(Jsf2ResourceUtil.isExternalContextPathString(value)){
+ rst = Jsf2ResourceUtil.processExternalContextPath(value);
+ }
+
if(Jsf2ResourceUtil.isJSF2ResourceString(rst)){
rst = Jsf2ResourceUtil.processCustomJSFAttributes(pageContext, rst);
}
Modified: trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/util/Jsf2ResourceUtil.java
===================================================================
--- trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/util/Jsf2ResourceUtil.java 2010-03-15 04:46:19 UTC (rev 20822)
+++ trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/util/Jsf2ResourceUtil.java 2010-03-15 13:11:02 UTC (rev 20823)
@@ -29,12 +29,60 @@
.compile("[#\\$]\\{\\s*resource\\s*\\[\\s*'(.*)'\\s*\\]\\s*\\}"); //$NON-NLS-1$
private static final Pattern resourcePatternWithDoableCoat = Pattern
.compile("[#\\$]\\{\\s*resource\\s*\\[\\s*\"(.*)\"\\s*\\]\\s*\\}"); //$NON-NLS-1$
+ private static final Pattern jsfExternalContextPath = Pattern
+ .compile("^\\s*(\\#|\\$)\\{facesContext.externalContext.requestContextPath\\}"); //$NON-NLS-1$
+ /**
+ * Check if node contains attributes like this src="#{facesContext.externalContext.requestContextPath}/images/sample.gif"
+ * @param sourceNode
+ * @return true if node contains #{facesContext.externalContext.requestContextPath}/images/sample.gif
+ * @author mareshkau, fix for https://jira.jboss.org/jira/browse/JBIDE-5985
+ */
+ public static boolean isContainJSFExternalContextPath(Node sourceNode) {
+ boolean result = false;
+ if (sourceNode.getNodeType() == Node.TEXT_NODE) {
+ String textValue = sourceNode.getNodeValue();
+ if (textValue != null) {
+ if (Jsf2ResourceUtil.isExternalContextPathString(textValue)) {
+ result = true;
+ }
+ }
+ } else {
+ final NamedNodeMap nodeMap = sourceNode.getAttributes();
+ if ((nodeMap != null) && (nodeMap.getLength() > 0)) {
+ for (int i = 0; i < nodeMap.getLength(); i++) {
+ if (Jsf2ResourceUtil
+ .isExternalContextPathString(((Attr) nodeMap
+ .item(i)).getValue())) {
+ result = true;
+ }
+ }
+ }
+ }
+ return result;
+ }
/**
+ * Checks string for jsf declaration
+ * @param attributeValue
+ * @return true is string contains #{facesContext.externalContext.requestContextPath}
+ * @author mareshkau, fix for https://jira.jboss.org/jira/browse/JBIDE-5985
+ */
+ public static boolean isExternalContextPathString(String attributeValue) {
+ Matcher externalContextPathMatcher = jsfExternalContextPath
+ .matcher(attributeValue);
+ boolean result = false;
+ if (externalContextPathMatcher.find()) {
+ result = true;
+ }
+ return result;
+ }
+
+ /**
* Checks is node contained jsf attributes declaration
+ *
* @param sourceNode
- * @return true if node has #{resource[...]} declarations
- * false otherwise
+ * @return true if node has #{resource[...]} declarations false otherwise
+ * @author mareshkau
*/
public static boolean isContainJSF2ResourceAttributes(Node sourceNode) {
boolean result = false;
@@ -59,25 +107,31 @@
}
return result;
}
+
/**
* Replaces custom jsf attribute with attribute from VPE
+ *
* @param pageContext
* @param value
* @return
*/
- public static final String processCustomJSFAttributes(VpePageContext pageContext, String value){
- String result =null;
- //fix for JBIDE-2550, author Maksim Areshkau
- Matcher singleCoatMatcher = resourcePatternWithSinglCoat.matcher(value);
- Matcher doubleCoatMatcher = resourcePatternWithDoableCoat.matcher(value);
- if(doubleCoatMatcher.find()) {
- result = FileUtil.getJSF2ResourcePath(pageContext, doubleCoatMatcher.group(1));
- }else if(singleCoatMatcher.find()){
- result = FileUtil.getJSF2ResourcePath(pageContext, singleCoatMatcher.group(1));
- }
+ public static final String processCustomJSFAttributes(
+ VpePageContext pageContext, String value) {
+ String result = null;
+ // fix for JBIDE-2550, author Maksim Areshkau
+ Matcher singleCoatMatcher = resourcePatternWithSinglCoat.matcher(value);
+ Matcher doubleCoatMatcher = resourcePatternWithDoableCoat
+ .matcher(value);
+ if (doubleCoatMatcher.find()) {
+ result = FileUtil.getJSF2ResourcePath(pageContext,
+ doubleCoatMatcher.group(1));
+ } else if (singleCoatMatcher.find()) {
+ result = FileUtil.getJSF2ResourcePath(pageContext,
+ singleCoatMatcher.group(1));
+ }
- return result;
- }
+ return result;
+ }
/**
* Checks if string is jsf 2 resource
@@ -96,4 +150,12 @@
}
return result;
}
+ /**
+ * Replaced "^\\s*(\\#|\\$)\\{facesContext.externalContext.requestContextPath\\}" with ""
+ * @param value
+ * @return replaced "^\\s*(\\#|\\$)\\{facesContext.externalContext.requestContextPath\\}" with ""
+ */
+ public static String processExternalContextPath(String value) {
+ return value.replaceFirst("^\\s*(\\#|\\$)\\{facesContext.externalContext.requestContextPath\\}", ""); //$NON-NLS-1$ //$NON-NLS-2$
+ }
}
14 years, 3 months
JBoss Tools SVN: r20822 - branches/jbosstools-3.1.x/documentation/guides/Beginners_Guide/en-US.
by jbosstools-commits＠lists.jboss.org
Author: irooskov(a)redhat.com
Date: 2010-03-15 00:46:19 -0400 (Mon, 15 Mar 2010)
New Revision: 20822
Modified:
branches/jbosstools-3.1.x/documentation/guides/Beginners_Guide/en-US/Service-Oriented_Architecture_Development.xml
Log:
updated ESB section with link
Modified: branches/jbosstools-3.1.x/documentation/guides/Beginners_Guide/en-US/Service-Oriented_Architecture_Development.xml
===================================================================
--- branches/jbosstools-3.1.x/documentation/guides/Beginners_Guide/en-US/Service-Oriented_Architecture_Development.xml 2010-03-15 04:45:54 UTC (rev 20821)
+++ branches/jbosstools-3.1.x/documentation/guides/Beginners_Guide/en-US/Service-Oriented_Architecture_Development.xml 2010-03-15 04:46:19 UTC (rev 20822)
@@ -13,9 +13,9 @@
<para>
jBPM supports the jBPM Process Definition Language (jPDL) and includes a perspective for easy creation and manipulation using the jPDL. Through this view you can add states, transitions and other processes and waypoints in order to create your own business workflow. Refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/jBPM_Tools_Re...">A Minimal Process Definition</ulink> section of the <citetitle pubwork="chapter">Creating an Empty Process Definition</citetitle> chapter within the <citetitle pubwork="book">jBPM Tools Reference Guide</citetitle> for more details.
</para>
- <para>
+ <!-- <para>
Refer to the <citetitle pubwork="book">jBPM Tools Reference Guide</citetitle> for further details.
- </para>
+ </para> -->
</section>
<section id="sect-Beginners_Guide-Service_Oriented_Architecture_Development-ESB_Editor">
@@ -59,7 +59,7 @@
</para>
</formalpara>
<para>
- Refer to the <citetitle pubwork="chapter">ESB Editor</citetitle> chapter of the <citetitle pubwork="book">ESB Tools Reference Guide</citetitle> for further information.
+ Refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/ESB_Tools_Ref...">ESB Editor</citetitle> chapter of the <citetitle pubwork="book">ESB Tools Reference Guide</citetitle> for further information.
</para>
<para>
JBoss ESB intergrates component messaging into the JBoss Service-Oriented Architecture, serving as an integral part of JBoss middleware suite. For information on how to use and configure JBoss ESB with the JBoss Service-Oriented Architecture refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/ESB_Tools_Ref...">Using and Configuring SOA Platform</ulink> chapter of the <citetitle pubwork="book">ESB Tools Reference Guide</citetitle>.
14 years, 3 months
JBoss Tools SVN: r20821 - trunk/documentation/guides/Beginners_Guide/en-US.
by jbosstools-commits＠lists.jboss.org
Author: irooskov(a)redhat.com
Date: 2010-03-15 00:45:54 -0400 (Mon, 15 Mar 2010)
New Revision: 20821
Modified:
trunk/documentation/guides/Beginners_Guide/en-US/Service-Oriented_Architecture_Development.xml
Log:
updated ESB section with link
Modified: trunk/documentation/guides/Beginners_Guide/en-US/Service-Oriented_Architecture_Development.xml
===================================================================
--- trunk/documentation/guides/Beginners_Guide/en-US/Service-Oriented_Architecture_Development.xml 2010-03-15 04:19:36 UTC (rev 20820)
+++ trunk/documentation/guides/Beginners_Guide/en-US/Service-Oriented_Architecture_Development.xml 2010-03-15 04:45:54 UTC (rev 20821)
@@ -13,9 +13,9 @@
<para>
jBPM supports the jBPM Process Definition Language (jPDL) and includes a perspective for easy creation and manipulation using the jPDL. Through this view you can add states, transitions and other processes and waypoints in order to create your own business workflow. Refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/jBPM_Tools_Re...">A Minimal Process Definition</ulink> section of the <citetitle pubwork="chapter">Creating an Empty Process Definition</citetitle> chapter within the <citetitle pubwork="book">jBPM Tools Reference Guide</citetitle> for more details.
</para>
- <para>
+ <!-- <para>
Refer to the <citetitle pubwork="book">jBPM Tools Reference Guide</citetitle> for further details.
- </para>
+ </para> -->
</section>
<section id="sect-Beginners_Guide-Service_Oriented_Architecture_Development-ESB_Editor">
@@ -59,7 +59,7 @@
</para>
</formalpara>
<para>
- Refer to the <citetitle pubwork="chapter">ESB Editor</citetitle> chapter of the <citetitle pubwork="book">ESB Tools Reference Guide</citetitle> for further information.
+ Refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/ESB_Tools_Ref...">ESB Editor</citetitle> chapter of the <citetitle pubwork="book">ESB Tools Reference Guide</citetitle> for further information.
</para>
<para>
JBoss ESB intergrates component messaging into the JBoss Service-Oriented Architecture, serving as an integral part of JBoss middleware suite. For information on how to use and configure JBoss ESB with the JBoss Service-Oriented Architecture refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/ESB_Tools_Ref...">Using and Configuring SOA Platform</ulink> chapter of the <citetitle pubwork="book">ESB Tools Reference Guide</citetitle>.
14 years, 3 months
JBoss Tools SVN: r20820 - branches/jbosstools-3.1.x/documentation/guides/Beginners_Guide/en-US.
by jbosstools-commits＠lists.jboss.org
Author: irooskov(a)redhat.com
Date: 2010-03-15 00:19:36 -0400 (Mon, 15 Mar 2010)
New Revision: 20820
Modified:
branches/jbosstools-3.1.x/documentation/guides/Beginners_Guide/en-US/Java_Web_(EE)_and_Standard_Edition_(SE).xml
branches/jbosstools-3.1.x/documentation/guides/Beginners_Guide/en-US/Service-Oriented_Architecture_Development.xml
branches/jbosstools-3.1.x/documentation/guides/Beginners_Guide/en-US/Workshops.xml
Log:
updated to incorporate QE feedback
Modified: branches/jbosstools-3.1.x/documentation/guides/Beginners_Guide/en-US/Java_Web_(EE)_and_Standard_Edition_(SE).xml
===================================================================
--- branches/jbosstools-3.1.x/documentation/guides/Beginners_Guide/en-US/Java_Web_(EE)_and_Standard_Edition_(SE).xml 2010-03-15 04:19:28 UTC (rev 20819)
+++ branches/jbosstools-3.1.x/documentation/guides/Beginners_Guide/en-US/Java_Web_(EE)_and_Standard_Edition_(SE).xml 2010-03-15 04:19:36 UTC (rev 20820)
@@ -31,7 +31,7 @@
</mediaobject>
</figure>
<para>
- Refer to the <citetitle pubwork="chapter">Editors</citetitle> chapter of <citetitle pubwork="book">Visual Web Tools Reference Guide</citetitle> for full details.
+ Refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/Visual_Web_To...">Editors</ulink> chapter of <citetitle pubwork="book">Visual Web Tools Reference Guide</citetitle> for full details.
</para>
</listitem>
</varlistentry>
Modified: branches/jbosstools-3.1.x/documentation/guides/Beginners_Guide/en-US/Service-Oriented_Architecture_Development.xml
===================================================================
--- branches/jbosstools-3.1.x/documentation/guides/Beginners_Guide/en-US/Service-Oriented_Architecture_Development.xml 2010-03-15 04:19:28 UTC (rev 20819)
+++ branches/jbosstools-3.1.x/documentation/guides/Beginners_Guide/en-US/Service-Oriented_Architecture_Development.xml 2010-03-15 04:19:36 UTC (rev 20820)
@@ -11,7 +11,7 @@
jBPM is a workflow tool for framework control over business processes and languages.
</para>
<para>
- jBPM supports the jBPM Process Definition Language (jPDL) and includes a perspective for easy creation and manipulation using the jPDL. Through this view you can add states, transitions and other processes and waypoints in order to create your own business workflow. Refer to the <citetitle pubwork="section">A Minimal Process Definition</citetitle> section of the <citetitle pubwork="chapter">Creating an Empty Process Definition</citetitle> chapter within the <citetitle pubwork="book">jBPM Tools Reference Guide</citetitle> for more details.
+ jBPM supports the jBPM Process Definition Language (jPDL) and includes a perspective for easy creation and manipulation using the jPDL. Through this view you can add states, transitions and other processes and waypoints in order to create your own business workflow. Refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/jBPM_Tools_Re...">A Minimal Process Definition</ulink> section of the <citetitle pubwork="chapter">Creating an Empty Process Definition</citetitle> chapter within the <citetitle pubwork="book">jBPM Tools Reference Guide</citetitle> for more details.
</para>
<para>
Refer to the <citetitle pubwork="book">jBPM Tools Reference Guide</citetitle> for further details.
@@ -62,7 +62,7 @@
Refer to the <citetitle pubwork="chapter">ESB Editor</citetitle> chapter of the <citetitle pubwork="book">ESB Tools Reference Guide</citetitle> for further information.
</para>
<para>
- Allowing for the value of messaging between middleware components to be used and intergrated into the JBoss Service-Oriented Architecture, the JBoss ESB is an integral part of JBoss middleware integration. For information on how to use and configure JBoss ESB with the JBoss Service-Oriented Architecture refer to the <citetitle pubwork="chapter">Using and Configuring SOA Platform</citetitle> chapter of the <citetitle pubwork="book">ESB Tools Reference Guide</citetitle>.
+ JBoss ESB intergrates component messaging into the JBoss Service-Oriented Architecture, serving as an integral part of JBoss middleware suite. For information on how to use and configure JBoss ESB with the JBoss Service-Oriented Architecture refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/ESB_Tools_Ref...">Using and Configuring SOA Platform</ulink> chapter of the <citetitle pubwork="book">ESB Tools Reference Guide</citetitle>.
</para>
</section>
@@ -72,7 +72,7 @@
JBoss Web Services is an integral part of the JBoss Application Server and JBoss Enterprise Application Platform, providing a standard means of working reliably between different software applications.
</para>
<para>
- A Web Service defines a collection of technologies that provide protocols and standards for the exchange of data between applications. You can create a Web Service for your application server through the use of wizards in the <application>JBoss Developer Studio</application>. For further details refer to the <citetitle pubwork="chapter">Creating a Web Service using JBossWS runtime</citetitle> chapter of the <citetitle pubwork="book">JBoss WS User Guide</citetitle>
+ A Web Service defines a collection of technologies that provide protocols and standards for the exchange of data between applications. You can create a Web Service for your application server through the use of wizards in the <application>JBoss Developer Studio</application>. For further details refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/JBoss_Web_Ser...">Creating a Web Service using JBossWS runtime</ulink> chapter of the <citetitle pubwork="book">JBoss WS User Guide</citetitle>
</para>
<figure id="figu-Beginners_Guide-Web_Services_Tools-Example_of_a_Web_Services_wizard">
<title>Example of a Web Services wizard</title>
@@ -101,7 +101,7 @@
Drools is a Business Rule Management System (BRMS) that uses an enhanced implementation of the Rete algorithm to become a forward chaining inference based rules engine (production rule system). Refer to the <citetitle pubwork="chapter">The Rule Engine</citetitle> chapter of the JBoss Enterprise SOA <citetitle pubwork="book">JBoss Rules Reference Guide</citetitle> for more details.
</para>
<para>
- Drools Tools includes wizards for creating new Drools projects and resources. The resources that can be created include a new rule, domain specific language, decision table and business rule. After these have been created there are numerous editors included to assist you with the rest of the development. Included editors are The Rule editor, The Domain Specific Language editor, The Rule Flow graphical editor and The Guided editor that provides a Graphical User Interface (GUI). Refer to the <citetitle pubwork="book">Drools Tools Reference Guide</citetitle> for more details.
+ Drools Tools includes wizards for creating new Drools projects and resources. The resources that can be created include a new rule, domain specific language, decision table and business rule. After these have been created there are numerous editors included to assist you with the rest of the development. Included editors are The Rule editor, The Domain Specific Language editor, The Rule Flow graphical editor and The Guided editor that provides a Graphical User Interface (GUI). Refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/Drools_Tools_...">Drools Tools Reference Guide</ulink> for more details.
</para>
<figure id="figu-Beginners_Guide-Drools_Tools-Rule_text_editor">
<title>Rule text editor</title>
Modified: branches/jbosstools-3.1.x/documentation/guides/Beginners_Guide/en-US/Workshops.xml
===================================================================
--- branches/jbosstools-3.1.x/documentation/guides/Beginners_Guide/en-US/Workshops.xml 2010-03-15 04:19:28 UTC (rev 20819)
+++ branches/jbosstools-3.1.x/documentation/guides/Beginners_Guide/en-US/Workshops.xml 2010-03-15 04:19:36 UTC (rev 20820)
@@ -74,7 +74,7 @@
</mediaobject>
</figure>
<para>
- There will be two issues to fix before you can continue.
+ There may be two issues to fix before you can continue. The description for each of these will be <guilabel>Target runtime JBoss 4.2.2 Runtime is not defined</guilabel> and <guilabel>Java compiler level does not match the version of the installed Java project facet</guilabel>. If they do not appear skip to <xref linkend="figu-Beginners_Guide-Workshops-Completed_fixing_the_issues"/>. If they do appear, the following steps will resolve these issues.
</para>
<figure id="figu-Beginners_Guide-Workshops-Quick_Fixes">
<title>Quick Fixes</title>
@@ -90,7 +90,7 @@
</mediaobject>
</figure>
<para>
- To fix the first issue with the description <guilabel>Target runtime JBoss 4.2.2 Runtime is not defined.</guilabel> click on this description and then click the <guibutton>Quick Fix</guibutton> button.
+ To fix the first issue with the description <guilabel>Target runtime JBoss 4.2.2 Runtime is not defined</guilabel> click on this description and then click the <guibutton>Quick Fix</guibutton> button.
</para>
<figure id="figu-Beginners_Guide-Workshops-Fixing_the_first_issue">
<title>Fixing the first issue</title>
@@ -149,7 +149,7 @@
</mediaobject>
</figure>
<para>
- To fix the second issue with the description <guilabel>Java compiler level does not match the version of the installed Java project facet.</guilabel> click on this description and then click the <guibutton>Quick Fix</guibutton> button.
+ To fix the second issue with the description <guilabel>Java compiler level does not match the version of the installed Java project facet</guilabel> click on this description and then click the <guibutton>Quick Fix</guibutton> button.
</para>
<para>
After clicking the <guibutton>Quick Fix</guibutton> button the Java compiler issue should disappear because the <application>JBoss Developer Studio</application> has made the necessary changes in the background to fix it.
14 years, 3 months
JBoss Tools SVN: r20819 - trunk/documentation/guides/Beginners_Guide/en-US.
by jbosstools-commits＠lists.jboss.org
Author: irooskov(a)redhat.com
Date: 2010-03-15 00:19:28 -0400 (Mon, 15 Mar 2010)
New Revision: 20819
Modified:
trunk/documentation/guides/Beginners_Guide/en-US/Java_Web_(EE)_and_Standard_Edition_(SE).xml
trunk/documentation/guides/Beginners_Guide/en-US/Service-Oriented_Architecture_Development.xml
trunk/documentation/guides/Beginners_Guide/en-US/Workshops.xml
Log:
updated to incorporate QE feedback
Modified: trunk/documentation/guides/Beginners_Guide/en-US/Java_Web_(EE)_and_Standard_Edition_(SE).xml
===================================================================
--- trunk/documentation/guides/Beginners_Guide/en-US/Java_Web_(EE)_and_Standard_Edition_(SE).xml 2010-03-15 02:20:56 UTC (rev 20818)
+++ trunk/documentation/guides/Beginners_Guide/en-US/Java_Web_(EE)_and_Standard_Edition_(SE).xml 2010-03-15 04:19:28 UTC (rev 20819)
@@ -31,7 +31,7 @@
</mediaobject>
</figure>
<para>
- Refer to the <citetitle pubwork="chapter">Editors</citetitle> chapter of <citetitle pubwork="book">Visual Web Tools Reference Guide</citetitle> for full details.
+ Refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/Visual_Web_To...">Editors</ulink> chapter of <citetitle pubwork="book">Visual Web Tools Reference Guide</citetitle> for full details.
</para>
</listitem>
</varlistentry>
Modified: trunk/documentation/guides/Beginners_Guide/en-US/Service-Oriented_Architecture_Development.xml
===================================================================
--- trunk/documentation/guides/Beginners_Guide/en-US/Service-Oriented_Architecture_Development.xml 2010-03-15 02:20:56 UTC (rev 20818)
+++ trunk/documentation/guides/Beginners_Guide/en-US/Service-Oriented_Architecture_Development.xml 2010-03-15 04:19:28 UTC (rev 20819)
@@ -11,7 +11,7 @@
jBPM is a workflow tool for framework control over business processes and languages.
</para>
<para>
- jBPM supports the jBPM Process Definition Language (jPDL) and includes a perspective for easy creation and manipulation using the jPDL. Through this view you can add states, transitions and other processes and waypoints in order to create your own business workflow. Refer to the <citetitle pubwork="section">A Minimal Process Definition</citetitle> section of the <citetitle pubwork="chapter">Creating an Empty Process Definition</citetitle> chapter within the <citetitle pubwork="book">jBPM Tools Reference Guide</citetitle> for more details.
+ jBPM supports the jBPM Process Definition Language (jPDL) and includes a perspective for easy creation and manipulation using the jPDL. Through this view you can add states, transitions and other processes and waypoints in order to create your own business workflow. Refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/jBPM_Tools_Re...">A Minimal Process Definition</ulink> section of the <citetitle pubwork="chapter">Creating an Empty Process Definition</citetitle> chapter within the <citetitle pubwork="book">jBPM Tools Reference Guide</citetitle> for more details.
</para>
<para>
Refer to the <citetitle pubwork="book">jBPM Tools Reference Guide</citetitle> for further details.
@@ -62,7 +62,7 @@
Refer to the <citetitle pubwork="chapter">ESB Editor</citetitle> chapter of the <citetitle pubwork="book">ESB Tools Reference Guide</citetitle> for further information.
</para>
<para>
- Allowing for the value of messaging between middleware components to be used and intergrated into the JBoss Service-Oriented Architecture, the JBoss ESB is an integral part of JBoss middleware integration. For information on how to use and configure JBoss ESB with the JBoss Service-Oriented Architecture refer to the <citetitle pubwork="chapter">Using and Configuring SOA Platform</citetitle> chapter of the <citetitle pubwork="book">ESB Tools Reference Guide</citetitle>.
+ JBoss ESB intergrates component messaging into the JBoss Service-Oriented Architecture, serving as an integral part of JBoss middleware suite. For information on how to use and configure JBoss ESB with the JBoss Service-Oriented Architecture refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/ESB_Tools_Ref...">Using and Configuring SOA Platform</ulink> chapter of the <citetitle pubwork="book">ESB Tools Reference Guide</citetitle>.
</para>
</section>
@@ -72,7 +72,7 @@
JBoss Web Services is an integral part of the JBoss Application Server and JBoss Enterprise Application Platform, providing a standard means of working reliably between different software applications.
</para>
<para>
- A Web Service defines a collection of technologies that provide protocols and standards for the exchange of data between applications. You can create a Web Service for your application server through the use of wizards in the <application>JBoss Developer Studio</application>. For further details refer to the <citetitle pubwork="chapter">Creating a Web Service using JBossWS runtime</citetitle> chapter of the <citetitle pubwork="book">JBoss WS User Guide</citetitle>
+ A Web Service defines a collection of technologies that provide protocols and standards for the exchange of data between applications. You can create a Web Service for your application server through the use of wizards in the <application>JBoss Developer Studio</application>. For further details refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/JBoss_Web_Ser...">Creating a Web Service using JBossWS runtime</ulink> chapter of the <citetitle pubwork="book">JBoss WS User Guide</citetitle>
</para>
<figure id="figu-Beginners_Guide-Web_Services_Tools-Example_of_a_Web_Services_wizard">
<title>Example of a Web Services wizard</title>
@@ -101,7 +101,7 @@
Drools is a Business Rule Management System (BRMS) that uses an enhanced implementation of the Rete algorithm to become a forward chaining inference based rules engine (production rule system). Refer to the <citetitle pubwork="chapter">The Rule Engine</citetitle> chapter of the JBoss Enterprise SOA <citetitle pubwork="book">JBoss Rules Reference Guide</citetitle> for more details.
</para>
<para>
- Drools Tools includes wizards for creating new Drools projects and resources. The resources that can be created include a new rule, domain specific language, decision table and business rule. After these have been created there are numerous editors included to assist you with the rest of the development. Included editors are The Rule editor, The Domain Specific Language editor, The Rule Flow graphical editor and The Guided editor that provides a Graphical User Interface (GUI). Refer to the <citetitle pubwork="book">Drools Tools Reference Guide</citetitle> for more details.
+ Drools Tools includes wizards for creating new Drools projects and resources. The resources that can be created include a new rule, domain specific language, decision table and business rule. After these have been created there are numerous editors included to assist you with the rest of the development. Included editors are The Rule editor, The Domain Specific Language editor, The Rule Flow graphical editor and The Guided editor that provides a Graphical User Interface (GUI). Refer to the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/Drools_Tools_...">Drools Tools Reference Guide</ulink> for more details.
</para>
<figure id="figu-Beginners_Guide-Drools_Tools-Rule_text_editor">
<title>Rule text editor</title>
Modified: trunk/documentation/guides/Beginners_Guide/en-US/Workshops.xml
===================================================================
--- trunk/documentation/guides/Beginners_Guide/en-US/Workshops.xml 2010-03-15 02:20:56 UTC (rev 20818)
+++ trunk/documentation/guides/Beginners_Guide/en-US/Workshops.xml 2010-03-15 04:19:28 UTC (rev 20819)
@@ -74,7 +74,7 @@
</mediaobject>
</figure>
<para>
- There will be two issues to fix before you can continue.
+ There may be two issues to fix before you can continue. The description for each of these will be <guilabel>Target runtime JBoss 4.2.2 Runtime is not defined</guilabel> and <guilabel>Java compiler level does not match the version of the installed Java project facet</guilabel>. If they do not appear skip to <xref linkend="figu-Beginners_Guide-Workshops-Completed_fixing_the_issues"/>. If they do appear, the following steps will resolve these issues.
</para>
<figure id="figu-Beginners_Guide-Workshops-Quick_Fixes">
<title>Quick Fixes</title>
@@ -90,7 +90,7 @@
</mediaobject>
</figure>
<para>
- To fix the first issue with the description <guilabel>Target runtime JBoss 4.2.2 Runtime is not defined.</guilabel> click on this description and then click the <guibutton>Quick Fix</guibutton> button.
+ To fix the first issue with the description <guilabel>Target runtime JBoss 4.2.2 Runtime is not defined</guilabel> click on this description and then click the <guibutton>Quick Fix</guibutton> button.
</para>
<figure id="figu-Beginners_Guide-Workshops-Fixing_the_first_issue">
<title>Fixing the first issue</title>
@@ -149,7 +149,7 @@
</mediaobject>
</figure>
<para>
- To fix the second issue with the description <guilabel>Java compiler level does not match the version of the installed Java project facet.</guilabel> click on this description and then click the <guibutton>Quick Fix</guibutton> button.
+ To fix the second issue with the description <guilabel>Java compiler level does not match the version of the installed Java project facet</guilabel> click on this description and then click the <guibutton>Quick Fix</guibutton> button.
</para>
<para>
After clicking the <guibutton>Quick Fix</guibutton> button the Java compiler issue should disappear because the <application>JBoss Developer Studio</application> has made the necessary changes in the background to fix it.
14 years, 3 months
JBoss Tools SVN: r20818 - branches/jbosstools-3.1.x/documentation/guides/MigrationGuide/en-US.
by jbosstools-commits＠lists.jboss.org
Author: irooskov(a)redhat.com
Date: 2010-03-14 22:20:56 -0400 (Sun, 14 Mar 2010)
New Revision: 20818
Modified:
branches/jbosstools-3.1.x/documentation/guides/MigrationGuide/en-US/migration.xml
Log:
updated to remove update steps that no longer work...and were marked as such but still included...confusing our readers
Modified: branches/jbosstools-3.1.x/documentation/guides/MigrationGuide/en-US/migration.xml
===================================================================
--- branches/jbosstools-3.1.x/documentation/guides/MigrationGuide/en-US/migration.xml 2010-03-15 02:19:37 UTC (rev 20817)
+++ branches/jbosstools-3.1.x/documentation/guides/MigrationGuide/en-US/migration.xml 2010-03-15 02:20:56 UTC (rev 20818)
@@ -11,16 +11,16 @@
</chapterinfo>
<title>Migration Process</title>
- <para>In this chapter you can find concise description of JBoss Developer Studio migration from
- 2.1.0 to 3.0.0 version.</para>
+ <para>This chapter describes the JBoss Developer Studio migration from version
+ 2.1 to 3.0.</para>
<section id="migration">
- <title>How to migrate from 2.1 to 3.0.0 JBoss Developer Studio</title>
+ <title>How to migrate the JBoss Developer Studio from 2.1 to 3.0</title>
<para></para>
- <para>To migrate from 2.1 to 3.0.0 you have to install a fresh JBDS 3.0.0 and go through all the steps of
+ <para>To migrate from 2.1 to 3.0 you have to perform a new install of the JBoss Developer Studio 3.0 and undertake all the steps of the
installation process that is fully described in
- <ulink url="gsglink">Getting Started with JBoss Developer Studio</ulink> guide.</para>
+ <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/Getting_Start...">Getting Started with JBoss Developer Studio</ulink> guide.</para>
<figure>
- <title>Process of JBDS 3.0.0 installation </title>
+ <title>Process of JBDS 3.0 installation </title>
<mediaobject>
<imageobject>
@@ -28,26 +28,13 @@
</imageobject>
</mediaobject>
</figure>
- <para>Now you can not update your JBDS 2.X to 3.0.0 using update site (https://devstudio.jboss.com/updates/3.0/ ), as it was available in previous versions:</para>
- <figure>
- <title>Installation from the update site</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/migration-guide-step-1.png" />
- </imageobject>
- </mediaobject>
- </figure>
- <para>The reason is that JBDS 3.0 uses Eclipse 3.5, whereas JBDS 2.x uses Eclipse 3.4.
- Because of this platform change, a full installation is required to migrate. </para>
- <para>When the installation process is complete you can point your JBDS 3.0.0 at your old workspace directory and continue working with your projects created using previous
- JBDS/Tools versions, or create a new one and import old projects into the new workspace.
+ <para>Since JBoss Developer Studio 3.0 uses a new version of Eclipse, an update from within Eclipse cannot be performed as it was when upgrading from JBoss Developer Studio 2.0 to 2.1.</para>
+ <para>When the installation process is complete you can point to your old workspace directory and continue working with your projects created using previous JBoss Developer Studio versions, or create a new one and import old projects into the new workspace.
</para>
<note>
<title>Note:</title>
- <para>In JBDS 3.0.0 Linux users no longer need to install the library libstdc+.so.5 on their mashines.
- Now this library is not required and can be removed from the system.
+ <para>In JBDS 3.0, Linux users no longer need to install the library <filename>libstdc+.so.5</filename>. This library is no longer required and can be removed from the system.
</para>
</note>
</section>
14 years, 3 months
JBoss Tools SVN: r20817 - trunk/documentation/guides/MigrationGuide/en-US.
by jbosstools-commits＠lists.jboss.org
Author: irooskov(a)redhat.com
Date: 2010-03-14 22:19:37 -0400 (Sun, 14 Mar 2010)
New Revision: 20817
Modified:
trunk/documentation/guides/MigrationGuide/en-US/migration.xml
Log:
updated to remove steps that no longer work....and were stated as such :S
Modified: trunk/documentation/guides/MigrationGuide/en-US/migration.xml
===================================================================
--- trunk/documentation/guides/MigrationGuide/en-US/migration.xml 2010-03-15 00:33:32 UTC (rev 20816)
+++ trunk/documentation/guides/MigrationGuide/en-US/migration.xml 2010-03-15 02:19:37 UTC (rev 20817)
@@ -11,16 +11,16 @@
</chapterinfo>
<title>Migration Process</title>
- <para>In this chapter you can find concise description of JBoss Developer Studio migration from
- 2.1.0 to 3.0.0 version.</para>
+ <para>This chapter describes the JBoss Developer Studio migration from version
+ 2.1 to 3.0.</para>
<section id="migration">
- <title>How to migrate from 2.1 to 3.0.0 JBoss Developer Studio</title>
+ <title>How to migrate the JBoss Developer Studio from 2.1 to 3.0</title>
<para></para>
- <para>To migrate from 2.1 to 3.0.0 you have to install a fresh JBDS 3.0.0 and go through all the steps of
+ <para>To migrate from 2.1 to 3.0 you have to perform a new install of the JBoss Developer Studio 3.0 and undertake all the steps of the
installation process that is fully described in
- <ulink url="gsglink">Getting Started with JBoss Developer Studio</ulink> guide.</para>
+ <ulink url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/3.0/Getting_Start...">Getting Started with JBoss Developer Studio</ulink> guide.</para>
<figure>
- <title>Process of JBDS 3.0.0 installation </title>
+ <title>Process of JBDS 3.0 installation </title>
<mediaobject>
<imageobject>
@@ -28,26 +28,13 @@
</imageobject>
</mediaobject>
</figure>
- <para>Now you can not update your JBDS 2.X to 3.0.0 using update site (https://devstudio.jboss.com/updates/3.0/ ), as it was available in previous versions:</para>
- <figure>
- <title>Installation from the update site</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/migration-guide-step-1.png" />
- </imageobject>
- </mediaobject>
- </figure>
- <para>The reason is that JBDS 3.0 uses Eclipse 3.5, whereas JBDS 2.x uses Eclipse 3.4.
- Because of this platform change, a full installation is required to migrate. </para>
- <para>When the installation process is complete you can point your JBDS 3.0.0 at your old workspace directory and continue working with your projects created using previous
- JBDS/Tools versions, or create a new one and import old projects into the new workspace.
+ <para>Since JBoss Developer Studio 3.0 uses a new version of Eclipse, an update from within Eclipse cannot be performed as it was when upgrading from JBoss Developer Studio 2.0 to 2.1.</para>
+ <para>When the installation process is complete you can point to your old workspace directory and continue working with your projects created using previous JBoss Developer Studio versions, or create a new one and import old projects into the new workspace.
</para>
<note>
<title>Note:</title>
- <para>In JBDS 3.0.0 Linux users no longer need to install the library libstdc+.so.5 on their mashines.
- Now this library is not required and can be removed from the system.
+ <para>In JBDS 3.0, Linux users no longer need to install the library <filename>libstdc+.so.5</filename>. This library is no longer required and can be removed from the system.
</para>
</note>
</section>
14 years, 3 months
JBoss Tools SVN: r20816 - in trunk: common/plugins/org.jboss.tools.common/src/org/jboss/tools/common and 1 other directories.
by jbosstools-commits＠lists.jboss.org
Author: akazakov
Date: 2010-03-14 20:33:32 -0400 (Sun, 14 Mar 2010)
New Revision: 20816
Modified:
trunk/cdi/plugins/org.jboss.tools.cdi.core/src/org/jboss/tools/cdi/core/CDIUtil.java
trunk/common/plugins/org.jboss.tools.common/src/org/jboss/tools/common/EclipseUtil.java
trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/preferences/SeamSettingsPreferencePage.java
Log:
https://jira.jboss.org/jira/browse/JBIDE-5902
Modified: trunk/cdi/plugins/org.jboss.tools.cdi.core/src/org/jboss/tools/cdi/core/CDIUtil.java
===================================================================
--- trunk/cdi/plugins/org.jboss.tools.cdi.core/src/org/jboss/tools/cdi/core/CDIUtil.java 2010-03-13 07:10:33 UTC (rev 20815)
+++ trunk/cdi/plugins/org.jboss.tools.cdi.core/src/org/jboss/tools/cdi/core/CDIUtil.java 2010-03-15 00:33:32 UTC (rev 20816)
@@ -20,6 +20,7 @@
import org.eclipse.jdt.core.IField;
import org.eclipse.jdt.core.IJavaElement;
import org.eclipse.jdt.core.IMethod;
+import org.eclipse.wst.validation.internal.plugin.ValidationPlugin;
import org.jboss.tools.common.EclipseUtil;
import org.jboss.tools.common.model.util.EclipseResourceUtil;
import org.jboss.tools.jst.web.kb.IKbProject;
@@ -28,6 +29,7 @@
* @author Alexey Kazakov
*/
public class CDIUtil {
+
/**
* Adds CDI and KB builders to the project.
*
@@ -40,6 +42,7 @@
EclipseResourceUtil.addNatureToProject(project,
IKbProject.NATURE_ID);
}
+ EclipseResourceUtil.addBuilderToProject(project, ValidationPlugin.VALIDATION_BUILDER_ID);
} catch (CoreException e) {
CDICorePlugin.getDefault().logError(e);
}
Modified: trunk/common/plugins/org.jboss.tools.common/src/org/jboss/tools/common/EclipseUtil.java
===================================================================
--- trunk/common/plugins/org.jboss.tools.common/src/org/jboss/tools/common/EclipseUtil.java 2010-03-13 07:10:33 UTC (rev 20815)
+++ trunk/common/plugins/org.jboss.tools.common/src/org/jboss/tools/common/EclipseUtil.java 2010-03-15 00:33:32 UTC (rev 20816)
@@ -13,6 +13,7 @@
import java.util.ArrayList;
import java.util.List;
+import org.eclipse.core.resources.ICommand;
import org.eclipse.core.resources.IFile;
import org.eclipse.core.resources.IProject;
import org.eclipse.core.resources.IProjectDescription;
@@ -108,6 +109,23 @@
proj.setDescription(description, null);
}
+ public static void addBuilderToProject(IProject project, String builderId) throws CoreException {
+ IProjectDescription desc = project.getDescription();
+ ICommand[] existing = desc.getBuildSpec();
+ for (ICommand command : existing) {
+ if(builderId.equals(command.getBuilderName())) {
+ return;
+ }
+ }
+ ICommand[] cmds = new ICommand[existing.length + 1];
+ ICommand newcmd = project.getDescription().newCommand();
+ newcmd.setBuilderName(builderId);
+ cmds[0] = newcmd;
+ System.arraycopy(existing, 0, cmds, 1, existing.length );
+ desc.setBuildSpec(cmds);
+ project.setDescription(desc, null);
+ }
+
public static void removeNatureFromProject(IProject project, String natureId) throws CoreException {
IProject proj = project.getProject();
IProjectDescription description = proj.getDescription();
Modified: trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/preferences/SeamSettingsPreferencePage.java
===================================================================
--- trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/preferences/SeamSettingsPreferencePage.java 2010-03-13 07:10:33 UTC (rev 20815)
+++ trunk/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/preferences/SeamSettingsPreferencePage.java 2010-03-15 00:33:32 UTC (rev 20816)
@@ -53,6 +53,7 @@
import org.eclipse.wst.common.project.facet.core.IProjectFacet;
import org.eclipse.wst.common.project.facet.core.IProjectFacetVersion;
import org.eclipse.wst.common.project.facet.core.ProjectFacetsManager;
+import org.eclipse.wst.validation.internal.plugin.ValidationPlugin;
import org.jboss.tools.common.model.util.EclipseResourceUtil;
import org.jboss.tools.common.ui.IValidator;
import org.jboss.tools.common.ui.preferences.SettingsPage;
@@ -965,6 +966,7 @@
if(!project.hasNature(IKbProject.NATURE_ID)) {
EclipseResourceUtil.addNatureToProject(project, IKbProject.NATURE_ID);
}
+ EclipseResourceUtil.addBuilderToProject(project, ValidationPlugin.VALIDATION_BUILDER_ID);
} catch (CoreException e) {
SeamGuiPlugin.getPluginLog().logError(e);
}
14 years, 3 months
JBoss Tools SVN: r20815 - in trunk: jsf/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/el/refactoring and 3 other directories.
by jbosstools-commits＠lists.jboss.org
Author: akazakov
Date: 2010-03-13 02:10:33 -0500 (Sat, 13 Mar 2010)
New Revision: 20815
Modified:
trunk/common/plugins/org.jboss.tools.common.el.core/src/org/jboss/tools/common/el/core/ca/AbstractELCompletionEngine.java
trunk/jsf/plugins/org.jboss.tools.jsf.text.ext/src/org/jboss/tools/jsf/text/ext/hyperlink/ExpressionHyperlink.java
trunk/jsf/plugins/org.jboss.tools.jsf.text.ext/src/org/jboss/tools/jsf/text/ext/hyperlink/JSPExprHyperlinkPartitioner.java
trunk/jsf/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/el/refactoring/RefactorSearcher.java
trunk/jsf/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/web/validation/ELValidator.java
trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/refactoring/SeamRefactorSearcher.java
Log:
https://jira.jboss.org/jira/browse/JBIDE-6054
Modified: trunk/common/plugins/org.jboss.tools.common.el.core/src/org/jboss/tools/common/el/core/ca/AbstractELCompletionEngine.java
===================================================================
--- trunk/common/plugins/org.jboss.tools.common.el.core/src/org/jboss/tools/common/el/core/ca/AbstractELCompletionEngine.java 2010-03-12 18:48:47 UTC (rev 20814)
+++ trunk/common/plugins/org.jboss.tools.common.el.core/src/org/jboss/tools/common/el/core/ca/AbstractELCompletionEngine.java 2010-03-13 07:10:33 UTC (rev 20815)
@@ -251,6 +251,9 @@
: operand;
ELResolutionImpl resolution = resolveELOperand(file, newOperand, returnEqualedVariablesOnly, prefixWasChanged);
+ if(resolution==null) {
+ return null;
+ }
if(prefixWasChanged) {
resolution.setSourceOperand(operand);
@@ -296,12 +299,18 @@
var.resolveValue("#{" + var.getElToken().getText() + suffix + "}"); //$NON-NLS-1$ //$NON-NLS-2$
ELResolutionImpl oldElResolution = resolveELOperand(file, operand, returnEqualedVariablesOnly, false);
- resolution.getProposals().addAll(oldElResolution.getProposals());
+ if(oldElResolution!=null) {
+ resolution.getProposals().addAll(oldElResolution.getProposals());
+ }
} else {
resolution = resolveELOperand(file, operand, returnEqualedVariablesOnly, false);
}
}
+ if(resolution==null) {
+ return null;
+ }
+
// JBIDE-512, JBIDE-2541 related changes ===>>>
if(!returnEqualedVariablesOnly && vars!=null) {
Modified: trunk/jsf/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/el/refactoring/RefactorSearcher.java
===================================================================
--- trunk/jsf/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/el/refactoring/RefactorSearcher.java 2010-03-12 18:48:47 UTC (rev 20814)
+++ trunk/jsf/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/el/refactoring/RefactorSearcher.java 2010-03-13 07:10:33 UTC (rev 20815)
@@ -414,11 +414,12 @@
context.setVars(vars);
ELResolution resolution = resolver.resolve(context, operand, offset);
-
- List<ELSegment> segments = resolution.findSegmentsByJavaElement(javaElement);
-
- for(ELSegment segment : segments){
- match(file, offset+segment.getSourceReference().getStartPosition(), segment.getSourceReference().getLength());
+ if(resolution!=null) {
+ List<ELSegment> segments = resolution.findSegmentsByJavaElement(javaElement);
+
+ for(ELSegment segment : segments){
+ match(file, offset+segment.getSourceReference().getStartPosition(), segment.getSourceReference().getLength());
+ }
}
}
}
Modified: trunk/jsf/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/web/validation/ELValidator.java
===================================================================
--- trunk/jsf/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/web/validation/ELValidator.java 2010-03-12 18:48:47 UTC (rev 20814)
+++ trunk/jsf/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/web/validation/ELValidator.java 2010-03-13 07:10:33 UTC (rev 20815)
@@ -307,6 +307,9 @@
for (int i = 0; i < resolvers.length; i++) {
ELResolution elResolution = resolvers[i].resolve(context, operandToken, documnetOffset);
+ if(elResolution==null) {
+ continue;
+ }
if(elResolution.isResolved()) {
resolution = elResolution;
break;
Modified: trunk/jsf/plugins/org.jboss.tools.jsf.text.ext/src/org/jboss/tools/jsf/text/ext/hyperlink/ExpressionHyperlink.java
===================================================================
--- trunk/jsf/plugins/org.jboss.tools.jsf.text.ext/src/org/jboss/tools/jsf/text/ext/hyperlink/ExpressionHyperlink.java 2010-03-12 18:48:47 UTC (rev 20814)
+++ trunk/jsf/plugins/org.jboss.tools.jsf.text.ext/src/org/jboss/tools/jsf/text/ext/hyperlink/ExpressionHyperlink.java 2010-03-13 07:10:33 UTC (rev 20815)
@@ -41,6 +41,9 @@
if(invocationExpression != null){
for(ELResolver resolver : context.getElResolvers()){
ELResolution resolution = resolver.resolve(context, invocationExpression, invocationExpression.getStartPosition());
+ if(resolution==null) {
+ return null;
+ }
ELSegment segment = resolution.findSegmentByOffset(offset-eStructure.reference.getStartPosition());
if(segment != null){
if(segment instanceof JavaMemberELSegment){
Modified: trunk/jsf/plugins/org.jboss.tools.jsf.text.ext/src/org/jboss/tools/jsf/text/ext/hyperlink/JSPExprHyperlinkPartitioner.java
===================================================================
--- trunk/jsf/plugins/org.jboss.tools.jsf.text.ext/src/org/jboss/tools/jsf/text/ext/hyperlink/JSPExprHyperlinkPartitioner.java 2010-03-12 18:48:47 UTC (rev 20814)
+++ trunk/jsf/plugins/org.jboss.tools.jsf.text.ext/src/org/jboss/tools/jsf/text/ext/hyperlink/JSPExprHyperlinkPartitioner.java 2010-03-13 07:10:33 UTC (rev 20815)
@@ -130,6 +130,9 @@
public boolean decide(ELContext context, ELExpression expression, ELInvocationExpression invocationExpression, int offset){
for(ELResolver resolver : context.getElResolvers()){
ELResolution resolution = resolver.resolve(context, invocationExpression, invocationExpression.getStartPosition());
+ if(resolution==null) {
+ return false;
+ }
ELSegment segment = resolution.findSegmentByOffset(offset);
if(segment != null){
if(segment instanceof JavaMemberELSegment){
Modified: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/refactoring/SeamRefactorSearcher.java
===================================================================
--- trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/refactoring/SeamRefactorSearcher.java 2010-03-12 18:48:47 UTC (rev 20814)
+++ trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/refactoring/SeamRefactorSearcher.java 2010-03-13 07:10:33 UTC (rev 20815)
@@ -139,11 +139,12 @@
context.setVars(vars);
ELResolution resolution = resolver.resolve(context, operand, offset);
-
- List<ELSegment> segments = resolution.findSegmentsByVariable(seamComponent);
-
- for(ELSegment segment : segments){
- match(file, offset+segment.getSourceReference().getStartPosition(), segment.getSourceReference().getLength());
+ if(resolution!=null) {
+ List<ELSegment> segments = resolution.findSegmentsByVariable(seamComponent);
+
+ for(ELSegment segment : segments){
+ match(file, offset+segment.getSourceReference().getStartPosition(), segment.getSourceReference().getLength());
+ }
}
}
}
14 years, 3 months