JBoss Tools SVN: r7613 - trunk/jsf/docs/jsf_tools_tutorial.
by jbosstools-commits＠lists.jboss.org
Author: newtonm
Date: 2008-04-18 09:29:04 -0400 (Fri, 18 Apr 2008)
New Revision: 7613
Modified:
trunk/jsf/docs/jsf_tools_tutorial/pom.xml
Log:
Renamed references to XSL files to match new layout and fixed dependencies.
Modified: trunk/jsf/docs/jsf_tools_tutorial/pom.xml
===================================================================
--- trunk/jsf/docs/jsf_tools_tutorial/pom.xml 2008-04-18 13:28:41 UTC (rev 7612)
+++ trunk/jsf/docs/jsf_tools_tutorial/pom.xml 2008-04-18 13:29:04 UTC (rev 7613)
@@ -10,14 +10,6 @@
<packaging>jdocbook</packaging>
<name>JSF_Tools_Tutorial</name>
-<dependencies>
- <dependency>
- <groupId>org.jboss</groupId>
- <artifactId>jbossorg-jdocbook-style</artifactId>
- <version>1.0.0</version>
- <type>jdocbook-style</type>
- </dependency>
-</dependencies>
<build>
<plugins>
<plugin>
@@ -29,12 +21,13 @@
<dependency>
<groupId>org.jboss</groupId>
<artifactId>jbossorg-docbook-xslt</artifactId>
- <version>1.0.0</version>
+ <version>1.1.0-SNAPSHOT</version>
</dependency>
<dependency>
- <groupId>org.richfaces.docs</groupId>
- <artifactId>highlight</artifactId>
- <version>3.1.4.GA</version>
+ <groupId>org.jboss</groupId>
+ <artifactId>jbossorg-jdocbook-style</artifactId>
+ <version>1.1.0-SNAPSHOT</version>
+ <type>jdocbook-style</type>
</dependency>
</dependencies>
<configuration>
@@ -52,22 +45,22 @@
<formats>
<format>
<formatName>pdf</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/pdf.xsl</stylesheetResource>
<finalName>${pom.name}.pdf</finalName>
</format>
<format>
<formatName>html</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-html.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/xhtml.xsl</stylesheetResource>
<finalName>index.html</finalName>
</format>
<format>
<formatName>html_single</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/nochunk-html.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/xhtml-single.xsl</stylesheetResource>
<finalName>index.html</finalName>
</format>
<format>
<formatName>eclipse</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-eclipse.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/eclipse.xsl</stylesheetResource>
<finalName>index.html</finalName>
</format>
</formats>
17 years, 8 months
- 1
- 0
JBoss Tools SVN: r7612 - trunk/jsf/docs/jsf_tools_ref_guide.
by jbosstools-commits＠lists.jboss.org
Author: newtonm
Date: 2008-04-18 09:28:41 -0400 (Fri, 18 Apr 2008)
New Revision: 7612
Modified:
trunk/jsf/docs/jsf_tools_ref_guide/pom.xml
Log:
Renamed references to XSL files to match new layout and fixed dependencies.
Modified: trunk/jsf/docs/jsf_tools_ref_guide/pom.xml
===================================================================
--- trunk/jsf/docs/jsf_tools_ref_guide/pom.xml 2008-04-18 13:28:09 UTC (rev 7611)
+++ trunk/jsf/docs/jsf_tools_ref_guide/pom.xml 2008-04-18 13:28:41 UTC (rev 7612)
@@ -10,14 +10,6 @@
<packaging>jdocbook</packaging>
<name>JSF_Tools_Reference_Guide</name>
-<dependencies>
- <dependency>
- <groupId>org.jboss</groupId>
- <artifactId>jbossorg-jdocbook-style</artifactId>
- <version>1.0.0</version>
- <type>jdocbook-style</type>
- </dependency>
-</dependencies>
<build>
<plugins>
<plugin>
@@ -29,12 +21,13 @@
<dependency>
<groupId>org.jboss</groupId>
<artifactId>jbossorg-docbook-xslt</artifactId>
- <version>1.0.0</version>
+ <version>1.1.0-SNAPSHOT</version>
</dependency>
<dependency>
- <groupId>org.richfaces.docs</groupId>
- <artifactId>highlight</artifactId>
- <version>3.1.4.GA</version>
+ <groupId>org.jboss</groupId>
+ <artifactId>jbossorg-jdocbook-style</artifactId>
+ <version>1.1.0-SNAPSHOT</version>
+ <type>jdocbook-style</type>
</dependency>
</dependencies>
<configuration>
@@ -52,22 +45,22 @@
<formats>
<format>
<formatName>pdf</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/pdf.xsl</stylesheetResource>
<finalName>${pom.name}.pdf</finalName>
</format>
<format>
<formatName>html</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-html.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/xhtml.xsl</stylesheetResource>
<finalName>index.html</finalName>
</format>
<format>
<formatName>html_single</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/nochunk-html.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/xhtml-single.xsl</stylesheetResource>
<finalName>index.html</finalName>
</format>
<format>
<formatName>eclipse</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-eclipse.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/eclipse.xsl</stylesheetResource>
<finalName>index.html</finalName>
</format>
</formats>
17 years, 8 months
- 1
- 0
JBoss Tools SVN: r7611 - trunk/seam/docs/reference.
by jbosstools-commits＠lists.jboss.org
Author: newtonm
Date: 2008-04-18 09:28:09 -0400 (Fri, 18 Apr 2008)
New Revision: 7611
Modified:
trunk/seam/docs/reference/pom.xml
Log:
Renamed references to XSL files to match new layout and fixed dependencies.
Modified: trunk/seam/docs/reference/pom.xml
===================================================================
--- trunk/seam/docs/reference/pom.xml 2008-04-18 13:27:40 UTC (rev 7610)
+++ trunk/seam/docs/reference/pom.xml 2008-04-18 13:28:09 UTC (rev 7611)
@@ -10,14 +10,6 @@
<packaging>jdocbook</packaging>
<name>Seam_Reference_Guide</name>
-<dependencies>
- <dependency>
- <groupId>org.jboss</groupId>
- <artifactId>jbossorg-jdocbook-style</artifactId>
- <version>1.1.0-SNAPSHOT</version>
- <type>jdocbook-style</type>
- </dependency>
-</dependencies>
<build>
<plugins>
<plugin>
@@ -32,9 +24,10 @@
<version>1.1.0-SNAPSHOT</version>
</dependency>
<dependency>
- <groupId>org.richfaces.docs</groupId>
- <artifactId>highlight</artifactId>
- <version>3.1.4.GA</version>
+ <groupId>org.jboss</groupId>
+ <artifactId>jbossorg-jdocbook-style</artifactId>
+ <version>1.1.0-SNAPSHOT</version>
+ <type>jdocbook-style</type>
</dependency>
</dependencies>
<configuration>
@@ -52,22 +45,22 @@
<formats>
<format>
<formatName>pdf</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/pdf.xsl</stylesheetResource>
<finalName>${pom.name}.pdf</finalName>
</format>
<format>
<formatName>html</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-html.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/xhtml.xsl</stylesheetResource>
<finalName>index.html</finalName>
</format>
<format>
<formatName>html_single</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/nochunk-html.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/xhtml-single.xsl</stylesheetResource>
<finalName>index.html</finalName>
</format>
<format>
<formatName>eclipse</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-eclipse.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/eclipse.xsl</stylesheetResource>
<finalName>index.html</finalName>
</format>
</formats>
17 years, 8 months
- 1
- 0
JBoss Tools SVN: r7610 - trunk/jbpm/docs/reference.
by jbosstools-commits＠lists.jboss.org
Author: newtonm
Date: 2008-04-18 09:27:40 -0400 (Fri, 18 Apr 2008)
New Revision: 7610
Modified:
trunk/jbpm/docs/reference/pom.xml
Log:
Renamed references to XSL files to match new layout and fixed dependencies.
Modified: trunk/jbpm/docs/reference/pom.xml
===================================================================
--- trunk/jbpm/docs/reference/pom.xml 2008-04-18 13:26:50 UTC (rev 7609)
+++ trunk/jbpm/docs/reference/pom.xml 2008-04-18 13:27:40 UTC (rev 7610)
@@ -10,14 +10,6 @@
<packaging>jdocbook</packaging>
<name>JBPM_Reference_Guide</name>
-<dependencies>
- <dependency>
- <groupId>org.jboss</groupId>
- <artifactId>jbossorg-jdocbook-style</artifactId>
- <version>1.1.0-SNAPSHOT</version>
- <type>jdocbook-style</type>
- </dependency>
-</dependencies>
<build>
<plugins>
<plugin>
@@ -32,9 +24,10 @@
<version>1.1.0-SNAPSHOT</version>
</dependency>
<dependency>
- <groupId>org.richfaces.docs</groupId>
- <artifactId>highlight</artifactId>
- <version>3.1.4.GA</version>
+ <groupId>org.jboss</groupId>
+ <artifactId>jbossorg-jdocbook-style</artifactId>
+ <version>1.1.0-SNAPSHOT</version>
+ <type>jdocbook-style</type>
</dependency>
</dependencies>
<configuration>
@@ -52,22 +45,22 @@
<formats>
<format>
<formatName>pdf</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/pdf.xsl</stylesheetResource>
<finalName>${pom.name}.pdf</finalName>
</format>
<format>
<formatName>html</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-html.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/xhtml.xsl</stylesheetResource>
<finalName>index.html</finalName>
</format>
<format>
<formatName>html_single</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/nochunk-html.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/xhtml-single.xsl</stylesheetResource>
<finalName>index.html</finalName>
</format>
<format>
<formatName>eclipse</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-eclipse.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/eclipse.xsl</stylesheetResource>
<finalName>index.html</finalName>
</format>
</formats>
17 years, 8 months
- 1
- 0
JBoss Tools SVN: r7609 - trunk/as/docs/reference.
by jbosstools-commits＠lists.jboss.org
Author: newtonm
Date: 2008-04-18 09:26:50 -0400 (Fri, 18 Apr 2008)
New Revision: 7609
Modified:
trunk/as/docs/reference/pom.xml
Log:
Renamed references to XSL files to match new layout.
Modified: trunk/as/docs/reference/pom.xml
===================================================================
--- trunk/as/docs/reference/pom.xml 2008-04-18 12:50:29 UTC (rev 7608)
+++ trunk/as/docs/reference/pom.xml 2008-04-18 13:26:50 UTC (rev 7609)
@@ -9,14 +9,7 @@
<version>1.0-SNAPSHOT</version>
<packaging>jdocbook</packaging>
<name>AS_Reference_Guide</name>
- <dependencies>
- <dependency>
- <groupId>org.jboss</groupId>
- <artifactId>jbossorg-jdocbook-style</artifactId>
- <version>1.1.0-SNAPSHOT</version>
- <type>jdocbook-style</type>
- </dependency>
- </dependencies>
+
<build>
<plugins>
<plugin>
@@ -30,11 +23,11 @@
<artifactId>jbossorg-docbook-xslt</artifactId>
<version>1.1.0-SNAPSHOT</version>
</dependency>
-
<dependency>
- <groupId>org.richfaces.docs</groupId>
- <artifactId>highlight</artifactId>
- <version>3.1.4.GA</version>
+ <groupId>org.jboss</groupId>
+ <artifactId>jbossorg-jdocbook-style</artifactId>
+ <version>1.1.0-SNAPSHOT</version>
+ <type>jdocbook-style</type>
</dependency>
</dependencies>
<configuration>
@@ -52,22 +45,22 @@
<formats>
<format>
<formatName>pdf</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/pdf.xsl</stylesheetResource>
<finalName>${pom.name}.pdf</finalName>
</format>
<format>
<formatName>html</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-html.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/xhtml.xsl</stylesheetResource>
<finalName>index.html</finalName>
</format>
<format>
<formatName>html_single</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/nochunk-html.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/xhtml-single.xsl</stylesheetResource>
<finalName>index.html</finalName>
</format>
<format>
<formatName>eclipse</formatName>
- <stylesheetResource>classpath:/xslt/org/jboss/main-eclipse.xsl</stylesheetResource>
+ <stylesheetResource>classpath:/xslt/org/jboss/eclipse.xsl</stylesheetResource>
<finalName>index.html</finalName>
</format>
</formats>
17 years, 8 months
- 1
- 0
JBoss Tools SVN: r7608 - trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/util.
by jbosstools-commits＠lists.jboss.org
Author: sdzmitrovich
Date: 2008-04-18 08:50:29 -0400 (Fri, 18 Apr 2008)
New Revision: 7608
Modified:
trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/util/TemplateManagingUtil.java
Log:
code adjustment
Modified: trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/util/TemplateManagingUtil.java
===================================================================
--- trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/util/TemplateManagingUtil.java 2008-04-18 11:07:31 UTC (rev 7607)
+++ trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/util/TemplateManagingUtil.java 2008-04-18 12:50:29 UTC (rev 7608)
@@ -84,7 +84,7 @@
* you will must review next code
*/
VpeNodeMapping nodeMapping = pageContext.getDomMapping()
- .getNearNodeMapping(getLastSelectedVisualNode(pageContext));
+ .getNearNodeMapping(getSelectedNode(getCurrentSelection(pageContext)));
if (nodeMapping != null) {
@@ -271,7 +271,7 @@
* @return
*/
public static nsIDOMNode getSelectedNode(nsISelection selection) {
-
+
if (selection.getIsCollapsed()) {
if (selection.getFocusNode() != null) {
if ((selection.getFocusNode().getNodeType() != nsIDOMNode.TEXT_NODE)
17 years, 8 months
- 1
- 0
JBoss Tools SVN: r7607 - trunk/jsf/plugins/org.jboss.tools.jsf.vpe.jsf/src/org/jboss/tools/jsf/vpe/jsf/template.
by jbosstools-commits＠lists.jboss.org
Author: sdzmitrovich
Date: 2008-04-18 07:07:31 -0400 (Fri, 18 Apr 2008)
New Revision: 7607
Modified:
trunk/jsf/plugins/org.jboss.tools.jsf.vpe.jsf/src/org/jboss/tools/jsf/vpe/jsf/template/AbstractOutputJsfTemplate.java
trunk/jsf/plugins/org.jboss.tools.jsf.vpe.jsf/src/org/jboss/tools/jsf/vpe/jsf/template/JsfOutputTextTemplate.java
Log:
http://jira.jboss.com/jira/browse/JBIDE-1835
Modified: trunk/jsf/plugins/org.jboss.tools.jsf.vpe.jsf/src/org/jboss/tools/jsf/vpe/jsf/template/AbstractOutputJsfTemplate.java
===================================================================
--- trunk/jsf/plugins/org.jboss.tools.jsf.vpe.jsf/src/org/jboss/tools/jsf/vpe/jsf/template/AbstractOutputJsfTemplate.java 2008-04-18 10:29:41 UTC (rev 7606)
+++ trunk/jsf/plugins/org.jboss.tools.jsf.vpe.jsf/src/org/jboss/tools/jsf/vpe/jsf/template/AbstractOutputJsfTemplate.java 2008-04-18 11:07:31 UTC (rev 7607)
@@ -236,4 +236,18 @@
return elementMapping;
}
+
+ /*
+ * (non-Javadoc)
+ *
+ * @see org.jboss.tools.vpe.editor.template.VpeAbstractTemplate#setPseudoContent(org.jboss.tools.vpe.editor.context.VpePageContext,
+ * org.w3c.dom.Node, org.mozilla.interfaces.nsIDOMNode,
+ * org.mozilla.interfaces.nsIDOMDocument)
+ */
+ @Override
+ public void setPseudoContent(VpePageContext pageContext,
+ Node sourceContainer, nsIDOMNode visualContainer,
+ nsIDOMDocument visualDocument) {
+ // Empty
+ }
}
Modified: trunk/jsf/plugins/org.jboss.tools.jsf.vpe.jsf/src/org/jboss/tools/jsf/vpe/jsf/template/JsfOutputTextTemplate.java
===================================================================
--- trunk/jsf/plugins/org.jboss.tools.jsf.vpe.jsf/src/org/jboss/tools/jsf/vpe/jsf/template/JsfOutputTextTemplate.java 2008-04-18 10:29:41 UTC (rev 7606)
+++ trunk/jsf/plugins/org.jboss.tools.jsf.vpe.jsf/src/org/jboss/tools/jsf/vpe/jsf/template/JsfOutputTextTemplate.java 2008-04-18 11:07:31 UTC (rev 7607)
@@ -62,18 +62,4 @@
return true;
}
- /*
- * (non-Javadoc)
- *
- * @see org.jboss.tools.vpe.editor.template.VpeAbstractTemplate#setPseudoContent(org.jboss.tools.vpe.editor.context.VpePageContext,
- * org.w3c.dom.Node, org.mozilla.interfaces.nsIDOMNode,
- * org.mozilla.interfaces.nsIDOMDocument)
- */
- @Override
- public void setPseudoContent(VpePageContext pageContext,
- Node sourceContainer, nsIDOMNode visualContainer,
- nsIDOMDocument visualDocument) {
- // Empty
- }
-
}
17 years, 8 months
- 1
- 0
JBoss Tools SVN: r7606 - in trunk/ws/plugins/org.jboss.tools.ws.core: META-INF and 4 other directories.
by jbosstools-commits＠lists.jboss.org
Author: Grid.Qian
Date: 2008-04-18 06:29:41 -0400 (Fri, 18 Apr 2008)
New Revision: 7606
Added:
trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/JbossWSCore
trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/JbossWSCoreMessage.java
trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/command/
trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/command/JbossWSRuntimeCommand.java
trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/facet/
trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/facet/delegate/
trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/facet/delegate/JbossWSInstallRuntimeDelegate.java
Modified:
trunk/ws/plugins/org.jboss.tools.ws.core/META-INF/MANIFEST.MF
trunk/ws/plugins/org.jboss.tools.ws.core/plugin.xml
trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/Activator.java
Log:
Modified: trunk/ws/plugins/org.jboss.tools.ws.core/META-INF/MANIFEST.MF
===================================================================
--- trunk/ws/plugins/org.jboss.tools.ws.core/META-INF/MANIFEST.MF 2008-04-18 09:39:24 UTC (rev 7605)
+++ trunk/ws/plugins/org.jboss.tools.ws.core/META-INF/MANIFEST.MF 2008-04-18 10:29:41 UTC (rev 7606)
@@ -7,6 +7,8 @@
Bundle-Activator: org.jboss.tools.ws.core.Activator
Require-Bundle: org.eclipse.ui,
org.eclipse.core.runtime,
- org.eclipse.wst.common.project.facet.core
+ org.eclipse.wst.common.project.facet.core,
+ org.eclipse.wst.common.frameworks,
+ org.eclipse.core.resources
Eclipse-LazyStart: true
Bundle-Vendor: %PLUGIN_PROVIDER
Modified: trunk/ws/plugins/org.jboss.tools.ws.core/plugin.xml
===================================================================
--- trunk/ws/plugins/org.jboss.tools.ws.core/plugin.xml 2008-04-18 09:39:24 UTC (rev 7605)
+++ trunk/ws/plugins/org.jboss.tools.ws.core/plugin.xml 2008-04-18 10:29:41 UTC (rev 7606)
@@ -17,7 +17,7 @@
<requires facet="jst.web" version="2.2,2.3,2.4,2.5"/>
</constraint>
<action type="INSTALL">
- <delegate class=""/>
+ <delegate class="org.jboss.tools.ws.core.facet.delegate.JbossWSInstallRuntimeDelegate"/>
</action>
<!--
<action type="UNINSTALL">
Modified: trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/Activator.java
===================================================================
--- trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/Activator.java 2008-04-18 09:39:24 UTC (rev 7605)
+++ trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/Activator.java 2008-04-18 10:29:41 UTC (rev 7606)
@@ -1,3 +1,15 @@
+/*******************************************************************************
+ * Copyright (c) 2008 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
+ *
+ * Contributors:
+ * Red Hat, Inc. - initial API and implementation
+ ******************************************************************************/
+
+
package org.jboss.tools.ws.core;
import org.eclipse.ui.plugin.AbstractUIPlugin;
Added: trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/JbossWSCore
===================================================================
--- trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/JbossWSCore (rev 0)
+++ trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/JbossWSCore 2008-04-18 10:29:41 UTC (rev 7606)
@@ -0,0 +1 @@
+PROGRESS_INSTALL_JBOSSWS_RUNTIME=JBoss Web Service Runtime
\ No newline at end of file
Added: trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/JbossWSCoreMessage.java
===================================================================
--- trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/JbossWSCoreMessage.java (rev 0)
+++ trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/JbossWSCoreMessage.java 2008-04-18 10:29:41 UTC (rev 7606)
@@ -0,0 +1,19 @@
+package org.jboss.tools.ws.core;
+
+import org.eclipse.osgi.util.NLS;
+
+public class JbossWSCoreMessage {
+
+ private static final String BUNDLE_NAME = "org.jboss.tools.ws.ui.JbossWSCore"; //$NON-NLS-1$
+
+ private JbossWSCoreMessage() {
+ // Do not instantiate
+ }
+
+ public static String PROGRESS_INSTALL_JBOSSWS_RUNTIME;
+
+
+ static {
+ NLS.initializeMessages(BUNDLE_NAME, JbossWSCoreMessage.class);
+ }
+}
\ No newline at end of file
Added: trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/command/JbossWSRuntimeCommand.java
===================================================================
--- trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/command/JbossWSRuntimeCommand.java (rev 0)
+++ trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/command/JbossWSRuntimeCommand.java 2008-04-18 10:29:41 UTC (rev 7606)
@@ -0,0 +1,166 @@
+/*******************************************************************************
+ * Copyright (c) 2008 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
+ *
+ * Contributors:
+ * Red Hat, Inc. - initial API and implementation
+ ******************************************************************************/
+
+package org.jboss.tools.ws.core.command;
+
+import java.io.File;
+import java.io.FileNotFoundException;
+import java.io.IOException;
+import java.util.ArrayList;
+import java.util.List;
+
+import org.eclipse.core.commands.ExecutionException;
+import org.eclipse.core.resources.IProject;
+import org.eclipse.core.runtime.IAdaptable;
+import org.eclipse.core.runtime.IPath;
+import org.eclipse.core.runtime.IProgressMonitor;
+import org.eclipse.core.runtime.IStatus;
+import org.eclipse.core.runtime.Path;
+import org.eclipse.core.runtime.Status;
+import org.eclipse.jface.preference.PreferenceStore;
+import org.eclipse.wst.common.frameworks.datamodel.AbstractDataModelOperation;
+
+
+public class JbossWSRuntimeCommand extends
+AbstractDataModelOperation {
+
+ IProject project;
+ String runtimelocation;
+
+ public JbossWSRuntimeCommand(IProject project){
+ PreferenceStore ps = new PreferenceStore("jbosswsui.properties");
+ try {
+ ps.load();
+ } catch (IOException e) {
+ // Ignore
+ }
+ runtimelocation = ps.getString("jbosswsruntimelocation");
+ this.project = project;
+ }
+
+ public IStatus execute(IProgressMonitor monitor, IAdaptable info)
+ throws ExecutionException {
+ return Status.OK_STATUS;
+ }
+
+ public IStatus executeOverride(IProgressMonitor monitor) {
+ // Copy the axis2 facet in to this project
+ IStatus status =null;
+// String runtimeLocation = null;
+// ContentCopyUtils contentCopyUtils = new ContentCopyUtils();
+// try {
+// if(context.isAxis2ServerPathRepresentsWar()
+// || RuntimePropertyUtils.getWarStatusFromPropertiesFile()){
+// runtimeLocation = Axis2RuntimeUtils.copyAxis2War(
+// monitor,
+// Axis2Constants.PROPERTY_KEY_PATH);
+// }else{
+//
+// runtimeLocation = Axis2WebappUtils.copyAxis2War(
+// monitor,
+// Axis2Constants.PROPERTY_KEY_PATH);
+// }
+// } catch (FileNotFoundException e) {
+// return handleExceptionStatus(e);
+// } catch (IOException e) {
+// return handleExceptionStatus(e);
+// } catch (Exception e) {
+// return handleExceptionStatus(e);
+// }
+//
+// // First Setting the libs folder as ignored and then copy the content of
+// // the runtime
+// IPath libPath = new Path(runtimeLocation);
+// libPath = libPath.append(Axis2Constants.DIR_WEB_INF);
+// libPath = libPath.append(Axis2Constants.DIR_LIB);
+// List<String> ignoreList = new ArrayList<String>();
+// ignoreList.add(libPath.toOSString());
+// contentCopyUtils.updateCheckList(ignoreList);
+//
+// status = contentCopyUtils.copyDirectoryRecursivelyIntoWorkspace(
+// runtimeLocation,
+// FacetContainerUtils.pathToWebProjectContainer(project.toString()),
+// monitor,
+// false
+// );
+//
+// // After that copy the nesessery set of libraries to the project again
+// List<String> includeList = new ArrayList<String>();
+// contentCopyUtils.updateCheckList(loadIncludeListWithAxis2Libs(libPath.toOSString(),
+// includeList));
+// String[] nodes = {Axis2Constants.DIR_WEB_INF,Axis2Constants.DIR_LIB};
+// status = contentCopyUtils.copyDirectoryRecursivelyIntoWorkspace(
+// libPath.toOSString(),
+// FileUtils.addNodesToPath(
+// FacetContainerUtils.pathToWebProjectContainer(project.toString()),
+// nodes),
+// monitor,
+// true
+// );
+//
+// // Merge web.xml Files
+// MergeWEBXMLCommand mergeWebXMLCommand = new MergeWEBXMLCommand();
+// mergeWebXMLCommand.setExtraAxis2TagsAdded(false);
+// mergeWebXMLCommand.setServerProject(project);
+// mergeWebXMLCommand.exexuteOverride(monitor);
+//
+// // clean up tempery files
+// File tempFacetDirectory = new File(runtimeLocation);
+// if (tempFacetDirectory.exists() && context.isAxis2ServerPathRepresentsWar()) {
+// FileUtils.deleteDir(tempFacetDirectory);
+// }
+// status = Status.OK_STATUS;
+ return status;
+ }
+
+ private void cleanupIfFacetStatusFailed(String runtimeLocation){
+// File tempFacetDirectory = new File(runtimeLocation);
+// if (tempFacetDirectory.exists()) {
+// FileUtils.deleteDir(tempFacetDirectory);
+// }
+ }
+
+ private IStatus handleExceptionStatus(Exception e){
+ IStatus status = null;
+// status = new Status(1,project.toString(),1,Axis2CoreUIMessages.ERROR_SERVER_IS_NOT_SET,e);
+// cleanupIfFacetStatusFailed(Axis2CoreUtils.tempAxis2Directory());
+ return status;
+ }
+
+ /**
+ * Load the exact libraries list from the axis2 jars with the correct
+ * versions to the <code>path</code>. Doing it this way introduce the
+ * scalability to the solution where the need comes in the future releases
+ * to include additional libraries and if needed filter out some libraries.
+ *
+ * @param runtimeLocation
+ * @param includeList
+ * @return loaded list
+ */
+ private List loadIncludeListWithAxis2Libs(String path, List includeList){
+// for (int i = 0; i < Axis2Constants.AXIS2_LIB_PREFIXES.length; i++) {
+// File[] jarFileList = FileUtils.getMatchingFiles(path,
+// Axis2Constants.AXIS2_LIB_PREFIXES[i],
+// Axis2Constants.JAR);
+// for (int j = 0; j < jarFileList.length; j++) {
+// includeList.add(jarFileList[j].getAbsolutePath());
+// }
+// // Fix for the 205972
+// File[] licenseFileList = FileUtils.getMatchingFiles(path,
+// Axis2Constants.AXIS2_LIB_PREFIXES[i],
+// Axis2Constants.TXT);
+// for (int k = 0; k < licenseFileList.length; k++) {
+// includeList.add(licenseFileList[k].getAbsolutePath());
+// }
+// }
+ return includeList;
+ }
+}
\ No newline at end of file
Added: trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/facet/delegate/JbossWSInstallRuntimeDelegate.java
===================================================================
--- trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/facet/delegate/JbossWSInstallRuntimeDelegate.java (rev 0)
+++ trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/facet/delegate/JbossWSInstallRuntimeDelegate.java 2008-04-18 10:29:41 UTC (rev 7606)
@@ -0,0 +1,47 @@
+/*******************************************************************************
+ * Copyright (c) 2008 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
+ *
+ * Contributors:
+ * Red Hat, Inc. - initial API and implementation
+ ******************************************************************************/
+
+
+package org.jboss.tools.ws.core.facet.delegate;
+
+import org.eclipse.core.resources.IProject;
+import org.eclipse.core.runtime.CoreException;
+import org.eclipse.core.runtime.IProgressMonitor;
+import org.eclipse.core.runtime.IStatus;
+import org.eclipse.core.runtime.Status;
+import org.eclipse.wst.common.project.facet.core.IDelegate;
+import org.eclipse.wst.common.project.facet.core.IProjectFacetVersion;
+import org.jboss.tools.ws.core.JbossWSCoreMessage;
+import org.jboss.tools.ws.core.command.JbossWSRuntimeCommand;
+
+public class JbossWSInstallRuntimeDelegate implements IDelegate {
+
+ private IStatus status;
+
+ public void execute(IProject project, IProjectFacetVersion arg1, Object arg2,
+ IProgressMonitor monitor) throws CoreException {
+ monitor.beginTask(JbossWSCoreMessage.PROGRESS_INSTALL_JBOSSWS_RUNTIME, 2 );
+
+ JbossWSRuntimeCommand command = new JbossWSRuntimeCommand(project);
+ status = command.executeOverride(monitor);
+// if (status.getCode() == Status.OK_STATUS.getCode() ){
+// RuntimePropertyUtils.writeServerStausToPropertiesFile(
+// Axis2Constants.SERVER_STATUS_PASS);
+// }else{
+// RuntimePropertyUtils.writeServerStausToPropertiesFile(
+// Axis2Constants.SERVER_STATUS_FAIL);
+// throw new CoreException(status);
+// }
+ monitor.worked( 1 );
+ monitor.done();
+ }
+
+}
17 years, 8 months
- 1
- 0
JBoss Tools SVN: r7605 - trunk/jsf/docs/userguide/en/modules.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2008-04-18 05:39:24 -0400 (Fri, 18 Apr 2008)
New Revision: 7605
Removed:
trunk/jsf/docs/userguide/en/modules/JSFStruts_tools.xml
Log:
http://jira.jboss.com/jira/browse/JBDS-261 - deleting the chapter because of the new guides organizing
Deleted: trunk/jsf/docs/userguide/en/modules/JSFStruts_tools.xml
===================================================================
--- trunk/jsf/docs/userguide/en/modules/JSFStruts_tools.xml 2008-04-18 08:49:52 UTC (rev 7604)
+++ trunk/jsf/docs/userguide/en/modules/JSFStruts_tools.xml 2008-04-18 09:39:24 UTC (rev 7605)
@@ -1,2927 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<chapter id="JSFStrutsTools">
- <?dbhtml filename="JSFStrutsTools.html"?>
- <title>JSF and Struts Tools</title>
-
- <para>This section provides information on JSF and Struts tooling in JBoss Developer Studio
- which allows you to develop JSF and Struts applications much faster and with far
- fewer errors so sparing your time.</para>
-
- <section id="JSF_support">
- <title>JavaServer Faces Support</title>
- <para>JBoss Developer Studio is especially designed for supporting JSF and
- JSF-related technologies. JBDS provides extensible and exemplary tools for
- building JSF-based applications as well as adding JSF capabilities to
- existing web projects, importing JSF projects (created outside JBDS) and
- choosing any JSF implementation while developing JSF application.</para>
-
- <section id="SupportForJSFEnvironmentsJSF_RIMyFacesFaceletsShaleOrAnyCustom442">
- <title>Support for JSF Environments: JSF-RI, MyFaces, Facelets or any Custom</title>
- <para>With Developer Studio, we don't lock you into any one
- <property>JavaServer Faces</property> implementation. Select
- the one you want to use for your project.</para>
- <para>When you:</para>
- <itemizedlist>
- <listitem>
- <para>Create a new <property>JSF project</property></para>
- </listitem>
- <listitem>
- <para>Add <property>JSF capability</property> to any
- existing Eclipse project</para>
- </listitem>
- <listitem>
- <para>Add <property>JSF capability</property> to any
- existing project (created outside JBDS)</para>
- </listitem>
- </itemizedlist>
- <para>You can always select which JSF implementation to use.</para>
-
- <para>You can also create your own custom JSF environments.</para>
- <figure>
- <title>Choosing JSF Environment</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_11.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>JBoss Developer Studio will add all the required libraries for the
- selected version to your project.</para>
- </section>
-
- <!--
-<section id="AddingSupportForTheOracleADFComponentsLibraryOrAnyOtherSupport64">
-<?dbhtml filename="AddingSupportForTheOracleADFComponentsLibraryOrAnyOtherSupport.html"?>
-<title>Adding Support for the Oracle ADF Components Library or Any Other Support</title>
-
-<para>JBoss Developer Studio is set up to work with the <property>ADF Faces Component Library</property>, but still requires a few extra
- steps to complete the support. First, you will need to download the 2 jar files for the library from the
- Oracle site down to your system. Then, you just need to follow these steps to add ADF Faces support to your projects:</para>
-
-<itemizedlist>
- <listitem><para>Select <emphasis><property>Window > Preferences > Red Hat > Library Sets</property></emphasis> from the menu bar.</para></listitem>
- <listitem><para>Select <emphasis><property>OracleADF</property></emphasis> in the upper pane.</para></listitem>
- <listitem>Then, click <emphasis><property>Add</property></emphasis> in the lower pane and browse to the location where you have both ADF jar files:
-<itemizedlist>
- <listitem><para>adf-faces-api-eaXX.jar</para></listitem>
- <listitem><para>adf-faces-impl-eaXX.jar</para></listitem>
- </itemizedlist></listitem>
- <listitem>In Preferences, select <emphasis><property>Custom Capability</property></emphasis>. Notice that Custom Capability ADF has the OracleADF
- library set to which we just added the required Jar libraries. We don't need to do anything here.</listitem>
- <listitem><para>Click <emphasis><property>OK</property></emphasis> and then click <emphasis><property>OK</property></emphasis> again.</para></listitem>
-<listitem>After this is done, you can always add in the library files to a project by just right-clicking
- your project and selecting <emphasis><property>JBoss Developer Studio > Add Custom Capability...</property></emphasis> from the context menu and select a needed capability.</listitem>
-</itemizedlist>
-
-<para>You can add any custom capability (support) to your project using Library Sets in the same fashion. </para>
-</section>
--->
-
- <section id="FaceletsSupport865">
-
- <title>Facelets Support</title>
- <para>This section will perform you all concepts that JBDS involves to use
- the Facelets.</para>
-
- <para>The Facelets extends JavaServer Faces by providing a lightweight
- framework that radically simplifies the design of presentation pages
- for JSF. JBoss Developer Studio provides support for Facelets in a
- variety of ways:</para>
-
- <itemizedlist>
- <listitem>
- <para>The New JSF Project wizard contains templates for
- creating Facelets projects based on version 1.2 of
- the JSF Reference Implementation. Select the <emphasis>
- <property>JSF 1.2 with Facelets</property>
- </emphasis> in JSF Environment section.</para>
- </listitem>
- </itemizedlist>
-
-
- <figure>
- <title>Choosing Facelets Environment</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_2.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Once you select the environment, you can specify the one of three
- available templates:</para>
-
- <figure>
- <title>Choosing Facelets Template</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_3.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>The following table lists possible Facelets templates for any JSF
- project and gives a proper description for each one.</para>
- <table>
- <title>Facelets Templates</title>
- <tgroup cols="2">
- <colspec colnum="1" colwidth="2*"/>
- <colspec colnum="2" colwidth="3*"/>
-
-
- <thead>
- <row>
- <entry align="center">
- <para>Template</para>
- </entry>
-
- <entry align="center">
- <para>Description</para>
- </entry>
- </row>
- </thead>
-
- <tbody>
-
- <row>
- <entry>
- <para>
- <emphasis>
- <property>FaceletsBlankWithoutLibs</property>
- </emphasis>
- </para>
- </entry>
-
- <entry>
- <para>Some servers already provide
- jsf libs and you take risk
- of getting conflicting
- libraries while deploying
- your project. To avoid such
- conflicts, use a template
- without libs if you have a
- server with its own jsf
- libraries</para>
- </entry>
- </row>
-
- <row>
- <entry>
- <para>
- <emphasis>
- <property>FaceletsKickStartWithRILibs</property>
- </emphasis>
- </para>
- </entry>
-
- <entry>
- <para>a sample application with
- Facelets that is ready to
- run</para>
- </entry>
- </row>
-
- <row>
- <entry>
- <para>
- <emphasis>
- <property>FaceletsKickStartWithoutLibs</property>
- </emphasis>
- </para>
- </entry>
-
- <entry>
- <para>a sample application without
- libraries</para>
- </entry>
- </row>
-
- </tbody>
- </tgroup>
- </table>
-
-
-
- <itemizedlist>
- <listitem>
- <para>The <link linkend="palette">JBoss Tools Palette</link>
- comes with the Facelets components ready to use. A
- useful tip appears when you hover the mouse cursor
- over the tag, the tip includes a detailed
- description of the tag component, the syntax and
- available attributes.</para>
- </listitem>
- </itemizedlist>
-
-
-
- <!-- JBoss Developer Studio does not provide templates for MyFaces right out of the box, but you can easily do it
- yourself with the "Save As Template" feature (available on the File submenu). Just create a small project
- with MyFaces and Facelets and then save it as a template for future use.
-
- How can I add Facelets support to an existing project?</para>
- <para>A: Right-click on the folder of existing project and select <emphasis>JBoss Tools > Add Custom Capabilities.. > Facelets</emphasis>. </para>
- -->
- <figure>
- <title>Facelets Components</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_4.png"
- scale="85"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <itemizedlist>
- <listitem>
- <para>Code assist (Ctrl + Space) for <property>Facelets
- tags</property> is available when editing <emphasis>
- <property>.xhtml</property>
- </emphasis> files.</para>
- </listitem>
- </itemizedlist>
-
- <figure>
- <title>XHTML File Code Assist</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_5.png"
- scale="70"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>What's more, code assist is also available for <emphasis
- role="italic">
- <property>"jsfc"</property>
- </emphasis> attribute in any HTML tag.</para>
-
- <figure>
- <title>Code Assist for Jsfc Attribute</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_6.png"
- scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>After selecting <emphasis role="italic">
- <property>"jsfc"</property>
- </emphasis> you get the code assist for JSF components available on
- a page.</para>
-
- <figure>
- <title>Code Assist for JSF Components</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_7.png"
- scale="80"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>When a component is chosen you will see all available attributes for
- it.</para>
-
- <figure>
- <title>Available Attributes for the Component</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_8.png"
- scale="80"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <itemizedlist>
- <listitem>
- <para>JBDS provides Eclipse's <emphasis>
- <property>OpenOn</property>
- </emphasis> feature for editing Facelets files.
- Using this feature, you can easily navigate between
- the <property>Facelets templates</property> and
- other parts of your projects. Just by holding down
- the Control key while hovering the mouse cursor over
- a reference to a template, the reference becomes a
- hyperlink to open that template.</para>
- </listitem>
- </itemizedlist>
-
- <figure>
- <title>Template Hyperlink</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_9.png"
- scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <!-- <para>Additionally, when hovering the mouse cursor over <emphasis role="italic"><property>"Facelets tag"</property></emphasis> attributes, JBoss Developer Studio provides a pop-up help tip:</para>
- <figure>
-<title>Pop-up Help Tip for Facelets Tag Attributes</title>
-<mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_support/defaultImage.png"/>
- </imageobject>
-</mediaobject>
- </figure>
-
- -->
- <!-- <para>See <link linkend="faq_facelets">FAQ</link> concerning Facelets
- support.</para>
- -->
- <section>
- <title>Relevant Resources Links</title>
- <para>Necessary information and support for Facelets find out <ulink
- url="https://facelets.dev.java.net/"
- >here</ulink>.</para>
- </section>
- </section>
- <section id="WorkingWithProjects7844">
-
- <title>Working with Projects</title>
- <para>To take an advantage of JSF support in <property>JBoss Developer
- Studio</property> firstly you should perform one of the next
- steps:</para>
-
- <itemizedlist>
- <listitem>
- <para>Create new JSF projects</para>
- </listitem>
- <listitem>
- <para>Import (open) existing JSF projects</para>
- </listitem>
- <listitem>
- <para>Add JSF capability to any existing Eclipse
- project</para>
- </listitem>
- <listitem>
- <para>Import and add JSF capability to any existing project
- created outside Eclipse.</para>
- </listitem>
- </itemizedlist>
- <para>In this section we're going to stop on each of them in
- detail.</para>
- <section id="CreatingANewJSFProject96">
-
- <title>Creating a New JSF Project</title>
-
- <para>If you want your project has already contained all JSF
- libraries, tag libraries and JSF configuration file, just
- organize a new brand JSF project. <property>JBoss Developer
- Studio</property> allows to do this easily with the
- help of the special wizard. To get it, select<emphasis>
- <property> File > New > Project
- > JBoos Tools Web > JSF
- > JSF Project</property>
- </emphasis> and click <emphasis>
- <property>Next</property>.</emphasis></para>
-
- <figure>
- <title>Choosing a JSF Project</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_10.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>On the next form you'll be prompted to enter
- <property>Project Name</property> and select a
- location for the project or just leave a default path.</para>
- <para>Here, JSF Version also allows you to select which JSF
- implementation to use.</para>
- <figure>
- <title>Creating a New JSF Project</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_11.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para><property>JBoss Developer Studio</property> comes with a
- number of predefined project templates that are flexible and
- easily customizable. Thus you can pick a different template
- on which the project should be based to. Almost all
- templates come in two variations: with jsf libraries and
- without ones.</para>
- <figure>
- <title>Choosing JSF Templates</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_12.png "
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>The table below provides description for each possible JSF
- template.</para>
- <table>
- <title>JSF Project Templates</title>
- <tgroup cols="2">
- <colspec colnum="1" colwidth="1*"/>
- <colspec colnum="2" colwidth="3*"/>
-
-
- <thead>
- <row>
- <entry align="center">
- <para>Template</para>
- </entry>
-
- <entry align="center">
- <para>Description</para>
- </entry>
- </row>
- </thead>
-
- <tbody>
-
- <row>
- <entry>
- <para>
- <emphasis>
- <property>JSFBlankWithLibs</property>
- </emphasis>
- </para>
- </entry>
-
- <entry>
- <para>This template will
- create a standard
- Web project
- structure with all
- JSF
- capabilities</para>
- </entry>
- </row>
-
- <row>
- <entry>
- <para>
- <emphasis>
- <property>JSFKickStartWithLibs</property>
- </emphasis>
- </para>
- </entry>
-
- <entry>
- <para>This template will
- create a standard
- Web project
- structure but will
- also include a
- sample application
- that is ready to
- run</para>
- </entry>
- </row>
-
- <row>
- <entry>
- <para>
- <emphasis>
- <property>JSFKickStartWithoutLibs</property>
- </emphasis>
- </para>
- </entry>
-
- <entry>
- <para>Some servers already
- provide jsf libs and
- you take risk of
- getting conflicting
- libraries while
- deploying your
- project. To avoid
- such conflicts, use
- a template without
- libs if you have a
- server with its own
- jsf libraries</para>
- </entry>
- </row>
-
- </tbody>
- </tgroup>
- </table>
-
-
- <!-- <para>You can of course create your own custom templates. More information
- on templates creation could be found in <link
- linkend="CreatingCustomJSPTemplates">Chapter 5</link>.</para>
- -->
-
- <para>On the next screen select what <emphasis>
- <property>Servlet version</property>
- </emphasis> to use and whether to register this application
- with JBoss AS (or other server) for running and testing of
- your application.</para>
-
- <para>The <emphasis>
- <property>Context Path</property>
- </emphasis> is the name under which the application will be
- deployed.</para>
-
- <para>The <emphasis>
- <property>Runtime</property>
- </emphasis> value tells Eclipse where to find Web libraries
- in order to build (compile) the project. It is not possible
- to finish project creation without selecting Runtime. If you
- don't have any values, select <emphasis>
- <property>New...</property>
- </emphasis> to add new Runtime.</para>
-
- <para>The <emphasis>
- <property>Target Server</property>
- </emphasis> allows you specifying whether to deploy the
- application. The Target Server corresponds to the Runtime
- value selected above. If you don't want to deploy
- the application, uncheck this value.</para>
- <figure>
- <title>Registering the Project on Server</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_14.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>When you are all done, you should have the project that has
- been appeared in the Package Explorer view:</para>
- <figure>
- <title>A New Project in the Package Explorer</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_15.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>At this point you can open <emphasis>
- <property>faces-config.xml</property>
- </emphasis> and start working on your application.
- <property>JBDS</property> provides a lot of features
- to develop JSF applications. We will describe the features
- further.</para>
- </section>
-
- <section id="ImportingExsJSFProjWithAnyStr74447">
-
- <title>Importing Existing JSF Projects with Any Structure</title>
-
- <para>For detailed information on migration projects to JBoss
- Developer Studio see <ulink
- url="../../Exadel-migration/html_single/index.html"
- >Migration Guide</ulink>. </para>
-
- </section>
- <section id="AddingJSFCapabilityToAnyExistingEclipseProject">
-
- <title>Adding JSF Capability to Any Existing Eclipse Project</title>
-
- <para>With <property>JBoss Developer Studio</property> it's
- also possible to add <property>JSF capability</property>
- (JSF libraries, tag libraries) to any existing Eclipse
- project in your workspace. After that you'll be
- able to make use of such <property>JBoss Developer
- Studio</property> editors as JSF configuration editor, JBoss
- Tools JSP editor and any others.</para>
- <para>Right click the project and select <emphasis>
- <property>JBoss Tools > Add JSF
- Capabilities</property>. </emphasis> This will start
- the process of adding all necessary libraries, files to make
- this a Web JSF project.</para>
- <figure>
- <title>Adding JSF Capabilities</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_16.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para>The wizard will first ask you to show the <emphasis>
- <property>web.xml</property>
- </emphasis> file location and the project name.</para>
- <figure>
- <title>Project Location</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_17.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para>On the last form you can set the different folders for your
- project as well as register this application with a servlet
- container.</para>
-
- <para>Make sure to select <emphasis>
- <property>Add Libraries</property>
- </emphasis> for <property>JBoss Developer Studio</property>
- to add all required JSF related libraries to this project.</para>
-
- <para>The <emphasis>
- <property>Context Path</property>
- </emphasis> is the name under which the application will be
- deployed.</para>
-
- <para>The <emphasis>
- <property>Runtime</property>
- </emphasis> value tells Eclipse where to find Web libraries
- in order to build (compile) the project. It is not possible
- to finish project import without selecting Runtime. If you
- don't have any values, select <emphasis>
- <property>New...</property>
- </emphasis> to add new Runtime.</para>
-
- <para>The <emphasis>
- <property>Target Server</property>
- </emphasis> allows you to specify whether to deploy the
- application. The Target Server corresponds to the Runtime
- value selected above. If you don't want to deploy
- the application, uncheck this value.</para>
- <figure>
- <title>Project Folders</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_18.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para>Once your project is imported you can see that JSF related
- libraries have been added to your project: <emphasis>
- <property>jsf-api.jar</property>
- </emphasis> and <emphasis>
- <property>jsf-impl.jar</property>
- </emphasis>.</para>
- <note>
- <title>Note:</title>
- <para>Some application servers provide their own jsf
- implementation libraries. So, to avoid conflicts you
- should not add jsf libraries while adding jsf
- capabilities.</para>
- </note>
- <para>You are now ready to work with JSF by creating a new JSF
- configuration file:</para>
-
-
- <figure>
- <title>Creating a New JSF Configuration File</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_19.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Once the file have been created, it should be open in a
- special <link
- linkend="GraphicalEditorAndViewingForJSFConfigurationFiles76331"
- >Faces Config Editor</link>.</para>
- </section>
- <section id="AddingYourOwnProjectTemplates853">
-
- <title>Adding Your Own Project Templates</title>
- <para>Template is a set of files that serve as a basis to facilitate
- the creation of a new project. Project templates provide
- content and structure for a project.</para>
- <para><property>JBoss Developer Studio</property> has a powerful
- templating capability for creating new and importing
- existing Struts and JSF projects. This templating facility
- has a variety of aspects to consider. But, let's
- start with the most straightforward case and consider the
- process of creating a template from your existing JSF
- project.</para>
-
- <para>Let's say you have a project that you want to use as
- the basis for a new <property>template</property>. Follow
- these steps to make a template out of it:</para>
- <itemizedlist>
- <listitem>
- <para>In the Web Projects view, right-click the
- project and select <emphasis>
- <property>JBoss Tools JSF > Save As
- Template</property>
- </emphasis></para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>Saving Your Project as Template</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_20.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <itemizedlist>
- <listitem>
- <para>In the first dialog box, you can choose a name
- for the template (defaults to the project
- name) and confirm what run-time
- implementation of the project's
- technology will be used</para>
- </listitem>
-
- </itemizedlist>
- <figure>
- <title>Define Template Properties</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_20_1.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
-
- <itemizedlist>
- <listitem>
- <para>Select <emphasis>
- <property>Next</property>
- </emphasis> and you will be sent to a dialog
- box with your project structure displayed
- with check boxes. Here you can check only
- those parts and files in your project
- directory that should be part of the
- template</para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>Define Template Properties</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_20_2.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <itemizedlist>
- <listitem>
- <para>At this point, unless you want to designate
- some extra files as having Velocity template
- coding inside them, you should click <emphasis>
- <property>Finish</property>
- </emphasis>.</para>
- </listitem>
- </itemizedlist>
- <para>That's it. Now, you can use this template with any
- new or imported project that uses the same run-time
- implementation as the project you turned into a
- template.</para>
- </section>
-
- <para>At this point, you have a fully configured project and now you can
- bring some new logic to it starting from JSF configuration
- file.</para>
- </section>
- <section id="GraphicalEditorAndViewingForJSFConfigurationFiles76331">
-
- <title>Graphical Editor and Viewing for JSF Configuration Files</title>
-
- <para>First, we should mention that JSF configuration file (<emphasis>
- <property>faces-config.xml</property>
- </emphasis>) is intended for registering JSF application resources
- such as Converters, Validators, Managed Beans and page-to-page
- navigation rules.</para>
- <para>Now, let's look at how you can easily configure this file by
- means of a special graphical editor. The editor has three main
- viewers (modes):</para>
-
- <itemizedlist>
- <listitem>
- <para>Diagram</para>
- </listitem>
- <listitem>
- <para>Tree</para>
- </listitem>
- <listitem>
- <para>Source</para>
- </listitem>
- </itemizedlist>
-
- <para>The modes can be selected via the tabs at the bottom of the editor.</para>
-
- <para>The JSF configuration editor also comes with a very useful <link
- linkend="OpenOnSelection4Hyperlinknavigation">OpenOn</link>
- selection feature.</para>
-
- <section id="Diagram9553">
-
- <title>Diagram</title>
- <para>The Diagram view displays the navigation rules in the JSF
- configuration file:</para>
- <figure>
- <title>Diagram View</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_21.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- <section id="CreatingNewViewPage85">
-
- <title>Creating New View (Page)</title>
-
- <para>To create a new page (view), you can click the page icon on
- this toolbar and then click anywhere on the diagram. A New
- Page Wizard will appear.</para>
-
- <para>To create a transition (rule) connecting pages:</para>
-
-
- <itemizedlist>
- <listitem>
- <para>Select the transition icon from the toolbar
- (2nd from the bottom).</para>
- </listitem>
- <listitem>
- <para>Click the source page.</para>
- </listitem>
- <listitem>
- <para>Click the target page.</para>
- </listitem>
- </itemizedlist>
-
- <para>A transition will appear between the two pages:</para>
- <figure>
- <title>Transition Between JSP Pages</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_22.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>It is also possible to create a new page with context menu by
- right-clicking anywhere on the diagram and selecting <emphasis>
- <property>New View</property>. </emphasis></para>
- <figure>
- <title>Creating a New View</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_23.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>To edit an existing transition, first select the transition
- line. Then, place the mouse cursor over the last black dot
- (on the target page). The mouse cursor will change to a big
- +. At this point, drag the line to a new target page:</para>
- <figure>
- <title>Editing Transition Between Views</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_24.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- <section id="TreeView11123">
-
- <title>Tree View</title>
-
- <para>The Tree mode for the editor displays all JSF application
- artifacts referenced in the configuration file in a tree
- format. By selecting any node you can see and edit its
- properties which will appear in the right-hand area. For
- example, a Managed Bean:</para>
- <figure>
- <title>Tree View</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_25.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>To edit some artifact, right-click any node and select one of
- the available actions in the context menu. You can also edit
- in the properties window to the right:</para>
- <figure>
- <title>Editing in Tree View</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_26.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para>The same way you can create a new artifact:</para>
- <figure>
- <title>Creating a New Artifact in Tree View</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_59.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- <section id="SourceView4643">
-
- <title>Source View</title>
-
- <para>The Source mode for the editor displays a text view of the JSF
- configuration file. All three viewers are always
- synchronized, so any changes made in one of the viewers will
- immediately appear in the others:</para>
- <figure>
- <title>Source View</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_27.png"
- scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- <section id="ContentAssist976">
-
- <title>Code Assist</title>
- <para>Code Assist provides pop-up tip to help you complete your code
- statements. It allows you to write your code faster and with
- more accuracy.</para>
- <para>Code assist is always available in the Source mode:</para>
- <figure>
- <title>Code Assist in Source View</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_28.png"
- scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- <section id="ErrorReporting3324">
-
- <title>Error Reporting</title>
- <para>When you are developing your project, JBoss Developer Studio
- constantly provides error checking. This greatly reduces
- your development time as it allows you to catch many of the
- errors during development.</para>
- <para>Errors will be reported by JBoss Developer Studio's
- <link linkend="verif_valid"> verification</link>
- facility:</para>
- <figure>
- <title>Error Reporting in Source View</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_29.png"
- scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Other errors are also reported.</para>
- <figure>
- <title>Other Errors Reporting</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_30.png"
- scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>You can also work in the Source editor with the help of the <emphasis>
- <property>Outline view</property>.</emphasis> The
- Outline views show a tree structure of the JSF configuration
- file. Simply select any element in the Outline view, and it
- will jump to the same place in the Source editor, so you can
- navigate through the source code with Outline view.</para>
- <figure>
- <title>Outline View</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_31.png"
- scale="60"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>If your diagram is large, within Outline view you can switch
- to a <emphasis>
- <property>Diagram Navigator</property>
- </emphasis> mode by selecting the middle icon at the top of
- the view window. It allows you to easily move around the
- diagram. Just move the blue area in any direction, and the
- diagram on the left will also move:</para>
- <figure>
- <title>Outline View for Diagram</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_32.png"
- scale="60"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>You can also edit the properties of the selected element in
- the <property>Tree</property> mode with the help of the
- Properties view as shown below:</para>
- <figure>
- <title>Properties View </title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_33.png"
- scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- </section>
- <section id="ManagedBeans96453">
-
- <title>Managed Beans</title>
-
- <para>JBoss Developer Studio gives you lots of power to work with
- <property>managed beans</property>.</para>
- <itemizedlist>
- <listitem>
- <para>Add and generate code for new managed beans</para>
- <itemizedlist>
- <listitem>
- <para>Generate code for attributes and
- getter/setter methods</para>
- </listitem>
- </itemizedlist>
- </listitem>
- <listitem>
- <para>Add existing managed beans to JSF configuration
- file</para>
- </listitem>
- </itemizedlist>
-
- <para>Thus, in this section we will guides you through all this possibilities.</para>
-
- <section id="CodeGenerationForManagedBeans421">
-
- <title>Code Generation for Managed Beans</title>
-
- <para>To start, create a new managed bean in JSF configuration file
- editor, in the Tree view.</para>
- <figure>
- <title>Creation of New Managed Bean</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_34.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <note>
- <title>Note:</title>
- <para>When you define a new managed bean, make sure that <emphasis>
- <property>Generate Source Code</property>
- </emphasis> is checked as shown in the figure
- below.</para>
- </note>
- <figure>
- <title>New Managed Bean</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_35.png"
- scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>After the <emphasis role="italic">
- <property>"Java"</property>
- </emphasis> class has been generated you can open it for
- additional editing. There are two ways to open the <emphasis
- role="italic">
- <property>"Java"</property>
- </emphasis> class:</para>
-
- <itemizedlist>
- <listitem>
- <para>click on <emphasis>
- <property>Managed-Bean-Class</property>
- </emphasis> link in the editor</para>
- </listitem>
- </itemizedlist>
- <para>or</para>
- <itemizedlist>
- <listitem>
- <para>right click the <emphasis>
- <property>managed bean</property>
- </emphasis> and select <emphasis>
- <property>Open Source</property>
- </emphasis></para>
- </listitem>
- </itemizedlist>
-
- <figure>
- <title>Opening of Created Managed Bean</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_36.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>The generated Java source:</para>
-
- <figure>
- <title>Java Source Code</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_37.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para>You can also generate source code for properties, also
- includes <emphasis role="italic">
- <property>"getter"</property>
- </emphasis> and <emphasis role="italic">
- <property>"setter"</property>
- </emphasis> methods. Right click on the bean and select <emphasis>
- <property>New > Property</property>
- </emphasis>. You will see <property>Add Property</property>
- dialog.</para>
- <figure>
- <title>Generation of Source Code for Properties</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_38.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para>When the form is open make sure that all the check boxes are
- selected:</para>
- <itemizedlist>
- <listitem>Add Java property</listitem>
- <listitem>Generate Getter</listitem>
- <listitem>Generate Setter</listitem>
- </itemizedlist>
- <para/>
- <figure>
- <title>"Add Property" Form</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_39.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para>Once the generation is complete, you can open the file and see
- the added property with <emphasis role="italic">
- <property>"getter"</property>
- </emphasis> and <emphasis role="italic">
- <property>"setter"</property>
- </emphasis> methods:</para>
- <figure>
- <title>Generated Java Source Code for Property</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_40.png"
- scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Thus, we've discussed everything which comes to
- creating a new Managed Bean. Further we will show you how to
- add an existing Bean into a JSF configuration file.</para>
- </section>
- <section id="AddExistingJavaBeansToAJSFConfigurationFile74332">
-
- <title>Add Existing Java Beans to a JSF Configuration File</title>
- <para>If you already have a Java bean you can easily add it to a
- <property>JSF configuration file</property>.</para>
- <para>You should start the same way you create a new managed bean.
- Use the <emphasis>
- <property>Browse...</property>
- </emphasis> button to add your existing Java class.</para>
- <figure>
- <title>New Managed Bean Form</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_42.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para>Once the class is set, it's <emphasis>
- <property>Name</property>
- </emphasis> will be set as well. But you can easily
- substitute it for the other one. Notice that <emphasis>
- <property>Generate Source Code</property>
- </emphasis> option is not available as the <emphasis
- role="italic">
- <property>"Java"</property>
- </emphasis> class already exists. </para>
- <para>After adding your class <emphasis>
- <property>Next</property>
- </emphasis> button will be activated. Pressing it
- you'll get <emphasis>
- <property>Managed Properties</property>
- </emphasis> dialog where all corresponding properties are
- displayed. Check the necessary ones to add them into your
- <property>JSF Configuration File</property>.</para>
-
- <figure>
- <title>Selection of Bean's Properties.</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_43.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>If you don't want to add any, just click <emphasis>
- <property>Finish</property>. </emphasis></para>
- </section>
- <para>Above-listed steps have demonstrated specifying an existing Bean in
- the JSF configuration file, i.e. <emphasis>
- <property>faces-config.xml</property>. </emphasis> In the
- next section you'll know how to organize and register a
- custom Converter to specify your own converting rules.</para>
- </section>
-
- <section id="CreateAndRegisterACustomConverter94230">
-
- <title>Create and Register a Custom Converter</title>
-
- <para>To create and register a custom converter it's necessary to
- go through the following steps:</para>
-
- <itemizedlist>
- <listitem>
- <para>In the Project Explorer view open <emphasis>
- <property>faces-config.xml</property>
- </emphasis> and select <emphasis>
- <property>Tree</property>
- </emphasis> tab.</para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>Converters</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_44.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <itemizedlist>
- <listitem>
- <para>Select <emphasis>
- <property>Converters</property>
- </emphasis> and click on<emphasis>
- <property> Add</property>
- </emphasis> button.</para>
- </listitem>
- <listitem>
- <para>On the form type the name of your converter in the <emphasis>
- <property>Converter-id</property>
- </emphasis> field and name of the class for
- converters. After clicking <emphasis>
- <property>Finish</property>
- </emphasis> button your custom converter is
- registered under the entered name.</para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>Add Converter Form</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_45.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <itemizedlist>
- <listitem>
- <para>Now you can create <emphasis role="italic">
- <property>"converter"</property>
- </emphasis> class. In the Converter section you
- should see your <emphasis>
- <property>Converter-id</property>
- </emphasis> and
- <emphasis><property>Converter-class</property>.</emphasis>
- Click on <emphasis>
- <property>Converter-class</property>
- </emphasis> to generate the source code.</para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>Generation of Source Code for Converter Class</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_46.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <itemizedlist>
- <listitem>
- <para>A usual wizard for creating a Java class will appear.
- All needed fields here will be adjusted
- automatically. Just leave everything without changes
- and click <emphasis>
- <property>Finish</property>.
- </emphasis></para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>New Java Class Form</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_47.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <itemizedlist>
- <listitem>
- <para>To open a converter class click again on <emphasis>
- <property>Converter-class</property>
- </emphasis> link in the Converter section. Now you
- are able to add a business logic of converter in the
- Java editor.</para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>Converter Class</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_48.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- </section>
-
- <section id="CreateAndRegisterACustomValidator5632">
-
- <title>Create and Register a Custom Validator</title>
-
- <para>With the help of JBDS it's also quite easy to develop your
- own custom Validators. You should perform the actions similar to
- previous. Go through the following steps:</para>
- <itemizedlist>
- <listitem>
- <para>In the Project Explorer view open<emphasis>
- <property> faces-config.xml</property>
- </emphasis> and select <emphasis>
- <property>Tree </property>
- </emphasis>tab.</para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>Validator in Faces Config Editor</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_49.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <itemizedlist>
- <listitem>
- <para>Select <emphasis>
- <property>Validators</property>
- </emphasis> and click on <emphasis>
- <property>Add </property>
- </emphasis>button.</para>
- </listitem>
- <listitem>
- <para>Type the name of your validator in the <emphasis>
- <property>Validator-id</property>
- </emphasis> field and name of the class for
- validators. After clicking <emphasis>
- <property>Finish</property>
- </emphasis> button your custom validator is
- registered under the entered name.</para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>Adding Validator</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_50.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Now you can create the "validator" class. </para>
- <itemizedlist>
- <listitem>
- <para>In the Validator section you can see your <emphasis>
- <property>Validator-id</property>
- </emphasis> and <emphasis>
- <property>Validator-class</property>
- </emphasis>. To generate the source code click on <emphasis>
- <property>Validator-class</property>.
- </emphasis></para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>Creating Validator Class</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_51.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <itemizedlist>
- <listitem>
- <para>Java class will be created automatically. Leave
- everything without changes and click <emphasis>
- <property>Finish</property>.
- </emphasis></para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>New Java Class Form</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_52.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <itemizedlist>
- <listitem>
- <para>To open validator class click again on <emphasis>
- <property>Validator-Class</property>
- </emphasis> link in the Validator section. Now you
- are able to write a business logic of validator in
- the Java editor.</para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>Converter Class Editing</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_53.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- </section>
-
- <section id="CreateAndRegisterReferencedBeans64322">
-
- <title>Create and Register Referenced Beans</title>
-
- <para>Creation of Referenced Beans is similar to creation of Custom
- Validator.</para>
-
- <itemizedlist>
- <listitem>
- <para>In the Project Explorer view open<emphasis>
- <property> faces-config.xml</property>
- </emphasis> and select <emphasis>
- <property>Tree </property>
- </emphasis>tab.</para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>Referenced Beans in Faces Config Editor</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_54.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <itemizedlist>
- <listitem>
- <para>Select <emphasis>
- <property>Referenced Beans</property>
- </emphasis> and click on <emphasis>
- <property>Add</property>
- </emphasis> button.</para>
- </listitem>
- <listitem>
- <para>Type in the name of your Referenced Bean and type in
- or select <emphasis>
- <property>Referenced-Bean-Class</property>
- </emphasis> by using <emphasis>
- <property>Browse</property>
- </emphasis> button.</para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>Add Referenced Bean</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_55.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <itemizedlist>
- <listitem>
- <para>In the Referenced Bean section you should see your <emphasis>
- <property>Referenced-Bean-Name</property>
- </emphasis> and
- <emphasis><property>Referenced-Bean-Class</property>.</emphasis>
- Click on the link to open the Java creation
- wizard.</para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>Create Referenced Bean Class</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_56.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <itemizedlist>
- <listitem>
- <para>Java class will be created automatically. Leave
- everything without changes and click <emphasis>
- <property>Finish</property>.
- </emphasis></para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>New Java Class Form</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_57.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <itemizedlist>
- <listitem>
- <para>To open Referenced Bean class click again on <emphasis>
- <property>Referenced-Bean-Class</property>
- </emphasis> in the Referenced Bean section. Now you
- are able to write business logic of Referenced Bean
- in the Java editor.</para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>Referenced Bean Class Editing</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/jsf_support/jsf_support_58.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- </section>
-
- <section>
- <title>Relevant Resources Links</title>
- <para>If you don't familiar with <ulink
- url="http://java.sun.com/javaee/javaserverfaces/">JSF
- technology</ulink>, we suggest that you walk through the
- information on the topic.</para>
- </section>
- </section>
-
- <section id="Struts_support">
-
- <title>Struts support</title>
- <para>If you prefer develop web applications using <property>Struts</property>
- technology JBoss Developer Studio also meets your needs.</para>
- <para>JBDS supports the <property>Struts 1.1</property>, <property>1.2.x</property>
- versions.</para>
-
- <section id="WorkingWithStrutsProjects866">
-
- <title>Working with Projects</title>
-
- <para>JBoss Developer Studio provides the following functionality when
- working with Struts:</para>
-
- <itemizedlist>
- <listitem>
- <para>Create new <property>Struts projects</property></para>
- </listitem>
- <listitem>
- <para>Import (open) existing Struts projects. You can import
- any project structure</para>
- </listitem>
- <listitem>
- <para>Add <property>Struts capabilities</property> to any
- existing Eclipse project</para>
- </listitem>
- <listitem>
- <para>Import and add Struts capabilities to any existing
- project created outside Eclipse.</para>
- </listitem>
- </itemizedlist>
-
-
- <section id="CreatingANewStrutsProjec745t">
-
- <title>Creating a New Struts Project</title>
-
-
- <para>JBoss Developer Studio includes a New Struts Project Wizard
- that radically simplifies the process for getting started
- with a new Struts project. You just need to follow these
- steps:</para>
- <itemizedlist>
- <listitem>
- <para>Select<emphasis>
- <property>File > New >
- Project...</property>
- </emphasis> from the menu bar. Then, select <emphasis>
- <property>JBoss Tools Web > Struts >
- Struts Project</property>
- </emphasis> in this dialog box. Click <emphasis>
- <property>Next</property>:
- </emphasis></para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>Selecting Struts Wizard</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_2.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <itemizedlist>
- <listitem>
- <para>On this form, provide the <property>Project
- Name</property>. You can also select
- where to create the project or use the
- default path.</para>
- <para>Next to <property>Struts
- Environment</property> set which Struts
- version to use.</para>
- </listitem>
- </itemizedlist>
-
- <figure>
- <title>Creating Struts Project</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_3.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <tip>
- <title>Tip:</title>
- <para>Don't put spaces in project names since some
- OS could experience problems with their processing
- and searching these files.</para>
- </tip>
-
- <para>You can select the KickStart template, then the project
- created will include a simple Hello World type application
- that is ready to run.</para>
-
- <figure>
- <title>Choosing Struts Template </title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_3_1.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <itemizedlist>
- <listitem>
- <para>Next, you register this application with the
- current servlet container defined for your
- workspace (JBoss AS, by default) in order to
- allow you to test your application more
- easily while still developing it. A new
- entry will be added in the servlet container
- configuration file to enable running the
- application in-place (called null deployment
- or link deployment). Uncheck the <emphasis
- role="italic">
- <property>"Target
- Server"</property>
- </emphasis> check box if for some reason you
- don't want to register your
- application at this point.</para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>Registering The Project at Server</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_4.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <itemizedlist>
- <listitem>
- <para>On the next form, you can select the TLD files
- to include in this project:</para>
- </listitem>
- </itemizedlist>
- <figure>
- <title>Selecting Tag Libraries</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_5.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>After the project is created, you should have the following
- project structure (if you used the KickStart template):</para>
-
- <figure>
- <title>Project Structure</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_6.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <tip>
- <title>Tip:</title>
- <para>If you want to hide the jar files from Web App
- Libraries in view, select the down-pointing arrow in
- the upper right corner, select
- <emphasis>Filters...</emphasis>, check the box next
- to Name filter patterns (matching names will be
- hidden), and type *.jar into the field. Then, click
- OK. </para>
- </tip>
- </section>
- <section id="ImportingAnExistingStrutsProjectWithAnyStructure9653">
-
- <title>Importing an Existing Struts Project with Any Structure</title>
-
- <para>For detailed information on migration projects to JBoss
- Developer Studio see <ulink
- url="../../Exadel-migration/html_single/index.html"
- >Migration Guide</ulink>.</para>
-
- </section>
- <section id="AddingStrutsCapabilityToAnExistingWebApplication532">
-
- <title>Adding Struts Capability to an Existing Web Application</title>
-
- <para>With JBoss Developer Studio you can add <property>Struts
- capabilities</property> (including Struts libraries,
- tag libraries and a Struts configuration file) to any
- existing Web application project in your Eclipse workspace.
- By adding a Struts Nature to your project, you can now edit
- files using JBoss Developer Studio editors, such as the
- Struts configuration editor and the JBoss Tools JSP editor.</para>
- <para>To add Struts Nature to your existing Project right-click the
- project and select <emphasis>
- <property>JBoss Tools > Add Struts
- Capabilities</property>
- </emphasis> from the context menu. This will start the
- process of adding all necessary libraries and files to make
- this a Web Struts project.</para>
-
- <figure>
- <title>Adding Struts Capabilities</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_7.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>In the wizard you should point to location of your deployment
- descriptor file web.xml and name of the project.</para>
-
- <figure>
- <title>Choosing Project Location</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_8.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para>After hitting <emphasis>
- <property>Next</property>, </emphasis> you will see
- the following screen. This screen simply means that you need
- to add at least one Struts module to your project to make
- this project a Struts project. Adding a Struts module means
- that a new struts-config.xml will be added to your project
- and registered in the web.xml file. In addition, all
- required Struts libraries will be added. To add a Struts
- module, select the <emphasis>
- <property>Add Struts Support</property>
- </emphasis> button.</para>
- <figure>
- <title>Project Modules</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_9.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Here you can select what Struts <property>Version</property>,
- <property>Servlet Class</property>, <property>URL
- Pattern</property> and <property>TLD</property>s to
- add to this project.</para>
-
- <figure>
- <title>Selecting Struts Support Options</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_10.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>When done, you will see the default Struts module
- configuration information. See how to Edit <link
- linkend="SupportForMultipleStrutsModules75">Struts
- modules</link>.</para>
-
- <figure>
- <title>Project Configuration Information</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_11.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>On the last screen you can set the different folders for your
- project as well as register this application with a servlet
- container. If you want the libraries (.jar files) will be
- automatically added to your project, click on the checkbox <emphasis>
- <property>Add Libraries</property>.</emphasis></para>
-
- <figure>
- <title>Registering the Project at Server</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_12.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>When done, you can open end edit the struts-config.xml file
- using usefull Struts configuration file editor provided by
- JBDS. (The Struts configuration is shown below in the Tree
- viewer).</para>
-
- <figure>
- <title>Struts-config.xml File</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_13.png"
- scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- </section>
- <section id="GraphicalEditorForStrutsConfigurationFiles564">
-
- <title>Graphical Editor for Struts Configuration Files</title>
-
- <para>The Struts configuration file editor has three modes with different
- representation of <emphasis>
- <property>struts-config.xml</property>: </emphasis>Diagram,
- Tree and Source. The modes can be selected via the tabs at the
- bottom of the editor. Any changes made in one mode are immediately
- visible when you switch to any other mode.</para>
-
- <para>When working in Source view, you always have all the following
- features available:</para>
- <itemizedlist>
- <listitem>
- <para>Content Assist</para>
- </listitem>
- <listitem>
- <para>Open On Selection</para>
- </listitem>
- <listitem>
- <para>File Folding</para>
- </listitem>
- </itemizedlist>
- <section id="StrutsDiagramMode453">
-
- <title>Diagram Mode</title>
-
- <para>The Diagram mode graphically displays the Web flow of the
- application defined in the Struts configuration file.</para>
-
- <figure>
- <title>Diagram Mode</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_14.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>The Diagram mode allows to edit navigation in your Struts
- application. Just by right-clicking anywhere on the diagram,
- you can use a context menu to create the building blocks of
- a Struts application:</para>
- <itemizedlist>
- <listitem>
- <para>Actions</para>
- </listitem>
- <listitem>
- <para>Global forwards</para>
- </listitem>
- <listitem>
- <para>Global exceptions</para>
- </listitem>
- <listitem>
- <para>JSP Pages</para>
- </listitem>
- </itemizedlist>
-
- <figure>
- <title>Diagram Context Menu</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_15.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Along the upper-left side of the editor is a stack of seven
- icons for changing the behavior of the cursor in the
- diagram. </para>
-
- <figure>
- <title>Editor Icons</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_16.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>The first icon switches to the default regular selection
- cursor, the second to the marquee selection cursor and the
- third to the new connection cursor. The last four icons
- switch the cursor to an insert cursor for each type of
- Struts build block listed above (and in the order listed).</para>
-
- <para>For instance, clicking on the first of these four icons (the
- one with the gears) will switch the cursor to insert
- actions. Clicking anywhere in the diagram with this cursor
- has the same effect as right-click and selecting <emphasis>
- <property>Add > Action...</property>
- </emphasis> from the context menu with the regular cursor
- active. It's just more efficient to use this cursor
- if you're adding more than one action at once.</para>
-
-
- </section>
- <section id="StrutsTreeMode42">
-
- <title>Tree Mode</title>
-
- <para>The Tree mode represents the different elements of the Struts
- application that are organized into functional categories on
- the left-hand side and a form for editing the properties of
- currently selected items on the right-hand side.</para>
-
- <figure>
- <title>Tree Mode</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_17.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>You can also right-click on any node in the category tree and
- perform appropriate operations through a context menu. For
- instance, by right-clicking on the action-mappings category
- node, you can add new actions to the application.</para>
-
- <figure>
- <title>Tree Context Menu</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_18.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- <section id="StrutsSourceMode9655">
-
- <title>Source Mode</title>
-
- <para>In the Source mode, you have complete editing control of the
- underlying XML coding.</para>
-
- <figure>
- <title>Source Mode</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_19.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>You can take advantage of <link
- linkend="CodeAssistAndDynamicCodeAssist42BasedOnProjectData"
- >code assist</link>.</para>
-
- <figure>
- <title>Code Assist</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_20.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>The editor will also immediately flag any errors.</para>
-
- <figure>
- <title>Errors in Source Mode</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_21.png"
- scale="83"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Finally, you can use the Outline view with the editor to
- easily navigate through the file.</para>
-
- <figure>
- <title>Outline View</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_22.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- </section>
-
- <para>Find more information about editor features <link
- linkend="editors_features">here</link>.</para>
-
- </section>
-
- <section id="GraphicalEditorForTilesFiles132">
-
- <title>Graphical Editor for Tiles Files</title>
-
- <para>The Tiles configuration file editor has three main modes: Tree,
- Diagram and Source. The modes can be selected via the tabs at the
- bottom of the editor. Any changes made in one mode are immediately
- visible when you switch to any other mode.</para>
-
- <para>When working in Source view, you always have all following features
- available:</para>
- <itemizedlist>
- <listitem>
- <para>Content Assist</para>
- </listitem>
- <listitem>
- <para>Open On Selection</para>
- </listitem>
- </itemizedlist>
- <section id="CreateNewTilesFile1422">
-
- <title>Create New Tiles File</title>
-
- <para>To create new Tiles files, right click any folder and select <emphasis>
- <property>New > Tiles File</property>.
- </emphasis></para>
- <figure>
- <title>Creating a New Tiles File</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_23.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- <section id="StrutsTreeView896">
-
- <title>Tree Mode</title>
-
- <para>The Tree mode represents the different elements of the Tiles
- file that are organized into functional categories on the
- left-hand side and a form for editing the properties of
- currently selected items on the right-hand side.</para>
- <figure>
- <title>Tree Mode</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_24.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>To edit the file, simply right click any node and select among
- the available actions.</para>
- <figure>
- <title>Editing in Tiles Editor</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_25.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- <section id="StrutsDiagramView4643">
-
- <title>Diagram Mode</title>
-
- <para>The Diagram mode allows you to create complex Tiles files in
- the form of a diagram.</para>
- <figure>
- <title>Diagram Mode</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_26.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>To create new definitions, simply right click anywhere in the
- diagram.</para>
- <figure>
- <title>Creating New Definition</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_27.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>You can also use the Diagram toolbar to make editing easier.</para>
- <figure>
- <title>Diagram Toolbar</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_28.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para> It contains four icons for changing the cursor state. The
- first one is the default cursor state for selecting existing
- nodes. The second icon is marquee selector. The third is
- used for creating new connections and the last one is for
- adding definition template to the content.</para>
- </section>
- <section id="StrutsSource75">
-
- <title>Source</title>
-
- <para>The other mode of the <property>Tiles editor</property> is the
- Source mode that gives you full control over the source. Any
- changes here will immediately appear in other modes when you
- switch to them.</para>
- <figure>
- <title>Source Mode</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_29.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para><link
- linkend="CodeAssistAndDynamicCodeAssist42BasedOnProjectData"
- >Code assist</link> is available in the Source mode.</para>
- <figure>
- <title>Code Assist</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_30.png"
- scale="85"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Any errors are immediately reported as shown below:</para>
- <figure>
- <title>Errors Reporting</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_31.png"
- scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>You can also use the Outline view together with the
- editor's Source mode. It provides an easier
- navigation through the file.</para>
- <figure>
- <title>Outline View</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_32.png"
- scale="85"/>
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- </section>
- <section id="GraphicalEditorForStrutsValidationFiles86">
-
- <title>Graphical Editor for Struts Validation Files</title>
-
- <para>Providing full support for development Struts applications JBoss
- Developer Studio comes with a visual validation editor. To create a
- new validation file, right click any folder in Project Explorer and
- select <emphasis>
- <property>File > New > Other...</property>
- </emphasis>from the context menu and then <emphasis>
- <property>JBoss Tools Web > Struts > Validation
- File</property>. </emphasis></para>
- <figure>
- <title>Creating New Validation File</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/struts/struts_33.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>The validation editor works with five modes: Formsets, Validators,
- Constants and standard Tree and Source that you can easily switch
- over using tabs at the bottom of the editor.</para>
- <para>The Formsets mode shows forms and their elements on the left side and
- the dialogue for defining their validation rules on the right side.</para>
- <figure>
- <title>Formsets Mode</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/struts/struts_34.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>The Constants mode let you set constant values for your validation
- rules.</para>
- <figure>
- <title>Constansts Mode</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/struts/struts_35.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>The validation file can also be viewed in a Tree mode.</para>
- <figure>
- <title>Tree Mode</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/struts/struts_36.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>At any point you have full control over the source by switching to the
- Source mode. Any editing in this mode will immediately be available
- in other modes of the editor.</para>
- <figure>
- <title>Source Mode</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/struts/struts_37.png"
- scale="85"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>You can also open your own custom or Struts-standard <emphasis>
- <property>validation-rules.xml</property>
- </emphasis> file.</para>
- <para>The Validators mode shows the validation rules for a selected
- validator. You can of course add your own rules.</para>
- <figure>
- <title>Validators Mode</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/struts/struts_38.png"
- scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Here are the validation rules shown in the Source mode.</para>
- <figure>
- <title>Validation Rules</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/struts/struts_39.png"
- scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- <section id="SupportForMultipleStrutsModules75">
-
- <title>Support for Multiple Struts Modules</title>
-
- <para>JBoss Developer Studio supports working with Struts projects that have
- multiple modules. You can easily do the following:</para>
- <itemizedlist>
- <listitem>
- <para>Add new modules</para>
- </listitem>
- <listitem>
- <para>Edit modules for an existing project or during Struts
- project import</para>
- </listitem>
- </itemizedlist>
-
- <section id="WhenImportingAStrutsProject432">
-
- <title>When Importing a Struts Project</title>
-
- <para>During Struts project import, if the project has multiple
- modules, you will see a screen with all existing modules.
- You can select each module and edit its details.</para>
-
- <figure>
- <title>Configuring Project Modules</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_40.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- <section id="EditingModulesInAnExistingProject1">
-
- <title>Editing Modules in an Existing Project</title>
- <para>To edit modules in an existing project, right click the
- project and select <emphasis>
- <property>JBoss Tools > Modules
- Configuration</property>. </emphasis></para>
- <figure>
- <title>Choosing Modules Configuration</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_41.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para>You will see the same screen as above where you will be able
- to select a module and edit its details.</para>
- <figure>
- <title>Modules Configuration</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_42.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- <section id="AddingNewModules1">
-
- <title>Adding New Modules</title>
-
- <para>Adding a new module is very simple. First switch to Web
- Project view. Expand your project to the Configuration
- folder. Under that folder you should see the current
- modules. Right click on Configuration and select <emphasis>
- <property>New > Struts Config</property>.
- </emphasis></para>
- <figure>
- <title>Adding New Modules</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_43.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para>You will see the screen below. You can specify a new module
- name and also add the new Struts configuration file to
- web.xml file.</para>
- <figure>
- <title>Adding New Modules</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/struts/struts_44.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- </section>
- <section id="CodeGenerationForActionFormBeanForwardAndExceptionClasses1">
-
- <title>Code Generation for Action, FormBean, Forward and Exception Classes</title>
-
- <para>JBoss Developer Studio comes with a <property>code
- generation</property> feature. You can generate stub code for Struts
- Actions, FormBeans, Forwards and Exceptions.</para>
-
- <para>The code generation in JBoss Developer Studio is based on Velocity
- templates which can be modified for your use. The templates are
- located at <emphasis>
- <property> {RedHatDeveloperStudioHome} > templates >
- codegeneration</property>. </emphasis></para>
-
- <para>There are a number of ways to invoke code generation. One is simply
- right-clicking the Struts diagram and selecting <emphasis>
- <property>Generate Java Code....</property>
- </emphasis></para>
-
- <figure>
- <title>Selecting Generate Java Code</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/struts/struts_45.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>On this screen you can select for which elements to generate code. If
- you select Next you will be able to specify more options for each of
- the categories you selected.</para>
-
- <figure>
- <title>Generate - Step 1</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/struts/struts_46.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <tip>
- <title>Tip:</title>
- <para>please be careful not to override your existing files.</para>
- </tip>
-
- <para>When generation is complete, a result window will appear letting you
- know how many classes were generated:</para>
-
- <figure>
- <title>Generation Finished</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/struts/struts_47.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>You don't always have to generate code for all elements at
- once. You can invoke generation for just an individual Struts
- artifact as well. Right-click an element on the diagram of the
- Struts configuration file and select <emphasis>
- <property>Generate Java Code...</property>
- </emphasis> from the context menu.</para>
-
- <figure>
- <title>Generation For Individual Struts Artifact</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/struts/struts_48.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>The same can be done from within the Tree viewer for the editor of the
- Struts configuration file.</para>
-
- <figure>
- <title>Generation in Struts Config Editor</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/struts/struts_49.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- <section id="StrutsConfigurationFileDebugger097">
-
- <title>Struts Configuration File Debugger</title>
-
- <para>JBoss Developer Studio comes with <property>Struts configuration file
- debugger</property>. It allows you to set break points on
- Struts diagram and then simply launch the server in debug mode.</para>
-
- <para>Simply right click an Action or a page and select Add <emphasis>
- <property>Breakpoint</property>. </emphasis></para>
- <figure>
- <title>Adding Breakpoint</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/struts/struts_50.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- <section id="CustomizablePageLinksRecognizer1">
-
- <title>Customizable Page Links Recognizer</title>
-
- <para><property>Custom page links</property> allow you to define custom
- Struts page links that will be recognizable in the Struts
- application diagram. You can define these links by selecting <emphasis>
- <property>Window > Preferences</property>
- </emphasis> from the menu bar and then selecting <emphasis>
- <property>JBoss Tools > Web > Struts >
- Customization</property>
- </emphasis> from the Preferences dialog box.</para>
- <figure>
- <title>Customization Panel</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/struts/struts_51.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- </section>
-
- <section>
- <title>Relevant Resources Links</title>
- <para>Find out necessary information on <ulink
- url="http://struts.apache.org/">Struts technology</ulink> if
- you don't know enough.</para>
- </section>
- </section>
-
- <section id="verif_valid">
- <title>Verification and Validation</title>
-
- <para>As you are developing your project, JBoss Developer Studio Verification
- constantly provides dynamic <property>validation</property>, consistency
- checking and error checking. This greatly reduces your development time as
- it allows you to catch many of the errors during development. JBoss
- Developer Studio provides dynamic verification for both JSF and Struts
- projects.</para>
-
-
- <section id="JSFProjectVerification754">
-
- <title>JSF Project Verification</title>
-
- <para>JBoss Developer Studio checks for many different rules for a JSF
- project that can be configured by selecting <emphasis>
- <property>Window > Preferences</property>
- </emphasis> from the menu bar, selecting <emphasis>
- <property>JBoss Tools > Web > Verification</property>
- </emphasis> from the Preferences dialog box and then expanding the
- JSF Rules node.</para>
- <figure>
- <title>JSF Rules</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/verif_valid/verif_valid_1.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para>Suppose you are working in the Source viewer for a JSF configuration
- file as shown below:</para>
- <figure>
- <title>Faces-config.xml File</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/verif_valid/verif_valid_2.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para>While typing a class name, you might make a minor typo (like <emphasis
- role="italic">
- <property>"jsfHello.PersonBean9"</property>
- </emphasis> instead of <emphasis role="italic">
- <property>"jsfHello.PersonBean"</property>
- </emphasis>). After saving the file, verification checks to make
- sure everything is correct and finds the error below:</para>
- <figure>
- <title>Error in Source View</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/verif_valid/verif_valid_3.png"
- scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Notice that the Package Explorer View shows a marked folder and a
- marked file where the error is.</para>
- <para>You can place the cursor over the line with an error message and get a
- detailed error message:</para>
- <figure>
- <title>Error Message</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/verif_valid/verif_valid_4.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para>Verification also checks navigation rules:</para>
- <figure>
- <title>Checking Navigation Rules</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/verif_valid/verif_valid_5.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para>If you provide a page name that does not exist, verification will let
- you know about that:</para>
- <figure>
- <title>Page Name Verification</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/verif_valid/verif_valid_6.png"
- scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>You can always call up verification explicitly by right-clicking any
- element in the tree and selecting Verify from the context menu. This
- works from both the Tree and Diagram viewers for the JSF
- configuration file editor. You can also invoke verification from the
- Web Projects view. Below we are checking all of the elements in the
- configuration file.</para>
- <figure>
- <title>Verify Command</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/verif_valid/verif_valid_7.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- <section id="strutsprojectverification783643">
-
- <title>Struts Project Verification</title>
-
- <para>JBoss Developer Studio provides the same functionality for Struts
- projects. To configure Struts project verification select <emphasis>
- <property>Window > Preferences</property>
- </emphasis> from the menu bar, select <emphasis>
- <property>JBoss Tools > Web > Verification</property>
- </emphasis> from the Preferences dialog box and then expand the
- Struts Rules node.</para>
- <figure>
- <title>Struts Rules</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/verif_valid/verif_valid_8.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para>Suppose you are working in the Source viewer for a Struts
- configuration file as shown below:</para>
- <figure>
- <title>Struts Configuration File</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/verif_valid/verif_valid_9.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para>While typing a class name or entering it from the graphical editor,
- you might make a minor typo (like <emphasis role="italic">
- <property>"sample.GreetingAction1"</property>
- </emphasis> instead of <emphasis role="italic">
- <property>"sample.GreetingAction"</property>
- </emphasis>). After saving the file,
- <property>verification</property> checks to make sure everything is
- correct and finds the error below:</para>
- <figure>
- <title>Error Reporting</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/verif_valid/verif_valid_10.png"
- scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Notice that the Package Explorer View shows a marked folder and a
- marked file where the error is.</para>
- <para>You can place the cursor over the line with the error to view a
- detailed error message:</para>
- <figure>
- <title>Error Message</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/verif_valid/verif_valid_11.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para>The verification also checks to make sure you have specified the
- correct JSP page for the forward:</para>
- <figure>
- <title>JSP Page Verification</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/verif_valid/verif_valid_12.png"
- scale="75"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Once you place the cursor over the line, you can see the error
- message:</para>
- <figure>
- <title>Error Message</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/verif_valid/verif_valid_13.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- <para>You can always invoke the verification by switching to the Diagram
- viewer, right-clicking and selecting <emphasis>
- <property>Verify</property>
- </emphasis> from the context menu:</para>
- <figure>
- <title>Verify Command</title>
- <mediaobject>
- <imageobject>
- <imagedata
- fileref="images/verif_valid/verif_valid_14.png"
- />
- </imageobject>
- </mediaobject>
- </figure>
- </section>
-
- </section>
-
-
-</chapter>
17 years, 8 months
- 1
- 0
JBoss Tools SVN: r7604 - in trunk/ws/plugins: org.jboss.tools.ws.core and 13 other directories.
by jbosstools-commits＠lists.jboss.org
Author: Grid.Qian
Date: 2008-04-18 04:49:52 -0400 (Fri, 18 Apr 2008)
New Revision: 7604
Added:
trunk/ws/plugins/org.jboss.tools.ws.core/
trunk/ws/plugins/org.jboss.tools.ws.core/.classpath
trunk/ws/plugins/org.jboss.tools.ws.core/.project
trunk/ws/plugins/org.jboss.tools.ws.core/META-INF/
trunk/ws/plugins/org.jboss.tools.ws.core/META-INF/MANIFEST.MF
trunk/ws/plugins/org.jboss.tools.ws.core/bin/
trunk/ws/plugins/org.jboss.tools.ws.core/bin/org/
trunk/ws/plugins/org.jboss.tools.ws.core/bin/org/jboss/
trunk/ws/plugins/org.jboss.tools.ws.core/bin/org/jboss/tools/
trunk/ws/plugins/org.jboss.tools.ws.core/bin/org/jboss/tools/ws/
trunk/ws/plugins/org.jboss.tools.ws.core/bin/org/jboss/tools/ws/core/
trunk/ws/plugins/org.jboss.tools.ws.core/bin/org/jboss/tools/ws/core/Activator.class
trunk/ws/plugins/org.jboss.tools.ws.core/build.properties
trunk/ws/plugins/org.jboss.tools.ws.core/plugin.properties
trunk/ws/plugins/org.jboss.tools.ws.core/plugin.xml
trunk/ws/plugins/org.jboss.tools.ws.core/src/
trunk/ws/plugins/org.jboss.tools.ws.core/src/org/
trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/
trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/
trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/
trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/
trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/Activator.java
Log:
../../qq.log
Added: trunk/ws/plugins/org.jboss.tools.ws.core/.classpath
===================================================================
--- trunk/ws/plugins/org.jboss.tools.ws.core/.classpath (rev 0)
+++ trunk/ws/plugins/org.jboss.tools.ws.core/.classpath 2008-04-18 08:49:52 UTC (rev 7604)
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<classpath>
+ <classpathentry kind="src" path="src"/>
+ <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
+ <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
+ <classpathentry kind="output" path="bin"/>
+</classpath>
Added: trunk/ws/plugins/org.jboss.tools.ws.core/.project
===================================================================
--- trunk/ws/plugins/org.jboss.tools.ws.core/.project (rev 0)
+++ trunk/ws/plugins/org.jboss.tools.ws.core/.project 2008-04-18 08:49:52 UTC (rev 7604)
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.jboss.tools.ws.core</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.jdt.core.javabuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.ManifestBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.SchemaBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.PluginNature</nature>
+ <nature>org.eclipse.jdt.core.javanature</nature>
+ </natures>
+</projectDescription>
Added: trunk/ws/plugins/org.jboss.tools.ws.core/META-INF/MANIFEST.MF
===================================================================
--- trunk/ws/plugins/org.jboss.tools.ws.core/META-INF/MANIFEST.MF (rev 0)
+++ trunk/ws/plugins/org.jboss.tools.ws.core/META-INF/MANIFEST.MF 2008-04-18 08:49:52 UTC (rev 7604)
@@ -0,0 +1,12 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %PLUGIN_NAME
+Bundle-SymbolicName: org.jboss.tools.ws.core;singleton:=true
+Bundle-Version: 1.0.0
+Bundle-Localization: plugin
+Bundle-Activator: org.jboss.tools.ws.core.Activator
+Require-Bundle: org.eclipse.ui,
+ org.eclipse.core.runtime,
+ org.eclipse.wst.common.project.facet.core
+Eclipse-LazyStart: true
+Bundle-Vendor: %PLUGIN_PROVIDER
Added: trunk/ws/plugins/org.jboss.tools.ws.core/bin/org/jboss/tools/ws/core/Activator.class
===================================================================
(Binary files differ)
Property changes on: trunk/ws/plugins/org.jboss.tools.ws.core/bin/org/jboss/tools/ws/core/Activator.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/ws/plugins/org.jboss.tools.ws.core/build.properties
===================================================================
--- trunk/ws/plugins/org.jboss.tools.ws.core/build.properties (rev 0)
+++ trunk/ws/plugins/org.jboss.tools.ws.core/build.properties 2008-04-18 08:49:52 UTC (rev 7604)
@@ -0,0 +1,5 @@
+source.. = src/
+output.. = bin/
+bin.includes = META-INF/,\
+ .,\
+ plugin.xml
Added: trunk/ws/plugins/org.jboss.tools.ws.core/plugin.properties
===================================================================
--- trunk/ws/plugins/org.jboss.tools.ws.core/plugin.properties (rev 0)
+++ trunk/ws/plugins/org.jboss.tools.ws.core/plugin.properties 2008-04-18 08:49:52 UTC (rev 7604)
@@ -0,0 +1,12 @@
+PLUGIN_NAME=JBossWS Core Plug-in
+PLUGIN_PROVIDER=Red Hat, Inc.
+
+JBOSSWS_CATOGERY_LABEL=JBoss Web Services
+JBOSSWS_CATOGERY_DISCRIPTION=Enables Web services generation through the JBoss Web services engine.
+
+JBOSSWS_FACET_CORE_LABEL=JBoss Web Services Core
+JBOSSWS_FACET_CORE_DISCRIPTION=Prepares the project for Web services generation through the JBoss Web services engine.
+
+
+JBOSSWS_FACET_EXT_LABEL=JBoss Web Services Extensions
+JBOSSWS_FACET_EXT_DISCRIPTION=Prepares the project for additional Web services support with the JBoss Web services runtime.
\ No newline at end of file
Added: trunk/ws/plugins/org.jboss.tools.ws.core/plugin.xml
===================================================================
--- trunk/ws/plugins/org.jboss.tools.ws.core/plugin.xml (rev 0)
+++ trunk/ws/plugins/org.jboss.tools.ws.core/plugin.xml 2008-04-18 08:49:52 UTC (rev 7604)
@@ -0,0 +1,50 @@
+<plugin>
+ <extension
+ point="org.eclipse.wst.common.project.facet.core.facets">
+ <category id="jbossws.category">
+ <label>%JBOSSWS_CATOGERY_LABEL</label>
+ <description>%JBOSSWS_CATOGERY_DISCRIPTION</description>
+ </category>
+
+ <project-facet id="jbossws.core">
+ <label>%JBOSSWS_FACET_CORE_LABEL</label>
+ <description>%JBOSSWS_FACET_CORE_DISCRIPTION</description>
+ <member category="jbossws.category "/>
+ </project-facet>
+
+ <project-facet-version facet="jbossws.core" version="1.1">
+ <constraint>
+ <requires facet="jst.web" version="2.2,2.3,2.4,2.5"/>
+ </constraint>
+ <action type="INSTALL">
+ <delegate class=""/>
+ </action>
+<!--
+ <action type="UNINSTALL">
+ <delegate class="org.eclipse.jst.ws.axis2.facet.deligate.Axis2CoreFacetUnInstallDelegate"/>
+ </action>
+-->
+ </project-facet-version>
+<!--
+ <project-facet id="axis2.ext">
+ <label>%JBOSSWS_FACET_EXT_LABEL</label>
+ <description>%JBOSSWS_FACET_EXT_DISCRIPTION</description>
+ <member category="axis2.category" />
+ </project-facet>
+
+ <project-facet-version facet="axis2.ext" version="1.1">
+ <constraint>
+ <requires facet="axis2.core" version="1.1"/>
+ </constraint>
+ <action type="INSTALL">
+ <delegate class="org.eclipse.jst.ws.axis2.facet.deligate.Axis2ExtFacetInstallDelegate"/>
+ </action>
+
+ <action type="UNINSTALL">
+ <delegate class="org.eclipse.jst.ws.axis2.facet.deligate.Axis2ExtFacetUnInstallDelegate"/>
+ </action>
+ </project-facet-version>
+-->
+ </extension>
+
+</plugin>
Added: trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/Activator.java
===================================================================
--- trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/Activator.java (rev 0)
+++ trunk/ws/plugins/org.jboss.tools.ws.core/src/org/jboss/tools/ws/core/Activator.java 2008-04-18 08:49:52 UTC (rev 7604)
@@ -0,0 +1,50 @@
+package org.jboss.tools.ws.core;
+
+import org.eclipse.ui.plugin.AbstractUIPlugin;
+import org.osgi.framework.BundleContext;
+
+/**
+ * The activator class controls the plug-in life cycle
+ */
+public class Activator extends AbstractUIPlugin {
+
+ // The plug-in ID
+ public static final String PLUGIN_ID = "org.jboss.tools.ws.core";
+
+ // The shared instance
+ private static Activator plugin;
+
+ /**
+ * The constructor
+ */
+ public Activator() {
+ }
+
+ /*
+ * (non-Javadoc)
+ * @see org.eclipse.ui.plugin.AbstractUIPlugin#start(org.osgi.framework.BundleContext)
+ */
+ public void start(BundleContext context) throws Exception {
+ super.start(context);
+ plugin = this;
+ }
+
+ /*
+ * (non-Javadoc)
+ * @see org.eclipse.ui.plugin.AbstractUIPlugin#stop(org.osgi.framework.BundleContext)
+ */
+ public void stop(BundleContext context) throws Exception {
+ plugin = null;
+ super.stop(context);
+ }
+
+ /**
+ * Returns the shared instance
+ *
+ * @return the shared instance
+ */
+ public static Activator getDefault() {
+ return plugin;
+ }
+
+}
17 years, 8 months
- 1
- 0