JBoss Tools SVN: r20619 - branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide.
by jbosstools-commits＠lists.jboss.org
Author: scabanovich
Date: 2010-03-03 10:08:57 -0500 (Wed, 03 Mar 2010)
New Revision: 20619
Modified:
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE5920Test.java
Log:
https://jira.jboss.org/jira/browse/JBIDE-5920
Modified: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE5920Test.java
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE5920Test.java 2010-03-03 15:03:40 UTC (rev 20618)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE5920Test.java 2010-03-03 15:08:57 UTC (rev 20619)
@@ -12,6 +12,7 @@
import org.eclipse.core.resources.IFile;
import org.eclipse.core.resources.IProject;
+import org.eclipse.core.resources.ResourcesPlugin;
import org.eclipse.ui.IEditorDescriptor;
import org.eclipse.ui.IEditorInput;
import org.eclipse.ui.IEditorRegistry;
@@ -21,7 +22,6 @@
import org.eclipse.ui.part.FileEditorInput;
import org.jboss.tools.jsf.vpe.jsf.test.JsfAllTests;
import org.jboss.tools.vpe.ui.test.OpenOnUtil;
-import org.jboss.tools.vpe.ui.test.ProjectsLoader;
import org.jboss.tools.vpe.ui.test.VpeTest;
/**
@@ -36,8 +36,8 @@
//test for https://jira.jboss.org/jira/browse/JBIDE-5920
public void testOpenOnInProjectWith2URLPatterns() throws Throwable{
- IProject project = ProjectsLoader.getInstance()
- .getProject(JsfAllTests.IMPORT_TEST_WITH_2_URL_PATTERNS_PROJECT_NAME);
+ IProject project = ResourcesPlugin.getWorkspace().getRoot().getProject(
+ JsfAllTests.IMPORT_TEST_WITH_2_URL_PATTERNS_PROJECT_NAME);
IFile file = (IFile) project.findMember("WebContent/index.jsp"); //$NON-NLS-1$
IEditorInput editorInput = new FileEditorInput(file);
OpenOnUtil.checkOpenOnInEditor(editorInput, getEditorId(file.getName()), 5, 30, "welcome.xhtml"); //$NON-NLS-1$
14 years, 2 months
- 1
- 0
JBoss Tools SVN: r20618 - in branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test: resources/TestWith2URLPatterns and 39 other directories.
by jbosstools-commits＠lists.jboss.org
Author: scabanovich
Date: 2010-03-03 10:03:40 -0500 (Wed, 03 Mar 2010)
New Revision: 20618
Added:
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.classpath
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.project
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/.jsdtscope
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.jdt.core.prefs
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.common.component
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.common.project.facet.core.xml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.jsdt.ui.superType.container
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.jsdt.ui.superType.name
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts-context.css
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts.css
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids-context.css
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids.css
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/layout.css
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/page.css
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset-context.css
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset-fonts-grids.css
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset.css
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/simple.css
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/MANIFEST.MF
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/richfaces-demo/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/richfaces-demo/pom.properties
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/richfaces-demo/pom.xml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/common/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/common/UserBean.class
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/function/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/function/FunctionBean.class
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/mediaOutput/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/mediaOutput/MediaBean.class
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/mediaOutput/MediaData.class
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/mediaOutput/text.swf
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/outputPanel/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/outputPanel/OutputPanelBean.class
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/push/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/push/Choice.class
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/push/ChoicesBean.class
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/faces-config.xml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/commons-beanutils-1.7.0.jar
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/commons-logging-1.1.1.jar
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/core-ui-4.0.0.ALPHA1.jar
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jboss-common-core-2.2.10.GA.jar
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jboss-logging-spi-2.0.5.GA.jar
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jbosscache-core-3.1.0.GA.jar
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jgroups-2.6.7.GA.jar
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jsf-api-2.0.0-SNAPSHOT.jar
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jsf-impl-2.0.0-SNAPSHOT.jar
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jta-1.1.jar
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/log4j-1.2.14.jar
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/richfaces-api-4.0.0.ALPHA1.jar
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/richfaces-impl-4.0.0.ALPHA1.jar
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/slf4j-api-1.5.8.jar
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/slf4j-log4j12-1.5.8.jar
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/web.xml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/images/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/images/ai.gif
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/images/richfaces-banner.png
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/index.jsp
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/message.css
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/messages.css
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/page.css
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/panel.css
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/img/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/img/footer_background.png
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/img/header_background.png
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/img/panel_header.png
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/message.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/messages.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/page.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/panel.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax/ajax.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/button/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/button/usage.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandButton.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandLink.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction/usage.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/link/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/link/usage.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log/usage.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/flashUsage.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/imgUsage.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/compositemessages.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/usage.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push/usage.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/referencedusage.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/usage.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/viewusage.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/script/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/script/swfobject.js
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/includes/
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/includes/navigation.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/main.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/welcome.xhtml
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE5920Test.java
Modified:
branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java
Log:
https://jira.jboss.org/jira/browse/JBIDE-5920
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.classpath
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.classpath (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.classpath 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<classpath>
+ <classpathentry kind="src" path="JavaSource"/>
+ <classpathentry kind="con" path="org.eclipse.jst.j2ee.internal.web.container"/>
+ <classpathentry kind="con" path="org.eclipse.jst.j2ee.internal.module.container"/>
+ <classpathentry kind="con" path="org.eclipse.jst.server.core.container/org.jboss.ide.eclipse.as.core.server.runtime.runtimeTarget/jboss-eap Runtime"/>
+ <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
+ <classpathentry kind="output" path="WebContent/WEB-INF/classes"/>
+</classpath>
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.classpath
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.project
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.project (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.project 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,48 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>TestWith2URLPatterns</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.wst.jsdt.core.javascriptValidator</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.wst.common.project.facet.core.builder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.jdt.core.javabuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.wst.validation.validationbuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.jboss.tools.common.verification.verifybuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.jboss.tools.jst.web.kb.kbbuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.jem.workbench.JavaEMFNature</nature>
+ <nature>org.eclipse.jdt.core.javanature</nature>
+ <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>
+ <nature>org.jboss.tools.jsf.jsfnature</nature>
+ <nature>org.eclipse.wst.common.project.facet.core.nature</nature>
+ <nature>org.eclipse.wst.jsdt.core.jsNature</nature>
+ <nature>org.jboss.tools.jst.web.kb.kbnature</nature>
+ </natures>
+</projectDescription>
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.project
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/.jsdtscope
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/.jsdtscope (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/.jsdtscope 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<classpath>
+ <classpathentry kind="con" path="org.eclipse.wst.jsdt.launching.JRE_CONTAINER"/>
+ <classpathentry kind="con" path="org.eclipse.wst.jsdt.launching.WebProject">
+ <attributes>
+ <attribute name="hide" value="true"/>
+ </attributes>
+ </classpathentry>
+ <classpathentry kind="con" path="org.eclipse.wst.jsdt.launching.baseBrowserLibrary"/>
+ <classpathentry kind="output" path=""/>
+</classpath>
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.jdt.core.prefs
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.jdt.core.prefs (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.jdt.core.prefs 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,7 @@
+#Wed Mar 03 14:38:20 MSK 2010
+eclipse.preferences.version=1
+org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.6
+org.eclipse.jdt.core.compiler.compliance=1.6
+org.eclipse.jdt.core.compiler.problem.assertIdentifier=error
+org.eclipse.jdt.core.compiler.problem.enumIdentifier=error
+org.eclipse.jdt.core.compiler.source=1.6
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.jdt.core.prefs
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.common.component
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.common.component (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.common.component 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project-modules id="moduleCoreId" project-version="1.5.0">
+<wb-module deploy-name="Richfaces-demo-4.0.0.ALPHA1-tomcat6">
+<wb-resource deploy-path="/" source-path="/WebContent"/>
+<property name="context-root" value="Richfaces-demo-4.0.0.ALPHA1-tomcat6"/>
+<property name="java-output-path"/>
+</wb-module>
+</project-modules>
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.common.project.facet.core.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.common.project.facet.core.xml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.common.project.facet.core.xml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<faceted-project>
+ <runtime name="JBoss 4.2 Runtime"/>
+ <fixed facet="jst.java"/>
+ <fixed facet="jst.web"/>
+ <installed facet="jst.java" version="6.0"/>
+ <installed facet="jst.web" version="2.3"/>
+</faceted-project>
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.common.project.facet.core.xml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.jsdt.ui.superType.container
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.jsdt.ui.superType.container (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.jsdt.ui.superType.container 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1 @@
+org.eclipse.wst.jsdt.launching.baseBrowserLibrary
\ No newline at end of file
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.jsdt.ui.superType.name
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.jsdt.ui.superType.name (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.jsdt.ui.superType.name 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1 @@
+Window
\ No newline at end of file
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts-context.css
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts-context.css (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts-context.css 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,46 @@
+/*
+Copyright (c) 2008, Yahoo! Inc. All rights reserved.
+Code licensed under the BSD License:
+http://developer.yahoo.net/yui/license.txt
+version: 3.0.0pr2
+*/
+/**
+ * Percents could work for IE, but for backCompat purposes, we are using keywords.
+ * x-small is for IE6/7 quirks mode.
+ */
+.yui-cssfonts body, .yui-cssfonts {
+ font:13px/1.231 arial,helvetica,clean,sans-serif;
+ *font-size:small; /* for IE */
+ *font:x-small; /* for IE in quirks mode */
+}
+
+/**
+ * Nudge down to get to 13px equivalent for these form elements
+ */
+.yui-cssfonts select,
+.yui-cssfonts input,
+.yui-cssfonts button,
+.yui-cssfonts textarea {
+ font:99% arial,helvetica,clean,sans-serif;
+}
+
+/**
+ * To help tables remember to inherit
+ */
+.yui-cssfonts table {
+ font-size:inherit;
+ font:100%;
+}
+
+/**
+ * Bump up IE to get to 13px equivalent for these fixed-width elements
+ */
+.yui-cssfonts pre,
+.yui-cssfonts code,
+.yui-cssfonts kbd,
+.yui-cssfonts samp,
+.yui-cssfonts tt {
+ font-family:monospace;
+ *font-size:108%;
+ line-height:100%;
+}
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts-context.css
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts.css
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts.css (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts.css 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,46 @@
+/*
+Copyright (c) 2008, Yahoo! Inc. All rights reserved.
+Code licensed under the BSD License:
+http://developer.yahoo.net/yui/license.txt
+version: 3.0.0pr2
+*/
+/**
+ * Percents could work for IE, but for backCompat purposes, we are using keywords.
+ * x-small is for IE6/7 quirks mode.
+ */
+body {
+ font:13px/1.231 arial,helvetica,clean,sans-serif;
+ *font-size:small; /* for IE */
+ *font:x-small; /* for IE in quirks mode */
+}
+
+/**
+ * Nudge down to get to 13px equivalent for these form elements
+ */
+select,
+input,
+button,
+textarea {
+ font:99% arial,helvetica,clean,sans-serif;
+}
+
+/**
+ * To help tables remember to inherit
+ */
+table {
+ font-size:inherit;
+ font:100%;
+}
+
+/**
+ * Bump up IE to get to 13px equivalent for these fixed-width elements
+ */
+pre,
+code,
+kbd,
+samp,
+tt {
+ font-family:monospace;
+ *font-size:108%;
+ line-height:100%;
+}
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts.css
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids-context.css
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids-context.css (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids-context.css 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,490 @@
+/*
+Copyright (c) 2008, Yahoo! Inc. All rights reserved.
+Code licensed under the BSD License:
+http://developer.yahoo.net/yui/license.txt
+version: 3.0.0pr2
+*/
+/*
+*
+* The YUI CSS Foundation uses the *property and _property CSS filter
+* techniques to shield a value from A-grade browsers [1] other than
+* IE6 & IE7 (*property) and IE6 (_property)
+*
+/
+Section: General Rules
+*/
+.yui-cssgrids body {
+ /* center the page - removed (SS)*/
+ /* text-align: center; */
+ margin-left: auto;
+ margin-right: auto;
+}
+/*
+Section: Page Width Rules (#doc, #doc2, #doc3, #doc4)
+*/
+/*
+Subsection: General
+*/
+.yui-cssgrids .yui-d0, /* 100% */
+.yui-cssgrids .yui-d1, /* 750px */
+.yui-cssgrids .yui-d1f, /* 750px fixed */
+.yui-cssgrids .yui-d2, /* 950px */
+.yui-cssgrids .yui-d2f, /* 950px fixed */
+.yui-cssgrids .yui-d3, /* 974px */
+.yui-cssgrids .yui-d3f { /* 974px fixed */
+ margin: auto;
+ text-align: left;
+ width: 57.69em;
+ *width: 56.25em; /* doc1*/
+}
+
+.yui-cssgrids .yui-t1,
+.yui-cssgrids .yui-t2,
+.yui-cssgrids .yui-t3,
+.yui-cssgrids .yui-t4,
+.yui-cssgrids .yui-t5,
+.yui-cssgrids .yui-t6 {
+ margin: auto;
+ text-align: left;
+ width: 100%;
+}
+
+/*
+Subsection: 100% (doc)
+*/
+.yui-cssgrids .yui-d0 {
+ /* Left and Right margins are not a structural part of Grids. Without them Grids
+ works fine, but content bleeds to the very edge of the document, which often
+ impairs readability and usability. They are
+ provided because they prevent the content from "bleeding" into the browser's chrome.*/
+ margin: auto 10px;
+ width: auto;
+}
+.yui-cssgrids .yui-d0f {
+ width: 100%;
+}
+
+/*
+Subsection: 950 Centered (doc2)
+*/
+.yui-cssgrids .yui-d2 {
+ width: 73.076em;
+ *width: 71.25em;
+}
+.yui-cssgrids .yui-d2f {
+ width: 950px;
+}
+/*
+Subsection: 974 Centered (doc3)
+*/
+.yui-cssgrids .yui-d3 {
+ width: 74.923em;
+ *width: 73.05em;
+}
+.yui-cssgrids .yui-d3f {
+ width: 974px;
+}
+/*
+Section: Preset Template Rules (.yui-t[1-6])
+*/
+/*
+Subsection: General
+*/
+
+/* to preserve source-order independence for Gecko without breaking IE */
+.yui-cssgrids .yui-b {
+ position: relative;
+}
+.yui-cssgrids .yui-b {
+ _position: static;
+}
+.yui-cssgrids .yui-main .yui-b {
+ position: static;
+}
+.yui-cssgrids .yui-main {
+ width: 100%;
+}
+.yui-cssgrids .yui-t1 .yui-main,
+.yui-cssgrids .yui-t2 .yui-main,
+.yui-cssgrids .yui-t3 .yui-main {
+ float: right;
+ /* IE: preserve layout at narrow widths */
+ margin-left: -25em;
+}
+.yui-cssgrids .yui-t4 .yui-main,
+.yui-cssgrids .yui-t5 .yui-main,
+.yui-cssgrids .yui-t6 .yui-main {
+ float: left;
+ /* IE: preserve layout at narrow widths */
+ margin-right: -25em;
+}
+
+/* Subsection: For Specific Template Presets */
+
+/**
+* Nudge down to get to 13px equivalent for these form elements
+*/
+
+/*
+TODO Create t1-6's that are based on fixed widths
+*/
+/* t1 narrow block = left, equivalent of 160px */
+.yui-cssgrids .yui-t1 .yui-b {
+ float: left;
+ width: 12.30769em;
+ *width: 12.00em;
+}
+.yui-cssgrids .yui-t1 .yui-main .yui-b {
+ margin-left: 13.30769em;
+ *margin-left:12.975em;
+}
+/* t2 narrow block = left, equivalent of 180px */
+.yui-cssgrids .yui-t2 .yui-b {
+ float: left;
+ width: 13.84615em;
+ *width: 13.50em;
+}
+.yui-cssgrids .yui-t2 .yui-main .yui-b {
+ margin-left: 14.84615em;
+ *margin-left: 14.475em;
+}
+/* t3 narrow block = left, equivalent of 300px */
+.yui-cssgrids .yui-t3 .yui-b {
+ float: left;
+ width: 23.0769em;
+ *width: 22.50em;
+}
+.yui-cssgrids .yui-t3 .yui-main .yui-b {
+ margin-left: 24.0769em;
+ *margin-left: 23.475em;
+}
+/* t4 narrow block = right, equivalent of 180px */
+.yui-cssgrids .yui-t4 .yui-b {
+ float: right;
+ width: 13.8456em;
+ *width: 13.50em;
+}
+.yui-cssgrids .yui-t4 .yui-main .yui-b {
+ margin-right: 14.8456em;
+ *margin-right: 14.475em;
+}
+/* t5 narrow block = right, equivalent of 240px */
+.yui-cssgrids .yui-t5 .yui-b {
+ float: right;
+ width: 18.4615em;
+ *width: 18.00em;
+}
+.yui-cssgrids .yui-t5 .yui-main .yui-b {
+ margin-right: 19.4615em;
+ *margin-right: 18.975em;
+}
+/* t6 narrow block = equivalent of 300px */
+.yui-cssgrids .yui-t6 .yui-b {
+ float: right;
+ width: 23.0769em;
+ *width: 22.50em;
+}
+.yui-cssgrids .yui-t6 .yui-main .yui-b {
+ margin-right: 24.0769em;
+ *margin-right: 23.475em;
+}
+
+.yui-cssgrids .yui-main .yui-b {
+ float: none;
+ width: auto;
+}
+
+/*
+Section: Grids and Nesting Grids
+*/
+
+/*
+Subsection: Children generally take half the available space
+*/
+
+.yui-cssgrids .yui-gb .yui-u,
+.yui-cssgrids .yui-g .yui-gb .yui-u,
+.yui-cssgrids .yui-gb .yui-g,
+.yui-cssgrids .yui-gb .yui-gb,
+.yui-cssgrids .yui-gb .yui-gc,
+.yui-cssgrids .yui-gb .yui-gd,
+.yui-cssgrids .yui-gb .yui-ge,
+.yui-cssgrids .yui-gb .yui-gf,
+.yui-cssgrids .yui-gc .yui-u,
+.yui-cssgrids .yui-gc .yui-g,
+.yui-cssgrids .yui-gd .yui-u {
+ float: left;
+}
+
+/*Float units (and sub grids) to the right */
+.yui-cssgrids .yui-g .yui-u,
+.yui-cssgrids .yui-g .yui-g,
+.yui-cssgrids .yui-g .yui-gb,
+.yui-cssgrids .yui-g .yui-gc,
+.yui-cssgrids .yui-g .yui-gd,
+.yui-cssgrids .yui-g .yui-ge,
+.yui-cssgrids .yui-g .yui-gf,
+.yui-cssgrids .yui-gc .yui-u,
+.yui-cssgrids .yui-gd .yui-g,
+.yui-cssgrids .yui-g .yui-gc .yui-u,
+.yui-cssgrids .yui-ge .yui-u,
+.yui-cssgrids .yui-ge .yui-g,
+.yui-cssgrids .yui-gf .yui-g,
+.yui-cssgrids .yui-gf .yui-u {
+ float: right;
+}
+
+/*Float units (and sub grids) to the left */
+.yui-cssgrids .yui-g div.first,
+.yui-cssgrids .yui-gb div.first,
+.yui-cssgrids .yui-gc div.first,
+.yui-cssgrids .yui-gd div.first,
+.yui-cssgrids .yui-ge div.first,
+.yui-cssgrids .yui-gf div.first,
+.yui-cssgrids .yui-g .yui-gc div.first,
+.yui-cssgrids .yui-g .yui-ge div.first,
+.yui-cssgrids .yui-gc div.first div.first {
+ float: left;
+}
+
+.yui-cssgrids .yui-g .yui-u,
+.yui-cssgrids .yui-g .yui-g,
+.yui-cssgrids .yui-g .yui-gb,
+.yui-cssgrids .yui-g .yui-gc,
+.yui-cssgrids .yui-g .yui-gd,
+.yui-cssgrids .yui-g .yui-ge,
+.yui-cssgrids .yui-g .yui-gf {
+ width: 49.1%;
+}
+
+.yui-cssgrids .yui-gb .yui-u,
+.yui-cssgrids .yui-g .yui-gb .yui-u,
+.yui-cssgrids .yui-gb .yui-g,
+.yui-cssgrids .yui-gb .yui-gb,
+.yui-cssgrids .yui-gb .yui-gc,
+.yui-cssgrids .yui-gb .yui-gd,
+.yui-cssgrids .yui-gb .yui-ge,
+.yui-cssgrids .yui-gb .yui-gf,
+.yui-cssgrids .yui-gc .yui-u,
+.yui-cssgrids .yui-gc .yui-g,
+.yui-cssgrids .yui-gd .yui-u {
+ width: 32%;
+ margin-left: 2.0%;
+}
+
+/* Give IE some extra breathing room for 1/3-based rounding issues */
+.yui-cssgrids .yui-gb .yui-u {
+ *width: 31.8%;
+ *margin-left: 1.9%;
+}
+
+.yui-cssgrids .yui-gc div.first,
+.yui-cssgrids .yui-gd .yui-u {
+ width: 66%;
+ _width: 65.7%;
+}
+.yui-cssgrids .yui-gd div.first {
+ width: 32%;
+ _width: 31.5%;
+}
+
+.yui-cssgrids .yui-ge div.first,
+.yui-cssgrids .yui-gf .yui-u {
+ width: 74.2%;
+ _width: 74%;
+}
+
+.yui-cssgrids .yui-ge .yui-u,
+.yui-cssgrids .yui-gf div.first {
+ width: 24%;
+ _width: 23.8%;
+}
+
+.yui-cssgrids .yui-g .yui-gb div.first,
+.yui-cssgrids .yui-gb div.first,
+.yui-cssgrids .yui-gc div.first,
+.yui-cssgrids .yui-gd div.first {
+ margin-left: 0;
+}
+
+/*
+Section: Deep Nesting
+*/
+.yui-cssgrids .yui-g .yui-g .yui-u,
+.yui-cssgrids .yui-gb .yui-g .yui-u,
+.yui-cssgrids .yui-gc .yui-g .yui-u,
+.yui-cssgrids .yui-gd .yui-g .yui-u,
+.yui-cssgrids .yui-ge .yui-g .yui-u,
+.yui-cssgrids .yui-gf .yui-g .yui-u {
+ width: 49%;
+ *width: 48.1%;
+ *margin-left: 0;
+}
+
+.yui-cssgrids .yui-g .yui-gb div.first,
+.yui-cssgrids .yui-gb .yui-gb div.first {
+ *margin-right: 0;
+ *width: 32%;
+ _width: 31.7%;
+}
+
+.yui-cssgrids .yui-g .yui-gc div.first,
+.yui-cssgrids .yui-gd .yui-g {
+ width: 66%;
+}
+
+.yui-cssgrids .yui-gb .yui-g div.first {
+ *margin-right: 4%;
+ _margin-right: 1.3%;
+}
+
+.yui-cssgrids .yui-gb .yui-gc div.first,
+.yui-cssgrids .yui-gb .yui-gd div.first {
+ *margin-right: 0;
+}
+
+.yui-cssgrids .yui-gb .yui-gb .yui-u,
+.yui-cssgrids .yui-gb .yui-gc .yui-u {
+ *margin-left: 1.8%;
+ _margin-left: 4%;
+}
+
+.yui-cssgrids .yui-g .yui-gb .yui-u {
+ _margin-left: 1.0%;
+}
+
+.yui-cssgrids .yui-gb .yui-gd .yui-u {
+ *width: 66%;
+ _width: 61.2%;
+}
+.yui-cssgrids .yui-gb .yui-gd div.first {
+ *width: 31%;
+ _width: 29.5%;
+}
+
+.yui-cssgrids .yui-g .yui-gc .yui-u,
+.yui-cssgrids .yui-gb .yui-gc .yui-u {
+ width: 32%;
+ _float: right;
+ margin-right: 0;
+ _margin-left: 0;
+}
+.yui-cssgrids .yui-gb .yui-gc div.first {
+ width: 66%;
+ *float: left;
+ *margin-left: 0;
+}
+
+.yui-cssgrids .yui-gb .yui-ge .yui-u,
+.yui-cssgrids .yui-gb .yui-gf .yui-u {
+ margin: 0;
+}
+
+.yui-cssgrids .yui-gb .yui-gb .yui-u {
+ _margin-left: .7%;
+}
+
+.yui-cssgrids .yui-gb .yui-g div.first,
+.yui-cssgrids .yui-gb .yui-gb div.first {
+ *margin-left:0;
+}
+
+.yui-cssgrids .yui-gc .yui-g .yui-u,
+.yui-cssgrids .yui-gd .yui-g .yui-u {
+ *width: 48.1%;
+ *margin-left: 0;
+}
+
+.yui-cssgrids .yui-gb .yui-gd div.first {
+ width: 32%;
+}
+.yui-cssgrids .yui-g .yui-gd div.first {
+ _width: 29.9%;
+}
+
+.yui-cssgrids .yui-ge .yui-g {
+ width: 24%;
+}
+.yui-cssgrids .yui-gf .yui-g {
+ width: 74.2%;
+}
+
+.yui-cssgrids .yui-gb .yui-ge div.yui-u,
+.yui-cssgrids .yui-gb .yui-gf div.yui-u {
+ float: right;
+}
+.yui-cssgrids .yui-gb .yui-ge div.first,
+.yui-cssgrids .yui-gb .yui-gf div.first {
+ float: left;
+}
+
+/* Width Accommodation for Nested Contexts */
+.yui-cssgrids .yui-gb .yui-ge .yui-u,
+.yui-cssgrids .yui-gb .yui-gf div.first {
+ *width: 24%;
+ _width: 20%;
+}
+
+/* Width Accommodation for Nested Contexts */
+
+.yui-cssgrids .yui-gc .yui-gf .yui-u {
+ width: 74%;
+ _width: 73%;
+}
+
+.yui-cssgrids .yui-gc .yui-gf div.first {
+ width: 24%;
+}
+
+.yui-cssgrids .yui-gb .yui-ge div.first,
+.yui-cssgrids .yui-gb .yui-gf .yui-u {
+ *width: 73.5%;
+ _width: 65.5%;
+}
+
+/* Patch for GD within GE */
+.yui-cssgrids .yui-ge div.first .yui-gd .yui-u {
+ width: 65%;
+}
+.yui-cssgrids .yui-ge div.first .yui-gd div.first {
+ width: 32%;
+}
+
+/*
+Section: Clearing. zoom for IE, :after for others
+*/
+
+.yui-cssgrids #bd:after,
+.yui-cssgrids .yui-g:after,
+.yui-cssgrids .yui-gb:after,
+.yui-cssgrids .yui-gc:after,
+.yui-cssgrids .yui-gd:after,
+.yui-cssgrids .yui-ge:after,
+.yui-cssgrids .yui-gf:after,
+.yui-cssgrids .yui-t1:after,
+.yui-cssgrids .yui-t2:after,
+.yui-cssgrids .yui-t3:after,
+.yui-cssgrids .yui-t4:after,
+.yui-cssgrids .yui-t5:after,
+.yui-cssgrids .yui-t6:after {
+ content: ".";
+ display: block;
+ height: 0;
+ clear: both;
+ visibility: hidden;
+}
+.yui-cssgrids #bd,
+.yui-cssgrids .yui-g,
+.yui-cssgrids .yui-gb,
+.yui-cssgrids .yui-gc,
+.yui-cssgrids .yui-gd,
+.yui-cssgrids .yui-ge,
+.yui-cssgrids .yui-gf,
+.yui-cssgrids .yui-t1,
+.yui-cssgrids .yui-t2,
+.yui-cssgrids .yui-t3,
+.yui-cssgrids .yui-t4,
+.yui-cssgrids .yui-t5,
+.yui-cssgrids .yui-t6 {
+ zoom: 1;
+}
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids-context.css
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids.css
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids.css (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids.css 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,480 @@
+/*
+Copyright (c) 2008, Yahoo! Inc. All rights reserved.
+Code licensed under the BSD License:
+http://developer.yahoo.net/yui/license.txt
+version: 3.0.0pr2
+*/
+/*
+*
+* The YUI CSS Foundation uses the *property and _property CSS filter
+* techniques to shield a value from A-grade browsers [1] other than
+* IE6 & IE7 (*property) and IE6 (_property)
+*
+/
+Section: General Rules
+*/
+body {
+ /* center the page - removed (SS)*/
+ /*text-align: center; */
+ margin-left: auto;
+ margin-right: auto;
+}
+/*
+Section: Page Width Rules (#doc, #doc2, #doc3, #doc4)
+*/
+/*
+Subsection: General
+*/
+.yui-d0, /* 100% */
+.yui-d1, /* 750px */
+.yui-d1f, /* 750px fixed */
+.yui-d2, /* 950px */
+.yui-d2f, /* 950px fixed */
+.yui-d3, /* 974px */
+.yui-d3f { /* 974px fixed */
+ margin: auto;
+ text-align: left;
+ width: 57.69em;
+ *width: 56.25em; /* doc1*/
+}
+
+.yui-t1,
+.yui-t2,
+.yui-t3,
+.yui-t4,
+.yui-t5,
+.yui-t6 {
+ margin: auto;
+ text-align: left;
+ width: 100%;
+}
+
+/*
+Subsection: 100% (doc)
+*/
+.yui-d0 {
+ /* Left and Right margins are not a structural part of Grids. Without them Grids
+ works fine, but content bleeds to the very edge of the document, which often
+ impairs readability and usability. They are
+ provided because they prevent the content from "bleeding" into the browser's chrome.*/
+ margin: auto 10px;
+ width: auto;
+}
+.yui-d0f {
+ width: 100%;
+}
+
+/*
+Subsection: 950 Centered (doc2)
+*/
+.yui-d2 {
+ width: 73.076em;
+ *width: 71.25em;
+}
+.yui-d2f {
+ width: 950px;
+}
+/*
+Subsection: 974 Centered (doc3)
+*/
+.yui-d3 {
+ width: 74.923em;
+ *width: 73.05em;
+}
+.yui-d3f {
+ width: 974px;
+}
+/*
+Section: Preset Template Rules (.yui-t[1-6])
+*/
+/*
+Subsection: General
+*/
+
+/* to preserve source-order independence for Gecko without breaking IE */
+.yui-b {
+ position: relative;
+}
+.yui-b {
+ _position: static;
+}
+.yui-main .yui-b {
+ position: static;
+}
+.yui-main {
+ width: 100%;
+}
+.yui-t1 .yui-main,
+.yui-t2 .yui-main,
+.yui-t3 .yui-main {
+ float: right;
+ /* IE: preserve layout at narrow widths */
+ margin-left: -25em;
+}
+.yui-t4 .yui-main,
+.yui-t5 .yui-main,
+.yui-t6 .yui-main {
+ float: left;
+ /* IE: preserve layout at narrow widths */
+ margin-right: -25em;
+}
+
+/* Subsection: For Specific Template Presets */
+
+/**
+* Nudge down to get to 13px equivalent for these form elements
+*/
+
+/*
+TODO Create t1-6's that are based on fixed widths
+*/
+/* t1 narrow block = left, equivalent of 160px */
+.yui-t1 .yui-b {
+ float: left;
+ width: 12.30769em;
+ *width: 12.00em;
+}
+.yui-t1 .yui-main .yui-b {
+ margin-left: 13.30769em;
+ *margin-left:12.975em;
+}
+/* t2 narrow block = left, equivalent of 180px */
+.yui-t2 .yui-b {
+ float: left;
+ width: 13.84615em;
+ *width: 13.50em;
+}
+.yui-t2 .yui-main .yui-b {
+ margin-left: 14.84615em;
+ *margin-left: 14.475em;
+}
+/* t3 narrow block = left, equivalent of 300px */
+.yui-t3 .yui-b {
+ float: left;
+ width: 23.0769em;
+ *width: 22.50em;
+}
+.yui-t3 .yui-main .yui-b {
+ margin-left: 24.0769em;
+ *margin-left: 23.475em;
+}
+/* t4 narrow block = right, equivalent of 180px */
+.yui-t4 .yui-b {
+ float: right;
+ width: 13.8456em;
+ *width: 13.50em;
+}
+.yui-t4 .yui-main .yui-b {
+ margin-right: 14.8456em;
+ *margin-right: 14.475em;
+}
+/* t5 narrow block = right, equivalent of 240px */
+.yui-t5 .yui-b {
+ float: right;
+ width: 18.4615em;
+ *width: 18.00em;
+}
+.yui-t5 .yui-main .yui-b {
+ margin-right: 19.4615em;
+ *margin-right: 18.975em;
+}
+/* t6 narrow block = equivalent of 300px */
+.yui-t6 .yui-b {
+ float: right;
+ width: 23.0769em;
+ *width: 22.50em;
+}
+.yui-t6 .yui-main .yui-b {
+ margin-right: 24.0769em;
+ *margin-right: 23.475em;
+}
+
+.yui-main .yui-b {
+ float: none;
+ width: auto;
+}
+
+/*
+Section: Grids and Nesting Grids
+*/
+
+/*
+Subsection: Children generally take half the available space
+*/
+
+.yui-gb .yui-u,
+.yui-g .yui-gb .yui-u,
+.yui-gb .yui-g,
+.yui-gb .yui-gb,
+.yui-gb .yui-gc,
+.yui-gb .yui-gd,
+.yui-gb .yui-ge,
+.yui-gb .yui-gf,
+.yui-gc .yui-u,
+.yui-gc .yui-g,
+.yui-gd .yui-u {
+ float: left;
+}
+
+/*Float units (and sub grids) to the right */
+.yui-g .yui-u,
+.yui-g .yui-g,
+.yui-g .yui-gb,
+.yui-g .yui-gc,
+.yui-g .yui-gd,
+.yui-g .yui-ge,
+.yui-g .yui-gf,
+.yui-gc .yui-u,
+.yui-gd .yui-g,
+.yui-g .yui-gc .yui-u,
+.yui-ge .yui-u,
+.yui-ge .yui-g,
+.yui-gf .yui-g,
+.yui-gf .yui-u {
+ float: right;
+}
+
+/*Float units (and sub grids) to the left */
+.yui-g div.first,
+.yui-gb div.first,
+.yui-gc div.first,
+.yui-gd div.first,
+.yui-ge div.first,
+.yui-gf div.first,
+.yui-g .yui-gc div.first,
+.yui-g .yui-ge div.first,
+.yui-gc div.first div.first {
+ float: left;
+}
+
+.yui-g .yui-u,
+.yui-g .yui-g,
+.yui-g .yui-gb,
+.yui-g .yui-gc,
+.yui-g .yui-gd,
+.yui-g .yui-ge,
+.yui-g .yui-gf {
+ width: 49.1%;
+}
+
+.yui-gb .yui-u,
+.yui-g .yui-gb .yui-u,
+.yui-gb .yui-g,
+.yui-gb .yui-gb,
+.yui-gb .yui-gc,
+.yui-gb .yui-gd,
+.yui-gb .yui-ge,
+.yui-gb .yui-gf,
+.yui-gc .yui-u,
+.yui-gc .yui-g,
+.yui-gd .yui-u {
+ width: 32%;
+ margin-left: 2.0%;
+}
+
+/* Give IE some extra breathing room for 1/3-based rounding issues */
+.yui-gb .yui-u {
+ *width: 31.8%;
+ *margin-left: 1.9%;
+}
+
+.yui-gc div.first,
+.yui-gd .yui-u {
+ width: 66%;
+ _width: 65.7%;
+}
+.yui-gd div.first {
+ width: 32%;
+ _width: 31.5%;
+}
+
+.yui-ge div.first,
+.yui-gf .yui-u {
+ width: 74.2%;
+ _width: 74%;
+}
+
+.yui-ge .yui-u,
+.yui-gf div.first {
+ width: 24%;
+ _width: 23.8%;
+}
+
+.yui-g .yui-gb div.first,
+.yui-gb div.first,
+.yui-gc div.first,
+.yui-gd div.first {
+ margin-left: 0;
+}
+
+/*
+Section: Deep Nesting
+*/
+.yui-g .yui-g .yui-u,
+.yui-gb .yui-g .yui-u,
+.yui-gc .yui-g .yui-u,
+.yui-gd .yui-g .yui-u,
+.yui-ge .yui-g .yui-u,
+.yui-gf .yui-g .yui-u {
+ width: 49%;
+ *width: 48.1%;
+ *margin-left: 0;
+}
+
+.yui-g .yui-gb div.first,
+.yui-gb .yui-gb div.first {
+ *margin-right: 0;
+ *width: 32%;
+ _width: 31.7%;
+}
+
+.yui-g .yui-gc div.first,
+.yui-gd .yui-g {
+ width: 66%;
+}
+
+.yui-gb .yui-g div.first {
+ *margin-right: 4%;
+ _margin-right: 1.3%;
+}
+
+.yui-gb .yui-gc div.first,
+.yui-gb .yui-gd div.first {
+ *margin-right: 0;
+}
+
+.yui-gb .yui-gb .yui-u,
+.yui-gb .yui-gc .yui-u {
+ *margin-left: 1.8%;
+ _margin-left: 4%;
+}
+
+.yui-g .yui-gb .yui-u {
+ _margin-left: 1.0%;
+}
+
+.yui-gb .yui-gd .yui-u {
+ *width: 66%;
+ _width: 61.2%;
+}
+.yui-gb .yui-gd div.first {
+ *width: 31%;
+ _width: 29.5%;
+}
+
+.yui-g .yui-gc .yui-u,
+.yui-gb .yui-gc .yui-u {
+ width: 32%;
+ _float: right;
+ margin-right: 0;
+ _margin-left: 0;
+}
+.yui-gb .yui-gc div.first {
+ width: 66%;
+ *float: left;
+ *margin-left: 0;
+}
+
+.yui-gb .yui-ge .yui-u,
+.yui-gb .yui-gf .yui-u {
+ margin: 0;
+}
+
+.yui-gb .yui-gb .yui-u {
+ _margin-left: .7%;
+}
+
+.yui-gb .yui-g div.first,
+.yui-gb .yui-gb div.first {
+ *margin-left:0;
+}
+
+.yui-gc .yui-g .yui-u,
+.yui-gd .yui-g .yui-u {
+ *width: 48.1%;
+ *margin-left: 0;
+}
+
+.yui-gb .yui-gd div.first {
+ width: 32%;
+}
+.yui-g .yui-gd div.first {
+ _width: 29.9%;
+}
+
+.yui-ge .yui-g {
+ width: 24%;
+}
+.yui-gf .yui-g {
+ width: 74.2%;
+}
+
+.yui-gb .yui-ge div.yui-u,
+.yui-gb .yui-gf div.yui-u {
+ float: right;
+}
+.yui-gb .yui-ge div.first,
+.yui-gb .yui-gf div.first {
+ float: left;
+}
+
+/* Width Accommodation for Nested Contexts */
+.yui-gb .yui-ge .yui-u,
+.yui-gb .yui-gf div.first {
+ *width: 24%;
+ _width: 20%;
+}
+
+/* Width Accommodation for Nested Contexts */
+.yui-gb .yui-ge div.first,
+.yui-gb .yui-gf .yui-u {
+ *width: 73.5%;
+ _width: 65.5%;
+}
+
+/* Patch for GD within GE */
+.yui-ge div.first .yui-gd .yui-u {
+ width: 65%;
+}
+.yui-ge div.first .yui-gd div.first {
+ width: 32%;
+}
+
+/*
+Section: Clearing. zoom for IE, :after for others
+*/
+
+#bd:after,
+.yui-g:after,
+.yui-gb:after,
+.yui-gc:after,
+.yui-gd:after,
+.yui-ge:after,
+.yui-gf:after,
+.yui-t1:after,
+.yui-t2:after,
+.yui-t3:after,
+.yui-t4:after,
+.yui-t5:after,
+.yui-t6:after {
+ content: ".";
+ display: block;
+ height: 0;
+ clear: both;
+ visibility: hidden;
+}
+#bd,
+.yui-g,
+.yui-gb,
+.yui-gc,
+.yui-gd,
+.yui-ge,
+.yui-gf,
+.yui-t1,
+.yui-t2,
+.yui-t3,
+.yui-t4,
+.yui-t5,
+.yui-t6 {
+ zoom: 1;
+}
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids.css
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/layout.css
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/layout.css (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/layout.css 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,285 @@
+/*
+Copyright (c) 2008, Yahoo! Inc. All rights reserved.
+Code licensed under the BSD License:
+http://developer.yahoo.net/yui/license.txt
+version: 3.0.0pr2
+*/
+/*
+*
+* The YUI CSS Foundation uses the *property and _property CSS filter
+* techniques to shield a value from A-grade browsers [1] other than
+* IE6 & IE7 (*property) and IE6 (_property)
+*
+
+/*
+Section: Grids and Nesting Grids
+*/
+
+/*
+Subsection: Children generally take half the available space
+*/
+
+.yui-gb .yui-u,
+.yui-g .yui-gb .yui-u,
+.yui-gb .yui-g,
+.yui-gb .yui-gb,
+.yui-gb .yui-gc,
+.yui-gb .yui-gd,
+.yui-gb .yui-ge,
+.yui-gb .yui-gf,
+.yui-gc .yui-u,
+.yui-gc .yui-g,
+.yui-gd .yui-u {
+ float: left;
+}
+
+/*Float units (and sub grids) to the right */
+.yui-g .yui-u,
+.yui-g .yui-g,
+.yui-g .yui-gb,
+.yui-g .yui-gc,
+.yui-g .yui-gd,
+.yui-g .yui-ge,
+.yui-g .yui-gf,
+.yui-gc .yui-u,
+.yui-gd .yui-g,
+.yui-g .yui-gc .yui-u,
+.yui-ge .yui-u,
+.yui-ge .yui-g,
+.yui-gf .yui-g,
+.yui-gf .yui-u {
+ float: right;
+}
+
+/*Float units (and sub grids) to the left */
+.yui-g div.first,
+.yui-gb div.first,
+.yui-gc div.first,
+.yui-gd div.first,
+.yui-ge div.first,
+.yui-gf div.first,
+.yui-g .yui-gc div.first,
+.yui-g .yui-ge div.first,
+.yui-gc div.first div.first {
+ float: left;
+}
+
+.yui-g .yui-u,
+.yui-g .yui-g,
+.yui-g .yui-gb,
+.yui-g .yui-gc,
+.yui-g .yui-gd,
+.yui-g .yui-ge,
+.yui-g .yui-gf {
+ width: 49.1%;
+}
+
+.yui-gb .yui-u,
+.yui-g .yui-gb .yui-u,
+.yui-gb .yui-g,
+.yui-gb .yui-gb,
+.yui-gb .yui-gc,
+.yui-gb .yui-gd,
+.yui-gb .yui-ge,
+.yui-gb .yui-gf,
+.yui-gc .yui-u,
+.yui-gc .yui-g,
+.yui-gd .yui-u {
+ width: 32%;
+ margin-left: 2.0%;
+}
+
+/* Give IE some extra breathing room for 1/3-based rounding issues */
+.yui-gb .yui-u {
+ *width: 31.8%;
+ *margin-left: 1.9%;
+}
+
+.yui-gc div.first,
+.yui-gd .yui-u {
+ width: 66%;
+ _width: 65.7%;
+}
+.yui-gd div.first {
+ width: 32%;
+ _width: 31.5%;
+}
+
+.yui-ge div.first,
+.yui-gf .yui-u {
+ width: 74.2%;
+ _width: 74%;
+}
+
+.yui-ge .yui-u,
+.yui-gf div.first {
+ width: 24%;
+ _width: 23.8%;
+}
+
+.yui-g .yui-gb div.first,
+.yui-gb div.first,
+.yui-gc div.first,
+.yui-gd div.first {
+ margin-left: 0;
+}
+
+/*
+Section: Deep Nesting
+*/
+.yui-g .yui-g .yui-u,
+.yui-gb .yui-g .yui-u,
+.yui-gc .yui-g .yui-u,
+.yui-gd .yui-g .yui-u,
+.yui-ge .yui-g .yui-u,
+.yui-gf .yui-g .yui-u {
+ width: 49%;
+ *width: 48.1%;
+ *margin-left: 0;
+}
+
+.yui-g .yui-gb div.first,
+.yui-gb .yui-gb div.first {
+ *margin-right: 0;
+ *width: 32%;
+ _width: 31.7%;
+}
+
+.yui-g .yui-gc div.first,
+.yui-gd .yui-g {
+ width: 66%;
+}
+
+.yui-gb .yui-g div.first {
+ *margin-right: 4%;
+ _margin-right: 1.3%;
+}
+
+.yui-gb .yui-gc div.first,
+.yui-gb .yui-gd div.first {
+ *margin-right: 0;
+}
+
+.yui-gb .yui-gb .yui-u,
+.yui-gb .yui-gc .yui-u {
+ *margin-left: 1.8%;
+ _margin-left: 4%;
+}
+
+.yui-g .yui-gb .yui-u {
+ _margin-left: 1.0%;
+}
+
+.yui-gb .yui-gd .yui-u {
+ *width: 66%;
+ _width: 61.2%;
+}
+.yui-gb .yui-gd div.first {
+ *width: 31%;
+ _width: 29.5%;
+}
+
+.yui-g .yui-gc .yui-u,
+.yui-gb .yui-gc .yui-u {
+ width: 32%;
+ _float: right;
+ margin-right: 0;
+ _margin-left: 0;
+}
+.yui-gb .yui-gc div.first {
+ width: 66%;
+ *float: left;
+ *margin-left: 0;
+}
+
+.yui-gb .yui-ge .yui-u,
+.yui-gb .yui-gf .yui-u {
+ margin: 0;
+}
+
+.yui-gb .yui-gb .yui-u {
+ _margin-left: .7%;
+}
+
+.yui-gb .yui-g div.first,
+.yui-gb .yui-gb div.first {
+ *margin-left:0;
+}
+
+.yui-gc .yui-g .yui-u,
+.yui-gd .yui-g .yui-u {
+ *width: 48.1%;
+ *margin-left: 0;
+}
+
+.yui-gb .yui-gd div.first {
+ width: 32%;
+}
+.yui-g .yui-gd div.first {
+ _width: 29.9%;
+}
+
+.yui-ge .yui-g {
+ width: 24%;
+}
+.yui-gf .yui-g {
+ width: 74.2%;
+}
+
+.yui-gb .yui-ge div.yui-u,
+.yui-gb .yui-gf div.yui-u {
+ float: right;
+}
+.yui-gb .yui-ge div.first,
+.yui-gb .yui-gf div.first {
+ float: left;
+}
+
+/* Width Accommodation for Nested Contexts */
+.yui-gb .yui-ge .yui-u,
+.yui-gb .yui-gf div.first {
+ *width: 24%;
+ _width: 20%;
+}
+
+/* Width Accommodation for Nested Contexts */
+.yui-gb .yui-ge div.first,
+.yui-gb .yui-gf .yui-u {
+ *width: 73.5%;
+ _width: 65.5%;
+}
+
+/* Patch for GD within GE */
+.yui-ge div.first .yui-gd .yui-u {
+ width: 65%;
+}
+.yui-ge div.first .yui-gd div.first {
+ width: 32%;
+}
+
+/*
+Section: Clearing. zoom for IE, :after for others
+*/
+
+#bd:after,
+.yui-g:after,
+.yui-gb:after,
+.yui-gc:after,
+.yui-gd:after,
+.yui-ge:after,
+.yui-gf:after {
+ content: ".";
+ display: block;
+ height: 0;
+ clear: both;
+ visibility: hidden;
+}
+#bd,
+.yui-g,
+.yui-gb,
+.yui-gc,
+.yui-gd,
+.yui-ge,
+.yui-gf {
+ zoom: 1;
+}
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/layout.css
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/page.css
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/page.css (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/page.css 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,57 @@
+/*
+Copyright (c) 2008, Yahoo! Inc. All rights reserved.
+Code licensed under the BSD License:
+http://developer.yahoo.net/yui/license.txt
+version: 2.5.2
+*/
+/*
+ Note: Throughout this file, the *property filter is used to
+ give a value to IE that other browsers do not see.
+*/
+
+/*
+ Section: General Rules
+*/
+
+ body {
+ text-align:center;
+ }
+
+ .rich-page-footer {
+ clear:both;
+ }
+
+/*
+ Section: Page Width Rules (#doc, #doc2, #doc3, #doc4)
+*/
+
+ /*
+ Subsection: General
+ */
+
+ .rich-page {
+ margin:auto;
+ text-align:left;
+ min-width:750px;
+ }
+
+/*
+ Section: Preset Template Rules (.yui-t[1-6])
+*/
+
+ /*
+ Subsection: General
+ */
+
+ /* to preserve source-order independence for Gecko */
+ .rich-page-sidebar{position:relative;}
+ .rich-page-sidebar,.rich-page-body{_position:static;}
+ .rich-page-body{position:static;}
+
+ .rich-page-main {width:100%;}
+/*
+ Section: Clearing
+*/
+
+.rich-page-content:after {content:".";display:block;height:0;clear:both;visibility:hidden;}
+.rich-page-content {zoom:1;}
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/page.css
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset-context.css
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset-context.css (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset-context.css 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,125 @@
+/*
+Copyright (c) 2008, Yahoo! Inc. All rights reserved.
+Code licensed under the BSD License:
+http://developer.yahoo.net/yui/license.txt
+version: 3.0.0pr2
+*/
+/*e
+ TODO will need to remove settings on HTML since we can't namespace it.
+ TODO with the prefix, should I group by selector or property for weight savings?
+*/
+.yui-cssreset html{
+ color:#000;
+ background:#FFF;
+}
+/*
+ TODO remove settings on BODY since we can't namespace it.
+*/
+/*
+ TODO test putting a class on HEAD.
+ - Fails on FF.
+*/
+.yui-cssreset body,
+.yui-cssreset div,
+.yui-cssreset dl,
+.yui-cssreset dt,
+.yui-cssreset dd,
+.yui-cssreset ul,
+.yui-cssreset ol,
+.yui-cssreset li,
+.yui-cssreset h1,
+.yui-cssreset h2,
+.yui-cssreset h3,
+.yui-cssreset h4,
+.yui-cssreset h5,
+.yui-cssreset h6,
+.yui-cssreset pre,
+.yui-cssreset code,
+.yui-cssreset form,
+.yui-cssreset fieldset,
+.yui-cssreset legend,
+.yui-cssreset input,
+.yui-cssreset textarea,
+.yui-cssreset p,
+.yui-cssreset blockquote,
+.yui-cssreset th,
+.yui-cssreset td {
+ margin:0;
+ padding:0;
+}
+.yui-cssreset table {
+ border-collapse:collapse;
+ border-spacing:0;
+}
+.yui-cssreset fieldset,
+.yui-cssreset img {
+ border:0;
+}
+/*
+ TODO think about hanlding inheritence differently, maybe letting IE6 fail a bit...
+*/
+.yui-cssreset address,
+.yui-cssreset caption,
+.yui-cssreset cite,
+.yui-cssreset code,
+.yui-cssreset dfn,
+.yui-cssreset em,
+.yui-cssreset strong,
+.yui-cssreset th,
+.yui-cssreset var {
+ font-style:normal;
+ font-weight:normal;
+}
+/*
+ TODO Figure out where this list-style rule is best set. Hedger has a request to investigate.
+*/
+.yui-cssreset li {
+ list-style:none;
+}
+
+.yui-cssreset caption,
+.yui-cssreset th {
+ text-align:left;
+}
+.yui-cssreset h1,
+.yui-cssreset h2,
+.yui-cssreset h3,
+.yui-cssreset h4,
+.yui-cssreset h5,
+.yui-cssreset h6 {
+ font-size:100%;
+ font-weight:normal;
+}
+.yui-cssreset q:before,
+.yui-cssreset q:after {
+ content:'';
+}
+.yui-cssreset abbr,
+.yui-cssreset acronym {
+ border:0;
+ font-variant:normal;
+}
+/* to preserve line-height and selector appearance */
+.yui-cssreset sup {
+ vertical-align:text-top;
+}
+.yui-cssreset sub {
+ vertical-align:text-bottom;
+}
+.yui-cssreset input,
+.yui-cssreset textarea,
+.yui-cssreset select {
+ font-family:inherit;
+ font-size:inherit;
+ font-weight:inherit;
+}
+/*to enable resizing for IE*/
+.yui-cssreset input,
+.yui-cssreset textarea,
+.yui-cssreset select {
+ *font-size:100%;
+}
+/*because legend doesn't inherit in IE */
+.yui-cssreset legend {
+ color:#000;
+}
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset-context.css
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset-fonts-grids.css
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset-fonts-grids.css (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset-fonts-grids.css 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,8 @@
+/*
+Copyright (c) 2008, Yahoo! Inc. All rights reserved.
+Code licensed under the BSD License:
+http://developer.yahoo.net/yui/license.txt
+version: 2.5.2
+*/
+html{color:#000;background:#FFF;}body,div,dl,dt,dd,ul,ol,li,h1,h2,h3,h4,h5,h6,pre,code,form,fieldset,legend,input,textarea,p,blockquote,th,td{margin:0;padding:0;}table{border-collapse:collapse;border-spacing:0;}fieldset,img{border:0;}address,caption,cite,code,dfn,em,strong,th,var{font-style:normal;font-weight:normal;}li{list-style:none;}caption,th{text-align:left;}h1,h2,h3,h4,h5,h6{font-size:100%;font-weight:normal;}q:before,q:after{content:'';}abbr,acronym {border:0;font-variant:normal;}sup {vertical-align:text-top;}sub {vertical-align:text-bottom;}input,textarea,select{font-family:inherit;font-size:inherit;font-weight:inherit;}input,textarea,select{*font-size:100%;}legend{color:#000;}body {font:13px/1.231 arial,helvetica,clean,sans-serif;*font-size:small;*font:x-small;}table {font-size:inherit;font:100%;}pre,code,kbd,samp,tt{font-family:monospace;*font-size:108%;line-height:100%;}
+body{text-align:center;}#ft{clear:both;}#doc,#doc2,#doc3,#doc4,.yui-t1,.yui-t2,.yui-t3,.yui-t4,.yui-t5,.yui-t6,.yui-t7{margin:auto;text-align:left;width:57.69em;*width:56.25em;min-width:750px;}#doc2{width:73.076em;*width:71.25em;}#doc3{margin:auto 10px;width:auto;}#doc4{width:74.923em;*width:73.05em;}.yui-b{position:relative;}.yui-b{_position:static;}#yui-main .yui-b{position:static;}#yui-main{width:100%;}.yui-t1 #yui-main,.yui-t2 #yui-main,.yui-t3 #yui-main{float:right;margin-left:-25em;}.yui-t4 #yui-main,.yui-t5 #yui-main,.yui-t6 #yui-main{float:left;margin-right:-25em;}.yui-t1 .yui-b{float:left;width:12.30769em;*width:12.00em;}.yui-t1 #yui-main .yui-b{margin-left:13.30769em;*margin-left:13.05em;}.yui-t2 .yui-b{float:left;width:13.8461em;*width:13.50em;}.yui-t2 #yui-main .yui-b{margin-left:14.8461em;*margin-left:14.55em;}.yui-t3 .yui-b{float:left;width:23.0769em;*width:22.50em;}.yui-t3 #yui-main .yui-b{margin-left:24.0769em;*margin-left:23.62em;}.yui-t4 .yui-b{float:right!
;width:13.8456em;*width:13.50em;}.yui-t4 #yui-main .yui-b{margin-right:14.8456em;*margin-right:14.55em;}.yui-t5 .yui-b{float:right;width:18.4615em;*width:18.00em;}.yui-t5 #yui-main .yui-b{margin-right:19.4615em;*margin-right:19.125em;}.yui-t6 .yui-b{float:right;width:23.0769em;*width:22.50em;}.yui-t6 #yui-main .yui-b{margin-right:24.0769em;*margin-right:23.62em;}.yui-t7 #yui-main .yui-b{display:block;margin:0 0 1em 0;}#yui-main .yui-b{float:none;width:auto;}.yui-gb .yui-u,.yui-g .yui-gb .yui-u,.yui-gb .yui-g,.yui-gb .yui-gb,.yui-gb .yui-gc,.yui-gb .yui-gd,.yui-gb .yui-ge,.yui-gb .yui-gf,.yui-gc .yui-u,.yui-gc .yui-g,.yui-gd .yui-u{float:left;}.yui-g .yui-u,.yui-g .yui-g,.yui-g .yui-gb,.yui-g .yui-gc,.yui-g .yui-gd,.yui-g .yui-ge,.yui-g .yui-gf,.yui-gc .yui-u,.yui-gd .yui-g,.yui-g .yui-gc .yui-u,.yui-ge .yui-u,.yui-ge .yui-g,.yui-gf .yui-g,.yui-gf .yui-u{float:right;}.yui-g div.first,.yui-gb div.first,.yui-gc div.first,.yui-gd div.first,.yui-ge div.first,.yui-gf div.first,.y!
ui-g .yui-gc div.first,.yui-g .yui-ge div.first,.yui-gc div.fi!
rst div.
first{float:left;}.yui-g .yui-u,.yui-g .yui-g,.yui-g .yui-gb,.yui-g .yui-gc,.yui-g .yui-gd,.yui-g .yui-ge,.yui-g .yui-gf{width:49.1%;}.yui-gb .yui-u,.yui-g .yui-gb .yui-u,.yui-gb .yui-g,.yui-gb .yui-gb,.yui-gb .yui-gc,.yui-gb .yui-gd,.yui-gb .yui-ge,.yui-gb .yui-gf,.yui-gc .yui-u,.yui-gc .yui-g,.yui-gd .yui-u{width:32%;margin-left:1.99%;}.yui-gb .yui-u{*margin-left:1.9%;*width:31.9%;}.yui-gc div.first,.yui-gd .yui-u{width:66%;}.yui-gd div.first{width:32%;}.yui-ge div.first,.yui-gf .yui-u{width:74.2%;}.yui-ge .yui-u,.yui-gf div.first{width:24%;}.yui-g .yui-gb div.first,.yui-gb div.first,.yui-gc div.first,.yui-gd div.first{margin-left:0;}.yui-g .yui-g .yui-u,.yui-gb .yui-g .yui-u,.yui-gc .yui-g .yui-u,.yui-gd .yui-g .yui-u,.yui-ge .yui-g .yui-u,.yui-gf .yui-g .yui-u{width:49%;*width:48.1%;*margin-left:0;}.yui-g .yui-gb div.first,.yui-gb .yui-gb div.first{*margin-right:0;*width:32%;_width:31.7%;}.yui-g .yui-gc div.first,.yui-gd .yui-g{width:66%;}.yui-gb .yui-g div.first{*margin!
-right:4%;_margin-right:1.3%;}.yui-gb .yui-gc div.first,.yui-gb .yui-gd div.first{*margin-right:0;}.yui-gb .yui-gb .yui-u,.yui-gb .yui-gc .yui-u{*margin-left:1.8%;_margin-left:4%;}.yui-g .yui-gb .yui-u{_margin-left:1.0%;}.yui-gb .yui-gd .yui-u{*width:66%;_width:61.2%;}.yui-gb .yui-gd div.first{*width:31%;_width:29.5%;}.yui-g .yui-gc .yui-u,.yui-gb .yui-gc .yui-u{width:32%;_float:right;margin-right:0;_margin-left:0;}.yui-gb .yui-gc div.first{width:66%;*float:left;*margin-left:0;}.yui-gb .yui-ge .yui-u,.yui-gb .yui-gf .yui-u{margin:0;}.yui-gb .yui-gb .yui-u{_margin-left:.7%;}.yui-gb .yui-g div.first,.yui-gb .yui-gb div.first{*margin-left:0;}.yui-gc .yui-g .yui-u,.yui-gd .yui-g .yui-u{*width:48.1%;*margin-left:0;}s .yui-gb .yui-gd div.first{width:32%;}.yui-g .yui-gd div.first{_width:29.9%;}.yui-ge .yui-g{width:24%;}.yui-gf .yui-g{width:74.2%;}.yui-gb .yui-ge div.yui-u,.yui-gb .yui-gf div.yui-u{float:right;}.yui-gb .yui-ge div.first,.yui-gb .yui-gf div.first{float:left;}.yui-gb!
.yui-ge .yui-u,.yui-gb .yui-gf div.first{*width:24%;_width:20!
%;}.yui-
gb .yui-ge div.first,.yui-gb .yui-gf .yui-u{*width:73.5%;_width:65.5%;}.yui-ge div.first .yui-gd .yui-u{width:65%;}.yui-ge div.first .yui-gd div.first{width:32%;}#bd:after,.yui-g:after,.yui-gb:after,.yui-gc:after,.yui-gd:after,.yui-ge:after,.yui-gf:after{content:".";display:block;height:0;clear:both;visibility:hidden;}#bd,.yui-g,.yui-gb,.yui-gc,.yui-gd,.yui-ge,.yui-gf{zoom:1;}
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset-fonts-grids.css
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset.css
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset.css (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset.css 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,125 @@
+/*
+Copyright (c) 2008, Yahoo! Inc. All rights reserved.
+Code licensed under the BSD License:
+http://developer.yahoo.net/yui/license.txt
+version: 3.0.0pr2
+*/
+/*
+ TODO will need to remove settings on HTML since we can't namespace it.
+ TODO with the prefix, should I group by selector or property for weight savings?
+*/
+html{
+ color:#000;
+ background:#FFF;
+}
+/*
+ TODO remove settings on BODY since we can't namespace it.
+*/
+/*
+ TODO test putting a class on HEAD.
+ - Fails on FF.
+*/
+body,
+div,
+dl,
+dt,
+dd,
+ul,
+ol,
+li,
+h1,
+h2,
+h3,
+h4,
+h5,
+h6,
+pre,
+code,
+form,
+fieldset,
+legend,
+input,
+textarea,
+p,
+blockquote,
+th,
+td {
+ margin:0;
+ padding:0;
+}
+table {
+ border-collapse:collapse;
+ border-spacing:0;
+}
+fieldset,
+img {
+ border:0;
+}
+/*
+ TODO think about hanlding inheritence differently, maybe letting IE6 fail a bit...
+*/
+address,
+caption,
+cite,
+code,
+dfn,
+em,
+strong,
+th,
+var {
+ font-style:normal;
+ font-weight:normal;
+}
+/*
+ TODO Figure out where this list-style rule is best set. Hedger has a request to investigate.
+*/
+li {
+ list-style:none;
+}
+
+caption,
+th {
+ text-align:left;
+}
+h1,
+h2,
+h3,
+h4,
+h5,
+h6 {
+ font-size:100%;
+ font-weight:normal;
+}
+q:before,
+q:after {
+ content:'';
+}
+abbr,
+acronym {
+ border:0;
+ font-variant:normal;
+}
+/* to preserve line-height and selector appearance */
+sup {
+ vertical-align:text-top;
+}
+sub {
+ vertical-align:text-bottom;
+}
+input,
+textarea,
+select {
+ font-family:inherit;
+ font-size:inherit;
+ font-weight:inherit;
+}
+/*to enable resizing for IE*/
+input,
+textarea,
+select {
+ *font-size:100%;
+}
+/*because legend doesn't inherit in IE */
+legend {
+ color:#000;
+}
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset.css
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/simple.css
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/simple.css (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/simple.css 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,117 @@
+body {
+ background: #CACACA url(../images/background.png) repeat-x;
+ font-family: "Trebuchet MS", Verdana, serif
+}
+#container {
+ margin: 0 auto;
+ width: 750px
+}
+#header {
+ width: 100%
+}
+#sub_header {
+ text-align: right;
+ font-weight: bold;
+ font-size: 20px;
+ color: #FFFFFF;
+ padding-right: 20px;
+ padding-bottom: 20px;
+}
+#main_content {
+ margin: 0 auto;
+ width: 100%;
+ background: #FFFFFF url('../images/background_content.gif');
+ background-repeat: repeat-y
+}
+#main_content_top {
+ height: 30px;
+ background: #FFFFFF url('../images/background_top.gif');
+}
+#main_content_bottom {
+ height: 30px;
+ background: #FFFFFF url('../images/background_bottom.gif');
+}
+#footer {
+ text-align: center;
+ font-size: 12px;
+ margin: 10px auto
+}
+.content {
+ float: left;
+ width: 510px;
+ text-align: justify;
+ padding: 0 30px 0 30px;
+ font-size: 12px
+}
+.menu {
+ width: 139px;
+ float: right;
+ padding: 0 20px 0 20px;
+ border-left: #8C8484 1px solid;
+ font-size: 12px
+}
+.menu ul {
+ margin: 0;
+ padding: 10px 0 10px 15px
+}
+.menu il {
+ list-style-type: disc
+}
+#header h1 {
+ margin-bottom: 0px;
+ font-size: 28px;
+ font-weight: bold;
+ color: #A40008
+}
+.content h2 {
+ margin-top: 0px;
+ font-size: 18px;
+ font-weight: bold;
+ color: #A40008
+}
+#clear {
+ display: block;
+ clear: both;
+ width: 100%;
+ height:1px;
+ overflow:hidden;
+}
+.menu_title {
+ font-size: 18px;
+ font-weight: bold;
+ color: #A40008
+}
+.menu ul {
+ margin: 0;
+ padding: 10px 0 20px 15px
+}
+.menu li {
+ padding-top: 2px;
+ list-style-type: circle
+}
+a {
+ color: #A40008;
+ font-weight: bold;
+ text-decoration: none
+}
+a:hover {
+ color: #A40008;
+ font-weight: bold;
+ text-decoration: underline
+}
+a.menu_link {
+ color: #000000;
+ font-weight: bold;
+ text-decoration: underline
+}
+a.menu_link:hover {
+ color: #A40008;
+ font-weight: bold;
+ text-decoration: none
+}
+.quote {
+ margin: 20px;
+ text-align: center;
+ font-weight: bold;
+ font-style: italic
+}
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/simple.css
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/MANIFEST.MF
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/MANIFEST.MF (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/MANIFEST.MF 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,6 @@
+Manifest-Version: 1.0
+Archiver-Version: Plexus Archiver
+Created-By: Apache Maven
+Built-By: Administrator
+Build-Jdk: 1.6.0_14
+
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/MANIFEST.MF
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/richfaces-demo/pom.properties
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/richfaces-demo/pom.properties (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/richfaces-demo/pom.properties 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,5 @@
+#Generated by Maven
+#Fri Aug 28 22:42:56 EEST 2009
+version=4.0.0.ALPHA1
+groupId=org.richfaces.examples
+artifactId=richfaces-demo
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/richfaces-demo/pom.properties
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/richfaces-demo/pom.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/richfaces-demo/pom.xml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/richfaces-demo/pom.xml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,115 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
+ http://maven.apache.org/xsd/maven-4.0.0.xsd">
+
+ <parent>
+ <groupId>org.richfaces</groupId>
+ <artifactId>examples</artifactId>
+ <version>4.0.0.ALPHA1</version>
+ </parent>
+
+ <modelVersion>4.0.0</modelVersion>
+ <groupId>org.richfaces.examples</groupId>
+ <artifactId>richfaces-demo</artifactId>
+ <packaging>war</packaging>
+ <name>richfaces demo application </name>
+
+ <repositories>
+ <repository>
+ <id>repository.jboss.org</id>
+ <name>Jboss Repository for Maven</name>
+ <url>http://repository.jboss.org/maven2/</url>
+ </repository>
+ <repository>
+ <id>snapshots.jboss.org</id>
+ <name>Jboss Snapshots Repository for Maven</name>
+ <url>http://snapshots.jboss.org/maven2/</url>
+ <snapshots>
+ <enabled>true</enabled>
+ </snapshots>
+ </repository>
+ <repository>
+ <snapshots>
+ <enabled>true</enabled>
+ </snapshots>
+ <id>maven-repository2.dev.java.net</id>
+ <name>Java.net Repository for Maven 2</name>
+ <url>http://download.java.net/maven/2</url>
+ </repository>
+ </repositories>
+
+ <dependencies>
+ <dependency>
+ <groupId>org.richfaces.ui.components</groupId>
+ <artifactId>core-ui</artifactId>
+ <version>4.0.0.ALPHA1</version>
+ </dependency>
+
+ <dependency>
+ <groupId>org.jboss.cache</groupId>
+ <artifactId>jbosscache-core</artifactId>
+ <version>3.1.0.GA</version>
+ </dependency>
+ <dependency>
+ <groupId>org.slf4j</groupId>
+ <artifactId>slf4j-log4j12</artifactId>
+ <version>1.5.8</version>
+ </dependency>
+ <dependency>
+ <groupId>org.slf4j</groupId>
+ <artifactId>slf4j-simple</artifactId>
+ <version>1.5.8</version>
+ <scope>provided</scope>
+ </dependency>
+ </dependencies>
+
+ <build>
+ <finalName>richfaces-demo</finalName>
+ </build>
+
+ <profiles>
+ <profile>
+ <id>release</id>
+ <build>
+ <plugins>
+ <plugin>
+ <artifactId>maven-war-plugin</artifactId>
+ <executions>
+ <execution>
+ <id>jee5</id>
+ <phase>package</phase>
+ <goals>
+ <goal>war</goal>
+ </goals>
+ <configuration>
+ <webappDirectory>${project.build.directory}/${project.build.finalName}-jee5</webappDirectory>
+ <classifier>jee5</classifier>
+ <packagingExcludes>WEB-INF/lib/jsf-api*,WEB-INF/lib/jsf-impl*,WEB-INF/lib/jta-*</packagingExcludes>
+ <warSourceExcludes>WEB-INF/lib/jsf-api*,WEB-INF/lib/jsf-impl*,WEB-INF/lib/jta-*</warSourceExcludes>
+ </configuration>
+ </execution>
+ </executions>
+ <configuration>
+ <classifier>tomcat6</classifier>
+ </configuration>
+ </plugin>
+ </plugins>
+ </build>
+ </profile>
+ <profile>
+ <id>jee5</id>
+ <build>
+ <plugins>
+ <plugin>
+ <artifactId>maven-war-plugin</artifactId>
+ <configuration>
+ <webappDirectory>${project.build.directory}/${project.build.finalName}-jee5</webappDirectory>
+ </configuration>
+ </plugin>
+ </plugins>
+ </build>
+ </profile>
+ </profiles>
+</project>
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/richfaces-demo/pom.xml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/common/UserBean.class
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/common/UserBean.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/function/FunctionBean.class
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/function/FunctionBean.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/mediaOutput/MediaBean.class
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/mediaOutput/MediaBean.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/mediaOutput/MediaData.class
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/mediaOutput/MediaData.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/mediaOutput/text.swf
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/mediaOutput/text.swf
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/outputPanel/OutputPanelBean.class
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/outputPanel/OutputPanelBean.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/push/Choice.class
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/push/Choice.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/push/ChoicesBean.class
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/push/ChoicesBean.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/faces-config.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/faces-config.xml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/faces-config.xml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,25 @@
+<?xml version='1.0' encoding='UTF-8'?>
+
+<faces-config xmlns="http://java.sun.com/xml/ns/javaee"
+ version="2.0">
+
+ <application>
+ <!-- system-event-listener>
+ <system-event-listener-class>org.richfaces.resource.MapBasedResourceCodecListener</system-event-listener-class>
+ <system-event-class>javax.faces.event.PostConstructApplicationEvent</system-event-class>
+ </system-event-listener -->
+ </application>
+
+ <managed-bean>
+ <managed-bean-name>opBean1</managed-bean-name>
+ <managed-bean-class>org.richfaces.demo.outputPanel.OutputPanelBean</managed-bean-class>
+ <managed-bean-scope>request</managed-bean-scope>
+ </managed-bean>
+ <managed-bean>
+ <managed-bean-name>opBean2</managed-bean-name>
+ <managed-bean-class>org.richfaces.demo.outputPanel.OutputPanelBean</managed-bean-class>
+ <managed-bean-scope>request</managed-bean-scope>
+ </managed-bean>
+
+
+</faces-config>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/faces-config.xml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/commons-beanutils-1.7.0.jar
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/commons-beanutils-1.7.0.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/commons-logging-1.1.1.jar
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/commons-logging-1.1.1.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/core-ui-4.0.0.ALPHA1.jar
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/core-ui-4.0.0.ALPHA1.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jboss-common-core-2.2.10.GA.jar
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jboss-common-core-2.2.10.GA.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jboss-logging-spi-2.0.5.GA.jar
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jboss-logging-spi-2.0.5.GA.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jbosscache-core-3.1.0.GA.jar
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jbosscache-core-3.1.0.GA.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jgroups-2.6.7.GA.jar
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jgroups-2.6.7.GA.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jsf-api-2.0.0-SNAPSHOT.jar
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jsf-api-2.0.0-SNAPSHOT.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jsf-impl-2.0.0-SNAPSHOT.jar
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jsf-impl-2.0.0-SNAPSHOT.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jta-1.1.jar
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jta-1.1.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/log4j-1.2.14.jar
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/log4j-1.2.14.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/richfaces-api-4.0.0.ALPHA1.jar
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/richfaces-api-4.0.0.ALPHA1.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/richfaces-impl-4.0.0.ALPHA1.jar
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/richfaces-impl-4.0.0.ALPHA1.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/slf4j-api-1.5.8.jar
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/slf4j-api-1.5.8.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/slf4j-log4j12-1.5.8.jar
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/slf4j-log4j12-1.5.8.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/web.xml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/web.xml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/web.xml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xmlns="http://java.sun.com/xml/ns/javaee"
+ xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
+ id="richfaces-demo" version="2.5">
+
+ <display-name>richfaces-demo3</display-name>
+ <welcome-file-list>
+ <welcome-file>index.html</welcome-file>
+ <welcome-file>index.htm</welcome-file>
+ <welcome-file>index.jsp</welcome-file>
+ <welcome-file>default.html</welcome-file>
+ <welcome-file>default.htm</welcome-file>
+ <welcome-file>default.jsp</welcome-file>
+ </welcome-file-list>
+
+ <context-param>
+ <param-name>org.richfaces.SKIN</param-name>
+ <param-value>#{skinBean.skin}</param-value>
+ </context-param>
+
+ <context-param>
+ <param-name>javax.faces.PROJECT_STAGE</param-name>
+ <param-value>Development</param-value>
+ </context-param>
+
+ <servlet>
+ <servlet-name>Faces Servlet</servlet-name>
+ <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+ <servlet-mapping>
+ <servlet-name>Faces Servlet</servlet-name>
+ <url-pattern>*.jsf</url-pattern>
+ </servlet-mapping>
+ <servlet-mapping>
+ <servlet-name>Faces Servlet</servlet-name>
+ <url-pattern>/faces/*</url-pattern>
+ </servlet-mapping>
+</web-app>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/web.xml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/images/ai.gif
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/images/ai.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/images/richfaces-banner.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/images/richfaces-banner.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/index.jsp
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/index.jsp (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/index.jsp 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,7 @@
+<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
+<html>
+<head></head>
+ <body>
+ <jsp:forward page="/welcome.jsf" />
+ </body>
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/index.jsp
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/message.css
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/message.css (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/message.css 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,3 @@
+rich-message{
+ color:red;
+}
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/message.css
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/messages.css
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/messages.css (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/messages.css 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,3 @@
+rich-messages{
+ color:red;
+}
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/messages.css
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/page.css
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/page.css (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/page.css 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,77 @@
+.rich-page{width:100%;}
+.body{
+ background: #FFFFFF;
+ margin:0px;
+}
+*{
+ font-size:11px;
+}
+.header_bg{
+ background-image:url(#{resource['rich/img/header_background.png']});
+ border-bottom:1px solid;
+ border-bottom-color:#FFFFFF;
+ background-color:#BED6F8;
+ background-repeat:repeat-x;
+ background-position:top left;
+}
+
+.footer_bg{
+ background-image:url(#{resource['rich/img/footer_background.png']});
+ border-top:1px solid;
+ border-top-color:#FFFFFF;
+ background-color:#BED6F8;
+ background-repeat:repeat-x;
+ background-position:center left;
+}
+
+.menu_col{
+ background:#FFFFFF;
+ vertical-align:top;
+ border-top:2px solid;
+ border-top-color:#BED6F8;
+ border-right:2px solid;
+ border-right-color:#BED6F8;
+ border-bottom:2px solid;
+ border-bottom-color:#BED6F8;
+}
+
+.content_col{
+ background:#FFFFFF;
+ vertical-align:top;
+ width:100%;
+ border-top:2px solid;
+ border-top-color:#BED6F8;
+ border-bottom:2px solid;
+ border-bottom-color:#BED6F8;
+}
+*.menu_col, *.content_col, *.footer_bg{
+ font-family:Arial, Verdana, sans-serif ;
+ color:#000000;
+ font-size:11px;
+}
+*.header_content{
+ font-family:Arial, Verdana, sans-serif;
+ color:#000000;
+ font-size:11px;
+}
+
+
+.page_size {
+ width : 100%
+ height : 100%
+}
+
+
+.header_content {
+ margin : 0px 0px 0px 0px
+ height : 95px position : relative
+}
+
+.spacer{font-size : 1px}
+
+
+.footer_bg_content {
+ margin : 0px 0px 0px 0px
+ height : 45px
+ position : relative
+}
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/page.css
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/panel.css
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/panel.css (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/panel.css 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,26 @@
+.rich-panel{
+ border-width: 1px;
+ border-style: solid;
+ padding : 1px;
+ color:#000000;
+ font-family:Arial,Verdana,sans-serif;
+ font-size:11px;
+ background-color:#FFFFFF;
+ border-color:#BED6F8;
+}
+
+.rich-panel-header{
+ padding : 2px;
+ border-width: 1px;
+ border-style: solid;
+ background-color:#BED6F8;
+ border-color:#BED6F8;
+ font-weight:bold;
+ background-position:left top;
+ background-repeat:repeat-x;
+ background-image: url(#{resource['rich/img/panel_header.png']})
+}
+
+.rich-panel-body{
+ padding : 10px;
+}
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/panel.css
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/img/footer_background.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/img/footer_background.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/img/header_background.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/img/header_background.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/img/panel_header.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/img/panel_header.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/message.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/message.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/message.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,30 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:c="http://java.sun.com/jsp/jstl/core"
+ xmlns:composite="http://java.sun.com/jsf/composite"
+ xmlns:a4j="http://richfaces.org/a4j">
+<head>
+<title>panel</title>
+</head>
+<body>
+
+<composite:interface>
+ <composite:attribute name="for" required="true" />
+ <composite:attribute name="style" required="false" />
+ <composite:attribute name="styleClass" required="false" />
+</composite:interface>
+
+<composite:implementation>
+ <h:outputStylesheet name="rich/css/message.css" />
+ <a4j:outputPanel ajaxRendered="true" layout="none">
+ <h:message for="#{cc.attrs.for}" showDetail="#{cc.attrs.showDetails}"
+ showSummary="#{cc.attrs.showSummary}" style="#{cc.attrs.style}"
+ styleClass="rich-message #{cc.attrs.styleClass}" />
+ </a4j:outputPanel>
+</composite:implementation>
+</body>
+</html>
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/message.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/messages.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/messages.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/messages.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,29 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:c="http://java.sun.com/jsp/jstl/core"
+ xmlns:composite="http://java.sun.com/jsf/composite"
+ xmlns:a4j="http://richfaces.org/a4j">
+<head>
+<title>panel</title>
+</head>
+<body>
+
+<composite:interface>
+ <composite:attribute name="style" required="false" />
+ <composite:attribute name="styleClass" required="false" />
+</composite:interface>
+
+<composite:implementation>
+ <h:outputStylesheet name="rich/css/messages.css" />
+ <a4j:outputPanel ajaxRendered="true" layout="none">
+ <h:messages layout="#{cc.attrs.layout}"
+ showSummary="true" style="#{cc.attrs.style}"
+ styleClass="rich-message #{cc.attrs.styleClass}" />
+ </a4j:outputPanel>
+</composite:implementation>
+</body>
+</html>
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/messages.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/page.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/page.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/page.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,69 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:c="http://java.sun.com/jsp/jstl/core"
+ xmlns:composite="http://java.sun.com/jsf/composite">
+ <head>
+ <title>page</title>
+ </head>
+<body>
+
+<composite:interface>
+ <composite:attribute name="style" />
+ <composite:attribute name="styleClass"/>
+ <composite:attribute name="headerClass"/>
+ <composite:attribute name="bodyClass"/>
+ <composite:attribute name="sidebarClass"/>
+</composite:interface>
+<composite:implementation>
+<h:outputText value="<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">" escape="false"/>
+<html xmlns="http://www.w3.org/1999/xhtml">
+<h:head>
+ <title>#{cc.attrs.pageTitle}</title>
+ <composite:renderFacet name="pageHeader"/>
+</h:head>
+<h:body>
+ <h:outputStylesheet name="rich/css/page.css" />
+ <table border="0" cellpadding="0" cellspacing="0" class="rich-page #{cc.attrs.pageClass}">
+ <tbody>
+ <tr>
+ <td class="header_bg">
+ <div class="header_content rich-page-header #{cc.attrs.headerClass}">
+ <composite:renderFacet name="header"/>
+ </div>
+ </td>
+ </tr>
+ <tr>
+ <td width="100%" height="100%" class="bg_tabbody">
+ <table cellpadding="0" cellspacing="0" border="0" width="100%" height="100%" class="rich-page-content #{cc.attrs.contentClass}">
+ <tbody>
+ <tr>
+ <td class="menu_col rich-page-sidebar #{cc.attrs.sidebarClass}">
+ <div class="menu_width spacer" style="width:#{cc.attrs.sidebarWidth}px"></div>
+ <composite:renderFacet name="sidebar"/>
+ </td>
+ <td class="content_col rich-page-body #{cc.attrs.bodyClass}">
+ <composite:insertChildren />
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </td>
+ </tr>
+ <tr>
+ <td class="footer_bg">
+ <div class="footer_bg_content rich-page-footer #{cc.attrs.footerClass}">
+ <composite:renderFacet name="footer"/>
+ </div>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</h:body>
+</html>
+</composite:implementation>
+</body>
+</html>
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/page.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/panel.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/panel.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/panel.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,49 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:c="http://java.sun.com/jsp/jstl/core"
+ xmlns:composite="http://java.sun.com/jsf/composite">
+ <head>
+ <title>panel</title>
+ </head>
+<body>
+
+<composite:interface>
+ <composite:attribute name="style" required="false"/>
+ <composite:attribute name="styleClass" required="false"/>
+ <composite:attribute name="headerClass" required="false"/>
+ <composite:attribute name="bodyClass" required="true"/>
+</composite:interface>
+
+<composite:implementation>
+ <h:outputStylesheet name="rich/css/panel.css" />
+
+ <div class="rich-panel #{compositeComponent.attrs.styleClass}"
+ style="#{compositeComponent.attrs.style}"
+ onclick="#{compositeComponent.attrs.onclick}"
+ ondblclick="#{compositeComponent.attrs.ondblclick}"
+ onkeydown="#{compositeComponent.attrs.onkeydown}"
+ onkeypress="#{compositeComponent.attrs.onkeypress}"
+ onkeyup="#{compositeComponent.attrs.onkeyup}"
+ onmousedown="#{compositeComponent.attrs.onmousedown}"
+ onmousemove="#{compositeComponent.attrs.onmousemove}"
+ onmouseout="#{compositeComponent.attrs.onmouseout}"
+ onmouseover="#{compositeComponent.attrs.onmouseover}"
+ onmouseup="#{compositeComponent.attrs.onmouseup}">
+
+ <h:panelGroup rendered="#{not empty cc.facets.header}">
+ <div class="rich-panel-header #{compositeComponent.attrs.headerClass}">
+ <composite:renderFacet name="header"/>
+ </div>
+ </h:panelGroup>
+ <div class="rich-panel-body #{compositeComponent.attrs.bodyClass}" >
+ <composite:insertChildren />
+ </div>
+
+ </div>
+</composite:implementation>
+</body>
+</html>
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/panel.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax/ajax.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax/ajax.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax/ajax.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,17 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:a4j="http://richfaces.org/a4j">
+
+ <ui:composition>
+ <h:form>
+ <h:inputText value="#{userBean.name}">
+ <a4j:ajax event="keyup" render="out"/>
+ </h:inputText>
+ <h:outputText value="#{userBean.name}" id="out"/>
+ </h:form>
+ </ui:composition>
+
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax/ajax.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,20 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets">
+
+ <ui:composition template="/templates/main.xhtml">
+ <ui:define name="body">
+ <p>
+ The behavior that adds javascript call for sending Ajax request
+ to specified event on parent component
+ </p>
+ <fieldset>
+ <legend>Simple sample</legend>
+ <ui:include src="/richfaces/ajax/ajax.xhtml" />
+ </fieldset>
+ </ui:define>
+ </ui:composition>
+
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/button/usage.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/button/usage.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/button/usage.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,29 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:a4j="http://richfaces.org/a4j">
+
+<ui:composition>
+ <style>
+ <!--
+ .outhello {
+ font-weight: bold;
+ }
+ -->
+ </style>
+ <h:form>
+ <h:panelGrid columns="3">
+ <h:outputText value="Name:" />
+ <h:inputText value="#{userBean.name}" />
+ <a4j:commandButton value="Say Hello" render="out" />
+ </h:panelGrid>
+ </h:form>
+ <br />
+ <a4j:outputPanel id="out">
+ <h:outputText value="Hello #{userBean.name} !" rendered="#{not empty userBean.name}" styleClass="outhello" />
+ </a4j:outputPanel>
+</ui:composition>
+
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/button/usage.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandButton.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandButton.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandButton.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,20 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets">
+
+<ui:composition template="/templates/main.xhtml">
+ <ui:define name="body">
+ <p>
+ The combination similar to h:commandButton with f:ajax. Inherits all
+ a4j:ajax special options.
+ </p>
+ <fieldset>
+ <legend>commandButton Sample</legend>
+ <ui:include src="/richfaces/button/usage.xhtml" />
+ </fieldset>
+ </ui:define>
+</ui:composition>
+
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandButton.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandLink.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandLink.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandLink.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,20 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets">
+
+<ui:composition template="/templates/main.xhtml">
+ <ui:define name="body">
+ <p>
+ The combination similar to h:commandLink with f:ajax. Inherits all
+ a4j:ajax special options.
+ </p>
+ <fieldset>
+ <legend>commandLink Sample</legend>
+ <ui:include src="/richfaces/link/usage.xhtml" />
+ </fieldset>
+ </ui:define>
+</ui:composition>
+
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandLink.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction/usage.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction/usage.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction/usage.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,33 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:a4j="http://richfaces.org/a4j">
+
+ <ui:composition>
+ <table width="400">
+ <tbody>
+ <tr>
+ <td><span onmouseover="updateName('Kate')"
+ onmouseout="updateName('')">Kate</span></td>
+ <td><span onmouseover="updateName('John')"
+ onmouseout="updateName('')">John</span></td>
+ <td><span onmouseover="updateName('Alex')"
+ onmouseout="updateName('')">Alex</span></td>
+ </tr>
+ <tr>
+ <td colspan="3">Name: <b><h:outputText id="showname"
+ value="#{functionBean.text}" /></b></td>
+ </tr>
+ </tbody>
+ </table>
+ <h:form>
+ <a4j:jsFunction name="updateName" render="showname"
+ action="#{functionBean.processHover}">
+ <f:param name="name" />
+ </a4j:jsFunction>
+ </h:form>
+ </ui:composition>
+
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction/usage.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,24 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets">
+
+<ui:composition template="/templates/main.xhtml">
+ <ui:define name="body">
+
+ <p><b>a4j:jsFunction</b> component also designed to send Ajax requests, but allows to perform
+ an the requests from a Javascript code directly. The component sends a request using
+ a standard JSF approach, so the JSF form is required. The following example
+ shows how the part of a page is re-rendered when a user hovers over the names.
+ </p>
+
+
+ <fieldset>
+ <legend>JS Function Sample</legend>
+ <ui:include src="/richfaces/jsFunction/usage.xhtml" />
+ </fieldset>
+ </ui:define>
+</ui:composition>
+
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/link/usage.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/link/usage.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/link/usage.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,28 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:a4j="http://richfaces.org/a4j">
+
+ <ui:composition>
+ <style>
+ <!--
+ .outhello {
+ font-weight: bold;
+ }
+ -->
+ </style>
+ <h:form>
+ <h:panelGrid columns="3">
+ <h:outputText value="Name:" />
+ <h:inputText value="#{userBean.name}" />
+ <a4j:commandLink value="Say Hello" render="out" />
+ </h:panelGrid>
+ </h:form>
+ <br />
+ <a4j:outputPanel id="out">
+ <h:outputText value="Hello #{userBean.name} !" rendered="#{not empty userBean.name}" styleClass="outhello" />
+ </a4j:outputPanel>
+</ui:composition>
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/link/usage.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log/usage.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log/usage.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log/usage.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,19 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:a4j="http://richfaces.org/a4j">
+
+ <ui:composition>
+ <h:form>
+ <h:inputText value="#{userBean.name}" />
+ <a4j:commandButton value="Submit" render="out"/>
+ <br/>
+ <a4j:outputPanel id="out">
+ <h:outputText value="Hello #{userBean.name}!" rendered="#{not empty userBean.name}"/>
+ </a4j:outputPanel>
+ </h:form>
+ <a4j:log/>
+ </ui:composition>
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log/usage.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,21 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets">
+
+<ui:composition template="/templates/main.xhtml">
+ <ui:define name="body">
+ <p>
+ Log component allows you to inspect client side activities
+ during an Ajax request. It shows reuqest data, response data, DOM
+ tree changes on update and other useful debug information.
+ </p>
+ <fieldset>
+ <legend>log Sample</legend>
+ <ui:include src="/richfaces/log/usage.xhtml" />
+ </fieldset>
+ </ui:define>
+</ui:composition>
+
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/flashUsage.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/flashUsage.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/flashUsage.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,36 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:a4j="http://richfaces.org/a4j">
+
+ <ui:composition>
+ <script src="#{facesContext.externalContext.requestContextPath}/script/swfobject.js" type="text/javascript"/>
+ <p>SWF Movie:</p>
+ <a4j:outputPanel id="flashPanelDynamic">
+
+ <a4j:mediaOutput element="a" id="swfLink" style="display: none;" cacheable="false" session="true"
+ createContent="#{mediaBean.paintFlash}" value="#{mediaData}" />
+
+ <a4j:outputPanel layout="block" id="myFlashContent" style="width: 200px; height: 200px">
+ <a href="http://www.adobe.com/go/getflashplayer">
+ <img src="http://www.adobe.com/images/shared/download_buttons/get_flash_player.gif" alt="Get Adobe Flash player" />
+ </a>
+ </a4j:outputPanel>
+
+ <script type="text/javascript">
+ var flashvars = {};
+ var params = {};
+ var attributes = {};
+ swfobject.embedSWF(document.getElementById('page:swfLink').href, document.getElementById('myFlashContent'), "200", "200", "9.0.0", false, flashvars, params, attributes);
+ </script>
+
+ </a4j:outputPanel>
+
+ <br />
+ <br />
+
+ </ui:composition>
+
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/flashUsage.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/imgUsage.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/imgUsage.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/imgUsage.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,16 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:a4j="http://richfaces.org/a4j">
+
+ <ui:composition>
+ <p>Dynamically generated JPEG file:</p>
+
+ <a4j:mediaOutput element="img" cacheable="false" session="true"
+ createContent="#{mediaBean.paint}" value="#{mediaData}" mimeType="image/jpeg" />
+ <br/><br/>
+ </ui:composition>
+
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/imgUsage.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,44 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets">
+
+<ui:composition template="/templates/main.xhtml">
+ <ui:define name="body">
+ <p>a4j:mediaOutput allows to generate images, video, sounds and other binary
+ resources defined by a user on-the-fly.
+ </p>
+ <p><b>createContent</b> attribute references to the method that will be used
+ for content creating. The method accepts two parameters. The first parameter
+ has an OutputStream type. It is a reference to the steam that should be used for output.
+ The second parameter is a reference to a 'value' attribute of the component.
+ </p>
+ <p>
+ <b>value</b> attribute references to data that can be used as input data for a content
+ creator method. The data should be serializable because it is encoded to the URL
+ of the resource.
+ </p>
+ <p>
+ <b>mimeType</b> attribute defines the type of output content. It is used to define
+ the corresponded type in the header of an HTTP response.
+ </p>
+ <p>
+ <b>cacheable</b> attribute is a flag that defines the caching strategy. If 'cacheable'
+ is set to false, the response will not be cached. If it is set to true, it will be cached
+ and the serialized value of 'value' attribute plays the role of a cache key.
+ </p>
+ <fieldset>
+ <legend>Image output</legend>
+ <ui:include src="/richfaces/mediaOutput/imgUsage.xhtml" />
+ </fieldset>
+ <ui:remove>
+ <fieldset>
+ <legend>Flash output</legend>
+ <ui:include src="/richfaces/mediaOutput/flashUsage.xhtml" />
+ </fieldset>
+ </ui:remove>
+ </ui:define>
+</ui:composition>
+
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/compositemessages.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/compositemessages.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/compositemessages.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,34 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:a4j="http://richfaces.org/a4j"
+ xmlns:rich="http://java.sun.com/jsf/composite/rich">
+
+ <ui:composition>
+ <h:form>
+ <rich:panel id="psnel">
+ <f:facet name="header">
+ <h:outputText value="User Details Panel" />
+ </f:facet>
+ <h:panelGrid columns="2">
+ <h:panelGrid columns="2">
+ <h:outputText value="User name:" />
+ <h:inputText value="#{userBean.name}" required="true" label="Name">
+ <f:validateLength minimum="3" maximum="12"/>
+ </h:inputText>
+ <h:outputText value="Adress:" />
+ <h:inputTextarea value="#{userBean.address}" label="Adress" required="true">
+ <f:validateLength maximum="100"/>
+ </h:inputTextarea>
+ </h:panelGrid>
+ <rich:messages/>
+ </h:panelGrid>
+ <a4j:commandButton value="Submit" type="button" action="#{userBean.store}" render="out"/>
+ <h:outputText value="#{userBean.recordStatus}" id="out"/>
+ </rich:panel>
+ </h:form>
+ </ui:composition>
+
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/compositemessages.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/usage.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/usage.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/usage.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,70 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:rich="http://java.sun.com/jsf/composite/rich"
+ xmlns:a4j="http://richfaces.org/a4j">
+
+<ui:composition>
+ <style type="text/css">
+ .col {
+ width:50%;
+ padding:10px;
+ padding: 0px 30px 0px 0px;
+ vertical-align: top;
+ }
+ </style>
+ <h:panelGrid columns="2" width="100%" columnClasses="col">
+
+ <f:verbatim>
+ This code does not work as expected. The expected echo text does not appear
+ below even the condition for <code>'renderer'</code> returns <code>true</code>.
+ Also, the error message does not appear when the length of the text reaches the limit.
+ </f:verbatim>
+ <f:verbatim>
+ This code works properly. The <code>h:message</code> is marked for update during
+ each Ajaxrequest/response. The place for bottom label is reserved with
+ <code>outputPanel</code> while the component is not rendered.
+ </f:verbatim>
+
+ <a4j:outputPanel layout="block">
+
+
+ <a4j:outputPanel layout="block">
+ <h:form>
+ <h:message for="text1" style="color:red" />
+
+ <h:outputText style="font-weight: bold;" value="Enter Text: "/>
+ <h:inputText id="text1" label="text1" value="#{opBean1.text}">
+ <f:validateLength maximum="10"/>
+ <a4j:ajax event="keyup" execute="@this" render="out1" onerror="function(){return false}"/>
+ </h:inputText>
+
+ <h:outputText id="out1" rendered="#{not empty opBean1.text}" value="Approved Text: #{opBean1.text}" />
+ </h:form>
+ </a4j:outputPanel>
+
+ </a4j:outputPanel>
+
+ <a4j:outputPanel layout="block">
+ <h:form>
+ <a4j:outputPanel ajaxRendered="true" layout="block">
+ <h:message for="text2" style="color:red" />
+ </a4j:outputPanel>
+
+ <h:outputText style="font-weight: bold;" value="Enter Text: "/>
+ <h:inputText id="text2" label="text2" value="#{opBean2.text}">
+ <f:validateLength maximum="10"/>
+ <a4j:ajax event="keyup" execute="@this" render="out2" />
+ </h:inputText>
+
+ <a4j:outputPanel id="out2" layout="block">
+ <h:outputText rendered="#{not empty opBean2.text}" value="Approved Text: #{opBean2.text}" />
+ </a4j:outputPanel>
+ </h:form>
+ </a4j:outputPanel>
+ </h:panelGrid>
+</ui:composition>
+
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/usage.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,40 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets">
+
+<ui:composition template="/templates/main.xhtml">
+ <ui:define name="body">
+ <p>
+ <b>a4j:outputPanel</b> component designed to provide next features:
+ <ul>
+ <li><b>Automaticall updates</b> of the child content on Ajax requests</li>
+ <li>Wrapper component for <b>conditional rendering of nested elements</b> via Ajax</li>
+ <li><b>Configurable layouts</b>:
+ <ul>
+ <li>inline - rendered as span element</li>
+ <li>block - rendered as div element</li>
+ <li>none - special layout for nested components confitional rendering cases</li>
+ </ul>
+ </li>
+ <li></li>
+ </ul>
+ </p>
+ <fieldset>
+ <legend>Sample</legend>
+ <ui:include src="/richfaces/outputPanel/usage.xhtml" />
+ </fieldset>
+ <p>
+ Next sample shows how you could simply create composite component from
+ standard h:messages and a4j:outputPanel in order to get them updated
+ for any ajax request without render definition.
+ </p>
+ <fieldset>
+ <legend>Sample</legend>
+ <ui:include src="/richfaces/outputPanel/compositemessages.xhtml" />
+ </fieldset>
+ </ui:define>
+</ui:composition>
+
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push/usage.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push/usage.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push/usage.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,48 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:a4j="http://richfaces.org/a4j">
+
+<ui:composition>
+ <h:form>
+ <h:dataTable value="#{choicesBean.choices}" var="choice" id="choiceVotes">
+ <f:facet name="header">
+ <h:outputText value="Voting for favorite fruit" />
+ </f:facet>
+ <h:column>
+ <f:facet name="header">
+ <h:outputText value="Choice name" />
+ </f:facet>
+ <h:outputText value="#{choice.label}" id="choiceLabel" />
+ </h:column>
+ <h:column>
+ <f:facet name="header">
+ <h:outputText value="Current Votes" />
+ </f:facet>
+ <h:outputText value="#{choice.votesCount}" id="choiceVotes" />
+ </h:column>
+ </h:dataTable>
+
+ <a4j:jsFunction name="startPush" action="#{choicesBean.start}" execute="@this" render="push, stop, start"/>
+ <a4j:jsFunction name="stopPush" action="#{choicesBean.stop}" execute="@this" render="push, stop, start"/>
+
+ <h:commandButton onclick="startPush()" value="Start" id="start" disabled="#{choicesBean.enabled}" type="button"/>
+
+ <h:commandButton onclick="stopPush()" type="button" value="Stop" id="stop" disabled="#{!choicesBean.enabled}"/>
+
+ <a4j:outputPanel layout="block" id="tempResults">
+ <h:outputText
+ value="Latest update votes was: #{choicesBean.updateInfo} at #{choicesBean.timeStamp}"
+ rendered="#{choicesBean.enabled}" />
+ </a4j:outputPanel>
+
+ <a4j:push enabled="#{choicesBean.enabled}" interval="1000"
+ eventProducer="#{choicesBean.addListener}" id="push" action="#{choicesBean.processUpdates}">
+ <a4j:ajax render="choiceVotes push tempResults" />
+ </a4j:push>
+ </h:form>
+</ui:composition>
+
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push/usage.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,28 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets">
+
+ <ui:composition template="/templates/main.xhtml">
+ <ui:define name="body">
+ <p>The <b><a4j:push></b> periodically perform AJAX request to
+ server, to simulate 'push' data.</p>
+ <p><b><a4j:push></b> makes request to
+ minimal code only (not to JSF tree) in order to check the presence of
+ messages in the queue. If the message exists the complete request will
+ be performed. The component doesn't poll registered beans but
+ registers EventListener which receives messages about events.</p>
+ <p>Attribute '<b>interval</b>' is used as for poll component. It
+ specifies the interval in ms. for call push request. Simple example of
+ usage:</p>
+ <fieldset>
+ <legend>
+ Push Sample
+ </legend>
+ <ui:include src="/richfaces/push/usage.xhtml" />
+ </fieldset>
+ </ui:define>
+ </ui:composition>
+
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/referencedusage.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/referencedusage.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/referencedusage.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,37 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:a4j="http://richfaces.org/a4j"
+ xmlns:rich="http://java.sun.com/jsf/composite/rich">
+<ui:composition>
+ <h:panelGrid columns="3" width="300px;">
+ <rich:panel>
+ <f:facet name="header">
+ <h:outputText value="User Details Panel" />
+ </f:facet>
+ <h:panelGrid columns="3">
+ <h:outputText value="User name:" />
+ <h:inputText value="#{userBean.name}" >
+ <a4j:ajax status="nameStatus" event="keyup"/>
+ </h:inputText>
+ <a4j:status name="nameStatus">
+ <f:facet name="start">
+ <h:graphicImage value="/images/ai.gif"/>
+ </f:facet>
+ </a4j:status>
+ <h:outputText value="Adress:" />
+ <h:inputText value="#{userBean.address}">
+ <a4j:ajax status="adressStatus" event="keyup"/>
+ </h:inputText>
+ <a4j:status name="adressStatus">
+ <f:facet name="start">
+ <h:graphicImage value="/images/ai.gif"/>
+ </f:facet>
+ </a4j:status>
+ </h:panelGrid>
+ </rich:panel>
+ </h:panelGrid>
+</ui:composition>
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/referencedusage.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/usage.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/usage.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/usage.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,38 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:rich="http://java.sun.com/jsf/composite/rich"
+ xmlns:a4j="http://richfaces.org/a4j">
+
+ <ui:composition>
+ <h:form>
+ <rich:panel id="psnel">
+ <f:facet name="header">
+ <h:outputText value="Panel with status" />
+ </f:facet>
+ <h:panelGrid columns="2">
+ <h:panelGrid columns="2">
+ <f:ajax event="keyup">
+ <h:outputText value="User name:" />
+ <h:inputText value="#{userBean.name}"/>
+ <h:outputText value="Adress:" />
+ <h:inputText value="#{userBean.address}"/>
+ </f:ajax>
+ </h:panelGrid>
+ <a4j:status>
+ <f:facet name="start">
+ <h:graphicImage value="/images/ai.gif"/>
+ </f:facet>
+ </a4j:status>
+ </h:panelGrid>
+ <h:commandButton value="Submit" type="button" action="#{userBean.store}">
+ <f:ajax render="out"/>
+ </h:commandButton>
+ <h:outputText value="#{userBean.recordStatus}" id="out"/>
+ </rich:panel>
+ </h:form>
+ </ui:composition>
+
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/usage.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/viewusage.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/viewusage.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/viewusage.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,48 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:rich="http://java.sun.com/jsf/composite/rich"
+ xmlns:a4j="http://richfaces.org/a4j">
+
+ <ui:composition>
+ <h:panelGrid columns="3">
+ <h:form>
+ <rich:panel id="psnel">
+ <f:facet name="header">
+ <h:outputText value="User Details Panel" />
+ </f:facet>
+ <h:panelGrid columns="2">
+ <f:ajax event="keyup">
+ <h:outputText value="User name:" />
+ <h:inputText value="#{userBean.name}"/>
+ <h:outputText value="Adress:" />
+ <h:inputText value="#{userBean.address}"/>
+ </f:ajax>
+ </h:panelGrid>
+ <h:commandButton value="Submit" type="button" action="#{userBean.store}">
+ <f:ajax render="out"/>
+ </h:commandButton>
+ <h:outputText value="#{userBean.recordStatus}" id="out"/>
+ </rich:panel>
+ </h:form>
+ <h:form>
+ <rich:panel>
+ <f:facet name="header">
+ <h:outputText value="Simple search panel" />
+ </f:facet>
+ <h:inputText value="Search..."/>
+ <h:commandButton value="Submit" type="button">
+ <f:ajax />
+ </h:commandButton>
+ </rich:panel>
+ </h:form>
+ <a4j:status>
+ <f:facet name="start">
+ <h:graphicImage value="/images/ai.gif"/>
+ </f:facet>
+ </a4j:status>
+ </h:panelGrid>
+ </ui:composition>
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/viewusage.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,43 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets">
+
+ <ui:composition template="/templates/main.xhtml">
+ <ui:define name="body">
+ <p>a4j:status is an indicator of an Ajax request. It has two states - start and stop. The start
+ state indicates that an Ajax request is in progress. When Ajax Response comes back,
+ the component switches to the stop stage.
+ </p>
+ <p> Status could be defined:
+ <ul>
+ <li>Default for View</li>
+ <li>Default for form</li>
+ <li>Referenced explicity from the component which sends request</li>
+ </ul>
+ </p>
+ <p>
+ Example of View scoped status
+ </p>
+ <fieldset>
+ <legend>Default view status sample</legend>
+ <ui:include src="/richfaces/status/viewusage.xhtml" />
+ </fieldset>
+ <p>
+ Example of form scoped status
+ </p>
+ <fieldset>
+ <legend>Default form status sample</legend>
+ <ui:include src="/richfaces/status/usage.xhtml" />
+ </fieldset>
+ <p>
+ Example of status which referenced from the components
+ </p>
+ <fieldset>
+ <legend>Referenced status sample</legend>
+ <ui:include src="/richfaces/status/referencedusage.xhtml" />
+ </fieldset>
+ </ui:define>
+ </ui:composition>
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/script/swfobject.js
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/script/swfobject.js (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/script/swfobject.js 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,733 @@
+/*! SWFObject v2.1 <http://code.google.com/p/swfobject/>
+ Copyright (c) 2007-2008 Geoff Stearns, Michael Williams, and Bobby van der Sluis
+ This software is released under the MIT License <http://www.opensource.org/licenses/mit-license.php>
+*/
+
+var swfobject = function() {
+
+ var UNDEF = "undefined",
+ OBJECT = "object",
+ SHOCKWAVE_FLASH = "Shockwave Flash",
+ SHOCKWAVE_FLASH_AX = "ShockwaveFlash.ShockwaveFlash",
+ FLASH_MIME_TYPE = "application/x-shockwave-flash",
+ EXPRESS_INSTALL_ID = "SWFObjectExprInst",
+
+ win = window,
+ doc = document,
+ nav = navigator,
+
+ domLoadFnArr = [],
+ regObjArr = [],
+ objIdArr = [],
+ listenersArr = [],
+ script,
+ timer = null,
+ storedAltContent = null,
+ storedAltContentId = null,
+ isDomLoaded = false,
+ isExpressInstallActive = false;
+
+ /* Centralized function for browser feature detection
+ - Proprietary feature detection (conditional compiling) is used to detect Internet Explorer's features
+ - User agent string detection is only used when no alternative is possible
+ - Is executed directly for optimal performance
+ */
+ var ua = function() {
+ var w3cdom = typeof doc.getElementById != UNDEF && typeof doc.getElementsByTagName != UNDEF && typeof doc.createElement != UNDEF,
+ playerVersion = [0,0,0],
+ d = null;
+ if (typeof nav.plugins != UNDEF && typeof nav.plugins[SHOCKWAVE_FLASH] == OBJECT) {
+ d = nav.plugins[SHOCKWAVE_FLASH].description;
+ if (d && !(typeof nav.mimeTypes != UNDEF && nav.mimeTypes[FLASH_MIME_TYPE] && !nav.mimeTypes[FLASH_MIME_TYPE].enabledPlugin)) { // navigator.mimeTypes["application/x-shockwave-flash"].enabledPlugin indicates whether plug-ins are enabled or disabled in Safari 3+
+ d = d.replace(/^.*\s+(\S+\s+\S+$)/, "$1");
+ playerVersion[0] = parseInt(d.replace(/^(.*)\..*$/, "$1"), 10);
+ playerVersion[1] = parseInt(d.replace(/^.*\.(.*)\s.*$/, "$1"), 10);
+ playerVersion[2] = /r/.test(d) ? parseInt(d.replace(/^.*r(.*)$/, "$1"), 10) : 0;
+ }
+ }
+ else if (typeof win.ActiveXObject != UNDEF) {
+ var a = null, fp6Crash = false;
+ try {
+ a = new ActiveXObject(SHOCKWAVE_FLASH_AX + ".7");
+ }
+ catch(e) {
+ try {
+ a = new ActiveXObject(SHOCKWAVE_FLASH_AX + ".6");
+ playerVersion = [6,0,21];
+ a.AllowScriptAccess = "always"; // Introduced in fp6.0.47
+ }
+ catch(e) {
+ if (playerVersion[0] == 6) {
+ fp6Crash = true;
+ }
+ }
+ if (!fp6Crash) {
+ try {
+ a = new ActiveXObject(SHOCKWAVE_FLASH_AX);
+ }
+ catch(e) {}
+ }
+ }
+ if (!fp6Crash && a) { // a will return null when ActiveX is disabled
+ try {
+ d = a.GetVariable("$version"); // Will crash fp6.0.21/23/29
+ if (d) {
+ d = d.split(" ")[1].split(",");
+ playerVersion = [parseInt(d[0], 10), parseInt(d[1], 10), parseInt(d[2], 10)];
+ }
+ }
+ catch(e) {}
+ }
+ }
+ var u = nav.userAgent.toLowerCase(),
+ p = nav.platform.toLowerCase(),
+ webkit = /webkit/.test(u) ? parseFloat(u.replace(/^.*webkit\/(\d+(\.\d+)?).*$/, "$1")) : false, // returns either the webkit version or false if not webkit
+ ie = false,
+ windows = p ? /win/.test(p) : /win/.test(u),
+ mac = p ? /mac/.test(p) : /mac/.test(u);
+ /*@cc_on
+ ie = true;
+ @if (@_win32)
+ windows = true;
+ @elif (@_mac)
+ mac = true;
+ @end
+ @*/
+ return { w3cdom:w3cdom, pv:playerVersion, webkit:webkit, ie:ie, win:windows, mac:mac };
+ }();
+
+ /* Cross-browser onDomLoad
+ - Based on Dean Edwards' solution: http://dean.edwards.name/weblog/2006/06/again/
+ - Will fire an event as soon as the DOM of a page is loaded (supported by Gecko based browsers - like Firefox -, IE, Opera9+, Safari)
+ */
+ var onDomLoad = function() {
+ if (!ua.w3cdom) {
+ return;
+ }
+ addDomLoadEvent(main);
+ if (ua.ie && ua.win) {
+ try { // Avoid a possible Operation Aborted error
+ doc.write("<scr" + "ipt id=__ie_ondomload defer=true src=//:></scr" + "ipt>"); // String is split into pieces to avoid Norton AV to add code that can cause errors
+ script = getElementById("__ie_ondomload");
+ if (script) {
+ addListener(script, "onreadystatechange", checkReadyState);
+ }
+ }
+ catch(e) {}
+ }
+ if (ua.webkit && typeof doc.readyState != UNDEF) {
+ timer = setInterval(function() { if (/loaded|complete/.test(doc.readyState)) { callDomLoadFunctions(); }}, 10);
+ }
+ if (typeof doc.addEventListener != UNDEF) {
+ doc.addEventListener("DOMContentLoaded", callDomLoadFunctions, null);
+ }
+ addLoadEvent(callDomLoadFunctions);
+ }();
+
+ function checkReadyState() {
+ if (script.readyState == "complete") {
+ script.parentNode.removeChild(script);
+ callDomLoadFunctions();
+ }
+ }
+
+ function callDomLoadFunctions() {
+ if (isDomLoaded) {
+ return;
+ }
+ if (ua.ie && ua.win) { // Test if we can really add elements to the DOM; we don't want to fire it too early
+ var s = createElement("span");
+ try { // Avoid a possible Operation Aborted error
+ var t = doc.getElementsByTagName("body")[0].appendChild(s);
+ t.parentNode.removeChild(t);
+ }
+ catch (e) {
+ return;
+ }
+ }
+ isDomLoaded = true;
+ if (timer) {
+ clearInterval(timer);
+ timer = null;
+ }
+ var dl = domLoadFnArr.length;
+ for (var i = 0; i < dl; i++) {
+ domLoadFnArr[i]();
+ }
+ }
+
+ function addDomLoadEvent(fn) {
+ if (isDomLoaded) {
+ fn();
+ }
+ else {
+ domLoadFnArr[domLoadFnArr.length] = fn; // Array.push() is only available in IE5.5+
+ }
+ }
+
+ /* Cross-browser onload
+ - Based on James Edwards' solution: http://brothercake.com/site/resources/scripts/onload/
+ - Will fire an event as soon as a web page including all of its assets are loaded
+ */
+ function addLoadEvent(fn) {
+ if (typeof win.addEventListener != UNDEF) {
+ win.addEventListener("load", fn, false);
+ }
+ else if (typeof doc.addEventListener != UNDEF) {
+ doc.addEventListener("load", fn, false);
+ }
+ else if (typeof win.attachEvent != UNDEF) {
+ addListener(win, "onload", fn);
+ }
+ else if (typeof win.onload == "function") {
+ var fnOld = win.onload;
+ win.onload = function() {
+ fnOld();
+ fn();
+ };
+ }
+ else {
+ win.onload = fn;
+ }
+ }
+
+ /* Main function
+ - Will preferably execute onDomLoad, otherwise onload (as a fallback)
+ */
+ function main() { // Static publishing only
+ var rl = regObjArr.length;
+ for (var i = 0; i < rl; i++) { // For each registered object element
+ var id = regObjArr[i].id;
+ if (ua.pv[0] > 0) {
+ var obj = getElementById(id);
+ if (obj) {
+ regObjArr[i].width = obj.getAttribute("width") ? obj.getAttribute("width") : "0";
+ regObjArr[i].height = obj.getAttribute("height") ? obj.getAttribute("height") : "0";
+ if (hasPlayerVersion(regObjArr[i].swfVersion)) { // Flash plug-in version >= Flash content version: Houston, we have a match!
+ if (ua.webkit && ua.webkit < 312) { // Older webkit engines ignore the object element's nested param elements
+ fixParams(obj);
+ }
+ setVisibility(id, true);
+ }
+ else if (regObjArr[i].expressInstall && !isExpressInstallActive && hasPlayerVersion("6.0.65") && (ua.win || ua.mac)) { // Show the Adobe Express Install dialog if set by the web page author and if supported (fp6.0.65+ on Win/Mac OS only)
+ showExpressInstall(regObjArr[i]);
+ }
+ else { // Flash plug-in and Flash content version mismatch: display alternative content instead of Flash content
+ displayAltContent(obj);
+ }
+ }
+ }
+ else { // If no fp is installed, we let the object element do its job (show alternative content)
+ setVisibility(id, true);
+ }
+ }
+ }
+
+ /* Fix nested param elements, which are ignored by older webkit engines
+ - This includes Safari up to and including version 1.2.2 on Mac OS 10.3
+ - Fall back to the proprietary embed element
+ */
+ function fixParams(obj) {
+ var nestedObj = obj.getElementsByTagName(OBJECT)[0];
+ if (nestedObj) {
+ var e = createElement("embed"), a = nestedObj.attributes;
+ if (a) {
+ var al = a.length;
+ for (var i = 0; i < al; i++) {
+ if (a[i].nodeName == "DATA") {
+ e.setAttribute("src", a[i].nodeValue);
+ }
+ else {
+ e.setAttribute(a[i].nodeName, a[i].nodeValue);
+ }
+ }
+ }
+ var c = nestedObj.childNodes;
+ if (c) {
+ var cl = c.length;
+ for (var j = 0; j < cl; j++) {
+ if (c[j].nodeType == 1 && c[j].nodeName == "PARAM") {
+ e.setAttribute(c[j].getAttribute("name"), c[j].getAttribute("value"));
+ }
+ }
+ }
+ obj.parentNode.replaceChild(e, obj);
+ }
+ }
+
+ /* Show the Adobe Express Install dialog
+ - Reference: http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=6a253b75
+ */
+ function showExpressInstall(regObj) {
+ isExpressInstallActive = true;
+ var obj = getElementById(regObj.id);
+ if (obj) {
+ if (regObj.altContentId) {
+ var ac = getElementById(regObj.altContentId);
+ if (ac) {
+ storedAltContent = ac;
+ storedAltContentId = regObj.altContentId;
+ }
+ }
+ else {
+ storedAltContent = abstractAltContent(obj);
+ }
+ if (!(/%$/.test(regObj.width)) && parseInt(regObj.width, 10) < 310) {
+ regObj.width = "310";
+ }
+ if (!(/%$/.test(regObj.height)) && parseInt(regObj.height, 10) < 137) {
+ regObj.height = "137";
+ }
+ doc.title = doc.title.slice(0, 47) + " - Flash Player Installation";
+ var pt = ua.ie && ua.win ? "ActiveX" : "PlugIn",
+ dt = doc.title,
+ fv = "MMredirectURL=" + win.location + "&MMplayerType=" + pt + "&MMdoctitle=" + dt,
+ replaceId = regObj.id;
+ // For IE when a SWF is loading (AND: not available in cache) wait for the onload event to fire to remove the original object element
+ // In IE you cannot properly cancel a loading SWF file without breaking browser load references, also obj.onreadystatechange doesn't work
+ if (ua.ie && ua.win && obj.readyState != 4) {
+ var newObj = createElement("div");
+ replaceId += "SWFObjectNew";
+ newObj.setAttribute("id", replaceId);
+ obj.parentNode.insertBefore(newObj, obj); // Insert placeholder div that will be replaced by the object element that loads expressinstall.swf
+ obj.style.display = "none";
+ var fn = function() {
+ obj.parentNode.removeChild(obj);
+ };
+ addListener(win, "onload", fn);
+ }
+ createSWF({ data:regObj.expressInstall, id:EXPRESS_INSTALL_ID, width:regObj.width, height:regObj.height }, { flashvars:fv }, replaceId);
+ }
+ }
+
+ /* Functions to abstract and display alternative content
+ */
+ function displayAltContent(obj) {
+ if (ua.ie && ua.win && obj.readyState != 4) {
+ // For IE when a SWF is loading (AND: not available in cache) wait for the onload event to fire to remove the original object element
+ // In IE you cannot properly cancel a loading SWF file without breaking browser load references, also obj.onreadystatechange doesn't work
+ var el = createElement("div");
+ obj.parentNode.insertBefore(el, obj); // Insert placeholder div that will be replaced by the alternative content
+ el.parentNode.replaceChild(abstractAltContent(obj), el);
+ obj.style.display = "none";
+ var fn = function() {
+ obj.parentNode.removeChild(obj);
+ };
+ addListener(win, "onload", fn);
+ }
+ else {
+ obj.parentNode.replaceChild(abstractAltContent(obj), obj);
+ }
+ }
+
+ function abstractAltContent(obj) {
+ var ac = createElement("div");
+ if (ua.win && ua.ie) {
+ ac.innerHTML = obj.innerHTML;
+ }
+ else {
+ var nestedObj = obj.getElementsByTagName(OBJECT)[0];
+ if (nestedObj) {
+ var c = nestedObj.childNodes;
+ if (c) {
+ var cl = c.length;
+ for (var i = 0; i < cl; i++) {
+ if (!(c[i].nodeType == 1 && c[i].nodeName == "PARAM") && !(c[i].nodeType == 8)) {
+ ac.appendChild(c[i].cloneNode(true));
+ }
+ }
+ }
+ }
+ }
+ return ac;
+ }
+
+ /* Cross-browser dynamic SWF creation
+ */
+ function createSWF(attObj, parObj, id) {
+ var r, el = getElementById(id);
+ if (el) {
+ if (typeof attObj.id == UNDEF) { // if no 'id' is defined for the object element, it will inherit the 'id' from the alternative content
+ attObj.id = id;
+ }
+ if (ua.ie && ua.win) { // IE, the object element and W3C DOM methods do not combine: fall back to outerHTML
+ var att = "";
+ for (var i in attObj) {
+ if (attObj[i] != Object.prototype[i]) { // Filter out prototype additions from other potential libraries, like Object.prototype.toJSONString = function() {}
+ if (i.toLowerCase() == "data") {
+ parObj.movie = attObj[i];
+ }
+ else if (i.toLowerCase() == "styleclass") { // 'class' is an ECMA4 reserved keyword
+ att += ' class="' + attObj[i] + '"';
+ }
+ else if (i.toLowerCase() != "classid") {
+ att += ' ' + i + '="' + attObj[i] + '"';
+ }
+ }
+ }
+ var par = "";
+ for (var j in parObj) {
+ if (parObj[j] != Object.prototype[j]) { // Filter out prototype additions from other potential libraries
+ par += '<param name="' + j + '" value="' + parObj[j] + '" />';
+ }
+ }
+ el.outerHTML = '<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"' + att + '>' + par + '</object>';
+ objIdArr[objIdArr.length] = attObj.id; // Stored to fix object 'leaks' on unload (dynamic publishing only)
+ r = getElementById(attObj.id);
+ }
+ else if (ua.webkit && ua.webkit < 312) { // Older webkit engines ignore the object element's nested param elements: fall back to the proprietary embed element
+ var e = createElement("embed");
+ e.setAttribute("type", FLASH_MIME_TYPE);
+ for (var k in attObj) {
+ if (attObj[k] != Object.prototype[k]) { // Filter out prototype additions from other potential libraries
+ if (k.toLowerCase() == "data") {
+ e.setAttribute("src", attObj[k]);
+ }
+ else if (k.toLowerCase() == "styleclass") { // 'class' is an ECMA4 reserved keyword
+ e.setAttribute("class", attObj[k]);
+ }
+ else if (k.toLowerCase() != "classid") { // Filter out IE specific attribute
+ e.setAttribute(k, attObj[k]);
+ }
+ }
+ }
+ for (var l in parObj) {
+ if (parObj[l] != Object.prototype[l]) { // Filter out prototype additions from other potential libraries
+ if (l.toLowerCase() != "movie") { // Filter out IE specific param element
+ e.setAttribute(l, parObj[l]);
+ }
+ }
+ }
+ el.parentNode.replaceChild(e, el);
+ r = e;
+ }
+ else { // Well-behaving browsers
+ var o = createElement(OBJECT);
+ o.setAttribute("type", FLASH_MIME_TYPE);
+ for (var m in attObj) {
+ if (attObj[m] != Object.prototype[m]) { // Filter out prototype additions from other potential libraries
+ if (m.toLowerCase() == "styleclass") { // 'class' is an ECMA4 reserved keyword
+ o.setAttribute("class", attObj[m]);
+ }
+ else if (m.toLowerCase() != "classid") { // Filter out IE specific attribute
+ o.setAttribute(m, attObj[m]);
+ }
+ }
+ }
+ for (var n in parObj) {
+ if (parObj[n] != Object.prototype[n] && n.toLowerCase() != "movie") { // Filter out prototype additions from other potential libraries and IE specific param element
+ createObjParam(o, n, parObj[n]);
+ }
+ }
+ el.parentNode.replaceChild(o, el);
+ r = o;
+ }
+ }
+ return r;
+ }
+
+ function createObjParam(el, pName, pValue) {
+ var p = createElement("param");
+ p.setAttribute("name", pName);
+ p.setAttribute("value", pValue);
+ el.appendChild(p);
+ }
+
+ /* Cross-browser SWF removal
+ - Especially needed to safely and completely remove a SWF in Internet Explorer
+ */
+ function removeSWF(id) {
+ var obj = getElementById(id);
+ if (obj && (obj.nodeName == "OBJECT" || obj.nodeName == "EMBED")) {
+ if (ua.ie && ua.win) {
+ if (obj.readyState == 4) {
+ removeObjectInIE(id);
+ }
+ else {
+ win.attachEvent("onload", function() {
+ removeObjectInIE(id);
+ });
+ }
+ }
+ else {
+ obj.parentNode.removeChild(obj);
+ }
+ }
+ }
+
+ function removeObjectInIE(id) {
+ var obj = getElementById(id);
+ if (obj) {
+ for (var i in obj) {
+ if (typeof obj[i] == "function") {
+ obj[i] = null;
+ }
+ }
+ obj.parentNode.removeChild(obj);
+ }
+ }
+
+ /* Functions to optimize JavaScript compression
+ */
+ function getElementById(id) {
+ var el = null;
+ try {
+ el = doc.getElementById(id);
+ }
+ catch (e) {}
+ return el;
+ }
+
+ function createElement(el) {
+ return doc.createElement(el);
+ }
+
+ /* Updated attachEvent function for Internet Explorer
+ - Stores attachEvent information in an Array, so on unload the detachEvent functions can be called to avoid memory leaks
+ */
+ function addListener(target, eventType, fn) {
+ target.attachEvent(eventType, fn);
+ listenersArr[listenersArr.length] = [target, eventType, fn];
+ }
+
+ /* Flash Player and SWF content version matching
+ */
+ function hasPlayerVersion(rv) {
+ var pv = ua.pv, v = rv.split(".");
+ v[0] = parseInt(v[0], 10);
+ v[1] = parseInt(v[1], 10) || 0; // supports short notation, e.g. "9" instead of "9.0.0"
+ v[2] = parseInt(v[2], 10) || 0;
+ return (pv[0] > v[0] || (pv[0] == v[0] && pv[1] > v[1]) || (pv[0] == v[0] && pv[1] == v[1] && pv[2] >= v[2])) ? true : false;
+ }
+
+ /* Cross-browser dynamic CSS creation
+ - Based on Bobby van der Sluis' solution: http://www.bobbyvandersluis.com/articles/dynamicCSS.php
+ */
+ function createCSS(sel, decl) {
+ if (ua.ie && ua.mac) {
+ return;
+ }
+ var h = doc.getElementsByTagName("head")[0], s = createElement("style");
+ s.setAttribute("type", "text/css");
+ s.setAttribute("media", "screen");
+ if (!(ua.ie && ua.win) && typeof doc.createTextNode != UNDEF) {
+ s.appendChild(doc.createTextNode(sel + " {" + decl + "}"));
+ }
+ h.appendChild(s);
+ if (ua.ie && ua.win && typeof doc.styleSheets != UNDEF && doc.styleSheets.length > 0) {
+ var ls = doc.styleSheets[doc.styleSheets.length - 1];
+ if (typeof ls.addRule == OBJECT) {
+ try {
+ ls.addRule(sel, decl);
+ } catch(e) {}
+ }
+ }
+ }
+
+ function setVisibility(id, isVisible) {
+ var v = isVisible ? "visible" : "hidden";
+ if (isDomLoaded && getElementById(id)) {
+ getElementById(id).style.visibility = v;
+ }
+ else {
+ createCSS("#" + id, "visibility:" + v);
+ }
+ }
+
+ /* Filter to avoid XSS attacks
+ */
+ function urlEncodeIfNecessary(s) {
+ var regex = /[\\\"<>\.;]/;
+ var hasBadChars = regex.exec(s) != null;
+ return hasBadChars ? encodeURIComponent(s) : s;
+ }
+
+ /* Release memory to avoid memory leaks caused by closures, fix hanging audio/video threads and force open sockets/NetConnections to disconnect (Internet Explorer only)
+ */
+ var cleanup = function() {
+ if (ua.ie && ua.win) {
+ window.attachEvent("onunload", function() {
+ // remove listeners to avoid memory leaks
+ var ll = listenersArr.length;
+ for (var i = 0; i < ll; i++) {
+ listenersArr[i][0].detachEvent(listenersArr[i][1], listenersArr[i][2]);
+ }
+ // cleanup dynamically embedded objects to fix audio/video threads and force open sockets and NetConnections to disconnect
+ var il = objIdArr.length;
+ for (var j = 0; j < il; j++) {
+ removeSWF(objIdArr[j]);
+ }
+ // cleanup library's main closures to avoid memory leaks
+ for (var k in ua) {
+ ua[k] = null;
+ }
+ ua = null;
+ for (var l in swfobject) {
+ swfobject[l] = null;
+ }
+ swfobject = null;
+ });
+ }
+ }();
+
+
+ return {
+ /* Public API
+ - Reference: http://code.google.com/p/swfobject/wiki/SWFObject_2_0_documentation
+ */
+ registerObject: function(objectIdStr, swfVersionStr, xiSwfUrlStr) {
+ if (!ua.w3cdom || !objectIdStr || !swfVersionStr) {
+ return;
+ }
+ var regObj = {};
+ regObj.id = objectIdStr;
+ regObj.swfVersion = swfVersionStr;
+ regObj.expressInstall = xiSwfUrlStr ? xiSwfUrlStr : false;
+ regObjArr[regObjArr.length] = regObj;
+ setVisibility(objectIdStr, false);
+ },
+
+ getObjectById: function(objectIdStr) {
+ var r = null;
+ if (ua.w3cdom) {
+ var o = getElementById(objectIdStr);
+ if (o) {
+ var n = o.getElementsByTagName(OBJECT)[0];
+ if (!n || (n && typeof o.SetVariable != UNDEF)) {
+ r = o;
+ }
+ else if (typeof n.SetVariable != UNDEF) {
+ r = n;
+ }
+ }
+ }
+ return r;
+ },
+
+ embedSWF: function(swfUrlStr, replaceElemIdStr, widthStr, heightStr, swfVersionStr, xiSwfUrlStr, flashvarsObj, parObj, attObj) {
+ if (!ua.w3cdom || !swfUrlStr || !replaceElemIdStr || !widthStr || !heightStr || !swfVersionStr) {
+ return;
+ }
+ widthStr += ""; // Auto-convert to string
+ heightStr += "";
+ if (hasPlayerVersion(swfVersionStr)) {
+ setVisibility(replaceElemIdStr, false);
+ var att = {};
+ if (attObj && typeof attObj === OBJECT) {
+ for (var i in attObj) {
+ if (attObj[i] != Object.prototype[i]) { // Filter out prototype additions from other potential libraries
+ att[i] = attObj[i];
+ }
+ }
+ }
+ att.data = swfUrlStr;
+ att.width = widthStr;
+ att.height = heightStr;
+ var par = {};
+ if (parObj && typeof parObj === OBJECT) {
+ for (var j in parObj) {
+ if (parObj[j] != Object.prototype[j]) { // Filter out prototype additions from other potential libraries
+ par[j] = parObj[j];
+ }
+ }
+ }
+ if (flashvarsObj && typeof flashvarsObj === OBJECT) {
+ for (var k in flashvarsObj) {
+ if (flashvarsObj[k] != Object.prototype[k]) { // Filter out prototype additions from other potential libraries
+ if (typeof par.flashvars != UNDEF) {
+ par.flashvars += "&" + k + "=" + flashvarsObj[k];
+ }
+ else {
+ par.flashvars = k + "=" + flashvarsObj[k];
+ }
+ }
+ }
+ }
+ addDomLoadEvent(function() {
+ createSWF(att, par, replaceElemIdStr);
+ if (att.id == replaceElemIdStr) {
+ setVisibility(replaceElemIdStr, true);
+ }
+ });
+ }
+ else if (xiSwfUrlStr && !isExpressInstallActive && hasPlayerVersion("6.0.65") && (ua.win || ua.mac)) {
+ isExpressInstallActive = true; // deferred execution
+ setVisibility(replaceElemIdStr, false);
+ addDomLoadEvent(function() {
+ var regObj = {};
+ regObj.id = regObj.altContentId = replaceElemIdStr;
+ regObj.width = widthStr;
+ regObj.height = heightStr;
+ regObj.expressInstall = xiSwfUrlStr;
+ showExpressInstall(regObj);
+ });
+ }
+ },
+
+ getFlashPlayerVersion: function() {
+ return { major:ua.pv[0], minor:ua.pv[1], release:ua.pv[2] };
+ },
+
+ hasFlashPlayerVersion: hasPlayerVersion,
+
+ createSWF: function(attObj, parObj, replaceElemIdStr) {
+ if (ua.w3cdom) {
+ return createSWF(attObj, parObj, replaceElemIdStr);
+ }
+ else {
+ return undefined;
+ }
+ },
+
+ removeSWF: function(objElemIdStr) {
+ if (ua.w3cdom) {
+ removeSWF(objElemIdStr);
+ }
+ },
+
+ createCSS: function(sel, decl) {
+ if (ua.w3cdom) {
+ createCSS(sel, decl);
+ }
+ },
+
+ addDomLoadEvent: addDomLoadEvent,
+
+ addLoadEvent: addLoadEvent,
+
+ getQueryParamValue: function(param) {
+ var q = doc.location.search || doc.location.hash;
+ if (param == null) {
+ return urlEncodeIfNecessary(q);
+ }
+ if (q) {
+ var pairs = q.substring(1).split("&");
+ for (var i = 0; i < pairs.length; i++) {
+ if (pairs[i].substring(0, pairs[i].indexOf("=")) == param) {
+ return urlEncodeIfNecessary(pairs[i].substring((pairs[i].indexOf("=") + 1)));
+ }
+ }
+ }
+ return "";
+ },
+
+ // For internal usage only
+ expressInstallCallback: function() {
+ if (isExpressInstallActive && storedAltContent) {
+ var obj = getElementById(EXPRESS_INSTALL_ID);
+ if (obj) {
+ obj.parentNode.replaceChild(storedAltContent, obj);
+ if (storedAltContentId) {
+ setVisibility(storedAltContentId, true);
+ if (ua.ie && ua.win) {
+ storedAltContent.style.display = "block";
+ }
+ }
+ storedAltContent = null;
+ storedAltContentId = null;
+ isExpressInstallActive = false;
+ }
+ }
+ }
+ };
+}();
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/script/swfobject.js
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/includes/navigation.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/includes/navigation.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/includes/navigation.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,32 @@
+<ui:composition xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:a4j="http://richfaces.org/a4j"
+ xmlns:rich="http://java.sun.com/jsf/composite/rich">
+ <rich:panel>
+ <f:facet name="header">
+ <h:outputText value="Navigation" />
+ </f:facet>
+ <h:panelGrid columns="1">
+ <h:outputLink
+ value="#{facesContext.externalContext.requestContextPath}/richfaces/ajax.jsf">a4j:ajax</h:outputLink>
+ <h:outputLink
+ value="#{facesContext.externalContext.requestContextPath}/richfaces/jsFunction.jsf">a4j:jsFunction</h:outputLink>
+ <h:outputLink
+ value="#{facesContext.externalContext.requestContextPath}/richfaces/mediaOutput.jsf">a4j:mediaOutput</h:outputLink>
+ <h:outputLink
+ value="#{facesContext.externalContext.requestContextPath}/richfaces/push.jsf">a4j:push</h:outputLink>
+ <h:outputLink
+ value="#{facesContext.externalContext.requestContextPath}/richfaces/status.jsf">a4j:status</h:outputLink>
+ <h:outputLink
+ value="#{facesContext.externalContext.requestContextPath}/richfaces/outputPanel.jsf">a4j:outputPanel</h:outputLink>
+ <h:outputLink
+ value="#{facesContext.externalContext.requestContextPath}/richfaces/commandButton.jsf">a4j:commandButton</h:outputLink>
+ <h:outputLink
+ value="#{facesContext.externalContext.requestContextPath}/richfaces/commandLink.jsf">a4j:commandLink</h:outputLink>
+ <h:outputLink
+ value="#{facesContext.externalContext.requestContextPath}/richfaces/log.jsf">a4j:log</h:outputLink>
+ </h:panelGrid>
+ </rich:panel>
+</ui:composition>
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/includes/navigation.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/main.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/main.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/main.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,26 @@
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:rich="http://java.sun.com/jsf/composite/rich">
+<h:head>
+</h:head>
+<h:body>
+ <ui:composition>
+ <rich:page id="page">
+ <f:facet name="header">
+ <h1>Welcome to RichFaces demo!</h1>
+ </f:facet>
+ <f:facet name="sidebar">
+ <ui:include src="/templates/includes/navigation.xhtml" />
+ </f:facet>
+ <ui:insert name="body">
+ Body content missed
+ </ui:insert>
+ <f:facet name="footer">
+ footer
+ </f:facet>
+ </rich:page>
+ </ui:composition>
+</h:body>
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/main.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/welcome.xhtml
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/welcome.xhtml (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/welcome.xhtml 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,14 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:ui="http://java.sun.com/jsf/facelets">
+
+ <ui:composition template="/templates/main.xhtml">
+ <ui:define name="body">
+ Welcome To RichFaces 4.x Demo
+ </ui:define>
+
+ </ui:composition>
+
+</html>
\ No newline at end of file
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/welcome.xhtml
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Modified: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java 2010-03-03 14:54:26 UTC (rev 20617)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java 2010-03-03 15:03:40 UTC (rev 20618)
@@ -70,6 +70,7 @@
import org.jboss.tools.jsf.vpe.jsf.test.jbide.JBIDE4509Test;
import org.jboss.tools.jsf.vpe.jsf.test.jbide.JBIDE4510Test;
import org.jboss.tools.jsf.vpe.jsf.test.jbide.JBIDE4534Test;
+import org.jboss.tools.jsf.vpe.jsf.test.jbide.JBIDE5920Test;
import org.jboss.tools.jsf.vpe.jsf.test.jbide.MessageResolutionInPreviewTabTest;
import org.jboss.tools.jsf.vpe.jsf.test.jbide.NaturesChecker_JBIDE5701;
import org.jboss.tools.jsf.vpe.jsf.test.jbide.OpenOnInJarPackageFragment_JBIDE5682;
@@ -119,11 +120,13 @@
public static final String IMPORT_NATURES_CHECKER_PROJECT = "naturesCheckTest"; //$NON-NLS-1$
public static final String IMPORT_JSF_LOCALES_PROJECT_NAME = "jsfLocales"; //$NON-NLS-1$
public static final String IMPORT_JBIDE5460_PROJECT_NAME = "JBIDE5460TestProject"; //$NON-NLS-1$
+ public static final String IMPORT_TEST_WITH_2_URL_PATTERNS_PROJECT_NAME = "TestWith2URLPatterns"; //$NON-NLS-1$
public static Test suite() {
TestSuite suite = new TestSuite("Tests for Vpe Jsf components"); //$NON-NLS-1$
// $JUnit-BEGIN$
+ suite.addTestSuite(JBIDE5920Test.class);
suite.addTestSuite(RenderFacetAndInsertChildrenTest.class);
suite.addTestSuite(EditFontFamilyTest_JBIDE5872.class);
suite.addTestSuite(ChangeMessageBundleTest_JBIDE5818.class);
@@ -256,6 +259,11 @@
jsfLocalesProject.setImportProjectPath(JsfTestPlugin.getPluginResourcePath());
projectToImport.add(jsfLocalesProject);
+ ImportBean testWith2URLPatternsProject = new ImportBean();
+ testWith2URLPatternsProject.setImportProjectName(JsfAllTests.IMPORT_TEST_WITH_2_URL_PATTERNS_PROJECT_NAME);
+ testWith2URLPatternsProject.setImportProjectPath(JsfTestPlugin.getPluginResourcePath());
+ projectToImport.add(testWith2URLPatternsProject);
+
return new VpeTestSetup(suite, projectToImport);
}
}
Added: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE5920Test.java
===================================================================
--- branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE5920Test.java (rev 0)
+++ branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE5920Test.java 2010-03-03 15:03:40 UTC (rev 20618)
@@ -0,0 +1,59 @@
+/*******************************************************************************
+ * Copyright (c) 2007-2009 Red Hat, Inc.
+ * Distributed under license by Red Hat, Inc. All rights reserved.
+ * This program is made available under the terms of the
+ * Eclipse Public License v1.0 which accompanies this distribution,
+ * and is available at http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributor:
+ * Red Hat, Inc. - initial API and implementation
+ ******************************************************************************/
+package org.jboss.tools.jsf.vpe.jsf.test.jbide;
+
+import org.eclipse.core.resources.IFile;
+import org.eclipse.core.resources.IProject;
+import org.eclipse.ui.IEditorDescriptor;
+import org.eclipse.ui.IEditorInput;
+import org.eclipse.ui.IEditorRegistry;
+import org.eclipse.ui.IWorkbench;
+import org.eclipse.ui.PlatformUI;
+import org.eclipse.ui.editors.text.EditorsUI;
+import org.eclipse.ui.part.FileEditorInput;
+import org.jboss.tools.jsf.vpe.jsf.test.JsfAllTests;
+import org.jboss.tools.vpe.ui.test.OpenOnUtil;
+import org.jboss.tools.vpe.ui.test.ProjectsLoader;
+import org.jboss.tools.vpe.ui.test.VpeTest;
+
+/**
+ * @author V.I.Kabanovich
+ *
+ */
+public class JBIDE5920Test extends VpeTest{
+
+ public JBIDE5920Test(String name) {
+ super(name);
+ }
+
+ //test for https://jira.jboss.org/jira/browse/JBIDE-5920
+ public void testOpenOnInProjectWith2URLPatterns() throws Throwable{
+ IProject project = ProjectsLoader.getInstance()
+ .getProject(JsfAllTests.IMPORT_TEST_WITH_2_URL_PATTERNS_PROJECT_NAME);
+ IFile file = (IFile) project.findMember("WebContent/index.jsp"); //$NON-NLS-1$
+ IEditorInput editorInput = new FileEditorInput(file);
+ OpenOnUtil.checkOpenOnInEditor(editorInput, getEditorId(file.getName()), 5, 30, "welcome.xhtml"); //$NON-NLS-1$
+
+ file = (IFile) project.findMember("WebContent/welcome.xhtml"); //$NON-NLS-1$
+ editorInput = new FileEditorInput(file);
+ OpenOnUtil.checkOpenOnInEditor(editorInput, getEditorId(file.getName()), 7, 43, "main.xhtml"); //$NON-NLS-1$
+ }
+
+ private static final String getEditorId(String filename) {
+ IWorkbench workbench = PlatformUI.getWorkbench();
+ IEditorRegistry editorRegistry = workbench.getEditorRegistry();
+ IEditorDescriptor descriptor = editorRegistry
+ .getDefaultEditor(filename);
+ if (descriptor != null)
+ return descriptor.getId();
+ return EditorsUI.DEFAULT_TEXT_EDITOR_ID;
+ }
+}
Property changes on: branches/jbosstools-3.1.x/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE5920Test.java
___________________________________________________________________
Name: svn:mime-type
+ text/plain
14 years, 2 months
- 1
- 0
JBoss Tools SVN: r20617 - in trunk/documentation/jboss-tools-docs: index/en and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2010-03-03 09:54:26 -0500 (Wed, 03 Mar 2010)
New Revision: 20617
Modified:
trunk/documentation/jboss-tools-docs/all-guides.xml
trunk/documentation/jboss-tools-docs/index/en/master.xml
trunk/documentation/jboss-tools-docs/pom.xml
Log:
<html><head><meta name="qrichtext" content="1" /></head><body style="font-size:9pt;font-family:Sans Serif">
<p>https://jira.jboss.org/jira/browse/JBDS-1107 -Added Beginners Guide to doc bundle</p>
</body></html>
Modified: trunk/documentation/jboss-tools-docs/all-guides.xml
===================================================================
--- trunk/documentation/jboss-tools-docs/all-guides.xml 2010-03-03 14:26:45 UTC (rev 20616)
+++ trunk/documentation/jboss-tools-docs/all-guides.xml 2010-03-03 14:54:26 UTC (rev 20617)
@@ -33,7 +33,7 @@
<fileMode>0644</fileMode>
<directoryMode>0755</directoryMode>
</fileSet>
- <fileSet>
+ <!--fileSet>
<directory>index/target/docbook/publish/en-US/html_single/</directory>
<outputDirectory>../</outputDirectory>
<filtered>false</filtered>
@@ -45,7 +45,7 @@
<useDefaultExcludes>true</useDefaultExcludes>
<fileMode>0644</fileMode>
<directoryMode>0755</directoryMode>
- </fileSet>
+ </fileSet-->
<fileSet>
<directory>../guides/Exadel-migration/target/docbook/publish/en-US</directory>
<outputDirectory>/Exadel-migration</outputDirectory>
@@ -71,6 +71,19 @@
<useDefaultExcludes>true</useDefaultExcludes>
<fileMode>0644</fileMode>
<directoryMode>0755</directoryMode>
+ </fileSet>
+ <fileSet>
+ <directory>../guides/Beginners_Guide/target/docbook/publish/en-US</directory>
+ <outputDirectory>/beginners_guide</outputDirectory>
+ <filtered>false</filtered>
+ <lineEnding>keep</lineEnding>
+ <includes>
+ <include>**/*.*</include>
+ </includes>
+ <useStrictFiltering>false</useStrictFiltering>
+ <useDefaultExcludes>true</useDefaultExcludes>
+ <fileMode>0644</fileMode>
+ <directoryMode>0755</directoryMode>
</fileSet>
<!--fileSet>
<directory>../guides/GettingStartedGuide/en</directory>
@@ -358,4 +371,4 @@
</fileSet>
</fileSets>
-</assembly>
\ No newline at end of file
+</assembly>
Modified: trunk/documentation/jboss-tools-docs/index/en/master.xml
===================================================================
--- trunk/documentation/jboss-tools-docs/index/en/master.xml 2010-03-03 14:26:45 UTC (rev 20616)
+++ trunk/documentation/jboss-tools-docs/index/en/master.xml 2010-03-03 14:54:26 UTC (rev 20617)
@@ -21,8 +21,15 @@
>(pdf)</ulink>
</primaryie>
</indexentry>
-
<indexentry>
+ <primaryie>Beginners Guide <ulink
+ url="en/beginners_guide/html/index.html">(html)</ulink>
+ <ulink url="en/beginners_guide/html_single/index.html">(html single)</ulink>
+ <ulink url="en/beginners_guide/pdf/Beginners_Guide.pdf"
+ >(pdf)</ulink>
+ </primaryie>
+ </indexentry>
+ <indexentry>
<primaryie>Seam Dev Tools Reference Guide <ulink url="en/seam/html/index.html"
>(html)</ulink>
<ulink url="en/seam/html_single/index.html">(html single)</ulink>
Modified: trunk/documentation/jboss-tools-docs/pom.xml
===================================================================
--- trunk/documentation/jboss-tools-docs/pom.xml 2010-03-03 14:26:45 UTC (rev 20616)
+++ trunk/documentation/jboss-tools-docs/pom.xml 2010-03-03 14:54:26 UTC (rev 20617)
@@ -11,11 +11,12 @@
<name>All_Userguides</name>
<modules>
- <!--module>../jbosstools-docbook-xslt</module>
- <module>../jbosstools-jdocbook-style</module-->
+ <!--<module>../jbosstools-docbook-xslt</module>
+ <module>../jbosstools-jdocbook-style</module>-->
<module>../guides/Exadel-migration</module>
<module>../guides/GettingStartedGuide</module>
- <module>../../as/docs/reference</module>
+ <module>../guides/Beginners_Guide</module>
+ <!--<module>../../as/docs/reference</module>
<module>../../hibernatetools/docs/reference</module>
<module>../../jbpm/docs/reference</module>
<module>../../jsf/docs/userguide</module>
@@ -33,7 +34,7 @@
<module>../../smooks/docs/reference</module>
<module>../../jbpm/docs/converter_ref</module>
<module>../../jmx/docs/reference</module>
- <module>../../bpel/docs/reference</module>
+ <module>../../bpel/docs/reference</module>-->
<module>index</module>
@@ -50,7 +51,7 @@
<descriptor>all-guides.xml</descriptor>
</descriptors>
<finalName>en</finalName>
- <outputDirectory>nightly-docs</outputDirectory>
+ <outputDirectory>${pom.basedir}/nightly-docs</outputDirectory>
<appendAssemblyId>false</appendAssemblyId>
<ignoreDirFormatExtensions>true</ignoreDirFormatExtensions>
</configuration>
14 years, 2 months
- 1
- 0
JBoss Tools SVN: r20616 - in branches/jbosstools-3.1.x/portlet/docs/reference: en and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2010-03-03 09:26:45 -0500 (Wed, 03 Mar 2010)
New Revision: 20616
Modified:
branches/jbosstools-3.1.x/portlet/docs/reference/en/master.xml
branches/jbosstools-3.1.x/portlet/docs/reference/en/master_output.xml
branches/jbosstools-3.1.x/portlet/docs/reference/pom.xml
Log:
<html><head><meta name="qrichtext" content="1" /></head><body style="font-size:9pt;font-family:Sans Serif">
<p>https://jira.jboss.org/jira/browse/JBDS-1107 -Updated docs source files here with the ones for JBDS 3.0.0 GA release. </p>
<p></p>
</body></html>
Modified: branches/jbosstools-3.1.x/portlet/docs/reference/en/master.xml
===================================================================
--- branches/jbosstools-3.1.x/portlet/docs/reference/en/master.xml 2010-03-03 14:26:39 UTC (rev 20615)
+++ branches/jbosstools-3.1.x/portlet/docs/reference/en/master.xml 2010-03-03 14:26:45 UTC (rev 20616)
@@ -45,12 +45,12 @@
<copyright>
<year>2008</year>
- <year>2009</year>
+ <year>2009</year>
<year>2010</year>
<holder>JBoss by Red Hat</holder>
</copyright>
<releaseinfo>
- Version: 1.1.0.CR1
+ Version: 1.1.0.GA
</releaseinfo>
<abstract>
Modified: branches/jbosstools-3.1.x/portlet/docs/reference/en/master_output.xml
===================================================================
--- branches/jbosstools-3.1.x/portlet/docs/reference/en/master_output.xml 2010-03-03 14:26:39 UTC (rev 20615)
+++ branches/jbosstools-3.1.x/portlet/docs/reference/en/master_output.xml 2010-03-03 14:26:45 UTC (rev 20616)
@@ -4,10 +4,12 @@
[<!ENTITY intro SYSTEM "modules/intro.xml">
<!ENTITY installation SYSTEM "modules/installation.xml">
+<!ENTITY portlet_tools_tasks SYSTEM "modules/portlet_tools_tasks.xml">
<!ENTITY starting_project SYSTEM "modules/starting_project.xml">
<!ENTITY jsf_portlet SYSTEM "modules/jsf_portlet.xml">
<!ENTITY seam_portlet SYSTEM "modules/seam_portlet.xml">
-<!ENTITY portlets_to_nonWTP_projects SYSTEM "modules/portlets_to_nonWTP_projects.xml">
+<!ENTITY reference SYSTEM "modules/reference.xml">
+<!ENTITY summary SYSTEM "modules/summary.xml">
<!ENTITY seamlink "../../seam/html_single/index.html">
<!ENTITY aslink "../../as/html_single/index.html">
@@ -20,982 +22,1677 @@
<!ENTITY jsftutoriallink "../../jsf_tools_tutorial/html_single/index.html">
<!ENTITY strutsreflink "../../struts_tools_ref_guide/html_single/index.html">
<!ENTITY strutstutoriallink "../../struts_tools_tutorial/html_single/index.html">
-]><book xmlns:diffmk="http://diffmk.sf.net/ns/diff">
-
- <bookinfo>
- <title>JBoss Portal Tools Reference Guide</title>
- <corpauthor>
- <inlinemediaobject>
- <imageobject role="fo">
- <imagedata fileref="images/jbosstools_logo.png" format="PNG"></imagedata>
- </imageobject>
- <imageobject role="html">
- <imagedata></imagedata>
- </imageobject>
- </inlinemediaobject>
- </corpauthor>
- <author><firstname>Olga</firstname><surname>Chikvina</surname></author>
- <author><firstname>Snjezana</firstname><surname>Peco</surname><email>snjezana.peco(a)redhat.com</email></author>
- <author><firstname>Svetlana</firstname><surname>Mukhina</surname><email>smukhina(a)exadel.com</email></author>
- <author><firstname>Thomas</firstname><surname>Heute</surname><email>theute(a)jboss.org</email></author>
-
- <pubdate>September 2008</pubdate>
- <copyright>
- <year>2008</year>
- <year>2009</year>
- <holder>JBoss by Red Hat</holder>
- </copyright>
- <releaseinfo><diffmk:wrapper diffmk:change="changed">
- Version: 1.1.0.CR1
- </diffmk:wrapper></releaseinfo>
-
-<abstract>
- <title></title>
- <para>
- <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/jboss_portal_tools_r...">PDF version</ulink>
- </para>
-</abstract>
-
-
- </bookinfo>
- <toc></toc>
-
-
-
-<chapter id="intro" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/portlet/docs/reference/en/modules/intro.xml" xreflabel="intro">
- <?dbhtml filename="intro.html"?>
- <title>Introduction</title>
-
- <para>Starting from 3.0.0.Alpha1 version, JBoss set of plugins extends <property moreinfo="none">JBoss Portal</property>
- features. Thus, this guide is intended to explain you how to manage the functionality
- <property moreinfo="none">JBoss Tools</property> provide to ease the development with <property moreinfo="none">JBoss
- Portal</property>.</para>
-
- <section id="preface">
- <title>Preface</title>
- <para><property moreinfo="none">JBoss Portal</property> provides an open source platform for hosting and
- serving a portal's Web interface, publishing and managing its content, and customizing
- its experience. It supports a wide range of features, including standard portlets,
- single sign-on, clustering, and internationalization.</para>
- </section>
-
- <section id="key_features">
- <title>Key Features</title>
- <para>The next table lists key features supplied by <property moreinfo="none">JBoss Portal Tools</property>.</para>
-
- <table>
- <title>Key Functionality of JBoss Portal Tools</title>
- <tgroup cols="3">
-
- <colspec align="left" colnum="1" colwidth="1*"></colspec>
- <colspec colnum="2" colwidth="5*"></colspec>
- <colspec align="left" colnum="3" colwidth="1*"></colspec>
-
- <thead>
- <row>
- <entry>Feature</entry>
- <entry>Benefit</entry>
- <entry>Chapter</entry>
- </row>
- </thead>
-
- <tbody>
-
- <row>
- <entry>
- <para>Wizards for creating Projects with Portlet Facets</para>
- </entry>
- <entry>
- <para>New Dynamic Web Project wizard allows you to select a proper
- Configuration to enable Portlet Facet in it.</para>
- </entry>
- <entry>
- <link linkend="creating_project_with_jbossportal">Creating a Dynamic
- Web Project</link>
- </entry>
- </row>
-
-
- <row>
- <entry>
- <para>Create Java Portlet wizard</para>
- </entry>
-
- <entry>
- <para>The wizard enables creating a JSR-186/JSR-286 compliant
- portlet.</para>
- </entry>
- <entry>
- <link linkend="adding_java_portlet">Adding Java Portlet to a
- project</link>
- </entry>
- </row>
-
- <row>
- <entry>
- <para>Create JSF/Seam Portlet wizard</para>
- </entry>
- <entry>
- <para>This wizard allows to create JSF/Seam portlets</para>
- </entry>
- <entry>
- <link linkend="jsf_portlet">Creating JSF Portlet</link>
- <link linkend="seam_portlet">Creating Seam Portlet</link>
- </entry>
- </row>
-
- </tbody>
- </tgroup>
- </table>
- </section>
-
- <section id="rel_resources">
- <title>Other relevant resources on the topic</title>
-
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://www.jboss.org/jbossportal/">JBoss Portal Home Page</ulink>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <ulink url="http://wiki.jboss.org/wiki/JBossPortal">JBoss Portal Wiki</ulink>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <ulink url="http://www.jboss.org/tools/">JBoss Tools Home Page</ulink>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss Tools Forum</ulink>
- </para>
- </listitem>
-
- <listitem>
- <para>
- <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">The latest
- JBossTools/JBDS documentation builds</ulink>
- </para>
- </listitem>
-
- <listitem>
- <para>JBoss Developer Studio/JBoss Tools release documentation you can find at<ulink url="http://docs.jboss.org/tools/">http://docs.jboss.org/tools</ulink> in the corresponding release directory.</para>
- </listitem>
- </itemizedlist>
-
- </section>
-</chapter>
-
-
-<chapter id="installation" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/portlet/docs/reference/en/modules/installation.xml" xreflabel="installation">
- <?dbhtml filename="installation.html"?>
- <title>Installation issues</title>
-
- <para>This section provides you with the steps on how to start with <property moreinfo="none">JBoss
- Portal</property> and integrated features using <property moreinfo="none">JBoss Tools</property>.</para>
-
- <itemizedlist>
- <listitem>
- <para>First, you need to have Eclipse Ganymede with JBoss Tools 3.0.0.Alpha1 and higher installed.</para>
-
- <tip>
- <title>Tip:</title>
- <para>Read <ulink url="../../GettingStartedGuide/html_single/index.html#JBossToolsInstall">JBoss Tools
- Installation</ulink> section in our Getting Started documentation to find out
- how to install <property moreinfo="none">JBoss Tools</property> onto Eclipse.</para>
- </tip>
- </listitem>
-
- <listitem>
- <para>Next, download the JBoss Portal + JBoss AS bundle from <ulink url="http://www.jboss.org/jbossportal/download/index.html">JBoss Portal Download
- page</ulink></para>
-
- <note>
- <title>Note:</title>
- <para>You need JBoss Portal 2.7 if you want to work with a Portlet 2.0</para>
- </note>
-
- </listitem>
-
- <listitem>
- <para>Extract the bundle wherever you want on your hard drive</para>
- </listitem>
- </itemizedlist>
-
- <para>Now, when you have it installed, we are going to demonstrate some powerful features of
- <property moreinfo="none">JBoss Portal</property> tooling for Eclipse.</para>
-</chapter>
-
-
-<chapter id="starting_project" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/portlet/docs/reference/en/modules/starting_project.xml" xreflabel="starting_project">
- <?dbhtml filename="starting_project.html"?>
- <title>Starting the Project with JBoss Portal</title>
-
- <para>To get started with <property moreinfo="none">JBoss Portal</property> and <property moreinfo="none">JBoss
- Tools</property>, you should first have a Web Project pointed to the JBoss Portal Runtime.
- Thus, in this chapter we are going to show you how to create a Dynamic Web Project, add Java
- Portlet to it and deploy it to the <property moreinfo="none">JBoss Portal</property>.</para>
-
- <section id="creating_project_with_jbossportal">
- <title>Creating a Dynamic Web Project</title>
-
- <para>To create a Dynamic Web Project, go to <emphasis>
- <property moreinfo="none">File > New > Dynamic Web Project</property>
- </emphasis> if you are in the <property moreinfo="none">Web Perspective</property> or <property moreinfo="none">File >
- New > Other > Web > Dynamic Web Project</property> in any other Perspective. The
- first page of the New Dynamic Web Project wizard looks as follows.</para>
-
- <figure float="0">
- <title>New Dynamic Web Project</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/starting_project_1.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Fill out the name of your project. Next, click the <emphasis>
- <property moreinfo="none">New</property>
- </emphasis> button in the <emphasis>
- <property moreinfo="none">Target Runtime</property>
- </emphasis> section to specify a new Target Runtime. Choose <emphasis>
- <property moreinfo="none"> JBoss Community > JBoss 4.2 Runtime</property>
- </emphasis> and select the <emphasis>
- <property moreinfo="none">Create a new local server</property>
- </emphasis> checkbox. Click <emphasis>
- <property moreinfo="none">Next</property>.</emphasis></para>
-
- <figure float="0">
- <title>New Server Runtime</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/starting_project_2.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>On the next page you should give a name to the runtime. Let's call it <emphasis>
- <property moreinfo="none">JBoss Portal 2.7 Runtime</property>
- </emphasis>, and then point it to the location of your JBoss AS + Portal
- installation.</para>
-
- <figure float="0">
- <title>New Server Runtime Environment</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/server_runtime_environment.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <note>
- <title>Note:</title>
-
- <para>The JBoss Tools Portlet feature has been tested using 2.6.5 and 2.7.0.ALPHA
- versions of <property moreinfo="none">JBoss Portal</property>. Remember, if you want to use Portlet
- version 2.0 (JSR-268), you have to choose JBoss Portal 2.7.</para>
- </note>
-
- <para>At this point a new JBoss Server instance will be created. Here you can verify the
- defined runtime information. If something is incorrect, press <emphasis>
- <property moreinfo="none">Back</property>
- </emphasis> to return on the previous wizard page.</para>
-
- <figure float="0">
- <title>Target Server</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/starting_project_3.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Click <emphasis>
- <property moreinfo="none">Finish</property>.</emphasis></para>
-
- <para>On the next step you should click the <emphasis>
- <property moreinfo="none">Modify</property>
- </emphasis> button next to the <property moreinfo="none">Configuration</property> section to enable
- Portlet Facets for the project.</para>
-
- <figure float="0">
- <title>Setting the Project Configuration</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/starting_project_4.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>On this page you should check the <emphasis>
- <property moreinfo="none">JBoss Core Portlet</property>
- </emphasis> and press <emphasis>
- <property moreinfo="none">OK</property>
- </emphasis>.</para>
-
- <figure float="0">
- <title>Enabling the Portlet Facet</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/starting_project_4_a.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <note>
- <title>Note:</title>
- <para>If the portlet libraries aren't available in the runtime you targeted,
- JBoss Portlet facets will be hidden on this page.</para>
- <para>To made portal functionality always visible no matter what the runtime support,
- you should go to <emphasis>
- <property moreinfo="none">Window > Preferences</property>
- </emphasis> and then <emphasis>
- <property moreinfo="none">JBoss Tools > JBoss Portlet</property>
- </emphasis> and deselect <emphasis>
- <property moreinfo="none">Check runtimes for Portlet Components</property>
- </emphasis> checkbox (see figure below).</para>
- </note>
-
- <figure float="0">
- <title>JBoss Runtime Preferences</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/portlet_preferences.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>The next page is for configuring web modules. Here all values are set, so you can
- leave everything as it is.</para>
-
- <figure float="0">
- <title>The Project Web Modules</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/starting_project_5.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Finally, the last wizard page will ask you to add JBoss Portlet capabilities to your
- project. Here you can choose whether to set up user libraries, libraries provided by
- server runtime or not include libraries at all.</para>
-
- <itemizedlist>
- <listitem><para>To set up server runtime libraries, you need to select <emphasis>
- <property moreinfo="none">Libraries provided by server runtime</property></emphasis> in the list box.</para>
- </listitem>
- </itemizedlist>
-
- <figure float="0">
- <title>Including Server Runtime Libraries</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/portlet_capabilities6.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <itemizedlist>
- <listitem>
- <para>For setting up user libraries, select <emphasis>
- <property moreinfo="none">User library</property></emphasis> in the list box and then press <emphasis>
- <property moreinfo="none">Add</property></emphasis> in the <emphasis>
- <property moreinfo="none">User Library</property></emphasis> section.</para>
- </listitem>
- </itemizedlist>
-
- <figure float="0">
- <title>Adding User Library</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/portlet_capabilities1.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Then press <emphasis>
- <property moreinfo="none">New</property></emphasis> and type the user library name in the appeared dialog.</para>
-
- <figure float="0">
- <title>Adding User Library</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/portlet_capabilities2.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Next add necessary jar's.</para>
-
- <figure float="0">
- <title>Adding the Portlet API Jar</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/portlet_capabilities3.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Hit <emphasis>
- <property moreinfo="none">OK</property>.</emphasis> The user library will be added.
- </para>
-
- <figure float="0">
- <title>User Library Added</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/portlet_capabilities4.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <itemizedlist>
- <listitem><para>If you don't need to include libraries at all, just deselect the <emphasis>
- <property moreinfo="none">Enable implementation library</property></emphasis> checkbox.</para>
- </listitem>
- </itemizedlist>
-
- <figure float="0">
- <title>Disabling Implementation Libraries</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/portlet_capabilities5.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>After setting JBoss Portlet capabilities press <emphasis>
- <property moreinfo="none">Finish</property>.</emphasis></para>
-
- <para>That's it! Our base project is done.</para>
-
- </section>
-
- <section id="structure_overview">
- <title>The Project Structure Overview</title>
-
- <para>Now, let's look at the structure of the just created project.</para>
-
- <figure float="0">
- <title>The Project Structure Overview</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/starting_project_6.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Here <property moreinfo="none">JBoos Tools</property> added JBoss Portlet facet to the project,
- created an empty <emphasis>
- <property moreinfo="none">portlet.xml</property>
- </emphasis> file and added the Portlet library to the project classpath.</para>
- </section>
-
- <section id="adding_java_portlet">
- <title>Adding a Java Portlet to the Project</title>
-
- <para>At this point we'll show what the steps you need to proceed to add a new Java
- Portlet to the project.</para>
-
- <para>Call the <property moreinfo="none">Create Portlet wizard</property> by selecting <emphasis>
- <property moreinfo="none">New > Other > JBoss Tools Web > Portlet > Java
- Portlet</property>.</emphasis></para>
-
- <figure float="0">
- <title>New Java Portlet</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/starting_project_7.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>The wizard fills in the Web Project and Source Folder fields for you. Then you need to
- specify the Java package and the Class name and click <emphasis>
- <property moreinfo="none">Next</property>
- </emphasis>.</para>
-
- <figure float="0">
- <title>Specifying Class File Destination</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/starting_project_8.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>On the other page you will be able to set the display name of the Portlet, a title, a
- description, the supported modes and init parameters.</para>
-
- <figure float="0">
- <title>Specifying Class File Destination</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/starting_project_9.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>On the next screen you can define which methods from
- <emphasis>GenericPortlet</emphasis> you want to override.</para>
-
- <figure float="0">
- <title>Specifying Class File Destination</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/starting_project_10.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>The last screen lets you build <property moreinfo="none">JBoss Portal</property> specific descriptors
- to create an instance during the deployment and place it directly on the Portal.</para>
-
- <figure float="0">
- <title>Specifying Class File Destination</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/starting_project_11.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <tip>
- <title>Tip:</title>
-
- <para>If you uncheck the <emphasis> Create Portlet Instance</emphasis> checkbox,
- <property moreinfo="none">JBoss Tools</property> won't create the deployment elements
- in the <emphasis> default-object.xml</emphasis> and <emphasis>
- portlet-instances.xml</emphasis> files.</para>
- </tip>
-
- <para>Once Java Portlet is created, new resources have been added to the project structure.
- As you can see on the figure below, it adds a Java Portlet class (<emphasis>
- <property moreinfo="none">TestPortlet.java</property>
- </emphasis> in our case), <emphasis>
- <property moreinfo="none">default-object.xml</property>
- </emphasis> and <emphasis>
- <property moreinfo="none">portlet-instances.xml</property>
- </emphasis> files and updates <emphasis>
- <property moreinfo="none">portlet.xml</property>
- </emphasis> as well.</para>
-
- <figure float="0">
- <title>The structure of Web Project with Java Portlet created</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/starting_project_12.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Thus, now the Project is ready to be built and deployed.</para>
- </section>
-
- <section id="deploying_to_portal">
- <title>Deploying a Portlet to JBoss Portal</title>
-
- <para>You can deploy the created project in the way you deploy any other Web Application.
- Right click on the project and do <emphasis>
- <property moreinfo="none">Run As > Run On Server</property>
- </emphasis> and accept the defaults. On the <emphasis>
- <property moreinfo="none">Add and Remove Projects</property>
- </emphasis> page move the created Project to the right and click <emphasis>
- <property moreinfo="none">Finish</property>.</emphasis></para>
-
- <figure float="0">
- <title>Deploying the Portlet Application</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/starting_project_13.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>It will deploy the Portlet Web Application and start <property moreinfo="none">JBoss
- AS</property>.</para>
-
- <tip>
- <title>Tip:</title>
-
- <para>You should use <emphasis>http://localhost:8080/portal</emphasis> URL to see your
- Portlet in the Browser.</para>
- </tip>
-
- <para>In the Browser the Portlet looks as follows:</para>
-
- <figure float="0">
- <title>Java Portlet in the Browser Window</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/starting_project/starting_project_14.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Consequently, here you learnt how to create a Dynamic Web Project, add Java Portlet to
- it and deploy the project to <property moreinfo="none">JBoss Portal</property>.</para>
- </section>
-
-</chapter>
-
-
-<chapter id="jsf_portlet" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/portlet/docs/reference/en/modules/jsf_portlet.xml" xreflabel="jsf_portlet">
- <?dbhtml filename="jsf_portlet.html"?>
- <title>Creating JSF Portlet</title>
-
- <para>This chapter will explain how you can configure JSF Portlet within Dynamic Web
- Project and JSF Project by using the wizards <property moreinfo="none">JBoss Tools</property> provides.</para>
-
- <section id="jsf_portlet1">
- <title>Adding JSF Portlet to Dynamic Web Project</title>
-
- <para>To add JSF Portlet to a Dynamic Web Project, you should set the Configuration to <emphasis>
- <property moreinfo="none">JavaServer Faces v1.1 Project</property>
- </emphasis> or <emphasis>
- <property moreinfo="none">JavaServer Faces v1.2 Project</property>
- </emphasis> and configure the JSF Portlet Facets in the <property moreinfo="none">New Dynamic Web
- Project wizard</property> by clicking the <emphasis>
- <property moreinfo="none">Modify</property>
- </emphasis> button.</para>
-
- <figure float="0">
- <title>Setting the JSF Configuration</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_portlet/jsf_portlet1.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>On the Project Facets dialog you should select <property moreinfo="none">JBoss Core Portlet</property>
- and <property moreinfo="none">JBoss JSF Portlet</property> check boxes.</para>
-
- <figure float="0">
- <title>Enabling the Portlet Facets</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_portlet/jsf_portlet2.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Next wizard page is for configuring JSF Capabilities. You can leave everything as it
- is here.</para>
-
- <figure float="0">
- <title>JSF Capabilities</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_portlet/jsf_portlet3.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>To support Portlets in JSF/Seam applications <property moreinfo="none">JBoss Tools</property> works
- with <property moreinfo="none">JBoss Portlet Bridge</property>. Thus on the next page you should add JSF Portlet
- capabilities by pointing to the Portletbridge Runtime location.</para>
-
- <figure float="0">
- <title>JSF Capabilities</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_portlet/jsf_portlet4.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <tip>
- <title>Tip:</title>
-
- <para>You can download JBoss Portlet Bridge 1.0.0.B4 from <ulink url="http://www.jboss.org/portletbridge/download/">Portletbridge Download page</ulink>.</para>
- </tip>
-
- <para>Next click <emphasis>
- <property moreinfo="none">Finish</property>
- </emphasis> to organize the Project.</para>
- <para id="add_jsf_portlet">To add JSF Portlet to generated project you should call the
- <property moreinfo="none">Create Portlet wizard</property> by navigating to <emphasis>
- <property moreinfo="none">New > Other > JBoss Tools Web > Portlet > JSF/Seam
- Portlet</property>.</emphasis></para>
-
- <figure float="0">
- <title>Calling New Portlet Wizard</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_portlet/jsf_portlet5.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>As you see, the Seam and JSF Portlet wizards are merged into one. We set JSF
- Configuration for the project, so default values in this wizard will be set as for a JSF
- portlet.</para>
-
- <figure float="0">
- <title>Creating JSF Portlet</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_portlet/jsf_portlet6.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Click <emphasis>
- <property moreinfo="none">Finish</property>
- </emphasis> to complete JSF Portlet creation. Now you can deploy the project the same
- way as it was <link linkend="deploying_to_portal">described above</link>.</para>
-
- <para>In the Browser JSF Portlet looks as follows.</para>
-
- <figure float="0">
- <title>JSF Portlet in the Browser</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_portlet/jsf_portlet7.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- </section>
-
- <section id="jsf_portlet_to_JSF_project">
- <title>Adding JSF Portlet to JSF Project</title>
-
- <para>How to organize a JSF Project you can find out in our <ulink url="../../jsf_tools_ref_guide/html_single/index.html#new_jsf_project">JSF Tools Reference Guide</ulink>. Just
- remember to point Target Runtime to JBoss Portal directory location.</para>
-
- <figure float="0">
- <title>Creating New JSF Project</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_portlet/jsf_portlet8.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Before adding a Portlet to the project you should enable necessary facets for it.
- Right-click the created project and click <emphasis>
- <property moreinfo="none">Preferences</property>
- </emphasis> to open the <property moreinfo="none">Project Preferences</property> screen.</para>
- <para>On the <property moreinfo="none">Project Facets</property> page select the <emphasis>
- <property moreinfo="none">JBoss Core Portlet</property>
- </emphasis> and <emphasis>
- <property moreinfo="none">JBoss JSF Portlet</property>
- </emphasis> checkboxes. And then the screen will ask you to enable <emphasis>
- <property moreinfo="none">JavaServer Faces</property>
- </emphasis> facet as well.</para>
-
- <figure float="0">
- <title>Project Facets</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_portlet/jsf_portlet9.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Notice, <emphasis>
- <property moreinfo="none">"Further configuration required..."</property>
- </emphasis> warning appears at the bottom of the screen. It means that you should click
- it to configure JSF and JSF Portlet Capabilities in the project.</para>
-
- <figure float="0">
- <title>JSF Capabilities</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_portlet/jsf_portlet10.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <figure float="0">
- <title>Project Facets</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/jsf_portlet/jsf_portlet11.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>After setting the path to Portletbridge Runtime location, click <emphasis>
- <property moreinfo="none">OK</property>
- </emphasis> and then <emphasis>
- <property moreinfo="none">OK</property>
- </emphasis> again.</para>
-
- <para>Now you can add JSF Portlet to the generated JSF Project. How to do it we showed in
- <link linkend="add_jsf_portlet">the previous section</link>.</para>
- </section>
-</chapter>
-
-
-<chapter id="seam_portlet" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/portlet/docs/reference/en/modules/seam_portlet.xml" xreflabel="seam_portlet">
- <?dbhtml filename="seam_portlet.html"?>
- <title>Creating Seam Portlet</title>
-
- <para>This chapter covers the steps on how to configure Seam Portlet within Dynamic Web
- Project and Seam Project by using the wizards <property moreinfo="none">JBoss Tools</property> provides.</para>
-
- <section id="seam_portlet1">
- <title>Adding Seam Portlet to Dynamic Web Project</title>
-
- <para>To add Seam Portlet to a Dynamic Web Project first you should organize New Dynamic Web
- Project with the Configuration setting to <emphasis>
- <property moreinfo="none">JBoss Seam Portlet Project v2.0</property>.</emphasis></para>
-
- <figure float="0">
- <title>Calling New Portlet Wizard</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/seam_portlet/seam_portlet1.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>It will add all needed facets to your project. By clicking the <emphasis>
- <property moreinfo="none">Modify</property>
- </emphasis> button you can observe the chosen configuration of facets as well as modify
- it. As you can see, all JBoss Portlets are checked.</para>
-
- <figure float="0">
- <title>Project Facets</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/seam_portlet/seam_portlet2.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Next wizard pages are for adjusting the Project Web Modules and JSF Configuration.
- They include default values, so you can skip them by pressing <emphasis>
- <property moreinfo="none">Next</property>.</emphasis></para>
-
- <para>On the <property moreinfo="none">Seam Facet</property> page <ulink url="../../seam/html_single/index.html#seamFacet">set
- Connection Profile</ulink> and hit <emphasis>
- <property moreinfo="none">Next</property>.</emphasis></para>
-
- <figure float="0">
- <title>Seam Facet Settings</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/seam_portlet/seam_portlet3.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Last wizard page will prompt you to set the path to Portletbridge Runtime
- location.</para>
-
- <figure float="0">
- <title>Setting the Portletbridge Runtime</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/seam_portlet/seam_portlet4.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <tip>
- <title>Tip:</title>
-
- <para>Thus you should have JBoss Portlet Bridge downloaded and extracted somewhere on
- your hard drive. You can download JBoss Portlet Bridge 1.0.0.B4 from <ulink url="http://www.jboss.org/portletbridge/download/">www.jboss.org/portletbridge/download</ulink>.</para>
- </tip>
-
- <para>Now, to add Seam Portlet to the project you should follow to <emphasis>
- <property moreinfo="none">New > Other > JBoss Tools Web > Portlet > JSF/Seam
- Portlet</property>.</emphasis> This will call the wizard for creating JSF/Seam
- Portlets.</para>
-
- <figure float="0">
- <title>Calling the Create Portlet Wizard</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/seam_portlet/seam_portlet5.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>As we set Seam Configuration for the Dynamic Web Project, the wizard puts the values
- as for Seam Portlet.</para>
-
- <figure float="0">
- <title>Creating Seam Portlet</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/seam_portlet/seam_portlet6.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>After creating the Seam Portlet, you should <link linkend="deploying_to_portal">deploy
- the project to JBoss Portal</link> and start the Server. In a Browser
- you'll see the following:</para>
-
- <figure float="0">
- <title>Seam Portlet in the Browser</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/seam_portlet/seam_portlet7.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- </section>
-
- <section id="seam_portlet_to_seam_project">
- <title>Adding Seam Portlet to Seam Project</title>
-
- <para>First start a Seam Project by following to <emphasis>
- <property moreinfo="none">New > Other > Seam > Seam Web Project</property>. </emphasis> On the first
- wizard page specify JBoss Portal directory location as <property moreinfo="none">Target
- Runtime</property> and <emphasis>
- <property moreinfo="none">JBoss Seam Portlet Project v2.0</property>
- </emphasis> as <property moreinfo="none">Configuration</property>.</para>
-
- <figure float="0">
- <title>Project Facets</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/seam_portlet/seam_portlet8.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Next steps will be the same as we did for the Dynamic Web Project in the <link linkend="seam_portlet1">Adding Seam Portlet to Dynamic Web Project</link>
- section.</para>
- </section>
-</chapter>
-
-
-<chapter id="portlets_to_nonWTP_projects" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/portlet/docs/reference/en/modules/portlets_to_nonWTP_projects.xml" xreflabel="portlets_to_nonWTP_projects">
- <?dbhtml filename="portlets_to_nonWTP_projects.html"?>
- <title>Adding Portlets to non-WTP Projects</title>
-
- <para>Starting from <property moreinfo="none">JBoss Tools 3.0.0.Beta1</property> version the JBoss Portlet
- wizards no longer require a WTP project to be able to create Portlets.</para>
-
- <note>
- <title>Note:</title>
- <para>Please note, if the project does not have the proper portlet API jar's, the generated
- classes will have compile errors.</para>
- </note>
-
- <para>In conclusion, with this document you've learnt how to get started with <property moreinfo="none">JBoss
- Portal</property> using <property moreinfo="none">JBoss Tools</property> suite of Eclipse plugins.
- The above chapters walked you through the steps on how to organize a web project with
- portlets which includes a sample staff and deploy it onto the <property moreinfo="none">JBoss
- Portal</property>.</para>
-
- <para>If you still have questions or suggestions you are always welcome on our <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">Forum</ulink>. Your feedback will be very much appreciated.</para>
-
-</chapter>
-
-
-</book>
+]><book xmlns:diffmk="http://diffmk.sf.net/ns/diff">
+
+ <bookinfo>
+ <title>JBoss Portlet Tools User Guide</title>
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/jbosstools_logo.png" format="PNG"></imagedata>
+ </imageobject>
+ <imageobject role="html">
+ <imagedata></imagedata>
+ </imageobject>
+ </inlinemediaobject>
+ </corpauthor>
+ <author><firstname>Olga</firstname><surname>Chikvina</surname></author>
+ <author><firstname>Snjezana</firstname><surname>Peco</surname><email>snjezana.peco(a)redhat.com</email></author>
+ <author><firstname>Svetlana</firstname><surname>Mukhina</surname><email>smukhina(a)exadel.com</email></author>
+ <author><firstname>Thomas</firstname><surname>Heute</surname><email>theute(a)jboss.org</email></author>
+
+ <copyright>
+ <year>2008</year>
+ <year>2009</year>
+ <year>2010</year>
+ <holder>JBoss by Red Hat</holder>
+ </copyright>
+ <releaseinfo><diffmk:wrapper diffmk:change="changed">
+ Version: 1.1.0.GA
+ </diffmk:wrapper></releaseinfo>
+
+<abstract>
+ <title></title>
+ <para>
+ <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/jboss_portal_tools_r...">PDF version</ulink>
+ </para>
+</abstract>
+
+
+ </bookinfo>
+ <toc></toc>
+
+
+
+<chapter id="intro" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/portlet/docs/reference/en/modules/intro.xml" xreflabel="intro">
+ <?dbhtml filename="intro.html"?>
+ <title>Introduction</title>
+
+ <para>Starting from 3.0.0.Alpha1 version, JBoss set of plugins includes tools for supporting <property moreinfo="none">JBoss Portal</property> and JSR-186/JSR-286 portlets.
+ Thus, this guide is intended to explain you how to get started and manage <property moreinfo="none">JBoss Portlet Tools</property>.</para>
+
+ <section id="preface">
+ <title>What is JBoss Portal and Portlet Tools?</title>
+ <para><property moreinfo="none">JBoss Portal</property> provides an open source platform for hosting and
+ serving a portal's Web interface, publishing and managing its content, and customizing
+ its experience. It supports a wide range of features, including standard portlets,
+ single sign-on, clustering, and internationalization. More about <property moreinfo="none">JBoss Portal</property> you can find visiting
+ its home page at: <ulink url="http://www.jboss.org/jbossportal/">http://www.jboss.org/jbossportal/</ulink>.</para>
+
+ <para>With <property moreinfo="none">JBoss Portlet Tools</property> you can easily create a Java, JSF and Seam portlet and deploy it to <property moreinfo="none">JBoss Portal</property>.</para>
+ </section>
+
+ <section id="key_features">
+ <title>Key Features of JBoss Portlet Tools</title>
+ <para><property moreinfo="none">JBoss Portlet Tools</property> supports the <ulink url="http://www.jcp.org/en/jsr/detail?id=168">JSR-168 Portlet Specification (Portlet 1.0)</ulink> and
+ <ulink url="http://www.jcp.org/en/jsr/detail?id=286">JSR-286 Portlet Specification (Portlet 2.0)</ulink> and works with
+ <ulink url="http://www.jboss.org/portletbridge/">JBoss Portlet Bridge</ulink> for supporting Portlets
+ in JSF/Seam applications. To enable these features, you need to add the JBoss Portlet facet to a new or an existing web project
+ (see <link linkend="portlet_tools_tasks">JBoss Portlet Tools Tasks</link>). The project could be a non-WTP project, but you should know that
+ if it does not have the proper portlet API jar's the generated classes will have compile errors.</para>
+
+ <para>The next table lists key features supplied by <property moreinfo="none">JBoss Portlet Tools</property>.</para>
+
+ <table>
+ <title>Key Features of JBoss Portlet Tools</title>
+ <tgroup cols="3">
+
+ <colspec align="left" colnum="1" colwidth="1*"></colspec>
+ <colspec colnum="2" colwidth="5*"></colspec>
+ <colspec align="left" colnum="3" colwidth="1*"></colspec>
+
+ <thead>
+ <row>
+ <entry>Feature</entry>
+ <entry>Benefit</entry>
+ <entry>Chapter</entry>
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>
+ <para>JBoss Portlet facets</para>
+ </entry>
+ <entry>
+ <para><property moreinfo="none">JBoss Portlet Tools</property> provides the Java, JSF and Seam Portlet facets that could be enabled for a Web project.</para>
+ </entry>
+ <entry>
+ <link linkend="portlet_tools_tasks">JBoss Portlet Tools Tasks</link>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>Java Portlet wizard</para>
+ </entry>
+
+ <entry>
+ <para>The wizard helps create a JSR-186/JSR-286 compliant
+ portlets</para>
+ </entry>
+ <entry>
+ <link linkend="java_portlet_wizard">Java Portlet Wizard</link>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>JSF/Seam Portlet wizard</para>
+ </entry>
+ <entry>
+ <para>This wizard helps create JSF/Seam portlets</para>
+ </entry>
+ <entry>
+ <link linkend="jsf_seam_portlet_wizard">JSF/Seam Portlet Wizard</link>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+
+ <section id="requirements_installation">
+ <title>Requirements and Installation</title>
+ <para><property moreinfo="none">JBoss
+ Portlet Tools</property> needs the following minimal requirements:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Eclipse 3.4.2/Ganymede</para>
+ </listitem>
+ <listitem>
+ <para>JBoss Tools 3.0.0.Alpha1 (for higher versions of JBoss Tools make sure you use the
+ <ulink url="http://www.jboss.org/community/wiki/Matrixofsupportedplatformsruntimesand...">compatible version of Eclipse</ulink>)</para>
+ </listitem>
+ <listitem><para>JDK 5 or higher</para></listitem>
+ <listitem>
+ <para>JBoss Portal + JBoss AS bundle from: <ulink url="http://www.jboss.org/jbossportal/download/index.html">http://www.jboss.org/jbossportal/download/index.html</ulink></para>
+ <note>
+ <title>Note:</title>
+ <para>JBoss Portlet Tools has been tested using 2.6.5 and 2.7.0.ALPHA
+ versions of <property moreinfo="none">JBoss Portal</property>. Remember, if you want to use Portlet
+ version 2.0 (JSR-268), you have to choose JBoss Portal 2.7.</para>
+ </note>
+ </listitem>
+ <listitem>
+ <para>JBoss Portlet Bridge (optionally) from: <ulink url="http://www.jboss.org/portletbridge/downloads.html">http://www.jboss.org/portletbridge/downloads.html</ulink></para>
+ </listitem>
+ </itemizedlist>
+
+ <para><property moreinfo="none">JBoss Portlet Tools</property> is included as part of <property moreinfo="none">JBoss Tools</property> project.
+ Refer to <ulink url="http://www.jboss.org/tools/download/installation.html">http://www.jboss.org/tools/download/installation.html</ulink>
+ for installation methods of <property moreinfo="none">JBoss Tools</property>.</para>
+ </section>
+</chapter>
+
+
+<chapter id="portlet_tools_tasks" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/portlet/docs/reference/en/modules/portlet_tools_tasks.xml" xreflabel="portlet_tools_tasks">
+ <?dbhtml filename="portlet_tools_tasks.html"?>
+ <title>JBoss Portlet Tools Tasks</title>
+
+
+<section id="starting_project" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/portlet/docs/reference/en/modules/starting_project.xml">
+ <title>Creating and Deploying a Java Portlet</title>
+
+ <para>This chapter shows how to create a Dynamic Web Project, add a Java
+ Portlet to it and deploy it to the <property moreinfo="none">JBoss Portal</property>.</para>
+
+ <section id="jboss_core_portlet">
+ <title>Creating a Web Project with JBoss Portlet Capabilities</title>
+ <para>Fallow the next procedure to create a Web project with JBoss Portlet capabilities pointed to the JBoss Portal runtime.</para>
+
+ <orderedlist continuation="restarts" inheritnum="ignore">
+ <listitem>
+ <para>Go to <emphasis>
+ <property moreinfo="none">File > New > Dynamic Web Project</property>
+ </emphasis> if you are in the <property moreinfo="none">Web</property> perspective or <emphasis><property moreinfo="none">File >
+ New > Other > Web > Dynamic Web Project</property></emphasis> in any other perspective.
+ The <property moreinfo="none">New Dynamic Web Project</property> wizard appears.</para>
+
+ <figure float="0">
+ <title>New Dynamic Web Project</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/starting_project/starting_project_1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+
+ <listitem><para>Specify the name of the project.</para></listitem>
+
+ <listitem>
+ <para>Click <emphasis>
+ <property moreinfo="none">New</property>
+ </emphasis> in the <emphasis>
+ <property moreinfo="none">Target Runtime</property>
+ </emphasis> area to create a JBoss Portal runtime. Choose <emphasis>
+ <property moreinfo="none">JBoss Community > JBoss 4.2 Runtime</property>
+ </emphasis> and select the <emphasis>
+ <property moreinfo="none">Create a new local server</property>
+ </emphasis> check box below. Click <emphasis>
+ <property moreinfo="none">Next</property>.</emphasis></para>
+
+ <figure float="0">
+ <title>New Server Runtime</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/starting_project/starting_project_2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+
+ <listitem>
+ <para>The <property moreinfo="none">New Server Runtime Environment</property> wizard appears. In the <emphasis>
+ <property moreinfo="none">Name</property></emphasis> field, type <emphasis>
+ <property moreinfo="none">JBoss Portal 2.7 Runtime</property>,
+ </emphasis> and then use the <emphasis>
+ <property moreinfo="none">Browse</property></emphasis> button to point to the location of JBoss Portal + JBoss AS extracted. Click <emphasis>
+ <property moreinfo="none">Next</property></emphasis> to proceed.</para>
+
+ <figure float="0">
+ <title>New Server Runtime Environment</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/starting_project/server_runtime_environment.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+
+ <listitem>
+ <para>At this point a new JBoss Server instance will be created. On the next page you can verify the
+ runtime information defined. If something is incorrect, press <emphasis>
+ <property moreinfo="none">Back</property>
+ </emphasis> to return to the previous wizard page. Click <emphasis>
+ <property moreinfo="none">Finish</property>.</emphasis></para>
+
+ <figure float="0">
+ <title>Target Server</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/starting_project/starting_project_3.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+
+ <listitem>
+ <para>Click <emphasis>
+ <property moreinfo="none">Modify</property>
+ </emphasis> in the <emphasis><property moreinfo="none">Configuration</property></emphasis> area to enable
+ a portlet facet for the project.</para>
+
+ <figure float="0">
+ <title>Setting the Project Configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/starting_project/starting_project_4.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+
+ <listitem>
+ <para>In the <property moreinfo="none">Project Facets</property> dialog, check <emphasis>
+ <property moreinfo="none">JBoss Core Portlet</property>
+ </emphasis> and press <emphasis>
+ <property moreinfo="none">OK</property>
+ </emphasis>.</para>
+
+ <figure float="0">
+ <title>Enabling the JBoss Core Portlet Facet</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/starting_project/starting_project_4_a.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <note>
+ <title>Note:</title>
+ <para>If the portlet libraries aren't available in the runtime you targeted,
+ <emphasis>
+ <property moreinfo="none">JBoss Portlets</property></emphasis> facets will be hidden on this page.</para>
+ <para>To make them always visible no matter what the runtime is set, you should enable the appropriate option in
+ <link linkend="preferences">JBoss Portlet Preferences</link>.</para>
+ </note>
+ </listitem>
+
+ <listitem>
+ <para>The <property moreinfo="none">Java</property> and <property moreinfo="none">Web Module</property> pages are for configuring Java and Web modules in the project.
+ Here all values are set, so leave everything as it is.</para>
+ </listitem>
+
+ <listitem>
+ <para>The last wizard page will ask you to add JBoss Portlet capabilities to the
+ project. Select <emphasis>
+ <property moreinfo="none">Portlet Target Runtime Provider</property></emphasis> and click <emphasis>
+ <property moreinfo="none">Finish</property></emphasis> to complete the project creation.</para>
+
+ <figure float="0">
+ <title>Including the Portlet Libraries Provided by Target Runtime</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/starting_project/portlet_capabilities6.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <note>
+ <title>Note:</title>
+ <para>All types available under <emphasis>
+ <property moreinfo="none">Portlet Implementation Library</property></emphasis> are fully described in the Wiki article at:
+ <ulink url="http://www.jboss.org/community/wiki/PortletFacetLibraries">http://www.jboss.org/community/wiki/PortletFacetLibraries</ulink>.</para>
+ </note>
+ </listitem>
+ </orderedlist>
+
+ <para>As the result, <property moreinfo="none">JBoss Portlet Tools</property> adds <emphasis>
+ <property moreinfo="none">JBoss Core Portlet</property></emphasis> facet to the project,
+ creates an empty <literal moreinfo="none">portlet.xml</literal> file and adds the JBoss Portlet library to the project classpath.</para>
+
+ <figure float="0">
+ <title>Portlet Project Structure Overview</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/starting_project/starting_project_6.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+
+ <section id="adding_java_portlet">
+ <title>Adding a Java Portlet to a Web Project</title>
+
+ <para>At the previous section you have created a web project with JBoss Portlet capabilities.
+ The next steps will show you how to add a new Java portlet to the project.</para>
+
+ <orderedlist continuation="restarts" inheritnum="ignore">
+ <listitem>
+ <para>Right-click the project and follow to <emphasis>
+ <property moreinfo="none">New > Other > JBoss Tools Web > Portlet > Java
+ Portlet</property>.</emphasis></para>
+
+ <figure float="0">
+ <title>New Java Portlet</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/starting_project/starting_project_7.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+
+ <listitem>
+ <para>The <property moreinfo="none">Create Portlet</property> wizard starts (for information about the wizard options, see
+ <link linkend="java_portlet_wizard">"Java Portlet Wizard"</link> in the guide reference).
+ The wizard fills in the <emphasis><property moreinfo="none">Project</property></emphasis> and <emphasis>
+ <property moreinfo="none">Source Folder</property></emphasis> fields for you. You should specify a Java package and a class name
+ (for instance, <emphasis>
+ <property moreinfo="none">org.example</property></emphasis> and <emphasis>
+ <property moreinfo="none">TestPortlet</property></emphasis>). Then click <emphasis>
+ <property moreinfo="none">Next</property>
+ </emphasis>.</para>
+
+ <figure float="0">
+ <title>Specifying Class File Destination</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/starting_project/starting_project_8.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+
+ <listitem><para>You may leave the next three pages with default values, on the last one hit <emphasis>
+ <property moreinfo="none">Finish</property>.</emphasis></para>
+ </listitem>
+ </orderedlist>
+
+ <para>Once a Java portlet is created, new resources are added to the project structure: a Java portlet class (<literal moreinfo="none">TestPortlet.java</literal>),
+ <literal moreinfo="none">default-object.xml</literal> and <literal moreinfo="none">portlet-instances.xml</literal> files and the <literal moreinfo="none">portlet.xml</literal> descriptor is updated as well.</para>
+
+ <figure float="0">
+ <title>Structure of the Project with a Java Portlet</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/starting_project/starting_project_12.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Thus, now the project is ready to be built and deployed.</para>
+ </section>
+
+ <section id="deploying_to_portal">
+ <title>Deploying a Portlet to JBoss Portal</title>
+
+ <para>You can deploy a portlet project in the way you deploy any other web application.</para>
+
+ <orderedlist continuation="restarts" inheritnum="ignore">
+ <listitem>
+ <para>Right-click the project and do <emphasis>
+ <property moreinfo="none">Run As > Run On Server</property>.
+ </emphasis> The <property moreinfo="none">Run On Server</property> wizard starts.</para>
+
+ <figure float="0">
+ <title>Running the Java Portlet on Server</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/starting_project/runOnServer.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+
+ <listitem>
+ <para>Select <emphasis><property moreinfo="none">JBoss Portal 2.7 Server</property></emphasis> created before and click <emphasis><property moreinfo="none">Next</property>.</emphasis></para>
+ </listitem>
+
+ <listitem>
+ <para>On the <emphasis>
+ <property moreinfo="none">Add and Remove</property>
+ </emphasis> page move the created project to the right and click <emphasis>
+ <property moreinfo="none">Finish</property>.</emphasis></para>
+
+ <figure float="0">
+ <title>Deploying the Portlet Application</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/starting_project/starting_project_13.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>It will deploy the portlet application and start <property moreinfo="none">JBoss
+ AS</property>.</para>
+ </listitem>
+
+ <listitem>
+ <para>Use the <emphasis>http://localhost:8080/portal/portal/default/default</emphasis> URL to see your
+ portlet in the browser.</para>
+
+ <figure float="0">
+ <title>Java Portlet in the Browser Window</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/starting_project/starting_project_14.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ </orderedlist>
+ </section>
+
+</section>
+
+
+<section id="jsf_portlet" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/portlet/docs/reference/en/modules/jsf_portlet.xml">
+ <title>Creating and Deploying a JSF Portlet</title>
+
+ <para>This chapter will explain how you can configure a JSF portlet within a JSF project with JBoss Portlet capabilities
+ and then deploy it to <property moreinfo="none">JBoss Portal</property>.</para>
+
+ <section id="jsf_portlet1">
+ <title>Creating a JSF Project with JBoss Portlet Capabilities</title>
+
+ <para>You can create a JSF project with JBoss Portlet capabilities in two ways:</para>
+
+ <orderedlist continuation="restarts" inheritnum="ignore">
+ <listitem>
+ <para>Create a dynamic Web project with the <emphasis><property moreinfo="none">JavaServer Faces</property></emphasis>
+ and <emphasis><property moreinfo="none">JBoss JSF Portlet</property></emphasis> facets enabled (
+ <link linkend="create_dyn_web_proj_jsf">the steps to proceed</link>)</para>
+ </listitem>
+ <listitem><para>Or create a JSF project using the wizard JBoss JSF Tools provides, then enable
+ JSF and JBoss Portlet facets and add JBoss Portlet capabilities (
+ <link linkend="create_jsf_proj">the steps to proceed</link>)</para></listitem>
+ </orderedlist>
+
+ <para>Refer to the further sections for the procedures on how to do this.</para>
+
+ <section id="create_dyn_web_proj_jsf">
+ <title>Creating a Dynamic Web Project with the JBoss Portlet Capabilities</title>
+
+ <para>The basic steps to create a dynamic Web project with the JBoss Portlet capabilities are as follows:</para>
+
+ <orderedlist continuation="restarts" inheritnum="ignore">
+ <listitem>
+ <para>Start the <emphasis><property moreinfo="none">Dynamic Web Project</property></emphasis> wizard navigating to
+ <emphasis><property moreinfo="none">File > New > Other > Web > Dynamic Web Project</property>.</emphasis></para>
+
+ <tip>
+ <title>Tip:</title>
+ <para>You can also select the <property moreinfo="none">Java EE</property> perspective and then go to
+ <emphasis><property moreinfo="none">File > New > Dynamic Web Project</property>.</emphasis></para>
+ </tip>
+
+ <figure float="0">
+ <title>Setting the JSF Configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_portlet/jsf_portlet1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+
+ <listitem>
+ <para>Specify the project name and set the target runtime to <property moreinfo="none">JBoss Portal</property> by following the points 3, 4 and 5 in the
+ <link linkend="jboss_core_portlet">"Creating a Web Project with JBoss Portlet Capabilities"</link> procedure.</para>
+ </listitem>
+
+ <listitem>
+ <para>In the <emphasis><property moreinfo="none">Configuration</property></emphasis>
+ area, click <emphasis><property moreinfo="none">Modify</property></emphasis> and enable <emphasis><property moreinfo="none">JavaServer Faces</property>,</emphasis>
+ <emphasis><property moreinfo="none">JBoss Core Portlet</property></emphasis> and <emphasis><property moreinfo="none">JBoss JSF Portlet</property></emphasis> facets.
+ Hit <emphasis><property moreinfo="none">OK</property>.</emphasis></para>
+
+ <figure float="0">
+ <title>Enabling the Portlet Facets</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_portlet/jsf_portlet2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+
+ <listitem>
+ <para>You may leave the next two wizard pages with defaults, just press <emphasis><property moreinfo="none">Next</property></emphasis> to proceed.</para>
+ </listitem>
+
+ <listitem>
+ <para>On the <property moreinfo="none">JBoss Portlet Capabilities</property> page, select <emphasis>
+ <property moreinfo="none">Portlet Target Runtime Provider</property></emphasis> and click <emphasis><property moreinfo="none">Next</property>.</emphasis></para>
+
+ <figure float="0">
+ <title>JBoss Portlet Capabilities</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_portlet/jsf_portlet2a.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <tip>
+ <title>Tip:</title>
+ <para>All types of the portlet implementation library are described more closely in the wiki article at:
+ <ulink url="http://www.jboss.org/community/wiki/PortletFacetLibraries">http://www.jboss.org/community/wiki/PortletFacetLibraries</ulink>.</para>
+ </tip>
+ </listitem>
+
+ <listitem>
+ <para>Next wizard page is for configuring JSF capabilities. You can leave everything as it
+ is here.</para>
+
+ <figure float="0">
+ <title>JSF Capabilities</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_portlet/jsf_portlet3.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+
+ <listitem>
+ <para>On the <property moreinfo="none">JBoss JSF Portlet Capabilities</property> page, select
+ <emphasis><property moreinfo="none">JSF Portlet Target Runtime Provider</property></emphasis> as the JSF portlet implementation library. It will
+ copy Portlet Bridge libraries from the server runtime to the project classpath.</para>
+
+ <figure float="0">
+ <title>JBoss JSF PortletCapabilities</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_portlet/jsf_portlet4.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <tip>
+ <title>Tip:</title>
+ <para>On this page, it is also possible to add the RichFaces libraries from the RichFaces distribution by checking
+ <emphasis><property moreinfo="none">Add/Change Richfaces Libraries</property>.</emphasis></para>
+ </tip>
+
+ <note>
+ <title>Note:</title>
+ <para>You can select the <emphasis><property moreinfo="none">JSF Portletbridge Runtime Provider</property></emphasis> type. Then it
+ is necessary to set the home of the Portlet Bridge distribution.</para>
+ <para>For information about all the JSF Portlet facet library providers, refer to the wiki article at:
+ <ulink url="http://community.jboss.org/wiki/PortletFacetLibraries">http://community.jboss.org/wiki/PortletFacetLibraries</ulink>.</para>
+ </note>
+ </listitem>
+
+ <listitem>
+ <para>Click <emphasis><property moreinfo="none">Finish</property>.</emphasis> The project will be created in the workbench.</para>
+ </listitem>
+ </orderedlist>
+ </section>
+
+ <section id="create_jsf_proj">
+ <title>Creating a JSF Project and adding the JBoss Portlet Capabilities</title>
+
+ <para>How to organize a JSF project you can find out in the <ulink url="../../jsf_tools_ref_guide/html_single/index.html#new_jsf_project">JSF Tools User Guide</ulink>. Just
+ remember to point the target runtime to <property moreinfo="none">JBoss Portal</property> directory location (see
+ how it is done for a dynamic Web project: steps 3, 4 and 5 in the
+ <link linkend="jboss_core_portlet">"Creating a Web Project with JBoss Portlet Capabilities"</link> procedure).</para>
+
+ <figure float="0">
+ <title>Creating New JSF Project</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_portlet/jsf_portlet8.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>To add the JBoss Portlet capabilities to the created JSF project you should complete the next steps:</para>
+
+ <orderedlist continuation="restarts" inheritnum="ignore">
+ <listitem>
+ <para>Right-click the project and click <emphasis>
+ <property moreinfo="none">Properties</property>
+ </emphasis> to open the project <property moreinfo="none">Properties</property> sheet. Select <property moreinfo="none">Project Facets</property>
+ on the left and enable the <emphasis><property moreinfo="none">JavaServer Faces</property>,</emphasis>
+ <emphasis><property moreinfo="none">JBoss Core Portlet</property></emphasis> and <emphasis><property moreinfo="none">JBoss JSF Portlet</property></emphasis> facets.</para>
+
+ <figure float="0">
+ <title>Project Facets</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_portlet/jsf_portlet9.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+
+ <listitem>
+ <para>Notice, <emphasis>
+ <property moreinfo="none">"Further configuration available..."</property>
+ </emphasis> warning appears at the bottom of the screen. It means that next you should configure the JSF Portlet capabilities in the project.
+ Click the link. The <property moreinfo="none">Modify Faceted Project</property> wizard appears.</para>
+ </listitem>
+
+ <listitem>
+ <para>Complete all wizard pages the same way as described in the steps 5, 6, 7 of the
+ <link linkend="jboss_core_portlet">"Creating a Dynamic Web Project with the JBoss Portlet Capabilities"</link> procedure.
+ Hit <emphasis><property moreinfo="none">OK</property>.</emphasis></para>
+ </listitem>
+
+ <listitem>
+ <para>To apply the changes click <emphasis><property moreinfo="none">Apply</property></emphasis> and then
+ <emphasis><property moreinfo="none">OK</property></emphasis> to close the project <property moreinfo="none">Properties</property> sheet.</para>
+ </listitem>
+ </orderedlist>
+ </section>
+ </section>
+
+ <section id="jsf_portlet_to_JSF_project">
+ <title>Adding a JSF Portlet to the Project and Deploying It to JBoss Portal</title>
+
+ <para>The previous section has shown how to create a JSF project with JBoss Portlet and JSF Portlet capabilities enabled. Use
+ the following procedure to add a JSF portlet to the created project and deploy it to <property moreinfo="none">JBoss Portal</property>.</para>
+
+ <orderedlist continuation="restarts" inheritnum="ignore">
+ <listitem>
+ <para>Call the
+ <property moreinfo="none">Create Portlet</property> wizard by navigating to <emphasis>
+ <property moreinfo="none">New > Other > JBoss Tools Web > Portlet > JSF/Seam
+ Portlet</property></emphasis> on the context menu of the project (for information about the wizard options, see
+ <link linkend="jsf_seam_portlet_wizard">"JSF/Seam Portlet Wizard"</link> in the guide reference).</para>
+
+ <figure float="0">
+ <title>Calling New Portlet Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_portlet/jsf_portlet5.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <tip>
+ <title>Tip:</title>
+ <para>As you see, the JSF and Seam Portlet wizards are merged into one. We have set the JSF
+ configuration for the project, so the default values in this wizard will be set as for a JSF
+ portlet.</para>
+ </tip>
+ </listitem>
+
+ <listitem>
+ <para>Leave all the wizard pages with default values by clicking the <emphasis><property moreinfo="none">Next</property></emphasis> button,
+ on the last one click <emphasis><property moreinfo="none">Finish</property></emphasis> to complete the JSF portlet creation.</para>
+ </listitem>
+
+ <listitem>
+ <para>Complete the steps described in the <link linkend="deploying_to_portal">"Deploying a Portlet to JBoss Portal"</link> procedure to
+ deploy a JSF portlet to <property moreinfo="none">JBoss Portal</property>. Just use the other URL to see it in the browser:
+ <emphasis>http://localhost:8080/portal/portal/default/JSFPortlet</emphasis>.</para>
+
+ <figure float="0">
+ <title>JSF Portlet in the Browser</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_portlet/jsf_portlet7.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ </orderedlist>
+
+ </section>
+</section>
+
+
+<section id="seam_portlet" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/portlet/docs/reference/en/modules/seam_portlet.xml">
+ <title>Creating and Deploying a Seam Portlet</title>
+
+ <para>This chapter covers the steps on how to configure a Seam portlet within a Seam
+ project with the help of the <property moreinfo="none">JBoss Portlet Tools</property> features.</para>
+
+ <section id="seam_portlet1">
+ <title>Creating a Seam Project with JBoss Portlet Capabilities</title>
+
+ <para>Follow one of two ways of creating a Seam project with JBoss Portlet capabilities enabled:</para>
+ <orderedlist continuation="restarts" inheritnum="ignore">
+ <listitem>
+ <para>Create a dynamic Web project with the <emphasis><property moreinfo="none">Seam</property></emphasis>
+ and <emphasis><property moreinfo="none">JBoss Portlets</property></emphasis> facets enabled (<link linkend="create_dyn_web_proj_seam">the steps to proceed</link>)</para>
+ </listitem>
+ <listitem><para>Or create a Seam project with the JBoss Seam portlet configuration using the wizard JBoss Seam Tools provides
+ and follow all the wizard steps to enable JBoss Portlet capabilities (<link linkend="create_seam_proj">the steps to proceed</link>)</para></listitem>
+ </orderedlist>
+
+ <section id="create_dyn_web_proj_seam">
+ <title>Creating a Dynamic Web Project with Seam and JBoss Portlet Capabilities</title>
+
+ <para>To create a dynamic Web project with Seam and JBoss Portlet capabilities you should take the following steps:</para>
+
+ <orderedlist continuation="restarts" inheritnum="ignore">
+ <listitem>
+ <para>In the <emphasis><property moreinfo="none">File</property></emphasis> menu, go to
+ <emphasis><property moreinfo="none">New > Other > Web > Dynamic Web Project</property>.</emphasis> The <property moreinfo="none">New Dynamic Web Project</property>
+ wizard starts.</para>
+
+ <figure float="0">
+ <title>Creating a New Dynamic Web Project</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/seam_portlet/seam_portlet1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+
+ <listitem>
+ <para>Give the project a name and follow the steps 3, 4, 5 of the
+ <link linkend="jboss_core_portlet">"Creating a Web Project with JBoss Portlet Capabilities"</link> procedure to set the target runtime.</para>
+ </listitem>
+
+ <listitem>
+ <para>In the <emphasis><property moreinfo="none">Configuration</property></emphasis> area of the first wizard page,
+ select <emphasis>
+ <property moreinfo="none">JBoss Seam Portlet Project v2.0</property>.</emphasis> It will add needed facets to the project.</para>
+
+ <tip>
+ <title>Tip:</title>
+ <para>If you now click the <emphasis><property moreinfo="none">Modify</property></emphasis> button, you should see the
+ <emphasis><property moreinfo="none">JavaServer Faces</property>,</emphasis> <emphasis><property moreinfo="none">Jboss Portlets</property></emphasis>
+ and <emphasis><property moreinfo="none">Seam</property></emphasis> facets enabled.</para>
+ </tip>
+
+ <figure float="0">
+ <title>Project Facets</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/seam_portlet/seam_portlet2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+
+ <listitem>
+ <para>The next two pages are for adjusting the project Java and Web modules.
+ They include the default values, so you can skip them by pressing <emphasis>
+ <property moreinfo="none">Next</property>.</emphasis></para>
+ </listitem>
+
+ <listitem>
+ <para>On the <property moreinfo="none">Jboss Portlet Capabilities</property> page, select
+ <emphasis><property moreinfo="none">Portlet Target Runtime Provider</property></emphasis> as the portlet implementation library.</para>
+
+ <tip>
+ <title>Tip:</title>
+ <para>All types of the portlet implementation library are described more closely in the wiki article at:
+ <ulink url="http://www.jboss.org/community/wiki/PortletFacetLibraries">http://www.jboss.org/community/wiki/PortletFacetLibraries</ulink>.</para>
+ </tip>
+ </listitem>
+
+ <listitem>
+ <para>The next page is for configuring JSF capabilities. As it contains the default values, just click
+ <emphasis><property moreinfo="none">Next</property></emphasis> to proceed.</para>
+ </listitem>
+
+ <listitem>
+ <para>On the <property moreinfo="none">Seam Facet</property> page, set a Seam runtime and
+ a connection profile.</para>
+
+ <tip>
+ <title>Tip:</title>
+ <para>For details about how to set a Seam runtime and a connection profile, see
+ <ulink url="../../seam/html_single/index.html#seamFacet">"Configure Seam Facet Settings"</ulink> in the Chapter 2,
+ <ulink url="../../seam/html_single/index.html">"Seam Dev Tools Reference Guide"</ulink>.</para>
+ </tip>
+
+ <figure float="0">
+ <title>Seam Facet Settings</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/seam_portlet/seam_portlet3.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+
+ <listitem>
+ <para>On the <property moreinfo="none">JBoss JSF Portlet Capabilities</property> page, select the
+ <emphasis><property moreinfo="none">JSF Portlet Target Runtime Provider</property></emphasis> type of the implementation library.</para>
+
+ <tip>
+ <title>Tip:</title>
+ <para>If you have <property moreinfo="none">JBoss Portlet Bridge</property> downloaded,
+ alternatively you can select <emphasis><property moreinfo="none">JSF Portletbridge Runtime Provider</property></emphasis> and then provide a path to
+ the <property moreinfo="none">JBoss Portlet Bridge</property> distribution.</para>
+ </tip>
+
+ <figure float="0">
+ <title>Setting Portlet Bridge Provider</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jsf_portlet/jsf_portlet4.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>It will add <property moreinfo="none">JBoss Portlet Bridge</property> libraries to the project classpath.</para>
+ </listitem>
+
+ <listitem>
+ <para>Hit <emphasis><property moreinfo="none">Finish</property></emphasis> to complete the project creation.</para>
+ </listitem>
+ </orderedlist>
+ </section>
+
+ <section id="create_seam_proj">
+ <title>Creating a Seam Project with JBoss Portlet Capabilities</title>
+
+ <para>The steps to create a Seam project with JBoss Portlet capabilities are as follows:</para>
+
+ <orderedlist continuation="restarts" inheritnum="ignore">
+ <listitem>
+ <para>In the <emphasis><property moreinfo="none">File</property></emphasis> menu, go to <emphasis>
+ <property moreinfo="none">New > Other > Seam > Seam Web Project</property>.</emphasis> The <property moreinfo="none">New Seam Project</property>
+ wizard appears.</para>
+ </listitem>
+
+ <listitem>
+ <para>Next steps are the same as in the <link linkend="create_dyn_web_proj_seam">"Creating a Dynamic Web Project with Seam and JBoss Portlet Capabilities"</link>
+ procedure starting from the step 2.</para>
+ </listitem>
+ </orderedlist>
+ </section>
+ </section>
+
+ <section id="seam_portlet_to_seam_project">
+ <title>Adding a Seam Portlet to the Project and Deploying It to JBoss Portal</title>
+
+ <para>The previous section has shown you how to create a Web project with Seam and JBoss Portlet capabilities. Now you can create a Seam portlet
+ and deploy it to <property moreinfo="none">JBoss Portal</property> by following the next procedure:</para>
+
+ <orderedlist continuation="restarts" inheritnum="ignore">
+ <listitem>
+ <para>In the <emphasis><property moreinfo="none">File</property></emphasis> or context menu of the project go to
+ <emphasis><property moreinfo="none">New > Other > JBoss Tools Web > Portlet > JSF/Seam
+ Portlet</property>.</emphasis></para>
+
+ <figure float="0">
+ <title>Calling the Create Portlet Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/seam_portlet/seam_portlet5.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+
+ <listitem>
+ <para>The <property moreinfo="none">Create Portlet</property> wizard starts (for more information about wizard options, see
+ <link linkend="jsf_seam_portlet_wizard">"JSF/Seam Portlet Wizard"</link> in the guide reference).
+ As the Seam configuration is set for the project, the wizard puts the values as for Seam portlet.</para>
+
+ <figure float="0">
+ <title>Creating Seam Portlet</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/seam_portlet/seam_portlet6.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+
+ <listitem>
+ <para>Next two pages are filled out with default values, just press <emphasis><property moreinfo="none">Next</property></emphasis> to
+ proceed. On the last one click <emphasis><property moreinfo="none">Finish</property></emphasis> to complete.</para>
+ </listitem>
+
+ <listitem>
+ <para>To deploy and run the portlet on <property moreinfo="none">JBoss Portal</property> complete the steps described in the
+ <link linkend="deploying_to_portal">"Deploying a Portlet to JBoss Portal"</link> procedure. Just use the following URL to see it in the browser:
+ <emphasis>http://localhost:8080/portal/portal/default/SeamPortlet</emphasis>.</para>
+
+ <figure float="0">
+ <title>Seam Portlet in the Browser Window</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/seam_portlet/seam_portlet7.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ </orderedlist>
+ </section>
+</section>
+
+</chapter>
+
+<chapter id="reference" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/portlet/docs/reference/en/modules/reference.xml" xreflabel="reference">
+ <?dbhtml filename="reference.html"?>
+ <title>Reference</title>
+
+ <para>This chapter includes detailed reference information about <property moreinfo="none">JBoss Portlet Tools</property>.</para>
+ <section id="project_overview">
+ <title>JBoss Portlet Descriptors</title>
+
+ <para>In order to a web project with portlets could be deployed to <property moreinfo="none">JBoss Portal</property>, it should include certain descriptors.
+ The next table lists and describes these configuration files.</para>
+
+ <table>
+ <title>JBoss Portlet Descriptors</title>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry>Name</entry>
+
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>portlet.xml</entry>
+ <entry>The mandatory portlet descriptor defined by the <ulink url="http://www.jcp.org/en/jsr/detail?id=168">JSR-168 Portlet Specification</ulink>.
+ It is used during deployment.</entry>
+ </row>
+
+ <row>
+ <entry>portlet-instances.xml</entry>
+ <entry>The optional <property moreinfo="none">JBoss Portal</property> specific descriptor. It allows to create a portlet instance from a portlet class definition.</entry>
+ </row>
+
+ <row>
+ <entry>*-object.xml</entry>
+ <entry>The optional <property moreinfo="none">JBoss Portal</property> specific descriptor. It helps define the layout of the portal.</entry>
+ </row>
+
+ <row>
+ <entry>jboss-portlet.xml</entry>
+ <entry>The optional <property moreinfo="none">JBoss Portal</property> specific descriptor. It allows to use JBoss
+ specific functionality within a portlet application.</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ <para>For more detail information about each descriptor, see
+ <ulink url="http://docs.jboss.org/jbportal/v2.7.1/referenceGuide/html_single/#descrip...">"Portlet Descriptors"</ulink> in Chapter 6,
+ <ulink url="http://docs.jboss.org/jbportal/v2.7.1/referenceGuide/html_single/">"JBoss Portal Reference Guide"</ulink>.</para>
+ </section>
+
+ <section id="wizards">
+ <title>Wizards</title>
+ <para>This section describes the <property moreinfo="none">JBoss Portlet Tools</property> wizards:</para>
+ <itemizedlist>
+ <listitem><para><link linkend="java_portlet_wizard">Java Portlet wizard</link></para></listitem>
+ <listitem><para><link linkend="jsf_seam_portlet_wizard">JSF/Seam Portlet wizard</link></para></listitem>
+ </itemizedlist>
+
+ <section id="java_portlet_wizard">
+ <title>Java Portlet Wizard</title>
+
+ <para>The <property moreinfo="none">Java Portlet</property> wizard helps you create a new Java portlet (1.0 or 2.0). It is based on the WTP's Create Servlet wizard,
+ but adapted to JBoss Portlet. You can call it from the <emphasis><property moreinfo="none">File</property></emphasis> or context menu of your project by following to
+ <emphasis><property moreinfo="none">New > Other > JBoss Tools Web > Portlet > Java Portlet</property>.</emphasis></para>
+
+ <para>The wizard consists of the four pages:</para>
+
+ <orderedlist continuation="restarts" inheritnum="ignore">
+ <listitem>
+ <para>The first one includes the next options to adjust:</para>
+
+ <table>
+ <title>Java Portlet Wizard. First Page Options.</title>
+ <tgroup cols="3">
+ <colspec align="left" colnum="1" colwidth="1*"></colspec>
+ <colspec colnum="2" colwidth="3*"></colspec>
+ <colspec align="left" colnum="3" colwidth="1*"></colspec>
+
+ <thead>
+ <row>
+ <entry>Option</entry>
+ <entry>Description</entry>
+ <entry>Default</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Project</entry>
+ <entry>Select the project to add a new Java portlet</entry>
+ <entry>The project selected when the wizard has been started</entry>
+ </row>
+
+ <row>
+ <entry>Source folder</entry>
+ <entry>The path to the source folder relative to the selected project</entry>
+ <entry>The source folder of the project selected in the <emphasis><property moreinfo="none">Project</property></emphasis> field</entry>
+ </row>
+
+ <row>
+ <entry>Java package</entry>
+ <entry>Enter a package to contain a new portlet. Either type a valid package name or click
+ <emphasis><property moreinfo="none">Browse</property></emphasis> to select a package via the dialog box.</entry>
+ <entry><blank></entry>
+ </row>
+
+ <row>
+ <entry>Class name</entry>
+ <entry>Type a name for a new Java portlet class</entry>
+ <entry><blank></entry>
+ </row>
+
+ <row>
+ <entry>Superclass</entry>
+ <entry>Type or click <emphasis><property moreinfo="none">Browse</property></emphasis> to select a superclass for a Java portlet class</entry>
+ <entry>javax.portlet.GenericPortlet</entry>
+ </row>
+
+ <row>
+ <entry>Use an existing Portlet class</entry>
+ <entry>Select this check box if you want to use an existing Java portlet class. In the appeared
+ <emphasis><property moreinfo="none">Class name</property></emphasis> field type or
+ click <emphasis><property moreinfo="none">Browse</property></emphasis> to select an existing portlet class.</entry>
+ <entry>Cleared</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </listitem>
+
+ <listitem>
+ <para>The second wizard page is for specifying modifiers, interfaces to implement and method stubs to generate.</para>
+
+ <figure float="0">
+ <title>Second Page of the Java Portlet Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/javaPortlet2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The descriptions of the options listed on this page are in the following table.</para>
+
+ <table>
+ <title>Java Portlet Wizard. Second Page Options.</title>
+ <tgroup cols="3">
+ <colspec align="left" colnum="1" colwidth="1*"></colspec>
+ <colspec align="left" colnum="2" colwidth="3*"></colspec>
+ <colspec align="left" colnum="3" colwidth="1*"></colspec>
+
+ <thead>
+ <row>
+ <entry>Option</entry>
+ <entry>Description</entry>
+ <entry>Default</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Modifiers</entry>
+ <entry>Select one or more access modifiers for a new Java portlet class:
+ <itemizedlist>
+ <listitem><para>Public</para></listitem>
+ <listitem><para>Abstract</para></listitem>
+ <listitem><para>Final</para></listitem>
+ </itemizedlist>
+ </entry>
+ <entry>Public</entry>
+ </row>
+
+ <row>
+ <entry>Interfaces</entry>
+ <entry>Click <emphasis><property moreinfo="none">Add</property></emphasis> to choose interfaces that a new class implements</entry>
+ <entry><blank></entry>
+ </row>
+
+ <row>
+ <entry>Which method stubs would you like to create?</entry>
+ <entry>Choose which methods from superclass to override in the Java portlet class:
+ <itemizedlist>
+ <listitem><para>Constructors from superclass</para></listitem>
+ <listitem><para>Inherited abstract methods</para></listitem>
+ <listitem><para>init</para></listitem>
+ <listitem><para>doView</para></listitem>
+ <listitem><para>doDispatch</para></listitem>
+ <listitem><para>destroy</para></listitem>
+ <listitem><para>doEdit</para></listitem>
+ <listitem><para>processAction</para></listitem>
+ <listitem><para>getPortletConfig</para></listitem>
+ <listitem><para>doHelp</para></listitem>
+ <listitem><para>render</para></listitem>
+ </itemizedlist>
+ </entry>
+ <entry>Inherited abstract methods, doView</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </listitem>
+
+ <listitem>
+ <para>The third page is for adjusting the portlet deployment descriptor settings.</para>
+
+ <figure float="0">
+ <title>Third Page of the Java Portlet Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/javaPortlet3.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <table>
+ <title>Java Portlet Wizard. Third Page Options.</title>
+ <tgroup cols="3">
+ <colspec align="left" colnum="1" colwidth="1*"></colspec>
+ <colspec align="left" colnum="2" colwidth="3*"></colspec>
+ <colspec align="left" colnum="3" colwidth="1*"></colspec>
+
+ <thead>
+ <row>
+ <entry>Option</entry>
+ <entry>Description</entry>
+ <entry>Default</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Name</entry>
+ <entry>Enter the portlet name. It does not have to be the portlet class name.</entry>
+ <entry>The name of the portlet class</entry>
+ </row>
+
+ <row>
+ <entry>Display name</entry>
+ <entry>Enter the display name of the Java portlet</entry>
+ <entry>The name of the portlet class</entry>
+ </row>
+
+ <row>
+ <entry>Title</entry>
+ <entry>Enter the title of the portlet</entry>
+ <entry>The name of the portlet class</entry>
+ </row>
+
+ <row>
+ <entry>Description</entry>
+ <entry>Enter the description of the portlet's function</entry>
+ <entry><blank></entry>
+ </row>
+
+ <row>
+ <entry>Portlet Modes</entry>
+ <entry>Select one or more of three modes defined by the JSR-286 specification:
+ <itemizedlist>
+ <listitem><para><emphasis>View</emphasis> - generates markup reflecting the current state of the portlet;</para></listitem>
+ <listitem><para><emphasis>Edit</emphasis> - allows customizing the behavior of the portlet;</para></listitem>
+ <listitem><para><emphasis>Help</emphasis> - provides an information on how to use the portlet.</para></listitem>
+ </itemizedlist>
+ </entry>
+ <entry>View</entry>
+ </row>
+
+ <row>
+ <entry>Initialization Parameters</entry>
+ <entry>Specify initialization parameters to create an initial state inside your portlet class. Click
+ <emphasis><property moreinfo="none">Add</property></emphasis> and fill in the
+ <emphasis><property moreinfo="none">Name</property>,</emphasis> <emphasis><property moreinfo="none">Value</property></emphasis> and
+ <emphasis><property moreinfo="none">Description</property></emphasis> (optional) fields to set a parameter.</entry>
+ <entry><blank></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ </listitem>
+
+ <listitem>
+ <para>The last wizard page helps configure the JBoss Portlet specific descriptors.</para>
+
+ <figure float="0">
+ <title>Last Page of the Java Portlet Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/javaPortlet4.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <table>
+ <title>Java Portlet Wizard. Last Page Options.</title>
+ <tgroup cols="3">
+ <colspec align="left" colnum="1" colwidth="1*"></colspec>
+ <colspec align="left" colnum="2" colwidth="3*"></colspec>
+ <colspec align="left" colnum="3" colwidth="1*"></colspec>
+
+ <thead>
+ <row>
+ <entry>Option</entry>
+ <entry>Description</entry>
+ <entry>Default</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Create Portlet Instance</entry>
+ <entry>Clear the <emphasis><property moreinfo="none">Create Portlet Instance</property></emphasis> check box,
+ if you don't wont the wizard to create the deployment elements
+ in the <literal moreinfo="none">default-object.xml</literal> and <literal moreinfo="none">
+ portlet-instances.xml</literal> files</entry>
+ <entry>Selected</entry>
+ </row>
+
+ <row>
+ <entry>If Exists</entry>
+ <entry>Select one of two options:
+ <itemizedlist>
+ <listitem><para><emphasis>overwrite</emphasis> - destroys the existing object and creates a new one based on the content of the deployment</para></listitem>
+ <listitem><para><emphasis>keep</emphasis> - maintains the existing object deployment or creates a new one if it does not exist</para></listitem>
+ </itemizedlist>
+ </entry>
+ <entry>overwrite</entry>
+ </row>
+
+ <row>
+ <entry>Instance Name</entry>
+ <entry>Enter a name of the portlet instance that the portlet window represents</entry>
+ <entry>[Portlet class name]Instance</entry>
+ </row>
+
+ <row>
+ <entry>Page Name</entry>
+ <entry>If set, the portlet page is created with the name defined</entry>
+ <entry><blank></entry>
+ </row>
+
+ <row>
+ <entry>Window Name</entry>
+ <entry>Enter a name of the portlet window</entry>
+ <entry>[Portlet class name]Window</entry>
+ </row>
+
+ <row>
+ <entry>Parent Reference</entry>
+ <entry>
+ <para>Define a reference to the parent object. The syntax for this element is <literal moreinfo="none">[portal-instance].[portal-page]</literal>.</para>
+ <para>For example, <literal moreinfo="none">default.default</literal> means that the window appears on the default page, in the default portal.</para>
+ </entry>
+ <entry>default.default</entry>
+ </row>
+
+ <row>
+ <entry>Region</entry>
+ <entry>Specify the region where the window should appear on the page</entry>
+ <entry>center</entry>
+ </row>
+
+ <row>
+ <entry>Height</entry>
+ <entry>Define the height of the window</entry>
+ <entry>1</entry>
+ </row>
+
+ <row>
+ <entry>Initial Window State</entry>
+ <entry>Set the window state indicator by selecting one of three states defined by the JSR-168 specification:
+ <itemizedlist>
+ <listitem><para><emphasis>normal</emphasis> - a portlet shares this page with other portlets</para></listitem>
+ <listitem><para><emphasis>minimized</emphasis> - a portlet may show very little information or none at all</para></listitem>
+ <listitem><para><emphasis>maximized</emphasis> - a portlet may be the only portlet displayed on this page</para></listitem>
+ </itemizedlist>
+ </entry>
+ <entry>maximized</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </listitem>
+ </orderedlist>
+ </section>
+
+ <section id="jsf_seam_portlet_wizard">
+ <title>JSF/Seam Portlet Wizard</title>
+
+ <para>The <property moreinfo="none">JSF/Seam Portlet</property> wizard, that is merged into one JSF and Seam Portlet wizards, helps you create a
+ JSF/Seam portlet that uses the <property moreinfo="none">JBoss Portlet Bridge</property> libraries. The default values in this wizard
+ depend on the configuration set for the project. For instance, if you set the JSF configuration, the default values in this wizard will be
+ as for a JSF portlet.</para>
+
+ <para>The <property moreinfo="none">JSF/Seam Portlet</property> wizard could be started from the <emphasis><property moreinfo="none">File</property></emphasis> or
+ context menu of your project by following to
+ <emphasis><property moreinfo="none">New > Other > JBoss Tools Web > Portlet > JSF/Seam Portlet</property>.</emphasis></para>
+
+ <para>The wizard includes three pages to adjust JSF/Seam portlet setting:</para>
+
+ <orderedlist continuation="restarts" inheritnum="ignore">
+ <listitem>
+ <para>The first wizard page asks to select a project to add JSF/Seam portlet and set a class file destination.</para>
+
+ <figure float="0">
+ <title>First Page of the JSF Portlet Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/jsf_seam_portlet1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <table>
+ <title>JSF/Seam Portlet Wizard. First Page Options.</title>
+ <tgroup cols="3">
+ <colspec align="left" colnum="1" colwidth="1*"></colspec>
+ <colspec align="left" colnum="2" colwidth="3*"></colspec>
+ <colspec align="left" colnum="3" colwidth="1*"></colspec>
+
+ <thead>
+ <row>
+ <entry>Option</entry>
+ <entry>Description</entry>
+ <entry>Default</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Project</entry>
+ <entry>Select the project to add a new JSF/Seam portlet</entry>
+ <entry>The project selected when the wizard has been started</entry>
+ </row>
+
+ <row>
+ <entry>Class name</entry>
+ <entry>Type or click <emphasis><property moreinfo="none">Browse</property></emphasis> to select a class for a JSF/Seam portlet</entry>
+ <entry>javax.portlet.faces.GenericFacesPortlet</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </listitem>
+
+ <listitem>
+ <para>The second page allows to configure a portlet deployment descriptors.</para>
+
+ <figure float="0">
+ <title>Second Page of the JSF Portlet Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/jsf_seam_portlet2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <table>
+ <title>JSF/Seam Portlet Wizard. Second Page Options.</title>
+ <tgroup cols="3">
+ <colspec align="left" colnum="1" colwidth="1*"></colspec>
+ <colspec align="left" colnum="2" colwidth="3*"></colspec>
+ <colspec align="left" colnum="3" colwidth="1*"></colspec>
+
+ <thead>
+ <row>
+ <entry>Option</entry>
+ <entry>Description</entry>
+ <entry>Default (JSF / Seam)</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Name</entry>
+ <entry>Enter the portlet name. It does not have to be the portlet class name.</entry>
+ <entry>riPortlet / seamPortlet</entry>
+ </row>
+
+ <row>
+ <entry>Display name</entry>
+ <entry>Enter the display name of the Java portlet</entry>
+ <entry>JBoss JSF Portlet / JBoss Seam Portlet</entry>
+ </row>
+
+ <row>
+ <entry>Title</entry>
+ <entry>Enter the title of the portlet</entry>
+ <entry>JBoss JSF Portlet / JBoss Seam Portlet</entry>
+ </row>
+
+ <row>
+ <entry>Description</entry>
+ <entry>Enter the description of the portlet's function</entry>
+ <entry><blank></entry>
+ </row>
+
+ <row>
+ <entry>Portlet Modes</entry>
+ <entry>Select one or more of three modes defined by the JSR-286 specification:
+ <itemizedlist>
+ <listitem><para><emphasis>View</emphasis> - generates markup reflecting the current state of the portlet</para></listitem>
+ <listitem><para><emphasis>Edit</emphasis> - allows customizing the behavior of the portlet</para></listitem>
+ <listitem><para><emphasis>Help</emphasis> - provides an information on how to use the portlet</para></listitem>
+ </itemizedlist>
+ </entry>
+ <entry>View, Edit, Help / View</entry>
+ </row>
+
+ <row>
+ <entry>Initialization Parameters</entry>
+ <entry>Specify initialization parameters to create an initial state inside your portlet class. Click
+ <emphasis><property moreinfo="none">Add</property></emphasis> and fill in the
+ <emphasis><property moreinfo="none">Name</property>,</emphasis> <emphasis><property moreinfo="none">Value</property></emphasis> and
+ <emphasis><property moreinfo="none">Description</property></emphasis> (optional) fields to set a parameter.</entry>
+ <entry>javax.portlet.faces.defaultViewId.view, javax.portlet.faces.defaultViewId.edit,
+ javax.portlet.faces.defaultViewId.help / javax.portlet.faces.defaultViewId.view</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </listitem>
+
+ <listitem>
+ <para>The last wizard page helps you configure the JBoss Portlet specific information.</para>
+
+ <figure float="0">
+ <title>Third Page of the JSF Portlet Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/jsf_seam_portlet3.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <table>
+ <title>JSF/Seam Portlet Wizard. Third Page Options.</title>
+ <tgroup cols="3">
+ <colspec align="left" colnum="1" colwidth="1*"></colspec>
+ <colspec align="left" colnum="2" colwidth="3*"></colspec>
+ <colspec align="left" colnum="3" colwidth="1*"></colspec>
+
+ <thead>
+ <row>
+ <entry>Option</entry>
+ <entry>Description</entry>
+ <entry>Default (JSF / Seam)</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Create Portlet Instance</entry>
+ <entry>Clear the <emphasis><property moreinfo="none">Create Portlet Instance</property></emphasis> check box,
+ if you don't wont the wizard to create the deployment elements
+ in the <literal moreinfo="none">default-object.xml</literal> and <literal moreinfo="none">
+ portlet-instances.xml</literal> files</entry>
+ <entry>Selected</entry>
+ </row>
+
+ <row>
+ <entry>If Exists</entry>
+ <entry>Select one of two options:
+ <itemizedlist>
+ <listitem><para><emphasis>overwrite</emphasis> - destroys the existing object and creates a new one based on the content of the deployment</para></listitem>
+ <listitem><para><emphasis>keep</emphasis> - maintains the existing object deployment or creates a new one if it does not exist</para></listitem>
+ </itemizedlist>
+ </entry>
+ <entry>overwrite</entry>
+ </row>
+
+ <row>
+ <entry>Instance Name</entry>
+ <entry>Enter a name of the portlet instance that the portlet window represents</entry>
+ <entry>JSFPortletInstance / SeamPortletInstance</entry>
+ </row>
+
+ <row>
+ <entry>Page Name</entry>
+ <entry>If set, the portlet page is created with the name defined</entry>
+ <entry>JSFPortlet / SeamPortlet</entry>
+ </row>
+
+ <row>
+ <entry>Window Name</entry>
+ <entry>Enter a name of the portlet window</entry>
+ <entry>JSFPortletWindow / SeamPortletWindow</entry>
+ </row>
+
+ <row>
+ <entry>Parent Reference</entry>
+ <entry>
+ <para>Define a reference to the parent object.</para>
+ <para>For example, <literal moreinfo="none">default</literal> means that the page appears in the default portal.</para>
+ </entry>
+ <entry>default</entry>
+ </row>
+
+ <row>
+ <entry>Region</entry>
+ <entry>Specify the region where the window should appear on the page</entry>
+ <entry>center</entry>
+ </row>
+
+ <row>
+ <entry>Height</entry>
+ <entry>Define the height of the window</entry>
+ <entry>1</entry>
+ </row>
+
+ <row>
+ <entry>Initial Window State</entry>
+ <entry>Set the window state indicator by selecting one of three states defined by the JSR-168 specification:
+ <itemizedlist>
+ <listitem><para><emphasis>normal</emphasis> - a portlet shares this page with other portlets</para></listitem>
+ <listitem><para><emphasis>minimized</emphasis> - a portlet may show very little information or none at all</para></listitem>
+ <listitem><para><emphasis>maximized</emphasis> - a portlet may be the only portlet displayed on this page</para></listitem>
+ </itemizedlist>
+ </entry>
+ <entry>maximized</entry>
+ </row>
+
+ <row>
+ <entry>Create JBoss Application</entry>
+ <entry>
+ <para>Select to add the <literal moreinfo="none">jboss-app.xml</literal> descriptor.</para>
+ <para><emphasis>riPortletApp / seamPortletApp</emphasis> - the default name of the JBoss application. You can change it by
+ typing a new one in the <emphasis><property moreinfo="none">JBoss Application Name</property></emphasis> field.</para>
+ </entry>
+ <entry>Selected</entry>
+ </row>
+
+ <row>
+ <entry>Add the jboss-portlet.xml file</entry>
+ <entry>Select to create the <literal moreinfo="none">jboss-portlet.xml</literal> file</entry>
+ <entry>Selected</entry>
+ </row>
+
+ <row>
+ <entry>Copy JSF Templates</entry>
+ <entry>Select to add the folder with JSF templates (<literal moreinfo="none">edit.jsp</literal>, <literal moreinfo="none">help.jsp</literal>,
+ <literal moreinfo="none">view.jsp</literal>) to the project</entry>
+ <entry>Cleared</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </listitem>
+ </orderedlist>
+ </section>
+ </section>
+
+ <section id="preferences">
+ <title>JBoss Portlet Preferences</title>
+
+ <para>To open <property moreinfo="none">JBoss Portlet Preferences</property> property sheet, go to <emphasis>
+ <property moreinfo="none">Window > Preferences</property>
+ </emphasis> and then <emphasis>
+ <property moreinfo="none">JBoss Tools > JBoss Portlet</property>.
+ </emphasis></para>
+
+ <figure float="0">
+ <title>JBoss Runtime Preferences</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/reference/portlet_preferences.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The <emphasis>
+ <property moreinfo="none">Check runtimes for Portlet Components</property>
+ </emphasis> option makes the JBoss Portlet functionality always visible no matter what the runtime is set. By default the option is checked.</para>
+ </section>
+</chapter>
+
+<chapter id="summary" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/portlet/docs/reference/en/modules/summary.xml" xreflabel="summary">
+ <?dbhtml filename="summary.html"?>
+ <title>Summary</title>
+
+ <para>In conclusion, with this document you could easily get started with <property moreinfo="none">JBoss
+ Portlet Tools</property>.
+ The above chapters walked you through the steps on how to organize a web project with
+ JBoss Portlet capabilities enabled, create a Java portlet, JSF or Seam portlet and deploy them to <property moreinfo="none">JBoss
+ Portal</property>. The document also includes the reference of <property moreinfo="none">JBoss Portlet Tools</property> features.</para>
+
+ <para>If you have questions or suggestions concerned both the documentation and tools behavior, you are welcome
+ to <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss Tools Users forum</ulink>.</para>
+
+ <para>Please, use <ulink url="https://jira.jboss.org/jira/browse/JBDS">Jira</ulink> to report bugs and requests on documentation.</para>
+
+ <section id="rel_resources">
+ <title>Other Relevant Resources on the Topic</title>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ JBoss Portal home page: <ulink url="http://www.jboss.org/jbossportal/">http://www.jboss.org/jbossportal/</ulink>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ JBoss Portal Wiki at: <ulink url="http://wiki.jboss.org/wiki/JBossPortal">http://wiki.jboss.org/wiki/JBossPortal</ulink>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>JBoss Portal documentation set at: <ulink url="http://docs.jboss.org/jbportal/">http://docs.jboss.org/jbportal/</ulink></para>
+ </listitem>
+
+ <listitem>
+ <para>
+ JBoss Tools home page at: <ulink url="http://www.jboss.org/tools/">http://www.jboss.org/tools/</ulink>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The latest JBossTools/JBDS documentation builds at: <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">http://download.jboss.org/jbosstools/nightly-docs/</ulink>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>JBoss Developer Studio/JBoss Tools release documentation you can
+ find at <ulink url="http://docs.jboss.org/tools/">http://docs.jboss.org/tools</ulink> in the corresponding release directory.</para>
+ </listitem>
+ </itemizedlist>
+
+ </section>
+</chapter>
+</book>
Modified: branches/jbosstools-3.1.x/portlet/docs/reference/pom.xml
===================================================================
--- branches/jbosstools-3.1.x/portlet/docs/reference/pom.xml 2010-03-03 14:26:39 UTC (rev 20615)
+++ branches/jbosstools-3.1.x/portlet/docs/reference/pom.xml 2010-03-03 14:26:45 UTC (rev 20616)
@@ -32,7 +32,7 @@
<profile>
<id>releaseJBDS</id>
<properties>
- <master>master_output.xml</master>
+ <master>master.xml</master>
<xsl-single>classpath:/xslt/com/jboss/tools/xhtml-single-release.xsl</xsl-single>
<xsl-chunked>classpath:/xslt/com/jboss/tools/xhtml-release.xsl</xsl-chunked>
<xsl-pdf>classpath:/xslt/com/jboss/tools/pdf.xsl</xsl-pdf>
14 years, 2 months
- 1
- 0
JBoss Tools SVN: r20615 - in branches/jbosstools-3.1.x/jbpm/plugins/org.jboss.tools.flow.jpdl4: src/org/jboss/tools/flow/jpdl4/wizard and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: koen.aers(a)jboss.com
Date: 2010-03-03 09:26:39 -0500 (Wed, 03 Mar 2010)
New Revision: 20615
Modified:
branches/jbosstools-3.1.x/jbpm/plugins/org.jboss.tools.flow.jpdl4/plugin.xml
branches/jbosstools-3.1.x/jbpm/plugins/org.jboss.tools.flow.jpdl4/src/org/jboss/tools/flow/jpdl4/wizard/ChooseJpdl4RuntimePage.java
branches/jbosstools-3.1.x/jbpm/plugins/org.jboss.tools.flow.jpdl4/src/org/jboss/tools/flow/jpdl4/wizard/ConfigureJpdl4RuntimePage.java
Log:
JBIDE-5906: Invalid perspectiveExtensions extension point in org.jboss.tools.flow.jpdl4
Modified: branches/jbosstools-3.1.x/jbpm/plugins/org.jboss.tools.flow.jpdl4/plugin.xml
===================================================================
--- branches/jbosstools-3.1.x/jbpm/plugins/org.jboss.tools.flow.jpdl4/plugin.xml 2010-03-03 14:22:11 UTC (rev 20614)
+++ branches/jbosstools-3.1.x/jbpm/plugins/org.jboss.tools.flow.jpdl4/plugin.xml 2010-03-03 14:26:39 UTC (rev 20615)
@@ -962,13 +962,6 @@
<view
id="org.jboss.tools.flow.jpdl4.details"
minimized="false"
- relationship="stack"
- relative="org.eclipse.mylyn.tasks.ui.views.tasks"
- visible="false">
- </view>
- <view
- id="org.jboss.tools.flow.jpdl4.details"
- minimized="false"
ratio="0.5"
relationship="top"
relative="org.eclipse.ui.views.ContentOutline"
Modified: branches/jbosstools-3.1.x/jbpm/plugins/org.jboss.tools.flow.jpdl4/src/org/jboss/tools/flow/jpdl4/wizard/ChooseJpdl4RuntimePage.java
===================================================================
--- branches/jbosstools-3.1.x/jbpm/plugins/org.jboss.tools.flow.jpdl4/src/org/jboss/tools/flow/jpdl4/wizard/ChooseJpdl4RuntimePage.java 2010-03-03 14:22:11 UTC (rev 20614)
+++ branches/jbosstools-3.1.x/jbpm/plugins/org.jboss.tools.flow.jpdl4/src/org/jboss/tools/flow/jpdl4/wizard/ChooseJpdl4RuntimePage.java 2010-03-03 14:26:39 UTC (rev 20615)
@@ -21,8 +21,6 @@
*/
package org.jboss.tools.flow.jpdl4.wizard;
-import java.util.Iterator;
-
import org.eclipse.jface.wizard.WizardPage;
import org.eclipse.swt.SWT;
import org.eclipse.swt.events.SelectionAdapter;
@@ -33,7 +31,6 @@
import org.eclipse.swt.widgets.Combo;
import org.eclipse.swt.widgets.Composite;
import org.eclipse.swt.widgets.Group;
-import org.jboss.tools.jbpm.preferences.PreferencesManager;
public class ChooseJpdl4RuntimePage extends WizardPage {
Modified: branches/jbosstools-3.1.x/jbpm/plugins/org.jboss.tools.flow.jpdl4/src/org/jboss/tools/flow/jpdl4/wizard/ConfigureJpdl4RuntimePage.java
===================================================================
--- branches/jbosstools-3.1.x/jbpm/plugins/org.jboss.tools.flow.jpdl4/src/org/jboss/tools/flow/jpdl4/wizard/ConfigureJpdl4RuntimePage.java 2010-03-03 14:22:11 UTC (rev 20614)
+++ branches/jbosstools-3.1.x/jbpm/plugins/org.jboss.tools.flow.jpdl4/src/org/jboss/tools/flow/jpdl4/wizard/ConfigureJpdl4RuntimePage.java 2010-03-03 14:26:39 UTC (rev 20615)
@@ -22,7 +22,6 @@
package org.jboss.tools.flow.jpdl4.wizard;
import java.io.File;
-import java.net.MalformedURLException;
import org.eclipse.core.runtime.Path;
import org.eclipse.jface.wizard.WizardPage;
@@ -41,7 +40,6 @@
import org.eclipse.swt.widgets.Label;
import org.eclipse.swt.widgets.Link;
import org.eclipse.swt.widgets.Text;
-import org.w3c.dom.Document;
public class ConfigureJpdl4RuntimePage extends WizardPage {
14 years, 2 months
- 1
- 0
JBoss Tools SVN: r20614 - in trunk: jst/plugins/org.jboss.tools.jst.jsp/src/org/jboss/tools/jst/jsp/jspeditor and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: dmaliarevich
Date: 2010-03-03 09:22:11 -0500 (Wed, 03 Mar 2010)
New Revision: 20614
Modified:
trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/editors/dnd/DefaultDropCommand.java
trunk/jst/plugins/org.jboss.tools.jst.jsp/src/org/jboss/tools/jst/jsp/jspeditor/JSPTextEditor.java
Log:
https://jira.jboss.org/jira/browse/JBIDE-5874 --- dialog opening logic was corrected.
Modified: trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/editors/dnd/DefaultDropCommand.java
===================================================================
--- trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/editors/dnd/DefaultDropCommand.java 2010-03-03 14:21:54 UTC (rev 20613)
+++ trunk/common/plugins/org.jboss.tools.common.model.ui/src/org/jboss/tools/common/model/ui/editors/dnd/DefaultDropCommand.java 2010-03-03 14:22:11 UTC (rev 20614)
@@ -15,7 +15,8 @@
import org.eclipse.core.runtime.CoreException;
import org.eclipse.core.runtime.NullProgressMonitor;
import org.eclipse.jface.wizard.WizardDialog;
-import org.eclipse.swt.widgets.Display;
+import org.eclipse.swt.widgets.Shell;
+import org.eclipse.ui.PlatformUI;
import org.jboss.tools.common.model.ui.ModelUIPlugin;
import org.jboss.tools.common.model.ui.editors.dnd.composite.TagProposalsComposite;
@@ -80,18 +81,33 @@
* @param data
*/
public void execute(DropData data) {
- getDefaultModel().setDropData(data);
- initialize();
- if(getDefaultModel().isWizardRequired()) {
- WizardDialog dialog = new DropWizardDialog(
- Display.getCurrent().getActiveShell(),
- createDropWizard()
- );
- dialog.open();
- } else {
- execute();
+ /*
+ * Fixes https://jira.jboss.org/jira/browse/JBIDE-5874
+ * Checks it the Dialog Shell was already opened.
+ * If so do not create one more instance.
+ */
+ Shell[] existedShells = PlatformUI.getWorkbench().getDisplay().getShells();
+ boolean dialogWasAlreadyOpened = false;
+ for (Shell sh : existedShells) {
+ if (DropWizardMessages.Wizard_Window_Title
+ .equalsIgnoreCase(sh.getText())) {
+ dialogWasAlreadyOpened = true;
+ }
}
- getDefaultModel().setDropData(null);
+ if (!dialogWasAlreadyOpened) {
+ getDefaultModel().setDropData(data);
+ initialize();
+ if(getDefaultModel().isWizardRequired()) {
+ WizardDialog dialog = new DropWizardDialog(
+ PlatformUI.getWorkbench().getDisplay().getActiveShell(),
+ createDropWizard()
+ );
+ dialog.open();
+ } else {
+ execute();
+ }
+ getDefaultModel().setDropData(null);
+ }
}
protected IDropWizard createDropWizard() {
Modified: trunk/jst/plugins/org.jboss.tools.jst.jsp/src/org/jboss/tools/jst/jsp/jspeditor/JSPTextEditor.java
===================================================================
--- trunk/jst/plugins/org.jboss.tools.jst.jsp/src/org/jboss/tools/jst/jsp/jspeditor/JSPTextEditor.java 2010-03-03 14:21:54 UTC (rev 20613)
+++ trunk/jst/plugins/org.jboss.tools.jst.jsp/src/org/jboss/tools/jst/jsp/jspeditor/JSPTextEditor.java 2010-03-03 14:22:11 UTC (rev 20614)
@@ -66,6 +66,7 @@
import org.eclipse.ui.IActionBars;
import org.eclipse.ui.IEditorInput;
import org.eclipse.ui.IEditorPart;
+import org.eclipse.ui.PlatformUI;
import org.eclipse.ui.actions.ActionFactory;
import org.eclipse.ui.editors.text.ILocationProvider;
import org.eclipse.ui.texteditor.ITextEditor;
@@ -735,7 +736,13 @@
public void runDropCommand(final String flavor, final String data) {
XModelBuffer b = XModelTransferBuffer.getInstance().getBuffer();
final XModelObject o = b == null ? null : b.source();
- Display.getDefault().asyncExec(new Runnable() {
+ /*
+ * Fixes https://jira.jboss.org/jira/browse/JBIDE-5874
+ * Display.getDefault() should always be replaced by
+ * PlatformUI.getWorkbench().getDisplay().
+ * syncExec() will reduce the number if simultaneously launched threads.
+ */
+ PlatformUI.getWorkbench().getDisplay().syncExec(new Runnable() {
public void run() {
if (o != null
&& !XModelTransferBuffer.getInstance().isEnabled()) {
14 years, 2 months
- 1
- 0
JBoss Tools SVN: r20613 - in branches/jbosstools-3.1.x/ws/docs/reference: en and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2010-03-03 09:21:54 -0500 (Wed, 03 Mar 2010)
New Revision: 20613
Modified:
branches/jbosstools-3.1.x/ws/docs/reference/en/master.xml
branches/jbosstools-3.1.x/ws/docs/reference/en/master_output.xml
branches/jbosstools-3.1.x/ws/docs/reference/pom.xml
Log:
<html><head><meta name="qrichtext" content="1" /></head><body style="font-size:9pt;font-family:Sans Serif">
<p>https://jira.jboss.org/jira/browse/JBDS-1107 -Updated docs source files here with the ones for JBDS 3.0.0 GA release. </p>
<p></p>
</body></html>
Modified: branches/jbosstools-3.1.x/ws/docs/reference/en/master.xml
===================================================================
--- branches/jbosstools-3.1.x/ws/docs/reference/en/master.xml 2010-03-03 14:17:47 UTC (rev 20612)
+++ branches/jbosstools-3.1.x/ws/docs/reference/en/master.xml 2010-03-03 14:21:54 UTC (rev 20613)
@@ -29,12 +29,12 @@
<copyright>
<year>2008</year>
- <year>2009</year>
+ <year>2009</year>
<year>2010</year>
<holder>JBoss by Red Hat</holder>
</copyright>
<releaseinfo>
- Version: 1.1.0.CR1
+ Version: 1.1.0.GA
</releaseinfo>
<abstract>
<title/>
Modified: branches/jbosstools-3.1.x/ws/docs/reference/en/master_output.xml
===================================================================
--- branches/jbosstools-3.1.x/ws/docs/reference/en/master_output.xml 2010-03-03 14:17:47 UTC (rev 20612)
+++ branches/jbosstools-3.1.x/ws/docs/reference/en/master_output.xml 2010-03-03 14:21:54 UTC (rev 20613)
@@ -7,698 +7,699 @@
<!ENTITY preference SYSTEM "modules/preference.xml">
<!ENTITY webproject SYSTEM "modules/webproject.xml">
<!ENTITY client SYSTEM "modules/client.xml">
-]><book xmlns:diffmk="http://diffmk.sf.net/ns/diff">
-
- <bookinfo>
- <title>JBoss WS User Guide</title>
-
- <corpauthor>
- <inlinemediaobject>
- <imageobject role="fo">
- <imagedata fileref="images/jbosstools_logo.png" format="PNG"></imagedata>
- </imageobject>
- <imageobject role="html">
- <imagedata></imagedata>
- </imageobject>
- </inlinemediaobject>
- </corpauthor>
- <author><firstname>Denny</firstname><surname>Xu</surname><email>dxu(a)redhat.com</email></author>
- <author><firstname>Grid</firstname><surname>Qian</surname><email>fqian(a)redhat.com</email></author>
- <pubdate>July 2008</pubdate>
- <copyright>
- <year>2008</year>
- <year>2009</year>
- <holder>JBoss by Red Hat</holder>
- </copyright>
- <releaseinfo><diffmk:wrapper diffmk:change="changed">
- Version: 1.1.0.CR1
- </diffmk:wrapper></releaseinfo>
-<abstract>
- <title></title>
- <para>
- <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/ws_ref_guide/pdf/WS_...">PDF version</ulink>
- </para>
-</abstract>
-
-
- </bookinfo>
-
- <toc></toc>
-
-<chapter id="overview" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/ws/docs/reference/en/modules/overview.xml">
- <title>JBossWS Runtime Overview</title>
-
- <para>JBossWS is a web service framework developed as a part of the JBoss Application Server. It implements the JAX-WS specification that defines a programming model and run-time architecture for implementing web services in Java, targeted at the Java Platform, Enterprise Edition 5 (Java EE 5).</para>
- <para>JBossWS integrates with most current JBoss Application Server releases as well as earlier ones, that did implement the J2EE 1.4 specifications. Even though JAX-RPC, the web service specification for J2EE 1.4, is still supported JBossWS does put a clear focus on JAX-WS.</para>
-
-<section>
- <title>Key Features of JBossWS</title>
- <para>For a start, we propose you to look through the table of main features of JBossWS Runtime:</para>
-
- <table>
-
- <title>Key Functionality for JBossWS</title>
- <tgroup cols="2">
-
- <colspec align="left" colnum="1" colwidth="2*"></colspec>
- <colspec colnum="2" colwidth="4*"></colspec>
-
-
- <thead>
- <row>
- <entry>Feature</entry>
- <entry>Benefit</entry>
-
- </row>
- </thead>
-
- <tbody>
-
- <row>
- <entry><para>JAX-RPC and JAX-WS support</para></entry>
- <entry><para>JBossWS implements both the JAX-WS and JAX-RPC specifications.</para></entry>
-
- </row>
-
- <row>
- <entry><para>EJB 2.1, EJB3 and JSE endpoints</para></entry>
- <entry><para>JBossWS supports EJB 2.1, EJB3 and JSE as Web Service Endpoints.</para></entry>
-
- </row>
-
- <row>
- <entry><para>WS-Security 1.0 for XML Encryption/Signature of the SOAP message</para></entry>
- <entry><para>WS-Security standardizes authorization, encryption, and digital signature processing of web services.</para></entry>
-
- </row>
-
- <row>
- <entry><para>JBoss AS</para></entry>
- <entry><para>JBoss Application Server 5 (JavaEE 5 compliant) web service stack.</para></entry>
-
- </row>
-
- <row>
- <entry><para>Support for MTOM/XOP and SwA-Ref</para></entry>
- <entry><para>Message Transmission Optimization Mechanism (MTOM) and XML-binary Optimized Packaging (XOP) more efficiently serialize XML Infosets that have certain types of content.</para></entry>
-
- </row>
-
- </tbody>
-
- </tgroup>
- </table>
-
-
-</section>
-<section>
- <title>Other relevant resources on the topic</title>
-
- <para>You can find some extra information on:</para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://www.jboss.org/community/wiki/JBossWS-FAQ#Tools">JBossWS Tools Wiki FAQ.</ulink>
- </para>
- </listitem>
- </itemizedlist>
-
-
- </section>
-
-
-
-
-</chapter>
-
-<chapter id="create_ws_topdown" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/ws/docs/reference/en/modules/topdown.xml">
- <?dbhtml filename="topdown.html"?>
- <chapterinfo>
- <keywordset>
- <keyword>JBoss Tools</keyword>
- <keyword>Web Service</keyword>
- <keyword>JBossWS Web Service runtime</keyword>
- </keywordset>
- </chapterinfo>
-
- <title>Creating a Web Service using JBossWS runtime</title>
- <para>In this chapter we provide you with the necessary steps to create a Web Service using
- JBossWS runtime. First you need to create a Dynamic Web project:</para>
-
- <section id="createproject">
- <title>Creating a Dynamic Web project</title>
-
- <para>Before creating a web service, you should have a Dynamic Web Project created:</para>
- <figure float="0">
- <title>Dynamic Web Project</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/topdown/jbossws_webproject_1.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Create a Web project by selecting <emphasis>
- <property moreinfo="none">New > Project... > Dynamic Web project</property></emphasis>. Enter the following information: </para>
- <itemizedlist>
- <listitem>
- <para>Project Name: enter a project name</para>
- </listitem>
- <listitem>
- <para>Target runtime: any server depending on your installation. If it is not listed,
- click <property moreinfo="none">New</property> button and browse to the location where it is installed to. You may set <emphasis>
- <property moreinfo="none">Target Runtime</property>
- </emphasis> to <emphasis>
- <property moreinfo="none">None</property></emphasis>, in this case, you should add <link linkend="addfacet">JBoss Web Service
- facet to the project</link>.</para>
- <figure float="0">
- <title>Dynamic Web Project Wizard</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/topdown/jbossws_webproject_2.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- </listitem>
- <listitem>
- <para>Configuration: You may add <link linkend="addfacet">JBoss Web Service
- facet to the project</link> by clicking <property moreinfo="none">Modify...</property> button. The opened page is like <property moreinfo="none">Figure 2.4</property>.</para>
- </listitem>
- <listitem>
- <para>Configure Web Module values:</para>
- <figure float="0">
- <title>Web Module Settings Configuration</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/topdown/jbossws_webproject_3.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- </listitem>
- </itemizedlist>
- <para>If you added the JBoss Web Service facet to the project, now the <property moreinfo="none">Finish</property> button is disable. You must click <property moreinfo="none">Next</property> button to set more information about the JBoss Web Service facet. The page is like <property moreinfo="none">Figure 2.5</property>. Then click on the <property moreinfo="none">Finish</property> button.</para>
- <para>If you didn't add the JBoss Web Service facet to the project, click on the <property moreinfo="none">Finish</property> button. Next you will need to add JBoss Web Service facet to the project.</para>
- </section>
-
- <section id="addfacet">
- <title>Configure JBoss Web Service facet settings</title>
- <para>If you have already created a new Dynamic Web project and not set the JBoss Web Service facet to the project, the next step is to add JBoss Web
- Service facet to the project. Right-click on the project, select its <emphasis><property moreinfo="none">Properties</property></emphasis> and then find <emphasis>Project Facets</emphasis> in the tree-view on the left-side of the project properties dialog.
- Tick on the check box for JBoss Web Services. You will see what like this: </para>
- <figure float="0" id="figure_addfacet_0">
- <title>Choose JBoss Web Service Facet</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/topdown/jbossws_facet_0.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- <para>At the bottom-left of the right-side of the project properties dialog, there is a error link: <emphasis><property moreinfo="none">Further configuration required...</property></emphasis> . You must click the link to set more information about JBoss Web Service facet.</para>
- <para>Click on the <emphasis><property moreinfo="none">Further configuration required...</property></emphasis> link. In the opened window</para>
- <figure float="0" id="figure_addfacet">
- <title>Configure JBoss Web Service Facet</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/topdown/jbossws_facet.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Server Supplied JBossWS Runtime: If you have already set a JBoss runtime to the
- project's target runtime, you may choose <emphasis>
- <property moreinfo="none">Server Supplied JBossWS Runtime</property>
- </emphasis> and then click <emphasis>
- <property moreinfo="none">Ok</property>
- </emphasis> to finish the configuration of JBoss Web Service facet. </para>
- <para>If the project has no <emphasis>
- <property moreinfo="none">Target Runtime</property>
- </emphasis> settings, you should check the second radio button and specify a JBossWS
- runtime from the list. You also can create a new JBossWS runtime, click on the <emphasis>
- <property moreinfo="none">New...</property>
- </emphasis> button will bring you to another dialog to configure new JBossWS runtime.</para>
- <figure float="0" id="figure_addfacet1">
- <title>Configure JBossWS Runtime</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/topdown/jbossws_newruntime.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- <para>See how to configure a new JBossWS runtime <link linkend="preference">here</link>.</para>
- <para>After setting the information about JBoss Web Service facet, for saving the result, you should click the <property moreinfo="none">Apply</property> or <property moreinfo="none">OK</property> button at the bottom-right of the right-side of the project properties dialog.</para>
- </section>
-
-
- <section id="topdownwebservice">
- <title>Creating a Web Service from a WSDL document using JBossWS runtime</title>
- <para>In this chapter we provide you with the necessary steps to create a Web Service from a
- WSDL document using JBossWS runtime.</para>
- <para>At first, please make sure that you have already created a dynamic Web project with
- JBoss Web Service facet installed. </para>
- <para>See how to make it <link linkend="createproject">here</link> and <link linkend="addfacet">here</link>.</para>
-
- <para>To create a Web Service using JBossWS runtime select<emphasis>
- <property moreinfo="none">File > New > Other > Web Services > Web Service</property>
- </emphasis> to run Web Service creation wizard. </para>
- <para>Let's get through the wizard step-by-step:</para>
- <figure float="0" id="figure_create_ws_topdown">
- <title>New Web Service Wizard</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/topdown/jbossws_ws_creation1.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- <para>First, please select <property moreinfo="none">Top down Java bean Web Service</property> from the Web
- Service type list, and select a WSDL document from workspace, click on the Server name
- link on the page will bring you to another dialog. Here you can specify the server to a
- JBoss Server and Web Service runtime to JBossWS runtime:</para>
- <figure float="0" id="figure_create_ws_topdown_setserver">
- <title>Select Server and Web Service runtime</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/topdown/jbossws_ws_creation1_1.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Click on the <emphasis>
- <property moreinfo="none">Finish</property>
- </emphasis> button to see the next wizard view opened:</para>
-
- <figure float="0" id="figure_create_ws_topdown1">
- <title>New Web Service Wizard</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/topdown/jbossws_ws_creation1.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Click on the <emphasis>
- <property moreinfo="none">Next</property>
- </emphasis> button to proceed:</para>
- <figure float="0" id="figure_create_ws_topdown_codegen">
- <title>New Web Service Wizard</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/topdown/jbossws_ws_creation2.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- <para>On this page, the default package name comes from the namespace of the WSDL document,
- you also can change it to any valid package name you want. JAX-WS specification should be
- set to 2.0 if your JBossWS runtime in JBoss Server is JBossWS native runtime. You can
- specify a catalog file and binding files if you have them. If you want the wizard to
- generate empty implementation classes for the Web Service, check the <emphasis>
- <property moreinfo="none">Generate default Web Service implementation classes</property>
- </emphasis> check box. If you want to update the default Web.xml file with the Web Service
- servlets configured, check the <emphasis>
- <property moreinfo="none">Update the default Web.xml</property>
- </emphasis> check box. Click on the <emphasis>
- <property moreinfo="none">Next</property>
- </emphasis> or on the <emphasis>
- <property moreinfo="none">Finish</property>
- </emphasis> button to generate code.</para>
-
- <para>Once the Web Service code is generated, you can view the implementation class and add
- business logic to each method.</para>
- <figure float="0" id="figure_impl_code">
- <title>The generated implementation Java code</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/topdown/jbossws_ws_Impl_code_view.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- <para>View the Web.xml file:</para>
- <figure float="0" id="figure_webxml">
- <title>Web.xml</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/topdown/jbossws_ws_webxml.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-<para>In the next chapter you will find out how to create a Web service from a Java bean.</para>
- </section>
-
- <section id="bottomupws">
- <title>Creating a Web service from a Java bean using JBossWS runtime</title>
- <para>The Web Service wizard assists you in creating a new Web service, configuring it for
- deployment, and then deploying it to the server.</para>
- <para>To create a Web service from a bean using JBoss WS:</para>
- <para>Setup <link linkend="preference">JBoss WS and development environment</link>.</para>
- <para>Create <link linkend="createproject">a Dynamic Web project</link>.</para>
- <para>Add <link linkend="addfacet">JBossWS Facet</link> to Web project.</para>
- <para>Create a Web Service from a java bean: </para>
- <itemizedlist>
- <listitem>
- <para>Switch to the Java EE perspective <emphasis>
- <property moreinfo="none">Window > Open Perspective > Java EE</property></emphasis>.</para>
- </listitem>
- <listitem>
- <para>In the Project Explorer view, select the bean that you created or imported into
- the source folder of your Web project.</para>
- <figure float="0">
- <title>Select the Bean Created</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/topdown/jbossws_bottomup.png" scale="80"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- </listitem>
- <listitem>
- <para>Click <emphasis>
- <property moreinfo="none">File > New > Other</property></emphasis>. Select Web Services in order to display various Web service wizards.
- Select the Web Service wizard. Click on the <property moreinfo="none">Next</property> button.</para>
- <figure float="0">
- <title>New Web Service</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/topdown/jbossws_bottomup_1.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- </listitem>
- <listitem>
- <para>On the first Web Service wizard page: select <property moreinfo="none">Bottom up Java bean Web
- service</property> as your Web service type, and select the Java bean from which
- the service will be created:</para>
- <figure float="0">
- <title>Set Web Service Common values</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/topdown/jbossws_bottomup_2.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- <itemizedlist>
- <listitem>
- <para>Select the stages of Web service development that you want to complete using
- the slider: </para>
- <itemizedlist>
- <listitem>
- <para>Develop: this will develop the WSDL definition and implementation of
- the Web service. This includes such tasks as creating modules that will
- contain generated code, WSDL files, deployment descriptors, and Java
- files when appropriate.</para>
- </listitem>
- <listitem>
- <para>Assemble: this ensures the project that will host the Web service or
- client gets associated to an EAR when required by the target application
- server.</para>
- </listitem>
- <listitem>
- <para>Deploy: this will create the deployment code for the service.</para>
- </listitem>
- <listitem>
- <para>Install: this will install and configure the Web module and EARs on
- the target server.</para>
- </listitem>
- <listitem>
- <para>Start: this will start the server once the service has been installed
- on it. The server-config.wsdd file will be generated.</para>
- </listitem>
- <listitem>
- <para>Test: this will provide various options for testing the service, such
- as using the Web Service Explorer or sample JSPs.</para>
- </listitem>
- </itemizedlist>
- </listitem>
- <listitem>
- <para>Select your server: the default server is displayed. If you want to deploy
- your service to a different server click the link to specify a different server.
- </para>
- </listitem>
- <listitem>
- <para>Select your runtime: ensure the JBoss WS runtime is selected.</para>
- </listitem>
- <listitem>
- <para>Select the service project: the project selected in your workspace is
- displayed. To select a different project click on the project link. If you are
- deploying to JBoss Application Server you will also be asked to select the EAR
- associated with the project. Ensure that the project selected as the Client Web
- Project is different from the Service Web Project, or the service will be
- overwritten by the client's generated artifacts.</para>
- </listitem>
- <listitem>
- <para>If you want to create a client, select the type of proxy to be generated
- and repeat the above steps for the client. The better way is to create a web
- service client project separately.</para>
- </listitem>
- </itemizedlist>
- <para>Click on the <property moreinfo="none">Next</property> button.</para>
- </listitem>
- <listitem>
- <para>On the JBoss Web Service Code Generation Configuration page, set the following
- values:</para>
- <figure float="0">
- <title>Set Web Service values for Code Generation</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/topdown/jbossws_bottomup_3.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- <itemizedlist>
- <listitem>
- <para>Generate WSDL file: select it, you will get a generated WSDL file in your
- project. But this wsdl's services' address location values are not a real
- address. </para>
- </listitem>
- <listitem>
- <para>After the Web service has been created, the following option can become
- available depending on the options you selected: Update the default web.xm
- file. If selected, you may test the web service by Explorer.</para>
- </listitem>
- </itemizedlist>
- <para>Click on the <property moreinfo="none">Next</property> button.</para>
- </listitem>
- <listitem>
- <para>On this page, the project is deployed to the server. You can start the server and
- test the web service. If you want to publish the web service to a UDDI registry, you
- may click the <property moreinfo="none">Next</property> button to publish it. If not, you may click
- the <property moreinfo="none">Finish</property> button.</para>
- <figure float="0">
- <title>Start a Server</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/topdown/jbossws_bottomup_4.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- </listitem>
- </itemizedlist>
- <para>After the Web Service has been created, the following options may become available
- depending on the options selected:</para>
- <itemizedlist>
- <listitem>
- <para>the generated web services code</para>
- </listitem>
- <listitem>
- <para>If you selected to generate a WSDL file, you will get the file in your project's wsdl folder.</para>
- <figure float="0">
- <title>The Generated HelloWorldService.wsdl File in the wsdl Folder</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/topdown/jbossws_bottomup_6.png" scale="80"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- </listitem>
- <listitem>
- <para>If you selected to update the default web.xml, you will test the web service in
- the browser. Open the Explorer, input the url for the web service according to
- web.xml plus <property moreinfo="none">?wsdl.</property>, you will get the WSDL file from Explorer. </para>
- <figure float="0">
- <title>The Updated web.xml file</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/topdown/jbossws_bottomup_5.png" scale="80"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- </listitem>
- </itemizedlist>
- <para>In the next chapter you will be able to create a Web Service Client from a WSDL document using JBoss WS.</para>
-
- </section>
-
-</chapter>
-
-
-<chapter id="client" revisionflag="added" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/ws/docs/reference/en/modules/client.xml">
- <title>Creating a Web Service Client from a WSDL Document using JBoss WS</title>
- <para>To create a Web Service Client from a WSDL Document using JBoss WS you need to fulfil the following steps:</para>
- <para>Setup <link linkend="preference">JBoss WS and development environment</link>.</para>
- <para><link linkend="createproject">Create a Dynamic Web project</link>.</para>
- <para><link linkend="addfacet">Add JBossWS Facet to Web project</link>.</para>
- <para>Then you can create a Web Service Client from a WSDL document: </para>
- <itemizedlist>
- <listitem>
- <para>Switch to the Java EE perspective <emphasis><property moreinfo="none">Window > Open Perspective > Java EE</property></emphasis>.</para>
- </listitem>
- <listitem>
- <para>Click <emphasis><property moreinfo="none">File > New > Other</property></emphasis>. Select Web Services in order to display the various Web service wizards. Select the Web Service Client wizard. Click on the <property moreinfo="none">Next</property> button.</para>
- <figure float="0">
- <title>New Web Service Client</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/client/jbossws_client.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- </listitem>
- <listitem>
- <para>The first and the second Web Service Client wizard pages are the same as for <link linkend="topdownwebservice">Web Service from a WSDL document</link>.</para>
- <figure float="0">
- <title>Set Web Service Common values</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/client/jbossws_client_1.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- <figure float="0">
- <title>Set Web Service values related to WSDL file</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/client/jbossws_client_2.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- <para>The only difference is:</para>
- <itemizedlist>
- <listitem>
- <para><property moreinfo="none">Client Type:</property> Support of Java Proxy only.</para>
- </listitem>
- </itemizedlist>
- <para>Click on the <property moreinfo="none">Finish</property> button.</para>
- </listitem>
- </itemizedlist>
- <para>After the Web Service Client has been created, the following may occur depending on the options you selected:</para>
- <itemizedlist>
- <listitem>
- <para> the generated web service and client codes</para>
- </listitem>
- <listitem>
- <para>a client sample class.</para>
- <figure float="0">
- <title>Client Sample Class</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/client/jbossws_client_3.png" scale="80"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- </listitem>
- </itemizedlist>
- <para>JBoss WS use a Java class to test Web Service. A client sample class will be generated, you may run this client as a java application to call a web service.</para>
-</chapter>
-
-
-<chapter id="preference" revisionflag="added" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/ws/docs/reference/en/modules/preference.xml">
- <title>JBoss WS and development environment</title>
-
- <para>In this chapter you will learn how to change JBossWS preferences and how to set default server and runtime.</para>
- <section id="jbosswspreference">
-
-
- <title>JBossWS Preferences</title>
-
- <para>In this section you will know how JBossWS preferences can be modified during the
- development process.</para>
-
- <para>JBossWS preferences can be set on the JBossWS preference page. Click on
- <emphasis><property moreinfo="none">Window > Preferences > JBoss Tools > Web > JBossWS
- Preferences</property>.</emphasis></para>
-
- <para>On this page you can manage the JBossWS Runtime. Use the appropriate buttons to
- <property moreinfo="none">Add</property> more runtimes or to <property moreinfo="none">Remove</property> those that
- are not needed.</para>
-
- <figure float="0">
- <title>JBossWS Preferences Page</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/preference/Jbossws_preference.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Clicking on <emphasis>
- <property moreinfo="none">Add</property>
- </emphasis> or <emphasis>
- <property moreinfo="none">Edit</property>
- </emphasis> button will open the form where you can configure a new JBossWS runtime and
- change the path to JBossWS runtime home folder, modify the name and version of the
- existing JBossWS runtime settings. Press <property moreinfo="none">Finish</property> to apply the
- changes.</para>
-
- <figure float="0">
- <title>Edit JBossWS Runtime</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/preference/Jbossws_preference_new.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
-
-
-
- <para>WS container allows Source and JavaDoc locations to be set via the Properties dialog on each contained .jar: right-click on any .jar file in the Project Explorer view, select <emphasis><property moreinfo="none">Properties</property></emphasis>. Choose <emphasis><property moreinfo="none">Java Source Attachment</property></emphasis> and select location (folder, JAR or zip) containing new source for the chosen .jar using one of the suggested options (workspace, external folder or file) or enter the path manually:</para>
-
- <figure float="0">
- <title>Classpath Container: Java Source Attachment</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/preference/jbossws_container1.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Click on <emphasis><property moreinfo="none">Apply</property></emphasis> and then on <emphasis><property moreinfo="none">Ok</property></emphasis>.</para>
- <para>To change JavaDoc Location choose <emphasis><property moreinfo="none">Javadoc Location</property></emphasis> and specify URL to the documentation generated by Javadoc. The Javadoc location will contain a file called <emphasis><property moreinfo="none">package-list</property></emphasis>:</para>
-
- <figure float="0">
- <title>Classpath Container: Javadoc Location</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/preference/jbossws_container2.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Click on <emphasis><property moreinfo="none">Apply</property></emphasis> and then on <emphasis><property moreinfo="none">Ok</property></emphasis>.</para>
-
-
-
-
-
-
- </section>
- <section id="serverruntime">
- <title>Default Server and Runtime</title>
- <para>Open <emphasis>
- <property moreinfo="none">Window > Preferences > Web Services > Server and Runtime</property></emphasis>. On this page, you can specify a default server and runtime.</para>
- <para>For ease of use, the better way is to set runtime to JBoss WS.</para>
- <para>After server and runtime are specified, click on the <property moreinfo="none">Apply</property> button
- to save the values.</para>
- <figure float="0">
- <title>Specifing a default server and runtime</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/preference/jbossws_server_runtime.png"></imagedata>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>On the whole, this guide covers the fundamental concepts of work with tooling for
- <property moreinfo="none">JBossWS</property>. It describes how to easily create a Web Service and a Web Service Client using
- JBossWS Runtime and adjust JBossWS and development environment as well.</para>
-
- <para>If the information on JBossWS tools in this guide isn't enough for you, ask
- questions on our <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">forum</ulink>. Your comments and suggestions are also welcome.</para>
- </section>
-</chapter>
-
-</book>
+]><book xmlns:diffmk="http://diffmk.sf.net/ns/diff">
+
+ <bookinfo>
+ <title>JBoss WS User Guide</title>
+
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/jbosstools_logo.png" format="PNG"></imagedata>
+ </imageobject>
+ <imageobject role="html">
+ <imagedata></imagedata>
+ </imageobject>
+ </inlinemediaobject>
+ </corpauthor>
+ <author><firstname>Denny</firstname><surname>Xu</surname><email>dxu(a)redhat.com</email></author>
+ <author><firstname>Grid</firstname><surname>Qian</surname><email>fqian(a)redhat.com</email></author>
+
+ <copyright>
+ <year>2008</year>
+ <year>2009</year>
+ <year>2010</year>
+ <holder>JBoss by Red Hat</holder>
+ </copyright>
+ <releaseinfo><diffmk:wrapper diffmk:change="changed">
+ Version: 1.1.0.GA
+ </diffmk:wrapper></releaseinfo>
+<abstract>
+ <title></title>
+ <para>
+ <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/ws_ref_guide/pdf/WS_...">PDF version</ulink>
+ </para>
+</abstract>
+
+
+ </bookinfo>
+
+ <toc></toc>
+
+<chapter id="overview" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/ws/docs/reference/en/modules/overview.xml">
+ <title>JBossWS Runtime Overview</title>
+
+ <para>JBossWS is a web service framework developed as a part of the JBoss Application Server. It implements the JAX-WS specification that defines a programming model and run-time architecture for implementing web services in Java, targeted at the Java Platform, Enterprise Edition 5 (Java EE 5).</para>
+ <para>JBossWS integrates with most current JBoss Application Server releases as well as earlier ones, that did implement the J2EE 1.4 specifications. Even though JAX-RPC, the web service specification for J2EE 1.4, is still supported JBossWS does put a clear focus on JAX-WS.</para>
+
+<section>
+ <title>Key Features of JBossWS</title>
+ <para>For a start, we propose you to look through the table of main features of JBossWS Runtime:</para>
+
+ <table>
+
+ <title>Key Functionality for JBossWS</title>
+ <tgroup cols="2">
+
+ <colspec align="left" colnum="1" colwidth="2*"></colspec>
+ <colspec colnum="2" colwidth="4*"></colspec>
+
+
+ <thead>
+ <row>
+ <entry>Feature</entry>
+ <entry>Benefit</entry>
+
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry><para>JAX-RPC and JAX-WS support</para></entry>
+ <entry><para>JBossWS implements both the JAX-WS and JAX-RPC specifications.</para></entry>
+
+ </row>
+
+ <row>
+ <entry><para>EJB 2.1, EJB3 and JSE endpoints</para></entry>
+ <entry><para>JBossWS supports EJB 2.1, EJB3 and JSE as Web Service Endpoints.</para></entry>
+
+ </row>
+
+ <row>
+ <entry><para>WS-Security 1.0 for XML Encryption/Signature of the SOAP message</para></entry>
+ <entry><para>WS-Security standardizes authorization, encryption, and digital signature processing of web services.</para></entry>
+
+ </row>
+
+ <row>
+ <entry><para>JBoss AS</para></entry>
+ <entry><para>JBoss Application Server 5 (JavaEE 5 compliant) web service stack.</para></entry>
+
+ </row>
+
+ <row>
+ <entry><para>Support for MTOM/XOP and SwA-Ref</para></entry>
+ <entry><para>Message Transmission Optimization Mechanism (MTOM) and XML-binary Optimized Packaging (XOP) more efficiently serialize XML Infosets that have certain types of content.</para></entry>
+
+ </row>
+
+ </tbody>
+
+ </tgroup>
+ </table>
+
+
+</section>
+<section>
+ <title>Other relevant resources on the topic</title>
+
+ <para>You can find some extra information on:</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://www.jboss.org/community/wiki/JBossWS-FAQ#Tools">JBossWS Tools Wiki FAQ.</ulink>
+ </para>
+ </listitem>
+ </itemizedlist>
+
+
+ </section>
+
+
+
+
+</chapter>
+
+<chapter id="create_ws_topdown" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/ws/docs/reference/en/modules/topdown.xml">
+ <?dbhtml filename="topdown.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Tools</keyword>
+ <keyword>Web Service</keyword>
+ <keyword>JBossWS Web Service runtime</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Creating a Web Service using JBossWS runtime</title>
+ <para>In this chapter we provide you with the necessary steps to create a Web Service using
+ JBossWS runtime. First you need to create a Dynamic Web project:</para>
+
+ <section id="createproject">
+ <title>Creating a Dynamic Web project</title>
+
+ <para>Before creating a web service, you should have a Dynamic Web Project created:</para>
+ <figure float="0">
+ <title>Dynamic Web Project</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_webproject_1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Create a Web project by selecting <emphasis>
+ <property moreinfo="none">New > Project... > Dynamic Web project</property></emphasis>. Enter the following information: </para>
+ <itemizedlist>
+ <listitem>
+ <para>Project Name: enter a project name</para>
+ </listitem>
+ <listitem>
+ <para>Target runtime: any server depending on your installation. If it is not listed,
+ click <property moreinfo="none">New</property> button and browse to the location where it is installed to. You may set <emphasis>
+ <property moreinfo="none">Target Runtime</property>
+ </emphasis> to <emphasis>
+ <property moreinfo="none">None</property></emphasis>, in this case, you should add <link linkend="addfacet">JBoss Web Service
+ facet to the project</link>.</para>
+ <figure float="0">
+ <title>Dynamic Web Project Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_webproject_2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>Configuration: You may add <link linkend="addfacet">JBoss Web Service
+ facet to the project</link> by clicking <property moreinfo="none">Modify...</property> button. The opened page is like <property moreinfo="none">Figure 2.4</property>.</para>
+ </listitem>
+ <listitem>
+ <para>Configure Web Module values:</para>
+ <figure float="0">
+ <title>Web Module Settings Configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_webproject_3.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ </itemizedlist>
+ <para>If you added the JBoss Web Service facet to the project, now the <property moreinfo="none">Finish</property> button is disable. You must click <property moreinfo="none">Next</property> button to set more information about the JBoss Web Service facet. The page is like <property moreinfo="none">Figure 2.5</property>. Then click on the <property moreinfo="none">Finish</property> button.</para>
+ <para>If you didn't add the JBoss Web Service facet to the project, click on the <property moreinfo="none">Finish</property> button. Next you will need to add JBoss Web Service facet to the project.</para>
+ </section>
+
+ <section id="addfacet">
+ <title>Configure JBoss Web Service facet settings</title>
+ <para>If you have already created a new Dynamic Web project and not set the JBoss Web Service facet to the project, the next step is to add JBoss Web
+ Service facet to the project. Right-click on the project, select its <emphasis><property moreinfo="none">Properties</property></emphasis> and then find <emphasis>Project Facets</emphasis> in the tree-view on the left-side of the project properties dialog.
+ Tick on the check box for JBoss Web Services. You will see what like this: </para>
+ <figure float="0" id="figure_addfacet_0">
+ <title>Choose JBoss Web Service Facet</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_facet_0.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>At the bottom-left of the right-side of the project properties dialog, there is a error link: <emphasis><property moreinfo="none">Further configuration required...</property></emphasis> . You must click the link to set more information about JBoss Web Service facet.</para>
+ <para>Click on the <emphasis><property moreinfo="none">Further configuration required...</property></emphasis> link. In the opened window</para>
+ <figure float="0" id="figure_addfacet">
+ <title>Configure JBoss Web Service Facet</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_facet.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Server Supplied JBossWS Runtime: If you have already set a JBoss runtime to the
+ project's target runtime, you may choose <emphasis>
+ <property moreinfo="none">Server Supplied JBossWS Runtime</property>
+ </emphasis> and then click <emphasis>
+ <property moreinfo="none">Ok</property>
+ </emphasis> to finish the configuration of JBoss Web Service facet. </para>
+ <para>If the project has no <emphasis>
+ <property moreinfo="none">Target Runtime</property>
+ </emphasis> settings, you should check the second radio button and specify a JBossWS
+ runtime from the list. You also can create a new JBossWS runtime, click on the <emphasis>
+ <property moreinfo="none">New...</property>
+ </emphasis> button will bring you to another dialog to configure new JBossWS runtime.</para>
+ <figure float="0" id="figure_addfacet1">
+ <title>Configure JBossWS Runtime</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_newruntime.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>See how to configure a new JBossWS runtime <link linkend="preference">here</link>.</para>
+ <para>After setting the information about JBoss Web Service facet, for saving the result, you should click the <property moreinfo="none">Apply</property> or <property moreinfo="none">OK</property> button at the bottom-right of the right-side of the project properties dialog.</para>
+ </section>
+
+
+ <section id="topdownwebservice">
+ <title>Creating a Web Service from a WSDL document using JBossWS runtime</title>
+ <para>In this chapter we provide you with the necessary steps to create a Web Service from a
+ WSDL document using JBossWS runtime.</para>
+ <para>At first, please make sure that you have already created a dynamic Web project with
+ JBoss Web Service facet installed. </para>
+ <para>See how to make it <link linkend="createproject">here</link> and <link linkend="addfacet">here</link>.</para>
+
+ <para>To create a Web Service using JBossWS runtime select<emphasis>
+ <property moreinfo="none">File > New > Other > Web Services > Web Service</property>
+ </emphasis> to run Web Service creation wizard. </para>
+ <para>Let's get through the wizard step-by-step:</para>
+ <figure float="0" id="figure_create_ws_topdown">
+ <title>New Web Service Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_ws_creation1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>First, please select <property moreinfo="none">Top down Java bean Web Service</property> from the Web
+ Service type list, and select a WSDL document from workspace, click on the Server name
+ link on the page will bring you to another dialog. Here you can specify the server to a
+ JBoss Server and Web Service runtime to JBossWS runtime:</para>
+ <figure float="0" id="figure_create_ws_topdown_setserver">
+ <title>Select Server and Web Service runtime</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_ws_creation1_1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Click on the <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis> button to see the next wizard view opened:</para>
+
+ <figure float="0" id="figure_create_ws_topdown1">
+ <title>New Web Service Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_ws_creation1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Click on the <emphasis>
+ <property moreinfo="none">Next</property>
+ </emphasis> button to proceed:</para>
+ <figure float="0" id="figure_create_ws_topdown_codegen">
+ <title>New Web Service Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_ws_creation2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>On this page, the default package name comes from the namespace of the WSDL document,
+ you also can change it to any valid package name you want. JAX-WS specification should be
+ set to 2.0 if your JBossWS runtime in JBoss Server is JBossWS native runtime. You can
+ specify a catalog file and binding files if you have them. If you want the wizard to
+ generate empty implementation classes for the Web Service, check the <emphasis>
+ <property moreinfo="none">Generate default Web Service implementation classes</property>
+ </emphasis> check box. If you want to update the default Web.xml file with the Web Service
+ servlets configured, check the <emphasis>
+ <property moreinfo="none">Update the default Web.xml</property>
+ </emphasis> check box. Click on the <emphasis>
+ <property moreinfo="none">Next</property>
+ </emphasis> or on the <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis> button to generate code.</para>
+
+ <para>Once the Web Service code is generated, you can view the implementation class and add
+ business logic to each method.</para>
+ <figure float="0" id="figure_impl_code">
+ <title>The generated implementation Java code</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_ws_Impl_code_view.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>View the Web.xml file:</para>
+ <figure float="0" id="figure_webxml">
+ <title>Web.xml</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_ws_webxml.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+<para>In the next chapter you will find out how to create a Web service from a Java bean.</para>
+ </section>
+
+ <section id="bottomupws">
+ <title>Creating a Web service from a Java bean using JBossWS runtime</title>
+ <para>The Web Service wizard assists you in creating a new Web service, configuring it for
+ deployment, and then deploying it to the server.</para>
+ <para>To create a Web service from a bean using JBoss WS:</para>
+ <para>Setup <link linkend="preference">JBoss WS and development environment</link>.</para>
+ <para>Create <link linkend="createproject">a Dynamic Web project</link>.</para>
+ <para>Add <link linkend="addfacet">JBossWS Facet</link> to Web project.</para>
+ <para>Create a Web Service from a java bean: </para>
+ <itemizedlist>
+ <listitem>
+ <para>Switch to the Java EE perspective <emphasis>
+ <property moreinfo="none">Window > Open Perspective > Java EE</property></emphasis>.</para>
+ </listitem>
+ <listitem>
+ <para>In the Project Explorer view, select the bean that you created or imported into
+ the source folder of your Web project.</para>
+ <figure float="0">
+ <title>Select the Bean Created</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_bottomup.png" scale="80"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis>
+ <property moreinfo="none">File > New > Other</property></emphasis>. Select Web Services in order to display various Web service wizards.
+ Select the Web Service wizard. Click on the <property moreinfo="none">Next</property> button.</para>
+ <figure float="0">
+ <title>New Web Service</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_bottomup_1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>On the first Web Service wizard page: select <property moreinfo="none">Bottom up Java bean Web
+ service</property> as your Web service type, and select the Java bean from which
+ the service will be created:</para>
+ <figure float="0">
+ <title>Set Web Service Common values</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_bottomup_2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Select the stages of Web service development that you want to complete using
+ the slider: </para>
+ <itemizedlist>
+ <listitem>
+ <para>Develop: this will develop the WSDL definition and implementation of
+ the Web service. This includes such tasks as creating modules that will
+ contain generated code, WSDL files, deployment descriptors, and Java
+ files when appropriate.</para>
+ </listitem>
+ <listitem>
+ <para>Assemble: this ensures the project that will host the Web service or
+ client gets associated to an EAR when required by the target application
+ server.</para>
+ </listitem>
+ <listitem>
+ <para>Deploy: this will create the deployment code for the service.</para>
+ </listitem>
+ <listitem>
+ <para>Install: this will install and configure the Web module and EARs on
+ the target server.</para>
+ </listitem>
+ <listitem>
+ <para>Start: this will start the server once the service has been installed
+ on it. The server-config.wsdd file will be generated.</para>
+ </listitem>
+ <listitem>
+ <para>Test: this will provide various options for testing the service, such
+ as using the Web Service Explorer or sample JSPs.</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>Select your server: the default server is displayed. If you want to deploy
+ your service to a different server click the link to specify a different server.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Select your runtime: ensure the JBoss WS runtime is selected.</para>
+ </listitem>
+ <listitem>
+ <para>Select the service project: the project selected in your workspace is
+ displayed. To select a different project click on the project link. If you are
+ deploying to JBoss Application Server you will also be asked to select the EAR
+ associated with the project. Ensure that the project selected as the Client Web
+ Project is different from the Service Web Project, or the service will be
+ overwritten by the client's generated artifacts.</para>
+ </listitem>
+ <listitem>
+ <para>If you want to create a client, select the type of proxy to be generated
+ and repeat the above steps for the client. The better way is to create a web
+ service client project separately.</para>
+ </listitem>
+ </itemizedlist>
+ <para>Click on the <property moreinfo="none">Next</property> button.</para>
+ </listitem>
+ <listitem>
+ <para>On the JBoss Web Service Code Generation Configuration page, set the following
+ values:</para>
+ <figure float="0">
+ <title>Set Web Service values for Code Generation</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_bottomup_3.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <itemizedlist>
+ <listitem>
+ <para>Generate WSDL file: select it, you will get a generated WSDL file in your
+ project. But this wsdl's services' address location values are not a real
+ address. </para>
+ </listitem>
+ <listitem>
+ <para>After the Web service has been created, the following option can become
+ available depending on the options you selected: Update the default web.xm
+ file. If selected, you may test the web service by Explorer.</para>
+ </listitem>
+ </itemizedlist>
+ <para>Click on the <property moreinfo="none">Next</property> button.</para>
+ </listitem>
+ <listitem>
+ <para>On this page, the project is deployed to the server. You can start the server and
+ test the web service. If you want to publish the web service to a UDDI registry, you
+ may click the <property moreinfo="none">Next</property> button to publish it. If not, you may click
+ the <property moreinfo="none">Finish</property> button.</para>
+ <figure float="0">
+ <title>Start a Server</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_bottomup_4.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ </itemizedlist>
+ <para>After the Web Service has been created, the following options may become available
+ depending on the options selected:</para>
+ <itemizedlist>
+ <listitem>
+ <para>the generated web services code</para>
+ </listitem>
+ <listitem>
+ <para>If you selected to generate a WSDL file, you will get the file in your project's wsdl folder.</para>
+ <figure float="0">
+ <title>The Generated HelloWorldService.wsdl File in the wsdl Folder</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_bottomup_6.png" scale="80"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>If you selected to update the default web.xml, you will test the web service in
+ the browser. Open the Explorer, input the url for the web service according to
+ web.xml plus <property moreinfo="none">?wsdl.</property>, you will get the WSDL file from Explorer. </para>
+ <figure float="0">
+ <title>The Updated web.xml file</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/topdown/jbossws_bottomup_5.png" scale="80"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ </itemizedlist>
+ <para>In the next chapter you will be able to create a Web Service Client from a WSDL document using JBoss WS.</para>
+
+ </section>
+
+</chapter>
+
+
+<chapter id="client" revisionflag="added" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/ws/docs/reference/en/modules/client.xml">
+ <title>Creating a Web Service Client from a WSDL Document using JBoss WS</title>
+ <para>To create a Web Service Client from a WSDL Document using JBoss WS you need to fulfil the following steps:</para>
+ <para>Setup <link linkend="preference">JBoss WS and development environment</link>.</para>
+ <para><link linkend="createproject">Create a Dynamic Web project</link>.</para>
+ <para><link linkend="addfacet">Add JBossWS Facet to Web project</link>.</para>
+ <para>Then you can create a Web Service Client from a WSDL document: </para>
+ <itemizedlist>
+ <listitem>
+ <para>Switch to the Java EE perspective <emphasis><property moreinfo="none">Window > Open Perspective > Java EE</property></emphasis>.</para>
+ </listitem>
+ <listitem>
+ <para>Click <emphasis><property moreinfo="none">File > New > Other</property></emphasis>. Select Web Services in order to display the various Web service wizards. Select the Web Service Client wizard. Click on the <property moreinfo="none">Next</property> button.</para>
+ <figure float="0">
+ <title>New Web Service Client</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/client/jbossws_client.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>The first and the second Web Service Client wizard pages are the same as for <link linkend="topdownwebservice">Web Service from a WSDL document</link>.</para>
+ <figure float="0">
+ <title>Set Web Service Common values</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/client/jbossws_client_1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <figure float="0">
+ <title>Set Web Service values related to WSDL file</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/client/jbossws_client_2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>The only difference is:</para>
+ <itemizedlist>
+ <listitem>
+ <para><property moreinfo="none">Client Type:</property> Support of Java Proxy only.</para>
+ </listitem>
+ </itemizedlist>
+ <para>Click on the <property moreinfo="none">Finish</property> button.</para>
+ </listitem>
+ </itemizedlist>
+ <para>After the Web Service Client has been created, the following may occur depending on the options you selected:</para>
+ <itemizedlist>
+ <listitem>
+ <para> the generated web service and client codes</para>
+ </listitem>
+ <listitem>
+ <para>a client sample class.</para>
+ <figure float="0">
+ <title>Client Sample Class</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/client/jbossws_client_3.png" scale="80"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ </itemizedlist>
+ <para>JBoss WS use a Java class to test Web Service. A client sample class will be generated, you may run this client as a java application to call a web service.</para>
+</chapter>
+
+
+<chapter id="preference" revisionflag="added" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/ws/docs/reference/en/modules/preference.xml">
+ <title>JBoss WS and development environment</title>
+
+ <para>In this chapter you will learn how to change JBossWS preferences and how to set default server and runtime.</para>
+ <section id="jbosswspreference">
+
+
+ <title>JBossWS Preferences</title>
+
+ <para>In this section you will know how JBossWS preferences can be modified during the
+ development process.</para>
+
+ <para>JBossWS preferences can be set on the JBossWS preference page. Click on
+ <emphasis><property moreinfo="none">Window > Preferences > JBoss Tools > Web > JBossWS
+ Preferences</property>.</emphasis></para>
+
+ <para>On this page you can manage the JBossWS Runtime. Use the appropriate buttons to
+ <property moreinfo="none">Add</property> more runtimes or to <property moreinfo="none">Remove</property> those that
+ are not needed.</para>
+
+ <figure float="0">
+ <title>JBossWS Preferences Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/preference/Jbossws_preference.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Clicking on <emphasis>
+ <property moreinfo="none">Add</property>
+ </emphasis> or <emphasis>
+ <property moreinfo="none">Edit</property>
+ </emphasis> button will open the form where you can configure a new JBossWS runtime and
+ change the path to JBossWS runtime home folder, modify the name and version of the
+ existing JBossWS runtime settings. Press <property moreinfo="none">Finish</property> to apply the
+ changes.</para>
+
+ <figure float="0">
+ <title>Edit JBossWS Runtime</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/preference/Jbossws_preference_new.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+
+
+
+ <para>WS container allows Source and JavaDoc locations to be set via the Properties dialog on each contained .jar: right-click on any .jar file in the Project Explorer view, select <emphasis><property moreinfo="none">Properties</property></emphasis>. Choose <emphasis><property moreinfo="none">Java Source Attachment</property></emphasis> and select location (folder, JAR or zip) containing new source for the chosen .jar using one of the suggested options (workspace, external folder or file) or enter the path manually:</para>
+
+ <figure float="0">
+ <title>Classpath Container: Java Source Attachment</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/preference/jbossws_container1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Click on <emphasis><property moreinfo="none">Apply</property></emphasis> and then on <emphasis><property moreinfo="none">Ok</property></emphasis>.</para>
+ <para>To change JavaDoc Location choose <emphasis><property moreinfo="none">Javadoc Location</property></emphasis> and specify URL to the documentation generated by Javadoc. The Javadoc location will contain a file called <emphasis><property moreinfo="none">package-list</property></emphasis>:</para>
+
+ <figure float="0">
+ <title>Classpath Container: Javadoc Location</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/preference/jbossws_container2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Click on <emphasis><property moreinfo="none">Apply</property></emphasis> and then on <emphasis><property moreinfo="none">Ok</property></emphasis>.</para>
+
+
+
+
+
+
+ </section>
+ <section id="serverruntime">
+ <title>Default Server and Runtime</title>
+ <para>Open <emphasis>
+ <property moreinfo="none">Window > Preferences > Web Services > Server and Runtime</property></emphasis>. On this page, you can specify a default server and runtime.</para>
+ <para>For ease of use, the better way is to set runtime to JBoss WS.</para>
+ <para>After server and runtime are specified, click on the <property moreinfo="none">Apply</property> button
+ to save the values.</para>
+ <figure float="0">
+ <title>Specifing a default server and runtime</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/preference/jbossws_server_runtime.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>On the whole, this guide covers the fundamental concepts of work with tooling for
+ <property moreinfo="none">JBossWS</property>. It describes how to easily create a Web Service and a Web Service Client using
+ JBossWS Runtime and adjust JBossWS and development environment as well.</para>
+
+ <para>If the information on JBossWS tools in this guide isn't enough for you, ask
+ questions on our <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">forum</ulink>. Your comments and suggestions are also welcome.</para>
+ </section>
+</chapter>
+
+</book>
Modified: branches/jbosstools-3.1.x/ws/docs/reference/pom.xml
===================================================================
--- branches/jbosstools-3.1.x/ws/docs/reference/pom.xml 2010-03-03 14:17:47 UTC (rev 20612)
+++ branches/jbosstools-3.1.x/ws/docs/reference/pom.xml 2010-03-03 14:21:54 UTC (rev 20613)
@@ -32,7 +32,7 @@
<profile>
<id>releaseJBDS</id>
<properties>
- <master>master_output.xml</master>
+ <master>master.xml</master>
<xsl-single>classpath:/xslt/com/jboss/tools/xhtml-single-release.xsl</xsl-single>
<xsl-chunked>classpath:/xslt/com/jboss/tools/xhtml-release.xsl</xsl-chunked>
<xsl-pdf>classpath:/xslt/com/jboss/tools/pdf.xsl</xsl-pdf>
14 years, 2 months
- 1
- 0
JBoss Tools SVN: r20612 - in branches/jbosstools-3.1.x/jbpm/docs/converter_ref: en-US and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2010-03-03 09:17:47 -0500 (Wed, 03 Mar 2010)
New Revision: 20612
Modified:
branches/jbosstools-3.1.x/jbpm/docs/converter_ref/en-US/master.xml
branches/jbosstools-3.1.x/jbpm/docs/converter_ref/en-US/master_output.xml
branches/jbosstools-3.1.x/jbpm/docs/converter_ref/pom.xml
Log:
<html><head><meta name="qrichtext" content="1" /></head><body style="font-size:9pt;font-family:Sans Serif">
<p>https://jira.jboss.org/jira/browse/JBDS-1107 -Updated docs source files here with the ones for JBDS 3.0.0 GA release. </p>
<p></p>
</body></html>
Modified: branches/jbosstools-3.1.x/jbpm/docs/converter_ref/en-US/master.xml
===================================================================
--- branches/jbosstools-3.1.x/jbpm/docs/converter_ref/en-US/master.xml 2010-03-03 14:14:59 UTC (rev 20611)
+++ branches/jbosstools-3.1.x/jbpm/docs/converter_ref/en-US/master.xml 2010-03-03 14:17:47 UTC (rev 20612)
@@ -30,7 +30,7 @@
<holder>JBoss by Red Hat</holder>
</copyright>
<releaseinfo>
- Version: 1.1.0.M2
+ Version: 1.1.0.GA
</releaseinfo>
<abstract>
<title/>
Modified: branches/jbosstools-3.1.x/jbpm/docs/converter_ref/en-US/master_output.xml
===================================================================
--- branches/jbosstools-3.1.x/jbpm/docs/converter_ref/en-US/master_output.xml 2010-03-03 14:14:59 UTC (rev 20611)
+++ branches/jbosstools-3.1.x/jbpm/docs/converter_ref/en-US/master_output.xml 2010-03-03 14:17:47 UTC (rev 20612)
@@ -8,26 +8,27 @@
<bookinfo>
<title>BPMN Convert User Guide</title>
- <corpauthor diffmk:change="added">
- <inlinemediaobject diffmk:change="added">
- <imageobject diffmk:change="added" role="fo">
- <imagedata diffmk:change="added" fileref="images/jbosstools_logo.png" format="PNG"></imagedata>
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/jbosstools_logo.png" format="PNG"></imagedata>
</imageobject>
- <imageobject diffmk:change="added" role="html">
- <imagedata diffmk:change="added"></imagedata>
+ <imageobject role="html">
+ <imagedata></imagedata>
</imageobject>
</inlinemediaobject>
</corpauthor>
<author><firstname>Grid</firstname><surname>Qian</surname><email>fqian(a)redhat.com</email></author>
- <pubdate>October 2008</pubdate>
+
<copyright>
<year>2008</year>
<year>2009</year>
- <holder><diffmk:wrapper diffmk:change="changed">JBoss by Red Hat</diffmk:wrapper></holder>
+ <year>2010</year>
+ <holder>JBoss by Red Hat</holder>
</copyright>
<releaseinfo><diffmk:wrapper diffmk:change="changed">
- Version: 1.1.0.M2
+ Version: 1.1.0.GA
</diffmk:wrapper></releaseinfo>
<abstract>
<title></title>
@@ -41,42 +42,42 @@
<toc></toc>
-<chapter id="overview" xml:base="file:///home/ochikvina/WORK/for_compare/trunk/jbpm/docs/converter_ref/en/modules/overview.xml">
+<chapter id="overview" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/jbpm/docs/converter_ref/en-US/overview.xml">
<title>BPMN Convert Overview</title>
- <para><diffmk:wrapper diffmk:change="changed">This chapter gives you a short overview of JBoss BPMN Convert module.</diffmk:wrapper></para>
- <para><diffmk:wrapper diffmk:change="changed">JBoss BPMN Convert module is a tool used for a BPMN file translation.</diffmk:wrapper></para>
+ <para>This chapter gives you a short overview of JBoss BPMN Convert module.</para>
+ <para>JBoss BPMN Convert module is a tool used for a BPMN file translation.</para>
<para>As a part of JBoss tools, JBoss BPMN Convert module implements BPMN -> JPDL translation. You can get a basic JPDL file from a BPMN file by using this module.</para>
<para>The BPMN file may be written by hands or with the help of some editors. In this guide, we use STP BPMN editor to draw a BPMN file.</para>
- <para>You can download the editor which is included into BPMN Modeler from Eclipse download or update site. On the <ulink url="http://www.eclipse.org/bpmn">Eclipse BPMN project page</ulink><diffmk:wrapper diffmk:change="added"> you can find the necessary links and other related information.</diffmk:wrapper></para>
+ <para>You can download the editor which is included into BPMN Modeler from Eclipse download or update site. On the <ulink url="http://www.eclipse.org/bpmn">Eclipse BPMN project page</ulink> you can find the necessary links and other related information.</para>
-<section diffmk:change="added">
- <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">Key Features of JBoss BPMN Convert module</diffmk:wrapper></title>
- <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">For a start, we propose you to look through the table of main features of JBoss BPMN Convert module:</diffmk:wrapper></para>
+<section>
+ <title>Key Features of JBoss BPMN Convert module</title>
+ <para>For a start, we propose you to look through the table of main features of JBoss BPMN Convert module:</para>
- <table diffmk:change="added">
+ <table>
- <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">Key Functionality of JBoss BPMN Convert module</diffmk:wrapper></title>
- <tgroup cols="3" diffmk:change="added">
+ <title>Key Functionality of JBoss BPMN Convert module</title>
+ <tgroup cols="3">
- <colspec align="left" colnum="1" colwidth="2*" diffmk:change="added"></colspec>
- <colspec colnum="2" colwidth="4*" diffmk:change="added"></colspec>
- <colspec align="left" colnum="3" colwidth="2*" diffmk:change="added"></colspec>
+ <colspec align="left" colnum="1" colwidth="2*"></colspec>
+ <colspec colnum="2" colwidth="4*"></colspec>
+ <colspec align="left" colnum="3" colwidth="2*"></colspec>
- <thead diffmk:change="added">
- <row diffmk:change="added">
- <entry diffmk:change="added"><diffmk:wrapper diffmk:change="added">Feature</diffmk:wrapper></entry>
- <entry diffmk:change="added"><diffmk:wrapper diffmk:change="added">Benefit</diffmk:wrapper></entry>
- <entry diffmk:change="added"><diffmk:wrapper diffmk:change="added">Chapter</diffmk:wrapper></entry>
+ <thead>
+ <row>
+ <entry>Feature</entry>
+ <entry>Benefit</entry>
+ <entry>Chapter</entry>
</row>
</thead>
- <tbody diffmk:change="added">
+ <tbody>
- <row diffmk:change="added">
- <entry diffmk:change="added"><para diffmk:change="added"><diffmk:wrapper diffmk:change="added">STP BPMN Editor</diffmk:wrapper></para></entry>
- <entry diffmk:change="added"><para diffmk:change="added"><diffmk:wrapper diffmk:change="added">JBoss BPMN Convert module contains STP Business Process Modeling Notation (BPMN) Editor which is a tool to express any processes in a graphical form (simple diagrams with a set of some graphical elements). Created BPMN files can then be converted to jPDL.</diffmk:wrapper></para></entry>
- <entry diffmk:change="added">
- <link diffmk:change="added" linkend="createbpmnfile"><diffmk:wrapper diffmk:change="added">creating a BPMN file by STP BPMN editor</diffmk:wrapper></link>
+ <row>
+ <entry><para>STP BPMN Editor</para></entry>
+ <entry><para>JBoss BPMN Convert module contains STP Business Process Modeling Notation (BPMN) Editor which is a tool to express any processes in a graphical form (simple diagrams with a set of some graphical elements). Created BPMN files can then be converted to jPDL.</para></entry>
+ <entry>
+ <link linkend="createbpmnfile">creating a BPMN file by STP BPMN editor</link>
</entry>
</row>
@@ -93,7 +94,7 @@
</chapter>
-<chapter id="bpmn2jpdl" xml:base="file:///home/ochikvina/WORK/for_compare/trunk/jbpm/docs/converter_ref/en/modules/bpmn2jpdl.xml">
+<chapter id="bpmn2jpdl" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/jbpm/docs/converter_ref/en-US/bpmn2jpdl.xml">
<title>Translate a Bpmn file to a JPDL file</title>
<para>In this chapter we provide you with the necessary steps to translate a Bpmn file to a JPDL file.</para>
@@ -213,8 +214,9 @@
</imageobject>
</mediaobject>
</figure>
- <para>We hope, this guide helped you to get started with the JBoss BPMN Convert module. Besides, for additional information you are welcome on <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss forum</ulink>.</para>
- </section>
+ <para>We hope, this guide helped you to get started with the JBoss BPMN Convert module. Besides, for additional information you are welcome on <ulink
+ url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss forum</ulink>.</para>
+ </section>
</chapter>
</book>
Modified: branches/jbosstools-3.1.x/jbpm/docs/converter_ref/pom.xml
===================================================================
--- branches/jbosstools-3.1.x/jbpm/docs/converter_ref/pom.xml 2010-03-03 14:14:59 UTC (rev 20611)
+++ branches/jbosstools-3.1.x/jbpm/docs/converter_ref/pom.xml 2010-03-03 14:17:47 UTC (rev 20612)
@@ -22,7 +22,7 @@
<profile>
<id>releaseJBDS</id>
<properties>
- <master>master_output.xml</master>
+ <master>master.xml</master>
<xsl-single>classpath:/xslt/com/jboss/tools/xhtml-single-release.xsl</xsl-single>
<xsl-chunked>classpath:/xslt/com/jboss/tools/xhtml-release.xsl</xsl-chunked>
<xsl-pdf>classpath:/xslt/com/jboss/tools/pdf.xsl</xsl-pdf>
14 years, 2 months
- 1
- 0
JBoss Tools SVN: r20611 - branches/jbosstools-3.1.x/jbpm/docs/reference.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2010-03-03 09:14:59 -0500 (Wed, 03 Mar 2010)
New Revision: 20611
Removed:
branches/jbosstools-3.1.x/jbpm/docs/reference/en/
Log:
<html><head><meta name="qrichtext" content="1" /></head><body style="font-size:9pt;font-family:Sans Serif">
<p>https://jira.jboss.org/jira/browse/JBDS-1107 -Updated docs source files here with the ones for JBDS 3.0.0 GA release. </p>
<p></p>
</body></html>
14 years, 2 months
- 1
- 0
JBoss Tools SVN: r20610 - in branches/jbosstools-3.1.x/jbpm/docs/reference: en-US and 7 other directories.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2010-03-03 09:04:09 -0500 (Wed, 03 Mar 2010)
New Revision: 20610
Added:
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Author_Group.xml
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Book_Info.xml
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Introduction.xml
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Preface.xml
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Quick_Howto_Guide.xml
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Revision_History.xml
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Test_Drive_Proc.xml
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/The_JBoss_jBPM_Int_Mech.xml
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/guided_tour_jboss_jbpmgpd.xml
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_1.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_2.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_3.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_4.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_5.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_6.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_7.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_8.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_9.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_1.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_2.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_3.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_4.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_5.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_6.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_7.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_8.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_1.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_2.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_3.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_4.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_5.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_6.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_7.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_8.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_9.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/favicon.ico
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_1.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_2.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_3.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_4.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_5.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_6.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_7.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_8.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_9.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/jbosstools_logo.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/runtime_installation/
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/runtime_installation/runtime_installation_1.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_0.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_1.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_10.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_2.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_3.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_4.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_5.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_6.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_7.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_8.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_9.png
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/jBPM_Tools_Reference_Guide.ent
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/jBPM_Tools_Reference_Guide.xml
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/jboss_jbpm_runtime_installation.xml
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/master.xml
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/master_output.xml
branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/the_views.xml
Log:
<html><head><meta name="qrichtext" content="1" /></head><body style="font-size:9pt;font-family:Sans Serif">
<p>https://jira.jboss.org/jira/browse/JBDS-1107 -Updated docs source files here with the ones for JBDS 3.0.0 GA release. </p>
<p></p>
</body></html>
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Author_Group.xml
===================================================================
--- branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Author_Group.xml (rev 0)
+++ branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Author_Group.xml 2010-03-03 14:04:09 UTC (rev 20610)
@@ -0,0 +1,26 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<authorgroup><author>
+ <firstname>Anatoly</firstname>
+ <surname>Fedosik</surname>
+ </author>
+ <author>
+ <firstname>Koen</firstname>
+ <surname>Aers</surname>
+ <email>koen.aers(a)jboss.com</email>
+ </author>
+ <author>
+ <firstname>Olga</firstname>
+ <surname>Chikvina</surname>
+ </author>
+ <author>
+ <firstname>Svetlana</firstname>
+ <surname>Mukhina</surname>
+ <email>smukhina(a)exadel.com</email>
+ </author>
+ <author>
+ <firstname>Tom</firstname>
+ <surname>Baeyens</surname>
+ <email>tom.baeyens(a)jboss.com</email>
+ </author></authorgroup>
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Book_Info.xml
===================================================================
--- branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Book_Info.xml (rev 0)
+++ branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Book_Info.xml 2010-03-03 14:04:09 UTC (rev 20610)
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<bookinfo><title>jBPM Tools Reference Guide</title><subtitle>Provides information relating to the jBPM Tools set.</subtitle><productname>JBoss Developer Studio</productname><productnumber>3.0</productnumber><edition>1.0</edition><pubsnumber>0</pubsnumber><abstract><para>The jBPM Tools Reference Guide explains how to use the jBPM Tools to create process definitions and workflow processes.</para></abstract><corpauthor><inlinemediaobject><imageobject><imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"></imagedata></imageobject></inlinemediaobject></corpauthor><xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></bookinfo>
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Introduction.xml
===================================================================
--- branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Introduction.xml (rev 0)
+++ branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Introduction.xml 2010-03-03 14:04:09 UTC (rev 20610)
@@ -0,0 +1,154 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="Introduction" xreflabel="Introduction">
+ <?dbhtml filename="TargetAudience.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>jBPM</keyword>
+ <keyword>Target</keyword>
+ <keyword>developers</keyword>
+ <keyword>Audience</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Introduction</title>
+ <para>All developers and process analysts who are beginning to use JBoss jBPM should read this
+ Getting Started guide. It will give them a jumpstart showing how to create a process definition.</para>
+ <section id="Preface">
+ <?dbhtml filename="Preface.html"?>
+ <title>Preface</title>
+ <para>This document introduces the use of the JBoss jBPM Graphical Process Designer (GPD) to
+ create workflow processes. It will help first time users with the following tasks :</para>
+ <itemizedlist>
+ <listitem>
+ <para>Install the JBoss jBPM GPD Eclipse plugin available from the JBoss jBPM download
+ area</para>
+ </listitem>
+ <listitem>
+ <para>Set up a Java project in Eclipse and prepare it to do test driven process
+ development</para>
+ </listitem>
+ <listitem>
+ <para>Using the creation wizard to create an empty process definition</para>
+ </listitem>
+ <listitem>
+ <para>Use the designer palette to draw the first processdefinition</para>
+ </listitem>
+ <listitem>
+ <para>Show how the xml processdefinition can be inspected as an xml file</para>
+ </listitem>
+ <listitem>
+ <para>Set up a Java project in Eclipse and prepare it to do test driven process
+ development</para>
+ </listitem>
+ <listitem>
+ <para>Write an example process test case</para>
+ </listitem>
+ </itemizedlist>
+ <para>If you have questions, please feel free to contact <ulink url="mailto:koen.aers@jboss.com"
+ >Koen Aers</ulink> or <ulink url="mailto:tom.baeyens@jboss.com">Tom Baeyens</ulink> for more
+ information.</para>
+ </section>
+
+ <section id="feature_list">
+
+ <title>Feature list</title>
+
+ <para> JBoss jBPM is a workflow that enables creating and automatization business processes. Look
+ at the list of features below to understand its main functionality.</para>
+ <table>
+ <title>Key Functionality for JBoss jBPM</title>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry>Feature</entry>
+ <entry>Benefit</entry>
+ </row>
+ </thead>
+ <tbody>
+
+ <row>
+ <entry>
+ <link linkend="minimal_process_definition">jBDL support</link>
+ </entry>
+ <entry>Enables managing workflow processes as well as human tasks and interactions between
+ them. jBDL combines the best both Java and declarative process techniques.</entry>
+ </row>
+
+ <row>
+ <entry>
+ <link linkend="GuidedTourJBossjBPMGPD">Support of Graphical Process Designer (GPD)</link>
+ </entry>
+ <entry>Is used for simplifying declarative process development and visualizations of all
+ actions.</entry>
+ </row>
+
+ <row>
+ <entry>
+ <link linkend="CreatingjBPMProject">Project Creation wizard</link>
+ </entry>
+ <entry>Allows to create a new jBPM template project that already includes all advanced
+ artifacts and core jBPM libraries.</entry>
+ </row>
+
+ <row>
+ <entry>
+ <link linkend="minimal_process_definition">Rich palette of pre-build process nodes</link>
+ </entry>
+ <entry>Provides process-building functionality and gives opportunity even non-programmers to
+ develop processes.</entry>
+ </row>
+
+ <row>
+ <entry>
+ <link linkend="the_views">A large range of special views, including:</link>
+ </entry>
+ <entry></entry>
+ </row>
+
+ <row>
+ <entry>
+ <link linkend="source_mode">Support of XML code view</link>
+ </entry>
+ <entry>Shows the corresponding XML that's generated automatically in the Source view
+ of the process definition editor when developing the process.</entry>
+ </row>
+
+ <row>
+ <entry>
+ <link linkend="the_properties_view">Properties view</link>
+ </entry>
+ <entry>Facilitates configuring and editing of all nodes properties.</entry>
+ </row>
+
+ <row>
+ <entry>
+ <link linkend="jbpm_gpd_editor">The jBPM Graphical Process Designer editor</link>
+ </entry>
+ <entry>The plugin is used for designing the workflow.</entry>
+ </row>
+
+
+ <row>
+ <entry>Interaction with all of the J2EE based integration technologies including Web Services,
+ Java Messaging, J2EE Connectors, JBDC, EJBs.</entry>
+ <entry>Enables implementation, provides better functionality and flexibility.</entry>
+ </row>
+
+ <row>
+ <entry>Integration with jBoss Seam</entry>
+ <entry>Allows to write applications with complex workflows and provides easier interactions
+ between them.</entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+
+ <section>
+ <title>Other relevant resources on the topic</title>
+ <para>All JBoss Developer Studio/JBoss Tools release documentation you can find at<ulink url="http://docs.jboss.org/tools/">http://docs.jboss.org/tools</ulink> in the corresponding release directory.</para>
+ <para>There is some extra information on <ulink url="http://www.jboss.org/community/wiki/JBPMWiki">JBoss Wiki. </ulink></para>
+ <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">http://download.jboss.org/jbosstools/nightly-docs</ulink>.</para>
+ </section>
+
+</chapter>
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Preface.xml
===================================================================
--- branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Preface.xml (rev 0)
+++ branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Preface.xml 2010-03-03 14:04:09 UTC (rev 20610)
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<preface><title>Preface</title><xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"><xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"><xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></xi:fallback></xi:include></preface>
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Quick_Howto_Guide.xml
===================================================================
--- branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Quick_Howto_Guide.xml (rev 0)
+++ branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Quick_Howto_Guide.xml 2010-03-03 14:04:09 UTC (rev 20610)
@@ -0,0 +1,175 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="Quick_Howto_Guide" xreflabel="Quick_Howto_Guide">
+ <?dbhtml filename="Quick_Howto_Guide.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>jBPM</keyword>
+ <keyword/>
+ <keyword/>
+ <keyword/>
+ <keyword/>
+ </keywordset>
+ </chapterinfo>
+ <title>Quick Howto Guide</title>
+
+ <para>This chapter contains additional information related to the <property>JBoss
+ jBPM</property>.</para>
+
+ <section id="change_core_jbpm_inst">
+ <title>Change the Default Core jBPM Installation</title>
+
+ <para> You can change the default <property>jBPM</property> installation by means of the
+ Eclipse preference mechanism. Open the Preferences dialog by selecting <emphasis>
+ <property>Window > Preferences</property>
+ </emphasis> and select the <emphasis>
+ <property>JBoss jBPM > Runtime Location</property>
+ </emphasis> category. Using this page you can add multiple <property>jBPM</property>
+ installation locations and change the default one. The default installation is used for
+ the classpath settings when creating a new Process Project. Changing the preferences has
+ no influence on already created projects. Getting rid of a <property>jBPM</property>
+ installation that's being referenced by a project however will cause the
+ classpath to contain errors. </para>
+
+
+ <figure>
+ <title>The jBPM Preferences Page</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+
+ <section>
+ <title>Configuring Task Nodes</title>
+
+ <para>Here, we'll examine how you can configure the Task nodes in jBPM jPDL GPD.</para>
+
+ <para> You can add Tasks to Task nodes and then configure them in a similar manner as the
+ Action configuration mechanism. Let's consider the process definition similar
+ to the previous one that contains three nodes: Start state, Task node and End state. The
+ <property>Properties view</property> for selected Task node includes several tabs. </para>
+
+ <figure>
+ <title>The Properties View of the selected Task Node</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_2.png"
+ scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>We should choose the Task tab and then bring up the context menu or click the button
+ in the top right corner of the view to add a Task to our Task node.</para>
+
+ <figure>
+ <title>Adding a Task to the Task Node</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_3.png"
+ scale="80"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Every added Task has its own configuration possibilities. You can access them through
+ the <property>Properties view</property> as well.</para>
+
+ <figure>
+ <title>The Task properties</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_4.png"
+ scale="80"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The <property>General page</property> is a place where you can specify the name of a
+ Task and its description. For instance, let it be <emphasis>
+ <property>approve oder</property>
+ </emphasis> with appropriate description that you can see in the figure below.</para>
+
+ <figure>
+ <title>The Task General Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_5.png"
+ scale="80"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Now, look at <property>Details page</property>. First, you should specify the due date
+ that is a mandatory property for the Task. The due date is the date on which the task
+ should be accomplished. Here you can also set a Task priority as well as signalling,
+ notifying or blocking. The <emphasis>
+ <property>Blocking</property>
+ </emphasis> attribute indicates that the process will not be able to continue if this
+ task is still unaccomplished. The <emphasis>
+ <property>Generate Form...</property>
+ </emphasis> button is for creating a simple task form that can be rendered by the jBPM
+ console.</para>
+
+ <figure>
+ <title>The Task Details Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_6.png"
+ scale="80"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>For our example, we specify the due date as 2 business days, choose the high priority
+ and also check the <emphasis>
+ <property>Signalling</property>
+ </emphasis> and <emphasis>
+ <property>Notify</property>
+ </emphasis> attributes. It means that the Task should be accomplished in 2 business days
+ and the assignee will be notified by email when the task is assigned. To specify how the
+ Task should be assigned switch on to the <property>Assignment page</property>.</para>
+
+ <figure>
+ <title>The Task Assignment Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_7.png"
+ scale="80"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>On the <property>Reminder page</property> you can specify whether the assignee will be reminded of the task
+ that awaits him.</para>
+
+ <figure>
+ <title>The Task Reminder Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_8.png"
+ scale="80"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>In our case, the assignee will be reminded by email after two business hours and
+ continue to get reminding every business hour after that.</para>
+ <para>In the next figure you can see our configuring generated into XML.</para>
+ <figure>
+ <title>The Task Reminder Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_9.png"
+ scale="80"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>We hope, our guide will help you to get started with the jPDL process language and jBPM
+ workflow on the whole. Besides, for additional information you are welcome on <ulink
+ url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss forum</ulink>.</para>
+ </section>
+</chapter>
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Revision_History.xml
===================================================================
--- branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Revision_History.xml (rev 0)
+++ branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Revision_History.xml 2010-03-03 14:04:09 UTC (rev 20610)
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<appendix><title>Revision History</title><simpara><revhistory><revision><revnumber>0</revnumber><date>Fri Nov 20 2009</date><author><firstname>Isaac</firstname><surname>Rooskov</surname><email>irooskov(a)redhat.com</email></author><revdescription><simplelist><member>Initial creation of book by publican</member></simplelist></revdescription></revision></revhistory></simpara></appendix>
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Test_Drive_Proc.xml
===================================================================
--- branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Test_Drive_Proc.xml (rev 0)
+++ branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/Test_Drive_Proc.xml 2010-03-03 14:04:09 UTC (rev 20610)
@@ -0,0 +1,173 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="Test_Drive_Proc_Development" xreflabel="Test_Drive_Proc_Development">
+ <?dbhtml filename="Test_Drive_Proc_Development.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>jBPM</keyword>
+ <keyword/>
+ <keyword/>
+ <keyword/>
+ <keyword/>
+ </keywordset>
+ </chapterinfo>
+ <title>Test Driven Process Development</title>
+
+ <para> One of the most important advantages of JBoss jBPM's lightweight approach to BPM
+ and workflow management is that developers can easily leverage their usual programming
+ skills and techniques. One of these well-known techniques is Unit Testing and Test Driven
+ Development. </para>
+ <para>In this chapter we will show how developers, making use of the JBoss jBPM GPD, can use a
+ technique we have baptized <property>Test Driven Process Development</property> to create
+ process definitions and test their correctness. </para>
+
+ <para> When creating the <emphasis>
+ <property>HellojBPM</property>
+ </emphasis> project the Project Creation wizard has already put in place all the library
+ requirements we need to start writing the jBPM unit tests. They are contained in the jBPM
+ Library container and the most important of them is the <emphasis>
+ <property>.jar</property>
+ </emphasis> file containing the core jBPM classes. While working on the project you could
+ find them all in the <property>Package Explorer</property>.</para>
+
+ <figure>
+ <title>The jBPM Libraries</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Test_Drive_Proc/test_driv_proc_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>It must be noted that it is possible to change the location of the core jBPM installation
+ by changing the preference settings. More on this <link linkend="change_core_jbpm_inst">see
+ later</link> in this book.</para>
+
+ <para> With that extra knowledge on the project settings, you can create your first test. To do
+ this, we create the <emphasis>
+ <property>com.jbay</property>
+ </emphasis> package in the <emphasis>
+ <property>test/java</property>
+ </emphasis> source folder. Then we bring up the context menu on this package and select <emphasis>
+ <property>New > Other...</property>
+ </emphasis></para>
+
+ <figure>
+ <title>Call the JUnit Test Case Creation wizard</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Test_Drive_Proc/test_driv_proc_2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para> And then <emphasis>
+ <property>Java > JUnit > JUnit Test Case</property>
+ </emphasis> to call the specialized JUnite Test case creation wizard.</para>
+ <figure>
+ <title>Call the JUnit Test Case Creation wizard</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Test_Drive_Proc/test_driv_proc_3.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The wizard looks as follows:</para>
+
+ <figure>
+ <title>Create Test Dialog</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Test_Drive_Proc/test_driv_proc_4.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>By default JUnite 3 version of testing framework is selected. Of course, you can choose
+ new advanced JUnit 4 version. In this case you'll be prompted to add new JUnit
+ Library to your build path. To add it automatically just click on the appropriate link. In
+ the <emphasis>
+ <property>Class under test</property>
+ </emphasis> section you can specify the class to test.</para>
+
+ <figure>
+ <title>A First Test Scenario</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Test_Drive_Proc/test_driv_proc_5.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Then, we call the test class <emphasis>
+ <property>HelloTest</property>
+ </emphasis> and press <emphasis>
+ <property>Finish</property>
+ </emphasis> button to complete.</para>
+
+ <para> Next, we should write a simple test scenario as shown on the next figure. Let's
+ study the code of this test case. </para>
+
+ <figure id="hello_test">
+ <title>A First Test Scenario</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Test_Drive_Proc/test_driv_proc_6.png" scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>In the first line of the method, a jBPM process archive object is created. We use a
+ constructor accepting the filename of the archive. In our case it is the <emphasis>
+ <property>hello</property>
+ </emphasis> file we created earlier and which lives in the <emphasis>
+ <property>src/main/jpdl</property>
+ </emphasis> folder of our project. After asserting that this object is really created, we
+ extract a process definition object from it. This object is fed to the constructor of a
+ process instance object. We have a process instance object, but this process is not yet
+ started, so we can safely assert that its root token still resides in the start node. After
+ signalling the token will move to the next state and the process will be in the <emphasis>
+ <property>auction</property>
+ </emphasis> state. Finally another signal will end the process. </para>
+
+
+ <para> After writing this test we can check whether it works as expected by running it .</para>
+
+ <figure>
+ <title>Running the Process Test</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Test_Drive_Proc/test_driv_proc_7.png" scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>All went well as we have a green light:</para>
+
+ <figure>
+ <title>Successful Test Run</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Test_Drive_Proc/test_driv_proc_8.png" scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para> Of course, this simple scenario was not very interesting, but the purpose of it was to
+ show how you can reuse your development skills in a very straightforward way when doing
+ process development. To see how more interesting processes and process test
+ scenario's can be developed, we suggest you to read the <ulink
+ url="http://docs.jboss.com/jbpm/v3/userguide/">JBoss jBPM User Guide</ulink> and to
+ study the API reference. You can find it in the jBPM download folder. (To get started we
+ downloaded jbpm-jpdl-3.2.2 in <link linkend="jboss_jbpm_runtime_installation">the second
+ chapter</link>. You should just remember where you extracted it.) All we've mentioned are in the 'javadoc- *' subfolders of the 'doc' folder.
+ Moreover, some more examples will be given later in this book.</para>
+
+</chapter>
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/The_JBoss_jBPM_Int_Mech.xml
===================================================================
--- branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/The_JBoss_jBPM_Int_Mech.xml (rev 0)
+++ branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/The_JBoss_jBPM_Int_Mech.xml 2010-03-03 14:04:09 UTC (rev 20610)
@@ -0,0 +1,241 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="The_JBoss_jBPM_Int_Mech" xreflabel="The_JBoss_jBPM_Int_Mech">
+ <?dbhtml filename="The_JBoss_jBPM_Int_Mech.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>jBPM</keyword>
+ <keyword/>
+ <keyword/>
+ <keyword/>
+ <keyword/>
+ </keywordset>
+ </chapterinfo>
+ <title>Actions : The JBoss jBPM Integration Mechanism</title>
+
+ <para> In this chapter we will show how to do software integration with <property>JBoss
+ jBPM</property>. The standard mechanism to implement this is to wrap the functionality you
+ want to integrate in a class that implements the <emphasis>
+ <property>ActionHandler</property>
+ </emphasis> interface. In order to demonstrate it let's specify Hello World action for our
+ process.</para>
+
+ <section>
+ <title>Creating a Hello World Action</title>
+
+ <para>Each Hello World process should integrate one or more Hello World actions, so this is
+ what we will be doing. We can integrate custom code at different points in the process
+ definition. To do this we have to specify an action handler, represented by an
+ implementation of the <emphasis>
+ <property>ActionHandler</property>
+ </emphasis> interface, and attach this piece of code to a particular event. These events
+ are amongst others, going over a transition, leaving or entering nodes, after and before
+ signalling. </para>
+
+ <para> To make things a little bit more concrete, let's create a new class called <emphasis>
+ <property>HelloActionHandler</property>.
+ </emphasis> For that firstly we'll create a new package <emphasis>
+ <property>com.jbay.action</property>
+ </emphasis> in the <emphasis>
+ <property>src/java/main</property>
+ </emphasis> folder of our project. Then, we should call New Class Creation wizard as
+ usual by right-clicking and navigating <emphasis>
+ <property>New > Class</property>.
+ </emphasis> </para>
+
+ <figure>
+ <title>Creating HelloActionHendler Class</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Notice that two first gaps have been filled automatically. Here, instead of <emphasis>
+ <property>Package</property>
+ </emphasis> option <emphasis>
+ <property>Enclose type</property>
+ </emphasis> option can be selected where a type in which to enclose a new class should
+ be specified.</para>
+
+ <para>In our case, we leave everything as it is, just type <emphasis>
+ <property>HelloActionHandler</property>
+ </emphasis> as a name of new class and add <emphasis>
+ <property>org.jbpm.graph.ActionHendler</property>
+ </emphasis> interface as it's shown in the picture above.</para>
+
+ <para>Thus, our <emphasis>
+ <property>HelloActionHandler</property>
+ </emphasis> implements the <emphasis>
+ <property>ActionHandler</property>
+ </emphasis> interface including the <emphasis>
+ <property>execute</property>
+ </emphasis> method as shown in the next figure. Here, we add a variable named <emphasis>
+ <property>greeting</property>
+ </emphasis> to the collection of process variables and put a message in it :
+ <emphasis>"Hello from ActionHandler"</emphasis>. </para>
+
+ <figure>
+ <title>A Simple Hello Action</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_2.png" scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Now, as we have <emphasis>
+ <property>HelloActionHandler</property>
+ </emphasis> class defined, let's explore how we can handle it.</para>
+ </section>
+
+ <section>
+ <title>Integrating the Hello World Action</title>
+
+ <para>The main purpose of this chapter is to provide you with the steps associating our
+ Hello World action with a particular event and test the correctness of our actions as
+ well.</para>
+
+ <para> As good Testcity citizens we will first create a Unit Test that proves the behaviour
+ we want to achieve by adding the <emphasis>
+ <property>ActionHandler</property>
+ </emphasis> to the process. So we implement another test.</para>
+
+ <para>At first, let's return to the
+ code we already saw <link linkend="hello_test">in the previous chapter</link> and add new test method <emphasis>
+ <property>testActionHendler</property></emphasis> to it. </para>
+
+ <figure>
+ <title>Create the Hello Action Test</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_3.png"
+ scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>We assert
+ that no variable called <emphasis>
+ <property>greeting</property>
+ </emphasis> exist. Then we give the process a signal to move it to the auction state. We
+ want to associate the execution of the action with the event of going over the
+ transition from the start state to the auction state. So after the signal, the process
+ should be in the auction state as in the previous scenario. But moreover, the <emphasis>
+ <property>greeting</property>
+ </emphasis> variable should exist and contain the string <emphasis>"Hello from
+ ActionHandler"</emphasis>. That's what we assert in the last lines of the test
+ method.</para>
+
+
+
+ <para> Running the tests now results in a failure. The point is that we did not associate
+ the action with any particular event in the process definition, so the process variable
+ did not get set. </para>
+
+ <figure>
+ <title>Test Results Before Integration</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_4.png"
+ scale="75"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para> Let's do something about it and add an action to the first transition of our
+ sample process. To do this you can use the Actions tab in the Properties Editor that is
+ under the graphical canvas. Bring up the popup menu of the action element container and
+ chose New Action as it's shown on the figure below. The other way to add an action
+ to the transition is simply to use the dropdown menu that is available under the action
+ icon in the right upper corner of the Properties View.</para>
+
+ <figure>
+ <title>Adding an Action to a Transition</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_5.png" scale="80"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>After adding the action a tabbed view with three pages will appear.</para>
+
+ <figure>
+ <title>Configuration Dialog for an Action</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_6.png" scale="80"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The first of these three pages allows you to give the Action a name. The last page
+ contains some advanced attributes such as whether the Action is asynchronous. The
+ Details page is the most important. It allows to choose and configure the actual action
+ handler implementation. </para>
+
+ <figure>
+ <title>The Details page of an Action Configuration Dialog</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_7.png" scale="80"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+
+ <para>Clicking on the <emphasis>
+ <property>Search...</property>
+ </emphasis> button brings us to a Choose Class dialog.</para>
+
+
+ <figure>
+ <title>The Choose Action Handler Dialog</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_8.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+
+ <para> We choose our previously created 'HelloActionHandler' class and
+ push the <property>OK</property> button. After the selection of the action handler for
+ the action, we can run the test and observe it gives us a green light.</para>
+
+ <figure>
+ <title>Test Results</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_9.png"
+ scale="70"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>There we are. The above objective has been achieved.</para>
+ </section>
+
+ <section>
+ <title> Integration Points</title>
+
+ <para> The different integration points in a process definition are thoroughly documented in
+ the <ulink
+ url="http://docs.jboss.com/jbpm/v3/userguide/">JBoss jBPM User Guide</ulink>. Instance nodes can contain many action
+ elements. Each of these will appear in the Action element list of the Actions tab. But
+ each Action also has a properties view of itself. You can navigate to this view by
+ selecting the added Action in the outline view. </para>
+
+ </section>
+
+</chapter>
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/guided_tour_jboss_jbpmgpd.xml
===================================================================
--- branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/guided_tour_jboss_jbpmgpd.xml (rev 0)
+++ branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/guided_tour_jboss_jbpmgpd.xml 2010-03-03 14:04:09 UTC (rev 20610)
@@ -0,0 +1,221 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="GuidedTourJBossjBPMGPD" xreflabel="GuidedTourJBossjBPMGPD">
+ <?dbhtml filename="GuidedTourJBossjBPMGPD.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>jBPM</keyword>
+ <keyword>JBoss</keyword>
+ <keyword>Process</keyword>
+ <keyword>Definition</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>A Guided Tour of JBoss jBPM GPD</title>
+ <para>In this chapter we suggest a step-by-step walk-through of creating and configuring your
+ own simple process. Let's try to organize a new jBPM project.</para>
+ <para>A wizard for creating a jBPM project is included in the GPD plugin. We have opted to
+ create a project based on a template already containing a number of advanced artifacts that
+ we will ignore for this section. In the future we will elaborate this wizard and offer the
+ possibility to create an empty jBPM project as well as projects based on templates taken
+ from the jBPM tutorial.</para>
+ <section id="CreatingjBPMProject">
+ <?dbhtml filename="CreatingjBPMProject.html"?>
+ <title>Creating a jBPM Project</title>
+ <para>This section will show you how to use the Creation wizard for creating a new jBPM
+ project with already included source folders.</para>
+ <para>At first you should select <emphasis>
+ <property>File >New Project...</property>
+ </emphasis> and then <emphasis>
+ <property>JBoss jBPM > Process Project</property>
+ </emphasis> in the New Project dialog:</para>
+ <figure>
+ <title>New Project Dialog</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para> Clicking <emphasis>
+ <property>Next</property>
+ </emphasis> brings us to the wizard page where it's necessary to specify the
+ name and location for the project. We choose, for example, <emphasis>
+ <property>HellojBPM</property>
+ </emphasis> as the name and accept the default location. </para>
+ <figure>
+ <title>Process Name and Location</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour_2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Thus, our project will be created in the workspace root directory by default. If you
+ want to change the directory for your future project, deselect <emphasis>
+ <property>Use default location</property>
+ </emphasis> and click <emphasis>
+ <property>Browse...</property>
+ </emphasis> button to set needed location or simply type it.</para>
+ <para>On the next screen you'll be prompted to select the core jBPM location that
+ we have defined in the previous chapter.</para>
+ <figure>
+ <title>Core jBPM Location Specifying</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour_9.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Clicking on <emphasis>
+ <property>Finish</property>
+ </emphasis> results in the project being generated. The wizard creates four source
+ folders: one for the processes (<emphasis>
+ <property>src/main/jpdl</property>
+ </emphasis>), one for the java sources (<emphasis>
+ <property>src/main/java</property>
+ </emphasis>), one for the unit tests (<emphasis>
+ <property>src/test/java</property>
+ </emphasis>) and one for the resources such as the jbpm.properties and the
+ hibernate.properties files (<emphasis>
+ <property>src/main/config</property>
+ </emphasis>). In addition a classpath container with all the core jBPM libraries is
+ added to the project</para>
+ <figure>
+ <title>Layout of the Process Project</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour_3.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Looking inside the different source folders will reveal a number of other artifacts
+ that were generated, but we will leave these untouched for the moment. Instead, we will
+ look at another wizard that enables us to create an empty process definition.</para>
+ </section>
+ <section id="creating_an_empty_process_definition">
+ <?dbhtml filename="creating_an_empty_process_definition.html"?>
+ <title>Creating an Empty Process Definition</title>
+ <para>Now when the project is set up, we can use a Creation wizard to create an empty
+ process definition. Bring up the <emphasis>
+ <property>New</property>
+ </emphasis> wizard by clicking the <emphasis>
+ <property>File > New > Other...</property>
+ </emphasis> menu item. The wizard opens on the <emphasis>
+ <property>Select Wizard</property>
+ </emphasis> page.</para>
+ <figure>
+ <title>The Select Wizard Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour_4.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Selecting the <emphasis>
+ <property>JBoss jBPM</property>
+ </emphasis> category, then the <emphasis>
+ <property>Process Definition</property>
+ </emphasis> item and clicking on the <emphasis>
+ <property>Next</property>
+ </emphasis> button brings us to the <emphasis>
+ <property>Create Process Definition</property>
+ </emphasis> page.</para>
+ <figure>
+ <title>The Create New Process Defining Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour_5.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>We choose <emphasis>
+ <property>hello</property>
+ </emphasis> as the name of the process archive file. Click on the <emphasis>
+ <property>Finish</property>
+ </emphasis> button to end the wizard and open the process definition editor.</para>
+ <figure>
+ <title>The Process Definition Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour_6.png"
+ scale="60"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+
+ <para>You can see in the Package Explorer that creating a process definition involves
+ creating a folder with the name of the process definition and populating this folder
+ with two .xml files : <emphasis>
+ <property>gpd.xml</property>
+ </emphasis> and <emphasis>
+ <property>processdefinition.xml</property>. </emphasis></para>
+ <para>The <emphasis>
+ <property>gpd.xml</property>
+ </emphasis> contains the graphical information used by the process definition editor.
+ The <emphasis>
+ <property>processdefinition.xml</property>
+ </emphasis> file contains the actual process definition info without the graphical
+ rendering info. At present, the GPD assumes that these two files are siblings. More
+ sophisticated configuration will be supported later.</para>
+
+ <section id="minimal_process_definition">
+ <?dbhtml filename="minimal_process_definition.html"?>
+ <title>A Minimal Process Definition</title>
+ <para>Now we are ready to create a very simple process definition consisting of a begin
+ state, an intermediate state and an end state.</para>
+ <para>To make the configuration of actions much easier it's better to use the
+ jPDL perspective. It provides the tabbed Properties Editor which allows to configure
+ all the relevant properties of the current selected item. </para>
+
+ <section id="adding_the_nodes">
+ <?dbhtml filename="adding_the_nodes.html"?>
+ <title>Adding the Nodes</title>
+ <para>At first select respectively <emphasis>
+ <property>Start</property>, </emphasis>
+ <emphasis>
+ <property>State</property>
+ </emphasis> and <emphasis>
+ <property>End</property>
+ </emphasis> on the tools palette and click on the canvas to add these nodes to
+ the process definition. The result should look similar to this:</para>
+ <figure>
+ <title>A Simple Process With Three Nodes</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour_7.png"
+ scale="60"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="adding_transitions">
+ <?dbhtml filename="adding_transitions.html"?>
+ <title>Adding Transitions</title>
+ <para>Then, we will connect the nodes with transitions. To do that select the <emphasis>
+ <property>Transition</property>
+ </emphasis> tool in the tools palette and click on the <emphasis>
+ <property>Start</property>
+ </emphasis> node, then move to the <emphasis>
+ <property>State</property>
+ </emphasis> node and click again to see the transition being drawn. Perform the
+ same steps to create a transition from the <emphasis>
+ <property>State</property>
+ </emphasis> node to the <emphasis>
+ <property>End</property>
+ </emphasis> node. The result will look like:</para>
+ <figure>
+ <title>A Simple Process With Transitions</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour_8.png"
+ scale="60"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Now, when you've got background knowledge of simple project creation,
+ let's move to more advanced tools.</para>
+ </section>
+ </section>
+ </section>
+
+</chapter>
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_3.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_4.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_5.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_5.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_6.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_6.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_7.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_7.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_8.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_8.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_9.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Quick_Howto_Guide/quick_howto_guide_9.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_3.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_4.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_5.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_5.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_6.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_6.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_7.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_7.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_8.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/Test_Drive_Proc/test_driv_proc_8.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_3.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_4.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_5.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_5.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_6.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_6.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_7.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_7.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_8.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_8.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_9.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_9.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/favicon.ico
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/favicon.ico
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_3.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_4.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_5.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_5.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_6.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_6.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_7.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_7.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_8.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_8.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_9.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/guided_tour_jboss_jbpmgpd/guided_tour_9.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/jbosstools_logo.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/jbosstools_logo.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/runtime_installation/runtime_installation_1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/runtime_installation/runtime_installation_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_0.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_0.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_1.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_10.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_10.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_2.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_3.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_4.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_5.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_5.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_6.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_6.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_7.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_7.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_8.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_8.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_9.png
===================================================================
(Binary files differ)
Property changes on: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/images/the_views/the_views_9.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/jBPM_Tools_Reference_Guide.ent
===================================================================
--- branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/jBPM_Tools_Reference_Guide.ent (rev 0)
+++ branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/jBPM_Tools_Reference_Guide.ent 2010-03-03 14:04:09 UTC (rev 20610)
@@ -0,0 +1,4 @@
+<!ENTITY PRODUCT "JBoss">
+<!ENTITY BOOKID "jBPM_Tools_Reference_Guide">
+<!ENTITY YEAR "2009">
+<!ENTITY HOLDER "Red Hat">
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/jBPM_Tools_Reference_Guide.xml
===================================================================
--- branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/jBPM_Tools_Reference_Guide.xml (rev 0)
+++ branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/jBPM_Tools_Reference_Guide.xml 2010-03-03 14:04:09 UTC (rev 20610)
@@ -0,0 +1,15 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<book>
+<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="jboss_jbpm_runtime_installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="guided_tour_jboss_jbpmgpd.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="the_views.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="Test_Drive_Proc.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="The_JBoss_jBPM_Int_Mech.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="Quick_Howto_Guide.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+</book>
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/jboss_jbpm_runtime_installation.xml
===================================================================
--- branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/jboss_jbpm_runtime_installation.xml (rev 0)
+++ branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/jboss_jbpm_runtime_installation.xml 2010-03-03 14:04:09 UTC (rev 20610)
@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="jboss_jbpm_runtime_installation" xreflabel="jboss_jbpm_runtime_installation">
+ <?dbhtml filename="jboss_jbpm_runtime_installation.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>jBPM</keyword>
+ <keyword>designer</keyword>
+ <keyword>process</keyword>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>jBPM runtime</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>JBoss jBPM Runtime Installation</title>
+ <para>The main purpose of this chapter is to let you know how to launch the <property>JBoss
+ jBPM</property> (business process management).</para>
+ <para>The jBPM plugin (jBPM Designer) is already included in the <property>JBoss Tools</property>.
+ To make it work, you should only download the jBPM runtime (<ulink
+ url="http://sourceforge.net/project/showfiles.php?group_id=70542&package_i..."
+ >jbpm-jpdl-3.2.3</ulink> currently) and specify the directory where you extracted the runtime
+ either when you create a jBPM project or by using the jBPM preference pages.</para>
+
+ <note>
+ <title>Note:</title>
+ <para>Try to avoid using spaces in the names of installation folders. It can provoke problems in
+ some situations with Sun-based VMs.</para>
+ </note>
+
+ <para>Navigate to <emphasis>
+ <property>Window > Preferences > JBoss jBPM > Runtime Locations</property>.
+ </emphasis> Here you can add, edit and remove JBoss jBPM installation locations. Click <emphasis>
+ <property>Add</property>
+ </emphasis> button. In the dialog that appeared enter a name for a newly added jBPM runtime and
+ point to the correct location of this package on your harddrive. Click <emphasis>
+ <property>OK</property>
+ </emphasis> then click <emphasis>
+ <property>OK</property>
+ </emphasis> again.</para>
+
+ <figure>
+ <title>Adding jBPM Location</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/runtime_installation/runtime_installation_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Now, when you have a runtime installed, we are going to demonstrate some powerful features of
+ the jBPM.</para>
+</chapter>
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/master.xml
===================================================================
--- branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/master.xml (rev 0)
+++ branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/master.xml 2010-03-03 14:04:09 UTC (rev 20610)
@@ -0,0 +1,91 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.docbook.org/xml/4.3/docbookx.dtd"
+
+
+[<!ENTITY introduction SYSTEM "Introduction.xml">
+<!ENTITY jboss_jbpm_runtime_installation SYSTEM "jboss_jbpm_runtime_installation.xml">
+<!ENTITY guided_tour_jboss_jbpmgpd SYSTEM "guided_tour_jboss_jbpmgpd.xml">
+<!ENTITY the_views SYSTEM "the_views.xml">
+<!ENTITY Test_Drive_Proc SYSTEM "Test_Drive_Proc.xml">
+<!ENTITY The_JBoss_jBPM_Int_Mech SYSTEM "The_JBoss_jBPM_Int_Mech.xml">
+<!ENTITY Quick_Howto_Guide SYSTEM "Quick_Howto_Guide.xml">
+
+<!ENTITY seamlink "../../seam/html_single/index.html">
+<!ENTITY aslink "../../as/html_single/index.html">
+<!ENTITY esblink "../../esb_ref_guide/html_single/index.html">
+<!ENTITY gsglink "../../GettingStartedGuide/html_single/index.html">
+<!ENTITY hibernatelink "../../hibernatetools/html_single/index.html">
+<!ENTITY jbpmlink "../../jbpm/html_single/index.html">
+<!ENTITY jsflink "../../jsf/html_single/index.html">
+<!ENTITY jsfreflink "../../jsf_tools_ref_guide/html_single/index.html">
+<!ENTITY jsftutoriallink "../../jsf_tools_tutorial/html_single/index.html">
+<!ENTITY strutsreflink "../../struts_tools_ref_guide/html_single/index.html">
+<!ENTITY strutstutoriallink "../../struts_tools_tutorial/html_single/index.html">
+
+ ]>
+<book>
+ <bookinfo>
+ <title>jBPM Tools Reference Guide</title>
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject role="fo">
+ <imagedata format="PNG" fileref="images/jbosstools_logo.png" />
+ </imageobject>
+ <imageobject role="html">
+ <imagedata/>
+ </imageobject>
+ </inlinemediaobject>
+ </corpauthor>
+
+ <author>
+ <firstname>Anatoly</firstname>
+ <surname>Fedosik</surname>
+ </author>
+ <author>
+ <firstname>Koen</firstname>
+ <surname>Aers</surname>
+ <email>koen.aers(a)jboss.com</email>
+ </author>
+ <author>
+ <firstname>Olga</firstname>
+ <surname>Chikvina</surname>
+ </author>
+ <author>
+ <firstname>Svetlana</firstname>
+ <surname>Mukhina</surname>
+ <email>smukhina(a)exadel.com</email>
+ </author>
+ <author>
+ <firstname>Tom</firstname>
+ <surname>Baeyens</surname>
+ <email>tom.baeyens(a)jboss.com</email>
+ </author>
+
+ <copyright>
+ <year>2007</year>
+ <year>2009</year>
+ <year>2010</year>
+ <holder>JBoss by Red Hat</holder>
+ </copyright>
+ <releaseinfo> Version: 4.0.0.trunk</releaseinfo>
+
+<abstract>
+ <title/>
+ <para>
+ <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/jbpm/pdf/JBPM_Refere...">PDF version</ulink>
+ </para>
+</abstract>
+
+ </bookinfo>
+
+ <toc/>
+ &introduction;
+ &jboss_jbpm_runtime_installation;
+ &guided_tour_jboss_jbpmgpd;
+ &the_views; &Test_Drive_Proc;
+ &The_JBoss_jBPM_Int_Mech;
+ &Quick_Howto_Guide;
+
+ <!-- TODO: drools used in this section is not available for eclipse .3.3 &AddBusinessProcess; -->
+</book>
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/master_output.xml
===================================================================
--- branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/master_output.xml (rev 0)
+++ branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/master_output.xml 2010-03-03 14:04:09 UTC (rev 20610)
@@ -0,0 +1,1317 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.docbook.org/xml/4.3/docbookx.dtd"
+
+
+[<!ENTITY introduction SYSTEM "modules/Introduction.xml">
+<!ENTITY jboss_jbpm_runtime_installation SYSTEM "modules/jboss_jbpm_runtime_installation.xml">
+<!ENTITY guided_tour_jboss_jbpmgpd SYSTEM "modules/guided_tour_jboss_jbpmgpd.xml">
+<!ENTITY the_views SYSTEM "modules/the_views.xml">
+<!ENTITY Test_Drive_Proc SYSTEM "modules/Test_Drive_Proc.xml">
+<!ENTITY The_JBoss_jBPM_Int_Mech SYSTEM "modules/The_JBoss_jBPM_Int_Mech.xml">
+<!ENTITY Quick_Howto_Guide SYSTEM "modules/Quick_Howto_Guide.xml">
+
+<!ENTITY seamlink "../../seam/html_single/index.html">
+<!ENTITY aslink "../../as/html_single/index.html">
+<!ENTITY esblink "../../esb_ref_guide/html_single/index.html">
+<!ENTITY gsglink "../../GettingStartedGuide/html_single/index.html">
+<!ENTITY hibernatelink "../../hibernatetools/html_single/index.html">
+<!ENTITY jbpmlink "../../jbpm/html_single/index.html">
+<!ENTITY jsflink "../../jsf/html_single/index.html">
+<!ENTITY jsfreflink "../../jsf_tools_ref_guide/html_single/index.html">
+<!ENTITY jsftutoriallink "../../jsf_tools_tutorial/html_single/index.html">
+<!ENTITY strutsreflink "../../struts_tools_ref_guide/html_single/index.html">
+<!ENTITY strutstutoriallink "../../struts_tools_tutorial/html_single/index.html">
+
+ ]><book xmlns:diffmk="http://diffmk.sf.net/ns/diff">
+ <bookinfo>
+ <title>jBPM Tools Reference Guide</title>
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/jbosstools_logo.png" format="PNG"></imagedata>
+ </imageobject>
+ <imageobject role="html">
+ <imagedata></imagedata>
+ </imageobject>
+ </inlinemediaobject>
+ </corpauthor>
+
+ <author>
+ <firstname>Anatoly</firstname>
+ <surname>Fedosik</surname>
+ </author>
+ <author>
+ <firstname>Koen</firstname>
+ <surname>Aers</surname>
+ <email>koen.aers(a)jboss.com</email>
+ </author>
+ <author>
+ <firstname>Olga</firstname>
+ <surname>Chikvina</surname>
+ </author>
+ <author>
+ <firstname>Svetlana</firstname>
+ <surname>Mukhina</surname>
+ <email>smukhina(a)exadel.com</email>
+ </author>
+ <author>
+ <firstname>Tom</firstname>
+ <surname>Baeyens</surname>
+ <email>tom.baeyens(a)jboss.com</email>
+ </author>
+
+ <copyright>
+ <year>2007</year>
+ <year>2009</year>
+ <year>2010</year>
+ <holder>JBoss by Red Hat</holder>
+ </copyright>
+ <releaseinfo><diffmk:wrapper diffmk:change="changed"> Version: 4.0.0.trunk</diffmk:wrapper></releaseinfo>
+
+<abstract>
+ <title></title>
+ <para>
+ <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/jbpm/pdf/JBPM_Refere...">PDF version</ulink>
+ </para>
+</abstract>
+
+ </bookinfo>
+
+ <toc></toc>
+
+<chapter id="Introduction" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/jbpm/docs/reference/en/modules/Introduction.xml" xreflabel="Introduction">
+ <?dbhtml filename="TargetAudience.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>jBPM</keyword>
+ <keyword>Target</keyword>
+ <keyword>developers</keyword>
+ <keyword>Audience</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Introduction</title>
+ <para>All developers and process analysts who are beginning to use JBoss jBPM should read this
+ Getting Started guide. It will give them a jumpstart showing how to create a process definition.</para>
+ <section id="Preface">
+ <?dbhtml filename="Preface.html"?>
+ <title>Preface</title>
+ <para>This document introduces the use of the JBoss jBPM Graphical Process Designer (GPD) to
+ create workflow processes. It will help first time users with the following tasks :</para>
+ <itemizedlist>
+ <listitem>
+ <para>Install the JBoss jBPM GPD Eclipse plugin available from the JBoss jBPM download
+ area</para>
+ </listitem>
+ <listitem>
+ <para>Set up a Java project in Eclipse and prepare it to do test driven process
+ development</para>
+ </listitem>
+ <listitem>
+ <para>Using the creation wizard to create an empty process definition</para>
+ </listitem>
+ <listitem>
+ <para>Use the designer palette to draw the first processdefinition</para>
+ </listitem>
+ <listitem>
+ <para>Show how the xml processdefinition can be inspected as an xml file</para>
+ </listitem>
+ <listitem>
+ <para>Set up a Java project in Eclipse and prepare it to do test driven process
+ development</para>
+ </listitem>
+ <listitem>
+ <para>Write an example process test case</para>
+ </listitem>
+ </itemizedlist>
+ <para>If you have questions, please feel free to contact <ulink url="mailto:koen.aers@jboss.com">Koen Aers</ulink> or <ulink url="mailto:tom.baeyens@jboss.com">Tom Baeyens</ulink> for more
+ information.</para>
+ </section>
+
+ <section id="feature_list">
+
+ <title>Feature list</title>
+
+ <para> JBoss jBPM is a workflow that enables creating and automatization business processes. Look
+ at the list of features below to understand its main functionality.</para>
+ <table>
+ <title>Key Functionality for JBoss jBPM</title>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry>Feature</entry>
+ <entry>Benefit</entry>
+ </row>
+ </thead>
+ <tbody>
+
+ <row>
+ <entry>
+ <link linkend="minimal_process_definition">jBDL support</link>
+ </entry>
+ <entry>Enables managing workflow processes as well as human tasks and interactions between
+ them. jBDL combines the best both Java and declarative process techniques.</entry>
+ </row>
+
+ <row>
+ <entry>
+ <link linkend="GuidedTourJBossjBPMGPD">Support of Graphical Process Designer (GPD)</link>
+ </entry>
+ <entry>Is used for simplifying declarative process development and visualizations of all
+ actions.</entry>
+ </row>
+
+ <row>
+ <entry>
+ <link linkend="CreatingjBPMProject">Project Creation wizard</link>
+ </entry>
+ <entry>Allows to create a new jBPM template project that already includes all advanced
+ artifacts and core jBPM libraries.</entry>
+ </row>
+
+ <row>
+ <entry>
+ <link linkend="minimal_process_definition">Rich palette of pre-build process nodes</link>
+ </entry>
+ <entry>Provides process-building functionality and gives opportunity even non-programmers to
+ develop processes.</entry>
+ </row>
+
+ <row>
+ <entry>
+ <link linkend="the_views">A large range of special views, including:</link>
+ </entry>
+ <entry></entry>
+ </row>
+
+ <row>
+ <entry>
+ <link linkend="source_mode">Support of XML code view</link>
+ </entry>
+ <entry>Shows the corresponding XML that's generated automatically in the Source view
+ of the process definition editor when developing the process.</entry>
+ </row>
+
+ <row>
+ <entry>
+ <link linkend="the_properties_view">Properties view</link>
+ </entry>
+ <entry>Facilitates configuring and editing of all nodes properties.</entry>
+ </row>
+
+ <row>
+ <entry>
+ <link linkend="jbpm_gpd_editor">The jBPM Graphical Process Designer editor</link>
+ </entry>
+ <entry>The plugin is used for designing the workflow.</entry>
+ </row>
+
+
+ <row>
+ <entry>Interaction with all of the J2EE based integration technologies including Web Services,
+ Java Messaging, J2EE Connectors, JBDC, EJBs.</entry>
+ <entry>Enables implementation, provides better functionality and flexibility.</entry>
+ </row>
+
+ <row>
+ <entry>Integration with jBoss Seam</entry>
+ <entry>Allows to write applications with complex workflows and provides easier interactions
+ between them.</entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+
+ <section>
+ <title>Other relevant resources on the topic</title>
+ <para>All JBoss Developer Studio/JBoss Tools release documentation you can find at<ulink url="http://docs.jboss.org/tools/">http://docs.jboss.org/tools</ulink> in the corresponding release directory.</para>
+ <para>There is some extra information on <ulink url="http://www.jboss.org/community/wiki/JBPMWiki">JBoss Wiki. </ulink></para>
+ <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">http://download.jboss.org/jbosstools/nightly-docs</ulink>.</para>
+ </section>
+
+</chapter>
+
+
+<chapter id="jboss_jbpm_runtime_installation" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/jbpm/docs/reference/en/modules/jboss_jbpm_runtime_installation.xml" xreflabel="jboss_jbpm_runtime_installation">
+ <?dbhtml filename="jboss_jbpm_runtime_installation.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>jBPM</keyword>
+ <keyword>designer</keyword>
+ <keyword>process</keyword>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>jBPM runtime</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>JBoss jBPM Runtime Installation</title>
+ <para>The main purpose of this chapter is to let you know how to launch the <property moreinfo="none">JBoss
+ jBPM</property> (business process management).</para>
+ <para>The jBPM plugin (jBPM Designer) is already included in the <property moreinfo="none">JBoss Tools</property>.
+ To make it work, you should only download the jBPM runtime (<ulink
+ url="http://sourceforge.net/project/showfiles.php?group_id=70542&
+ package_id=145174&release_id=607377"
+ >jbpm-jpdl-3.2.3</ulink> currently) and specify the directory where you extracted the runtime
+ either when you create a jBPM project or by using the jBPM preference pages.</para>
+
+ <note>
+ <title>Note:</title>
+ <para>Try to avoid using spaces in the names of installation folders. It can provoke problems in
+ some situations with Sun-based VMs.</para>
+ </note>
+
+ <para>Navigate to <emphasis>
+ <property moreinfo="none">Window > Preferences > JBoss jBPM > Runtime Locations</property>.
+ </emphasis> Here you can add, edit and remove JBoss jBPM installation locations. Click <emphasis>
+ <property moreinfo="none">Add</property>
+ </emphasis> button. In the dialog that appeared enter a name for a newly added jBPM runtime and
+ point to the correct location of this package on your harddrive. Click <emphasis>
+ <property moreinfo="none">OK</property>
+ </emphasis> then click <emphasis>
+ <property moreinfo="none">OK</property>
+ </emphasis> again.</para>
+
+ <figure float="0">
+ <title>Adding jBPM Location</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/runtime_installation/runtime_installation_1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Now, when you have a runtime installed, we are going to demonstrate some powerful features of
+ the jBPM.</para>
+</chapter>
+
+
+<chapter id="GuidedTourJBossjBPMGPD" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/jbpm/docs/reference/en/modules/guided_tour_jboss_jbpmgpd.xml" xreflabel="GuidedTourJBossjBPMGPD">
+ <?dbhtml filename="GuidedTourJBossjBPMGPD.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>jBPM</keyword>
+ <keyword>JBoss</keyword>
+ <keyword>Process</keyword>
+ <keyword>Definition</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>A Guided Tour of JBoss jBPM GPD</title>
+ <para>In this chapter we suggest a step-by-step walk-through of creating and configuring your
+ own simple process. Let's try to organize a new jBPM project.</para>
+ <para>A wizard for creating a jBPM project is included in the GPD plugin. We have opted to
+ create a project based on a template already containing a number of advanced artifacts that
+ we will ignore for this section. In the future we will elaborate this wizard and offer the
+ possibility to create an empty jBPM project as well as projects based on templates taken
+ from the jBPM tutorial.</para>
+ <section id="CreatingjBPMProject">
+ <?dbhtml filename="CreatingjBPMProject.html"?>
+ <title>Creating a jBPM Project</title>
+ <para>This section will show you how to use the Creation wizard for creating a new jBPM
+ project with already included source folders.</para>
+ <para>At first you should select <emphasis>
+ <property moreinfo="none">File >New Project...</property>
+ </emphasis> and then <emphasis>
+ <property moreinfo="none">JBoss jBPM > Process Project</property>
+ </emphasis> in the New Project dialog:</para>
+ <figure float="0">
+ <title>New Project Dialog</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour_1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para> Clicking <emphasis>
+ <property moreinfo="none">Next</property>
+ </emphasis> brings us to the wizard page where it's necessary to specify the
+ name and location for the project. We choose, for example, <emphasis>
+ <property moreinfo="none">HellojBPM</property>
+ </emphasis> as the name and accept the default location. </para>
+ <figure float="0">
+ <title>Process Name and Location</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour_2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Thus, our project will be created in the workspace root directory by default. If you
+ want to change the directory for your future project, deselect <emphasis>
+ <property moreinfo="none">Use default location</property>
+ </emphasis> and click <emphasis>
+ <property moreinfo="none">Browse...</property>
+ </emphasis> button to set needed location or simply type it.</para>
+ <para>On the next screen you'll be prompted to select the core jBPM location that
+ we have defined in the previous chapter.</para>
+ <figure float="0">
+ <title>Core jBPM Location Specifying</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour_9.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Clicking on <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis> results in the project being generated. The wizard creates four source
+ folders: one for the processes (<emphasis>
+ <property moreinfo="none">src/main/jpdl</property>
+ </emphasis>), one for the java sources (<emphasis>
+ <property moreinfo="none">src/main/java</property>
+ </emphasis>), one for the unit tests (<emphasis>
+ <property moreinfo="none">src/test/java</property>
+ </emphasis>) and one for the resources such as the jbpm.properties and the
+ hibernate.properties files (<emphasis>
+ <property moreinfo="none">src/main/config</property>
+ </emphasis>). In addition a classpath container with all the core jBPM libraries is
+ added to the project</para>
+ <figure float="0">
+ <title>Layout of the Process Project</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour_3.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Looking inside the different source folders will reveal a number of other artifacts
+ that were generated, but we will leave these untouched for the moment. Instead, we will
+ look at another wizard that enables us to create an empty process definition.</para>
+ </section>
+ <section id="creating_an_empty_process_definition">
+ <?dbhtml filename="creating_an_empty_process_definition.html"?>
+ <title>Creating an Empty Process Definition</title>
+ <para>Now when the project is set up, we can use a Creation wizard to create an empty
+ process definition. Bring up the <emphasis>
+ <property moreinfo="none">New</property>
+ </emphasis> wizard by clicking the <emphasis>
+ <property moreinfo="none">File > New > Other...</property>
+ </emphasis> menu item. The wizard opens on the <emphasis>
+ <property moreinfo="none">Select Wizard</property>
+ </emphasis> page.</para>
+ <figure float="0">
+ <title>The Select Wizard Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour_4.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Selecting the <emphasis>
+ <property moreinfo="none">JBoss jBPM</property>
+ </emphasis> category, then the <emphasis>
+ <property moreinfo="none">Process Definition</property>
+ </emphasis> item and clicking on the <emphasis>
+ <property moreinfo="none">Next</property>
+ </emphasis> button brings us to the <emphasis>
+ <property moreinfo="none">Create Process Definition</property>
+ </emphasis> page.</para>
+ <figure float="0">
+ <title>The Create New Process Defining Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour_5.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>We choose <emphasis>
+ <property moreinfo="none">hello</property>
+ </emphasis> as the name of the process archive file. Click on the <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis> button to end the wizard and open the process definition editor.</para>
+ <figure float="0">
+ <title>The Process Definition Editor</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour_6.png" scale="60"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+
+ <para>You can see in the Package Explorer that creating a process definition involves
+ creating a folder with the name of the process definition and populating this folder
+ with two .xml files : <emphasis>
+ <property moreinfo="none">gpd.xml</property>
+ </emphasis> and <emphasis>
+ <property moreinfo="none">processdefinition.xml</property>. </emphasis></para>
+ <para>The <emphasis>
+ <property moreinfo="none">gpd.xml</property>
+ </emphasis> contains the graphical information used by the process definition editor.
+ The <emphasis>
+ <property moreinfo="none">processdefinition.xml</property>
+ </emphasis> file contains the actual process definition info without the graphical
+ rendering info. At present, the GPD assumes that these two files are siblings. More
+ sophisticated configuration will be supported later.</para>
+
+ <section id="minimal_process_definition">
+ <?dbhtml filename="minimal_process_definition.html"?>
+ <title>A Minimal Process Definition</title>
+ <para>Now we are ready to create a very simple process definition consisting of a begin
+ state, an intermediate state and an end state.</para>
+ <para>To make the configuration of actions much easier it's better to use the
+ jPDL perspective. It provides the tabbed Properties Editor which allows to configure
+ all the relevant properties of the current selected item. </para>
+
+ <section id="adding_the_nodes">
+ <?dbhtml filename="adding_the_nodes.html"?>
+ <title>Adding the Nodes</title>
+ <para>At first select respectively <emphasis>
+ <property moreinfo="none">Start</property>, </emphasis>
+ <emphasis>
+ <property moreinfo="none">State</property>
+ </emphasis> and <emphasis>
+ <property moreinfo="none">End</property>
+ </emphasis> on the tools palette and click on the canvas to add these nodes to
+ the process definition. The result should look similar to this:</para>
+ <figure float="0">
+ <title>A Simple Process With Three Nodes</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour_7.png" scale="60"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="adding_transitions">
+ <?dbhtml filename="adding_transitions.html"?>
+ <title>Adding Transitions</title>
+ <para>Then, we will connect the nodes with transitions. To do that select the <emphasis>
+ <property moreinfo="none">Transition</property>
+ </emphasis> tool in the tools palette and click on the <emphasis>
+ <property moreinfo="none">Start</property>
+ </emphasis> node, then move to the <emphasis>
+ <property moreinfo="none">State</property>
+ </emphasis> node and click again to see the transition being drawn. Perform the
+ same steps to create a transition from the <emphasis>
+ <property moreinfo="none">State</property>
+ </emphasis> node to the <emphasis>
+ <property moreinfo="none">End</property>
+ </emphasis> node. The result will look like:</para>
+ <figure float="0">
+ <title>A Simple Process With Transitions</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/guided_tour_jboss_jbpmgpd/guided_tour_8.png" scale="60"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Now, when you've got background knowledge of simple project creation,
+ let's move to more advanced tools.</para>
+ </section>
+ </section>
+ </section>
+
+</chapter>
+
+
+<chapter id="the_views" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/jbpm/docs/reference/en/modules/the_views.xml" xreflabel="the_views">
+ <?dbhtml filename="the_views.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>jBPM</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>The views</title>
+
+ <para>Here, it will be explained how to work with views and editors provided by JBDS.</para>
+ <para>The views are used for representation and navigation the resources you are working on at
+ the moment. One of the advantages of all the views is that all modifications made in the
+ current active file are immediately displayed in them. Let’s get acquainted more closely
+ with those that the <property moreinfo="none">jPDL perspective</property> provides. </para>
+
+ <figure float="0">
+ <title>The jPDL Perspective Views and Editors</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_0.png" scale="80"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>As you can see in the picture above, the <property moreinfo="none">jPDL perspective</property> contains a
+ complete set of functionality that's necessary for working on the jBPM project.</para>
+
+ <section id="the_outline_view">
+ <?dbhtml filename="the_outline_view.html"?>
+ <title>The Outline View</title>
+ <para>To have a way to quickly see an outline of the process use the <emphasis>
+ <property moreinfo="none">Outline view</property>
+ </emphasis> that is presented as the classical tree. If it is not visible select <emphasis>
+ <property moreinfo="none">Window > Show view > Outline</property>. </emphasis></para>
+
+ <figure float="0">
+ <title>The Overview View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+
+ <section id="the_overview">
+ <?dbhtml filename="the_outline_view.html"?>
+ <title>The Overview</title>
+ <para>The main advantage of this view is that it gives visual representation of the whole
+ current developing process. Besides, the <emphasis>
+ <property moreinfo="none">Overview</property>
+ </emphasis> comes as a scrollable thumbnail which enables a better navigation of the
+ process structure if it's too large.</para>
+
+ <figure float="0">
+ <title>The Overview</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+
+ <section id="the_properties_view">
+ <?dbhtml filename="the_properties_view.html"?>
+ <title>The Properties View</title>
+ <para> Here, we dwell on the JBDS <property moreinfo="none">Properties view</property>.</para>
+ <para>Notice if it's not visible you can access it by navigating <emphasis>
+ <property moreinfo="none">Window > Show view > Properties</property>. </emphasis></para>
+ <para>The view shows the relevant properties of the selected item in the tabbed form. Every
+ item has its own set of properties, which can be directly editable in the Properties
+ view or by brining up the context menu.</para>
+
+ <figure float="0">
+ <title>The Properties View of selected Transition</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_3.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>For example, on the picture above the Properties view displays all the properties for
+ a selected transition. Its name has been changed to <emphasis>
+ <property moreinfo="none">to_auction</property>. </emphasis> We've done it directly in
+ active General tab of the view. The same way let's change the name for the
+ second transition to <emphasis>
+ <property moreinfo="none">to_end</property>. </emphasis></para>
+ <para>If no one item is selected, the view represents the properties of the whole process
+ definition. </para>
+
+ <figure float="0">
+ <title>The Properties View of Process Definition</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_4.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>In this case, it contains six tabs. The first one is the <emphasis>
+ <property moreinfo="none">General</property>.</emphasis> It allows to specify a process name and add
+ necessary description. To illustrate let's change the process definition name
+ to <emphasis>
+ <property moreinfo="none">jbay</property>. </emphasis></para>
+ </section>
+
+ <section id="jbpm_gpd_editor">
+ <?dbhtml filename="direct_editing.html"?>
+ <title>The jBPM Graphical Process Designer editor.</title>
+ <para>The <property moreinfo="none">jBPM GPD editor</property> includes four modes: Diagram, Deployment,
+ Design and Source, which are available as switchable tabs at the bottom of the editor.
+ Let's dwell on each of them.</para>
+
+ <section id="the_diagram_mode">
+ <title>The Diagram mode</title>
+ <para> In this mode we define the process in the form of a diagram by means of tools
+ provided on the left-hand side of the jBPM GPD. </para>
+
+ <figure float="0">
+ <title>The Diagram mode</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_5.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Besides, some properties can be directly edited in the <property moreinfo="none">Diagram
+ mode</property> of the graphical editor. One example of this is the <emphasis>
+ <property moreinfo="none">name</property>
+ </emphasis> property of nodes. You can edit this directly by selecting the node of
+ which you want to change the name and then click once inside this node. This enables
+ an editor in the node. We change the name of the node to <emphasis>
+ <property moreinfo="none">auction</property>. </emphasis></para>
+ </section>
+
+ <section id="source_mode">
+ <?dbhtml filename="the_source_view.html"?>
+ <title>The Source Mode</title>
+ <para>Now, that we have defined a simple process definition, we can have a look at the
+ XML that is being generated under the covers. To see this XML click on the Source
+ tab of the graphical process designer editor.</para>
+
+ <figure float="0">
+ <title>The Source Mode</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_6.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>The <property moreinfo="none">Source mode</property> enables to easily manipulate our XML. That is
+ manually inserting and editing necessary elements or attributes. In addition, here
+ you can take advantage of content assist.</para>
+ </section>
+
+ <section id="design_mode">
+ <?dbhtml filename="the_design_view.html"?>
+ <title>The Design Mode</title>
+ <para>One more way to edit your file is to use <property moreinfo="none">Design mode</property>. You can
+ see it in the next picture:</para>
+ <figure float="0">
+ <title>The Design Mode</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_7.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>As you can see above, this mode looks like a table in the first column of which
+ the process structure is performed. Here, you can also insert, remove and edit
+ elements or attributes, moreover add comments and instructions. Their values can be
+ directly edited in the second column of the Design mode table.</para>
+ <para>For instance, let’s add a comment on the second transition. For that, you should
+ bring up the context menu for it and choose <emphasis>
+ <property moreinfo="none">Add Before > Comment</property>. </emphasis></para>
+
+ <figure float="0">
+ <title>Adding a Comment</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_8.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Then, we can put the text <emphasis>This transition leads to the end
+ state</emphasis> in the right column as its value.</para>
+
+ <figure float="0">
+ <title>Comment is added</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_9.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ </section>
+
+ <section id="deployment_mode">
+ <?dbhtml filename="the_deployment_view.html"?>
+ <title>The Deployment Mode</title>
+ <para>Finally, to adjust the deployment settings of the project you should switch on to
+ the tab that opens the <property moreinfo="none">Deployment mode</property>. On the picture below
+ the <property moreinfo="none">Deployment mode</property> is performed with default settings. Here,
+ you can easily modify them or, if the settings won't match your needs, to
+ reset defaults. </para>
+ <figure float="0">
+ <title>The Deployment Mode</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_10.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The button <emphasis>
+ <property moreinfo="none">Test Connections</property>
+ </emphasis> is necessary to make sure whether all your settings are valid before
+ deploying the process.</para>
+ <para>Now that we've seen how to work with <property moreinfo="none">jPDL
+ perspective</property>, let's pass on to the project testing.</para>
+ </section>
+ </section>
+</chapter>
+
+<chapter id="Test_Drive_Proc_Development" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/jbpm/docs/reference/en/modules/Test_Drive_Proc.xml" xreflabel="Test_Drive_Proc_Development">
+ <?dbhtml filename="Test_Drive_Proc_Development.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>jBPM</keyword>
+ <keyword></keyword>
+ <keyword></keyword>
+ <keyword></keyword>
+ <keyword></keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Test Driven Process Development</title>
+
+ <para> One of the most important advantages of JBoss jBPM's lightweight approach to BPM
+ and workflow management is that developers can easily leverage their usual programming
+ skills and techniques. One of these well-known techniques is Unit Testing and Test Driven
+ Development. </para>
+ <para>In this chapter we will show how developers, making use of the JBoss jBPM GPD, can use a
+ technique we have baptized <property moreinfo="none">Test Driven Process Development</property> to create
+ process definitions and test their correctness. </para>
+
+ <para> When creating the <emphasis>
+ <property moreinfo="none">HellojBPM</property>
+ </emphasis> project the Project Creation wizard has already put in place all the library
+ requirements we need to start writing the jBPM unit tests. They are contained in the jBPM
+ Library container and the most important of them is the <emphasis>
+ <property moreinfo="none">.jar</property>
+ </emphasis> file containing the core jBPM classes. While working on the project you could
+ find them all in the <property moreinfo="none">Package Explorer</property>.</para>
+
+ <figure float="0">
+ <title>The jBPM Libraries</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Test_Drive_Proc/test_driv_proc_1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>It must be noted that it is possible to change the location of the core jBPM installation
+ by changing the preference settings. More on this <link linkend="change_core_jbpm_inst">see
+ later</link> in this book.</para>
+
+ <para> With that extra knowledge on the project settings, you can create your first test. To do
+ this, we create the <emphasis>
+ <property moreinfo="none">com.jbay</property>
+ </emphasis> package in the <emphasis>
+ <property moreinfo="none">test/java</property>
+ </emphasis> source folder. Then we bring up the context menu on this package and select <emphasis>
+ <property moreinfo="none">New > Other...</property>
+ </emphasis></para>
+
+ <figure float="0">
+ <title>Call the JUnit Test Case Creation wizard</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Test_Drive_Proc/test_driv_proc_2.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para> And then <emphasis>
+ <property moreinfo="none">Java > JUnit > JUnit Test Case</property>
+ </emphasis> to call the specialized JUnite Test case creation wizard.</para>
+ <figure float="0">
+ <title>Call the JUnit Test Case Creation wizard</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Test_Drive_Proc/test_driv_proc_3.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The wizard looks as follows:</para>
+
+ <figure float="0">
+ <title>Create Test Dialog</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Test_Drive_Proc/test_driv_proc_4.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>By default JUnite 3 version of testing framework is selected. Of course, you can choose
+ new advanced JUnit 4 version. In this case you'll be prompted to add new JUnit
+ Library to your build path. To add it automatically just click on the appropriate link. In
+ the <emphasis>
+ <property moreinfo="none">Class under test</property>
+ </emphasis> section you can specify the class to test.</para>
+
+ <figure float="0">
+ <title>A First Test Scenario</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Test_Drive_Proc/test_driv_proc_5.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Then, we call the test class <emphasis>
+ <property moreinfo="none">HelloTest</property>
+ </emphasis> and press <emphasis>
+ <property moreinfo="none">Finish</property>
+ </emphasis> button to complete.</para>
+
+ <para> Next, we should write a simple test scenario as shown on the next figure. Let's
+ study the code of this test case. </para>
+
+ <figure float="0" id="hello_test">
+ <title>A First Test Scenario</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Test_Drive_Proc/test_driv_proc_6.png" scale="75"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>In the first line of the method, a jBPM process archive object is created. We use a
+ constructor accepting the filename of the archive. In our case it is the <emphasis>
+ <property moreinfo="none">hello</property>
+ </emphasis> file we created earlier and which lives in the <emphasis>
+ <property moreinfo="none">src/main/jpdl</property>
+ </emphasis> folder of our project. After asserting that this object is really created, we
+ extract a process definition object from it. This object is fed to the constructor of a
+ process instance object. We have a process instance object, but this process is not yet
+ started, so we can safely assert that its root token still resides in the start node. After
+ signalling the token will move to the next state and the process will be in the <emphasis>
+ <property moreinfo="none">auction</property>
+ </emphasis> state. Finally another signal will end the process. </para>
+
+
+ <para> After writing this test we can check whether it works as expected by running it .</para>
+
+ <figure float="0">
+ <title>Running the Process Test</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Test_Drive_Proc/test_driv_proc_7.png" scale="75"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>All went well as we have a green light:</para>
+
+ <figure float="0">
+ <title>Successful Test Run</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Test_Drive_Proc/test_driv_proc_8.png" scale="75"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para> Of course, this simple scenario was not very interesting, but the purpose of it was to
+ show how you can reuse your development skills in a very straightforward way when doing
+ process development. To see how more interesting processes and process test
+ scenario's can be developed, we suggest you to read the <ulink url="http://docs.jboss.com/jbpm/v3/userguide/">JBoss jBPM User Guide</ulink> and to
+ study the API reference. You can find it in the jBPM download folder. (To get started we
+ downloaded jbpm-jpdl-3.2.2 in <link linkend="jboss_jbpm_runtime_installation">the second
+ chapter</link>. You should just remember where you extracted it.) All we've mentioned are in the 'javadoc- *' subfolders of the 'doc' folder.
+ Moreover, some more examples will be given later in this book.</para>
+
+</chapter>
+
+
+<chapter id="The_JBoss_jBPM_Int_Mech" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/jbpm/docs/reference/en/modules/The_JBoss_jBPM_Int_Mech.xml" xreflabel="The_JBoss_jBPM_Int_Mech">
+ <?dbhtml filename="The_JBoss_jBPM_Int_Mech.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>jBPM</keyword>
+ <keyword></keyword>
+ <keyword></keyword>
+ <keyword></keyword>
+ <keyword></keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Actions : The JBoss jBPM Integration Mechanism</title>
+
+ <para> In this chapter we will show how to do software integration with <property moreinfo="none">JBoss
+ jBPM</property>. The standard mechanism to implement this is to wrap the functionality you
+ want to integrate in a class that implements the <emphasis>
+ <property moreinfo="none">ActionHandler</property>
+ </emphasis> interface. In order to demonstrate it let's specify Hello World action for our
+ process.</para>
+
+ <section>
+ <title>Creating a Hello World Action</title>
+
+ <para>Each Hello World process should integrate one or more Hello World actions, so this is
+ what we will be doing. We can integrate custom code at different points in the process
+ definition. To do this we have to specify an action handler, represented by an
+ implementation of the <emphasis>
+ <property moreinfo="none">ActionHandler</property>
+ </emphasis> interface, and attach this piece of code to a particular event. These events
+ are amongst others, going over a transition, leaving or entering nodes, after and before
+ signalling. </para>
+
+ <para> To make things a little bit more concrete, let's create a new class called <emphasis>
+ <property moreinfo="none">HelloActionHandler</property>.
+ </emphasis> For that firstly we'll create a new package <emphasis>
+ <property moreinfo="none">com.jbay.action</property>
+ </emphasis> in the <emphasis>
+ <property moreinfo="none">src/java/main</property>
+ </emphasis> folder of our project. Then, we should call New Class Creation wizard as
+ usual by right-clicking and navigating <emphasis>
+ <property moreinfo="none">New > Class</property>.
+ </emphasis> </para>
+
+ <figure float="0">
+ <title>Creating HelloActionHendler Class</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Notice that two first gaps have been filled automatically. Here, instead of <emphasis>
+ <property moreinfo="none">Package</property>
+ </emphasis> option <emphasis>
+ <property moreinfo="none">Enclose type</property>
+ </emphasis> option can be selected where a type in which to enclose a new class should
+ be specified.</para>
+
+ <para>In our case, we leave everything as it is, just type <emphasis>
+ <property moreinfo="none">HelloActionHandler</property>
+ </emphasis> as a name of new class and add <emphasis>
+ <property moreinfo="none">org.jbpm.graph.ActionHendler</property>
+ </emphasis> interface as it's shown in the picture above.</para>
+
+ <para>Thus, our <emphasis>
+ <property moreinfo="none">HelloActionHandler</property>
+ </emphasis> implements the <emphasis>
+ <property moreinfo="none">ActionHandler</property>
+ </emphasis> interface including the <emphasis>
+ <property moreinfo="none">execute</property>
+ </emphasis> method as shown in the next figure. Here, we add a variable named <emphasis>
+ <property moreinfo="none">greeting</property>
+ </emphasis> to the collection of process variables and put a message in it :
+ <emphasis>"Hello from ActionHandler"</emphasis>. </para>
+
+ <figure float="0">
+ <title>A Simple Hello Action</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_2.png" scale="75"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Now, as we have <emphasis>
+ <property moreinfo="none">HelloActionHandler</property>
+ </emphasis> class defined, let's explore how we can handle it.</para>
+ </section>
+
+ <section>
+ <title>Integrating the Hello World Action</title>
+
+ <para>The main purpose of this chapter is to provide you with the steps associating our
+ Hello World action with a particular event and test the correctness of our actions as
+ well.</para>
+
+ <para> As good Testcity citizens we will first create a Unit Test that proves the behaviour
+ we want to achieve by adding the <emphasis>
+ <property moreinfo="none">ActionHandler</property>
+ </emphasis> to the process. So we implement another test.</para>
+
+ <para>At first, let's return to the
+ code we already saw <link linkend="hello_test">in the previous chapter</link> and add new test method <emphasis>
+ <property moreinfo="none">testActionHendler</property></emphasis> to it. </para>
+
+ <figure float="0">
+ <title>Create the Hello Action Test</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_3.png" scale="75"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>We assert
+ that no variable called <emphasis>
+ <property moreinfo="none">greeting</property>
+ </emphasis> exist. Then we give the process a signal to move it to the auction state. We
+ want to associate the execution of the action with the event of going over the
+ transition from the start state to the auction state. So after the signal, the process
+ should be in the auction state as in the previous scenario. But moreover, the <emphasis>
+ <property moreinfo="none">greeting</property>
+ </emphasis> variable should exist and contain the string <emphasis>"Hello from
+ ActionHandler"</emphasis>. That's what we assert in the last lines of the test
+ method.</para>
+
+
+
+ <para> Running the tests now results in a failure. The point is that we did not associate
+ the action with any particular event in the process definition, so the process variable
+ did not get set. </para>
+
+ <figure float="0">
+ <title>Test Results Before Integration</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_4.png" scale="75"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para> Let's do something about it and add an action to the first transition of our
+ sample process. To do this you can use the Actions tab in the Properties Editor that is
+ under the graphical canvas. Bring up the popup menu of the action element container and
+ chose New Action as it's shown on the figure below. The other way to add an action
+ to the transition is simply to use the dropdown menu that is available under the action
+ icon in the right upper corner of the Properties View.</para>
+
+ <figure float="0">
+ <title>Adding an Action to a Transition</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_5.png" scale="80"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>After adding the action a tabbed view with three pages will appear.</para>
+
+ <figure float="0">
+ <title>Configuration Dialog for an Action</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_6.png" scale="80"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The first of these three pages allows you to give the Action a name. The last page
+ contains some advanced attributes such as whether the Action is asynchronous. The
+ Details page is the most important. It allows to choose and configure the actual action
+ handler implementation. </para>
+
+ <figure float="0">
+ <title>The Details page of an Action Configuration Dialog</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_7.png" scale="80"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+
+ <para>Clicking on the <emphasis>
+ <property moreinfo="none">Search...</property>
+ </emphasis> button brings us to a Choose Class dialog.</para>
+
+
+ <figure float="0">
+ <title>The Choose Action Handler Dialog</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_8.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+
+ <para> We choose our previously created 'HelloActionHandler' class and
+ push the <property moreinfo="none">OK</property> button. After the selection of the action handler for
+ the action, we can run the test and observe it gives us a green light.</para>
+
+ <figure float="0">
+ <title>Test Results</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/The_JBoss_jBPM_Int_Mech/jboss_jbpm_int_mech_9.png" scale="70"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>There we are. The above objective has been achieved.</para>
+ </section>
+
+ <section>
+ <title> Integration Points</title>
+
+ <para> The different integration points in a process definition are thoroughly documented in
+ the <ulink url="http://docs.jboss.com/jbpm/v3/userguide/">JBoss jBPM User Guide</ulink>. Instance nodes can contain many action
+ elements. Each of these will appear in the Action element list of the Actions tab. But
+ each Action also has a properties view of itself. You can navigate to this view by
+ selecting the added Action in the outline view. </para>
+
+ </section>
+
+</chapter>
+
+
+<chapter id="Quick_Howto_Guide" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/jbpm/docs/reference/en/modules/Quick_Howto_Guide.xml" xreflabel="Quick_Howto_Guide">
+ <?dbhtml filename="Quick_Howto_Guide.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>jBPM</keyword>
+ <keyword></keyword>
+ <keyword></keyword>
+ <keyword></keyword>
+ <keyword></keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Quick Howto Guide</title>
+
+ <para>This chapter contains additional information related to the <property moreinfo="none">JBoss
+ jBPM</property>.</para>
+
+ <section id="change_core_jbpm_inst">
+ <title>Change the Default Core jBPM Installation</title>
+
+ <para> You can change the default <property moreinfo="none">jBPM</property> installation by means of the
+ Eclipse preference mechanism. Open the Preferences dialog by selecting <emphasis>
+ <property moreinfo="none">Window > Preferences</property>
+ </emphasis> and select the <emphasis>
+ <property moreinfo="none">JBoss jBPM > Runtime Location</property>
+ </emphasis> category. Using this page you can add multiple <property moreinfo="none">jBPM</property>
+ installation locations and change the default one. The default installation is used for
+ the classpath settings when creating a new Process Project. Changing the preferences has
+ no influence on already created projects. Getting rid of a <property moreinfo="none">jBPM</property>
+ installation that's being referenced by a project however will cause the
+ classpath to contain errors. </para>
+
+
+ <figure float="0">
+ <title>The jBPM Preferences Page</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_1.png"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+
+ <section>
+ <title>Configuring Task Nodes</title>
+
+ <para>Here, we'll examine how you can configure the Task nodes in jBPM jPDL GPD.</para>
+
+ <para> You can add Tasks to Task nodes and then configure them in a similar manner as the
+ Action configuration mechanism. Let's consider the process definition similar
+ to the previous one that contains three nodes: Start state, Task node and End state. The
+ <property moreinfo="none">Properties view</property> for selected Task node includes several tabs. </para>
+
+ <figure float="0">
+ <title>The Properties View of the selected Task Node</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_2.png" scale="75"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>We should choose the Task tab and then bring up the context menu or click the button
+ in the top right corner of the view to add a Task to our Task node.</para>
+
+ <figure float="0">
+ <title>Adding a Task to the Task Node</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_3.png" scale="80"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Every added Task has its own configuration possibilities. You can access them through
+ the <property moreinfo="none">Properties view</property> as well.</para>
+
+ <figure float="0">
+ <title>The Task properties</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_4.png" scale="80"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The <property moreinfo="none">General page</property> is a place where you can specify the name of a
+ Task and its description. For instance, let it be <emphasis>
+ <property moreinfo="none">approve oder</property>
+ </emphasis> with appropriate description that you can see in the figure below.</para>
+
+ <figure float="0">
+ <title>The Task General Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_5.png" scale="80"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Now, look at <property moreinfo="none">Details page</property>. First, you should specify the due date
+ that is a mandatory property for the Task. The due date is the date on which the task
+ should be accomplished. Here you can also set a Task priority as well as signalling,
+ notifying or blocking. The <emphasis>
+ <property moreinfo="none">Blocking</property>
+ </emphasis> attribute indicates that the process will not be able to continue if this
+ task is still unaccomplished. The <emphasis>
+ <property moreinfo="none">Generate Form...</property>
+ </emphasis> button is for creating a simple task form that can be rendered by the jBPM
+ console.</para>
+
+ <figure float="0">
+ <title>The Task Details Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_6.png" scale="80"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>For our example, we specify the due date as 2 business days, choose the high priority
+ and also check the <emphasis>
+ <property moreinfo="none">Signalling</property>
+ </emphasis> and <emphasis>
+ <property moreinfo="none">Notify</property>
+ </emphasis> attributes. It means that the Task should be accomplished in 2 business days
+ and the assignee will be notified by email when the task is assigned. To specify how the
+ Task should be assigned switch on to the <property moreinfo="none">Assignment page</property>.</para>
+
+ <figure float="0">
+ <title>The Task Assignment Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_7.png" scale="80"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>On the <property moreinfo="none">Reminder page</property> you can specify whether the assignee will be reminded of the task
+ that awaits him.</para>
+
+ <figure float="0">
+ <title>The Task Reminder Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_8.png" scale="80"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>In our case, the assignee will be reminded by email after two business hours and
+ continue to get reminding every business hour after that.</para>
+ <para>In the next figure you can see our configuring generated into XML.</para>
+ <figure float="0">
+ <title>The Task Reminder Page</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/Quick_Howto_Guide/quick_howto_guide_9.png" scale="80"></imagedata>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>We hope, our guide will help you to get started with the jPDL process language and jBPM
+ workflow on the whole. Besides, for additional information you are welcome on
+ <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss forum</ulink>.</para>
+ </section>
+</chapter>
+
+
+ <!-- TODO: drools used in this section is not available for eclipse .3.3 &AddBusinessProcess; -->
+</book>
Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/the_views.xml
===================================================================
--- branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/the_views.xml (rev 0)
+++ branches/jbosstools-3.1.x/jbpm/docs/reference/en-US/the_views.xml 2010-03-03 14:04:09 UTC (rev 20610)
@@ -0,0 +1,230 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="the_views" xreflabel="the_views">
+ <?dbhtml filename="the_views.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>jBPM</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>The views</title>
+
+ <para>Here, it will be explained how to work with views and editors provided by JBDS.</para>
+ <para>The views are used for representation and navigation the resources you are working on at
+ the moment. One of the advantages of all the views is that all modifications made in the
+ current active file are immediately displayed in them. Let’s get acquainted more closely
+ with those that the <property>jPDL perspective</property> provides. </para>
+
+ <figure>
+ <title>The jPDL Perspective Views and Editors</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_0.png" scale="80"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>As you can see in the picture above, the <property>jPDL perspective</property> contains a
+ complete set of functionality that's necessary for working on the jBPM project.</para>
+
+ <section id="the_outline_view">
+ <?dbhtml filename="the_outline_view.html"?>
+ <title>The Outline View</title>
+ <para>To have a way to quickly see an outline of the process use the <emphasis>
+ <property>Outline view</property>
+ </emphasis> that is presented as the classical tree. If it is not visible select <emphasis>
+ <property>Window > Show view > Outline</property>. </emphasis></para>
+
+ <figure>
+ <title>The Overview View</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+
+ <section id="the_overview">
+ <?dbhtml filename="the_outline_view.html"?>
+ <title>The Overview</title>
+ <para>The main advantage of this view is that it gives visual representation of the whole
+ current developing process. Besides, the <emphasis>
+ <property>Overview</property>
+ </emphasis> comes as a scrollable thumbnail which enables a better navigation of the
+ process structure if it's too large.</para>
+
+ <figure>
+ <title>The Overview</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+
+ <section id="the_properties_view">
+ <?dbhtml filename="the_properties_view.html"?>
+ <title>The Properties View</title>
+ <para> Here, we dwell on the JBDS <property>Properties view</property>.</para>
+ <para>Notice if it's not visible you can access it by navigating <emphasis>
+ <property>Window > Show view > Properties</property>. </emphasis></para>
+ <para>The view shows the relevant properties of the selected item in the tabbed form. Every
+ item has its own set of properties, which can be directly editable in the Properties
+ view or by brining up the context menu.</para>
+
+ <figure>
+ <title>The Properties View of selected Transition</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_3.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>For example, on the picture above the Properties view displays all the properties for
+ a selected transition. Its name has been changed to <emphasis>
+ <property>to_auction</property>. </emphasis> We've done it directly in
+ active General tab of the view. The same way let's change the name for the
+ second transition to <emphasis>
+ <property>to_end</property>. </emphasis></para>
+ <para>If no one item is selected, the view represents the properties of the whole process
+ definition. </para>
+
+ <figure>
+ <title>The Properties View of Process Definition</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_4.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>In this case, it contains six tabs. The first one is the <emphasis>
+ <property>General</property>.</emphasis> It allows to specify a process name and add
+ necessary description. To illustrate let's change the process definition name
+ to <emphasis>
+ <property>jbay</property>. </emphasis></para>
+ </section>
+
+ <section id="jbpm_gpd_editor">
+ <?dbhtml filename="direct_editing.html"?>
+ <title>The jBPM Graphical Process Designer editor.</title>
+ <para>The <property>jBPM GPD editor</property> includes four modes: Diagram, Deployment,
+ Design and Source, which are available as switchable tabs at the bottom of the editor.
+ Let's dwell on each of them.</para>
+
+ <section id="the_diagram_mode">
+ <title>The Diagram mode</title>
+ <para> In this mode we define the process in the form of a diagram by means of tools
+ provided on the left-hand side of the jBPM GPD. </para>
+
+ <figure>
+ <title>The Diagram mode</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_5.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Besides, some properties can be directly edited in the <property>Diagram
+ mode</property> of the graphical editor. One example of this is the <emphasis>
+ <property>name</property>
+ </emphasis> property of nodes. You can edit this directly by selecting the node of
+ which you want to change the name and then click once inside this node. This enables
+ an editor in the node. We change the name of the node to <emphasis>
+ <property>auction</property>. </emphasis></para>
+ </section>
+
+ <section id="source_mode">
+ <?dbhtml filename="the_source_view.html"?>
+ <title>The Source Mode</title>
+ <para>Now, that we have defined a simple process definition, we can have a look at the
+ XML that is being generated under the covers. To see this XML click on the Source
+ tab of the graphical process designer editor.</para>
+
+ <figure>
+ <title>The Source Mode</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_6.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>The <property>Source mode</property> enables to easily manipulate our XML. That is
+ manually inserting and editing necessary elements or attributes. In addition, here
+ you can take advantage of content assist.</para>
+ </section>
+
+ <section id="design_mode">
+ <?dbhtml filename="the_design_view.html"?>
+ <title>The Design Mode</title>
+ <para>One more way to edit your file is to use <property>Design mode</property>. You can
+ see it in the next picture:</para>
+ <figure>
+ <title>The Design Mode</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_7.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>As you can see above, this mode looks like a table in the first column of which
+ the process structure is performed. Here, you can also insert, remove and edit
+ elements or attributes, moreover add comments and instructions. Their values can be
+ directly edited in the second column of the Design mode table.</para>
+ <para>For instance, let’s add a comment on the second transition. For that, you should
+ bring up the context menu for it and choose <emphasis>
+ <property>Add Before > Comment</property>. </emphasis></para>
+
+ <figure>
+ <title>Adding a Comment</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_8.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Then, we can put the text <emphasis>This transition leads to the end
+ state</emphasis> in the right column as its value.</para>
+
+ <figure>
+ <title>Comment is added</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_9.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ </section>
+
+ <section id="deployment_mode">
+ <?dbhtml filename="the_deployment_view.html"?>
+ <title>The Deployment Mode</title>
+ <para>Finally, to adjust the deployment settings of the project you should switch on to
+ the tab that opens the <property>Deployment mode</property>. On the picture below
+ the <property>Deployment mode</property> is performed with default settings. Here,
+ you can easily modify them or, if the settings won't match your needs, to
+ reset defaults. </para>
+ <figure>
+ <title>The Deployment Mode</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/the_views/the_views_10.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The button <emphasis>
+ <property>Test Connections</property>
+ </emphasis> is necessary to make sure whether all your settings are valid before
+ deploying the process.</para>
+ <para>Now that we've seen how to work with <property>jPDL
+ perspective</property>, let's pass on to the project testing.</para>
+ </section>
+ </section>
+</chapter>
14 years, 2 months
- 1
- 0