March 2010 - jbosstools-commits - Jboss List Archives

JBoss Tools SVN: r20609 - branches/jbosstools-3.1.x/jbpm/docs/reference/en.

by jbosstools-commits＠lists.jboss.org

Author: ochikvina Date: 2010-03-03 08:25:16 -0500 (Wed, 03 Mar 2010) New Revision: 20609 Removed: branches/jbosstools-3.1.x/jbpm/docs/reference/en/modules/ 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
0 / 0

JBoss Tools SVN: r20608 - in trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test: resources and 40 other directories.

by jbosstools-commits＠lists.jboss.org

Author: scabanovich Date: 2010-03-03 08:23:10 -0500 (Wed, 03 Mar 2010) New Revision: 20608 Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.classpath trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.project trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/.jsdtscope trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.jdt.core.prefs trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.common.component trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.common.project.facet.core.xml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.jsdt.ui.superType.container trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.jsdt.ui.superType.name trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/JavaSource/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts-context.css trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts.css trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids-context.css trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids.css trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/layout.css trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/page.css trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset-context.css trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset-fonts-grids.css trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset.css trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/simple.css trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/MANIFEST.MF trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/richfaces-demo/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/richfaces-demo/pom.properties trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/richfaces-demo/pom.xml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/common/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/common/UserBean.class trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/function/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/function/FunctionBean.class trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/mediaOutput/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/mediaOutput/MediaBean.class trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/mediaOutput/MediaData.class trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/mediaOutput/text.swf trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/outputPanel/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/outputPanel/OutputPanelBean.class trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/push/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/push/Choice.class trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/classes/org/richfaces/demo/push/ChoicesBean.class trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/faces-config.xml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/commons-beanutils-1.7.0.jar trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/commons-logging-1.1.1.jar trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/core-ui-4.0.0.ALPHA1.jar trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jboss-common-core-2.2.10.GA.jar trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jboss-logging-spi-2.0.5.GA.jar trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jbosscache-core-3.1.0.GA.jar trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jgroups-2.6.7.GA.jar trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jsf-api-2.0.0-SNAPSHOT.jar trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jsf-impl-2.0.0-SNAPSHOT.jar trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/jta-1.1.jar trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/log4j-1.2.14.jar trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/richfaces-api-4.0.0.ALPHA1.jar trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/richfaces-impl-4.0.0.ALPHA1.jar trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/slf4j-api-1.5.8.jar trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/lib/slf4j-log4j12-1.5.8.jar trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/web.xml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/images/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/images/ai.gif trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/images/richfaces-banner.png trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/index.jsp trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/message.css trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/messages.css trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/page.css trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/panel.css trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/img/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/img/footer_background.png trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/img/header_background.png trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/img/panel_header.png trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/message.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/messages.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/page.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/panel.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax/ajax.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/button/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/button/usage.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandButton.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandLink.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction/usage.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/link/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/link/usage.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log/usage.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/flashUsage.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/imgUsage.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/compositemessages.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/usage.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push/usage.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/referencedusage.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/usage.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/viewusage.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/script/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/script/swfobject.js trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/includes/ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/includes/navigation.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/main.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/welcome.xhtml trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE5920Test.java Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/plugin.xml trunk/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 Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/plugin.xml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/plugin.xml 2010-03-03 13:22:05 UTC (rev 20607) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/plugin.xml 2010-03-03 13:23:10 UTC (rev 20608) @@ -30,6 +30,9 @@ <testProject name="JBIDE5460TestProject" path="resources/JBIDE5460TestProject"/> + <testProject + name="TestWith2URLPatterns" + path="resources/TestWith2URLPatterns"/> </extension> </plugin> Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.classpath =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.classpath (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.classpath 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.classpath ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.project =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.project (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.project 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.project ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/.jsdtscope =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/.jsdtscope (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/.jsdtscope 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.jdt.core.prefs =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.jdt.core.prefs (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.jdt.core.prefs 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.jdt.core.prefs ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.common.component =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.common.component (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.common.component 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.common.project.facet.core.xml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.common.project.facet.core.xml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.common.project.facet.core.xml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.jsdt.ui.superType.container =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.jsdt.ui.superType.container (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.jsdt.ui.superType.container 2010-03-03 13:23:10 UTC (rev 20608) @@ -0,0 +1 @@ +org.eclipse.wst.jsdt.launching.baseBrowserLibrary \ No newline at end of file Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.jsdt.ui.superType.name =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.jsdt.ui.superType.name (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/.settings/org.eclipse.wst.jsdt.ui.superType.name 2010-03-03 13:23:10 UTC (rev 20608) @@ -0,0 +1 @@ +Window \ No newline at end of file Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts-context.css =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts-context.css (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts-context.css 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts-context.css ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts.css =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts.css (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts.css 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/fonts.css ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids-context.css =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids-context.css (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids-context.css 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids-context.css ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids.css =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids.css (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids.css 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/grids.css ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/layout.css =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/layout.css (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/layout.css 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/layout.css ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/page.css =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/page.css (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/page.css 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/page.css ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset-context.css =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset-context.css (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset-context.css 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset-context.css ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset-fonts-grids.css =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset-fonts-grids.css (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset-fonts-grids.css 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset.css =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset.css (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset.css 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/reset.css ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/simple.css =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/simple.css (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/simple.css 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/CSS/yuiLayouts/simple.css ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/MANIFEST.MF =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/MANIFEST.MF (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/MANIFEST.MF 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/MANIFEST.MF ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/richfaces-demo/pom.properties =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/richfaces-demo/pom.properties (rev 0) +++ trunk/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 13:23:10 UTC (rev 20608) @@ -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: trunk/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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/richfaces-demo/pom.xml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/META-INF/maven/org.richfaces.examples/richfaces-demo/pom.xml (rev 0) +++ trunk/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 13:23:10 UTC (rev 20608) @@ -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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/faces-config.xml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/faces-config.xml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/faces-config.xml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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> +  + </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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/faces-config.xml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/web.xml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/web.xml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/web.xml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/WEB-INF/web.xml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/images/ai.gif =================================================================== (Binary files differ) Property changes on: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/images/ai.gif ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/images/richfaces-banner.png =================================================================== (Binary files differ) Property changes on: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/images/richfaces-banner.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/index.jsp =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/index.jsp (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/index.jsp 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/index.jsp ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/message.css =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/message.css (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/message.css 2010-03-03 13:23:10 UTC (rev 20608) @@ -0,0 +1,3 @@ +rich-message{ + color:red; +} \ No newline at end of file Property changes on: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/message.css ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/messages.css =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/messages.css (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/messages.css 2010-03-03 13:23:10 UTC (rev 20608) @@ -0,0 +1,3 @@ +rich-messages{ + color:red; +} \ No newline at end of file Property changes on: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/messages.css ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/page.css =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/page.css (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/page.css 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/page.css ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/panel.css =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/panel.css (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/panel.css 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/css/panel.css ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/img/footer_background.png =================================================================== (Binary files differ) Property changes on: trunk/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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/img/header_background.png =================================================================== (Binary files differ) Property changes on: trunk/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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/img/panel_header.png =================================================================== (Binary files differ) Property changes on: trunk/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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/message.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/message.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/message.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/message.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/messages.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/messages.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/messages.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/messages.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/page.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/page.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/page.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/page.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/panel.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/panel.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/panel.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/resources/rich/panel.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax/ajax.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax/ajax.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax/ajax.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax/ajax.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/ajax.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/button/usage.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/button/usage.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/button/usage.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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> +  + </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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/button/usage.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandButton.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandButton.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandButton.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandButton.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandLink.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandLink.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandLink.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/commandLink.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction/usage.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction/usage.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction/usage.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction/usage.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/jsFunction.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/link/usage.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/link/usage.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/link/usage.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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> +  + </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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/link/usage.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log/usage.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log/usage.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log/usage.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log/usage.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/log.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/flashUsage.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/flashUsage.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/flashUsage.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/flashUsage.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/imgUsage.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/imgUsage.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/imgUsage.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput/imgUsage.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/mediaOutput.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/compositemessages.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/compositemessages.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/compositemessages.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/compositemessages.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/usage.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/usage.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/usage.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel/usage.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/outputPanel.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push/usage.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push/usage.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push/usage.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push/usage.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/push.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/referencedusage.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/referencedusage.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/referencedusage.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/referencedusage.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/usage.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/usage.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/usage.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/usage.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/viewusage.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/viewusage.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/viewusage.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status/viewusage.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/richfaces/status.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/script/swfobject.js =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/script/swfobject.js (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/script/swfobject.js 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/script/swfobject.js ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/includes/navigation.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/includes/navigation.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/includes/navigation.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/includes/navigation.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/main.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/main.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/main.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/templates/main.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/welcome.xhtml =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/welcome.xhtml (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/welcome.xhtml 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/TestWith2URLPatterns/WebContent/welcome.xhtml ___________________________________________________________________ Name: svn:mime-type + text/plain Modified: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java 2010-03-03 13:22:05 UTC (rev 20607) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java 2010-03-03 13:23:10 UTC (rev 20608) @@ -66,6 +66,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.JBIDE675Test; import org.jboss.tools.jsf.vpe.jsf.test.jbide.JBIDE788Test; import org.jboss.tools.jsf.vpe.jsf.test.jbide.JBIDE924Test; @@ -114,11 +115,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); Added: trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE5920Test.java =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE5920Test.java (rev 0) +++ trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/jbide/JBIDE5920Test.java 2010-03-03 13:23:10 UTC (rev 20608) @@ -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: trunk/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
0 / 0

JBoss Tools SVN: r20607 - branches/jbosstools-3.1.x/jbpm/docs/reference/en.

by jbosstools-commits＠lists.jboss.org

Author: ochikvina Date: 2010-03-03 08:22:05 -0500 (Wed, 03 Mar 2010) New Revision: 20607 Added: branches/jbosstools-3.1.x/jbpm/docs/reference/en/Author_Group.xml branches/jbosstools-3.1.x/jbpm/docs/reference/en/Book_Info.xml branches/jbosstools-3.1.x/jbpm/docs/reference/en/Introduction.xml branches/jbosstools-3.1.x/jbpm/docs/reference/en/Preface.xml branches/jbosstools-3.1.x/jbpm/docs/reference/en/Quick_Howto_Guide.xml branches/jbosstools-3.1.x/jbpm/docs/reference/en/Revision_History.xml branches/jbosstools-3.1.x/jbpm/docs/reference/en/Test_Drive_Proc.xml branches/jbosstools-3.1.x/jbpm/docs/reference/en/The_JBoss_jBPM_Int_Mech.xml branches/jbosstools-3.1.x/jbpm/docs/reference/en/guided_tour_jboss_jbpmgpd.xml branches/jbosstools-3.1.x/jbpm/docs/reference/en/jBPM_Tools_Reference_Guide.ent branches/jbosstools-3.1.x/jbpm/docs/reference/en/jBPM_Tools_Reference_Guide.xml branches/jbosstools-3.1.x/jbpm/docs/reference/en/jboss_jbpm_runtime_installation.xml branches/jbosstools-3.1.x/jbpm/docs/reference/en/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/Author_Group.xml =================================================================== --- branches/jbosstools-3.1.x/jbpm/docs/reference/en/Author_Group.xml (rev 0) +++ branches/jbosstools-3.1.x/jbpm/docs/reference/en/Author_Group.xml 2010-03-03 13:22:05 UTC (rev 20607) @@ -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/Book_Info.xml =================================================================== --- branches/jbosstools-3.1.x/jbpm/docs/reference/en/Book_Info.xml (rev 0) +++ branches/jbosstools-3.1.x/jbpm/docs/reference/en/Book_Info.xml 2010-03-03 13:22:05 UTC (rev 20607) @@ -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/Introduction.xml =================================================================== --- branches/jbosstools-3.1.x/jbpm/docs/reference/en/Introduction.xml (rev 0) +++ branches/jbosstools-3.1.x/jbpm/docs/reference/en/Introduction.xml 2010-03-03 13:22:05 UTC (rev 20607) @@ -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/Preface.xml =================================================================== --- branches/jbosstools-3.1.x/jbpm/docs/reference/en/Preface.xml (rev 0) +++ branches/jbosstools-3.1.x/jbpm/docs/reference/en/Preface.xml 2010-03-03 13:22:05 UTC (rev 20607) @@ -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/Quick_Howto_Guide.xml =================================================================== --- branches/jbosstools-3.1.x/jbpm/docs/reference/en/Quick_Howto_Guide.xml (rev 0) +++ branches/jbosstools-3.1.x/jbpm/docs/reference/en/Quick_Howto_Guide.xml 2010-03-03 13:22:05 UTC (rev 20607) @@ -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/Revision_History.xml =================================================================== --- branches/jbosstools-3.1.x/jbpm/docs/reference/en/Revision_History.xml (rev 0) +++ branches/jbosstools-3.1.x/jbpm/docs/reference/en/Revision_History.xml 2010-03-03 13:22:05 UTC (rev 20607) @@ -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/Test_Drive_Proc.xml =================================================================== --- branches/jbosstools-3.1.x/jbpm/docs/reference/en/Test_Drive_Proc.xml (rev 0) +++ branches/jbosstools-3.1.x/jbpm/docs/reference/en/Test_Drive_Proc.xml 2010-03-03 13:22:05 UTC (rev 20607) @@ -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/The_JBoss_jBPM_Int_Mech.xml =================================================================== --- branches/jbosstools-3.1.x/jbpm/docs/reference/en/The_JBoss_jBPM_Int_Mech.xml (rev 0) +++ branches/jbosstools-3.1.x/jbpm/docs/reference/en/The_JBoss_jBPM_Int_Mech.xml 2010-03-03 13:22:05 UTC (rev 20607) @@ -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/guided_tour_jboss_jbpmgpd.xml =================================================================== --- branches/jbosstools-3.1.x/jbpm/docs/reference/en/guided_tour_jboss_jbpmgpd.xml (rev 0) +++ branches/jbosstools-3.1.x/jbpm/docs/reference/en/guided_tour_jboss_jbpmgpd.xml 2010-03-03 13:22:05 UTC (rev 20607) @@ -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/jBPM_Tools_Reference_Guide.ent =================================================================== --- branches/jbosstools-3.1.x/jbpm/docs/reference/en/jBPM_Tools_Reference_Guide.ent (rev 0) +++ branches/jbosstools-3.1.x/jbpm/docs/reference/en/jBPM_Tools_Reference_Guide.ent 2010-03-03 13:22:05 UTC (rev 20607) @@ -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/jBPM_Tools_Reference_Guide.xml =================================================================== --- branches/jbosstools-3.1.x/jbpm/docs/reference/en/jBPM_Tools_Reference_Guide.xml (rev 0) +++ branches/jbosstools-3.1.x/jbpm/docs/reference/en/jBPM_Tools_Reference_Guide.xml 2010-03-03 13:22:05 UTC (rev 20607) @@ -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/jboss_jbpm_runtime_installation.xml =================================================================== --- branches/jbosstools-3.1.x/jbpm/docs/reference/en/jboss_jbpm_runtime_installation.xml (rev 0) +++ branches/jbosstools-3.1.x/jbpm/docs/reference/en/jboss_jbpm_runtime_installation.xml 2010-03-03 13:22:05 UTC (rev 20607) @@ -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/the_views.xml =================================================================== --- branches/jbosstools-3.1.x/jbpm/docs/reference/en/the_views.xml (rev 0) +++ branches/jbosstools-3.1.x/jbpm/docs/reference/en/the_views.xml 2010-03-03 13:22:05 UTC (rev 20607) @@ -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
0 / 0

JBoss Tools SVN: r20606 - in branches/jbosstools-3.1.x/jbpm/docs/reference: en and 1 other directory.

by jbosstools-commits＠lists.jboss.org

Author: ochikvina Date: 2010-03-03 08:19:35 -0500 (Wed, 03 Mar 2010) New Revision: 20606 Modified: branches/jbosstools-3.1.x/jbpm/docs/reference/en/master.xml branches/jbosstools-3.1.x/jbpm/docs/reference/en/master_output.xml branches/jbosstools-3.1.x/jbpm/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/jbpm/docs/reference/en/master.xml =================================================================== --- branches/jbosstools-3.1.x/jbpm/docs/reference/en/master.xml 2010-03-03 13:15:19 UTC (rev 20605) +++ branches/jbosstools-3.1.x/jbpm/docs/reference/en/master.xml 2010-03-03 13:19:35 UTC (rev 20606) @@ -3,13 +3,13 @@ "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 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"> @@ -64,11 +64,11 @@ <copyright> <year>2007</year> - <year>2009</year> + <year>2009</year> <year>2010</year> <holder>JBoss by Red Hat</holder> </copyright> - <releaseinfo> Version: 4.0.0.CR1</releaseinfo> + <releaseinfo> Version: 4.0.0.trunk</releaseinfo> <abstract> <title/> Modified: branches/jbosstools-3.1.x/jbpm/docs/reference/en/master_output.xml =================================================================== --- branches/jbosstools-3.1.x/jbpm/docs/reference/en/master_output.xml 2010-03-03 13:15:19 UTC (rev 20605) +++ branches/jbosstools-3.1.x/jbpm/docs/reference/en/master_output.xml 2010-03-03 13:19:35 UTC (rev 20606) @@ -23,1292 +23,1295 @@ <!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> - - - <pubdate>April 2008</pubdate> - <copyright> - <year>2007</year> - <year>2009</year> - <holder>JBoss by Red Hat</holder> - </copyright> - <releaseinfo><diffmk:wrapper diffmk:change="changed"> Version: 4.0.0.CR1</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/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/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/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/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_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 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/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/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/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/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/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/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/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/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/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/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> - - -  -</book> + ]><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> + + +  +</book> Modified: branches/jbosstools-3.1.x/jbpm/docs/reference/pom.xml =================================================================== --- branches/jbosstools-3.1.x/jbpm/docs/reference/pom.xml 2010-03-03 13:15:19 UTC (rev 20605) +++ branches/jbosstools-3.1.x/jbpm/docs/reference/pom.xml 2010-03-03 13:19:35 UTC (rev 20606) @@ -23,7 +23,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> @@ -85,9 +85,9 @@ </dependencies> <configuration> <sourceDocumentName>${master}</sourceDocumentName> - <sourceDirectory>${pom.basedir}/en</sourceDirectory> + <sourceDirectory>${pom.basedir}/en-US</sourceDirectory> <imageResource> - <directory>${pom.basedir}/en</directory> + <directory>${pom.basedir}/en-US</directory> <includes> <include>images/**/*</include> </includes>

14 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r20605 - in branches/jbosstools-3.1.x/seam/docs/reference: en and 3 other directories.

by jbosstools-commits＠lists.jboss.org

Author: ochikvina Date: 2010-03-03 08:15:19 -0500 (Wed, 03 Mar 2010) New Revision: 20605 Modified: branches/jbosstools-3.1.x/seam/docs/reference/en/images/create_new_seam/create_seam_15.png branches/jbosstools-3.1.x/seam/docs/reference/en/images/create_new_seam/create_seam_16.png branches/jbosstools-3.1.x/seam/docs/reference/en/images/create_new_seam/create_seam_8.png branches/jbosstools-3.1.x/seam/docs/reference/en/images/directory_structure/directory_structure_3.png branches/jbosstools-3.1.x/seam/docs/reference/en/master.xml branches/jbosstools-3.1.x/seam/docs/reference/en/master_output.xml branches/jbosstools-3.1.x/seam/docs/reference/en/modules/directory_structure.xml branches/jbosstools-3.1.x/seam/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/seam/docs/reference/en/images/create_new_seam/create_seam_15.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.1.x/seam/docs/reference/en/images/create_new_seam/create_seam_16.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.1.x/seam/docs/reference/en/images/create_new_seam/create_seam_8.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.1.x/seam/docs/reference/en/images/directory_structure/directory_structure_3.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.1.x/seam/docs/reference/en/master.xml =================================================================== --- branches/jbosstools-3.1.x/seam/docs/reference/en/master.xml 2010-03-03 12:38:25 UTC (rev 20604) +++ branches/jbosstools-3.1.x/seam/docs/reference/en/master.xml 2010-03-03 13:15:19 UTC (rev 20605) @@ -56,14 +56,14 @@ <author><firstname>Svetlana</firstname><surname>Mukhina</surname><email>smukhina(a)exadel.com</email></author> <copyright> - <year>2007</year> + <year>2007</year> <year>2008</year> - <year>2009</year> + <year>2009</year> <year>2010</year> <holder>JBoss by Red Hat</holder> </copyright> <releaseinfo> - Version: 3.1.0.CR1 + Version: 3.1.0.GA </releaseinfo> <abstract> @@ -79,7 +79,7 @@ &intro; &creating_new_seam; -&creating_mavenized_seam; +  &directory_structure; &menus_and_actions; &seam_wizards; Modified: branches/jbosstools-3.1.x/seam/docs/reference/en/master_output.xml =================================================================== --- branches/jbosstools-3.1.x/seam/docs/reference/en/master_output.xml 2010-03-03 12:38:25 UTC (rev 20604) +++ branches/jbosstools-3.1.x/seam/docs/reference/en/master_output.xml 2010-03-03 13:15:19 UTC (rev 20605) @@ -54,14 +54,15 @@ <author><firstname>Svetlana</firstname><surname>Mukhina</surname><email>smukhina(a)exadel.com</email></author> - <pubdate>April 2008</pubdate> <copyright> <year>2007</year> + <year>2008</year> <year>2009</year> + <year>2010</year> <holder>JBoss by Red Hat</holder> </copyright> <releaseinfo><diffmk:wrapper diffmk:change="changed"> - Version: 3.1.0.CR1 + Version: 3.1.0.GA </diffmk:wrapper></releaseinfo> <abstract> @@ -76,7 +77,7 @@ <toc></toc> -<chapter id="intro" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/seam/docs/reference/en/modules/intro.xml" xreflabel="intro"> +<chapter id="intro" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/seam/docs/reference/en/modules/intro.xml" xreflabel="intro"> <?dbhtml filename="intro.html"?> <chapterinfo> <keywordset> @@ -224,7 +225,7 @@ </chapter> -<chapter id="create_seam" role="updated" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/seam/docs/reference/en/modules/creating_new_seam.xml" xreflabel="create_seam"> +<chapter id="create_seam" role="updated" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/seam/docs/reference/en/modules/creating_new_seam.xml" xreflabel="create_seam"> <?dbhtml filename="create_new_seam.html"?> <chapterinfo> <keywordset> @@ -234,11 +235,11 @@ </keywordset> </chapterinfo> <title>Creating a New Seam Project via the New Seam Project wizard</title> - <para><diffmk:wrapper diffmk:change="changed">In this chapter we provide you with the necessary steps to start working with Seam - Framework.</diffmk:wrapper></para> - <para><diffmk:wrapper diffmk:change="changed">At first, we suggest to set the specific Seam perspective that combines a number of + <para>In this chapter we provide you with the necessary steps to start working with Seam + Framework.</para> + <para>At first, we suggest to set the specific Seam perspective that combines a number of different views and editors needed for work with resources concerned. For that select - </diffmk:wrapper><emphasis> + <emphasis> <property moreinfo="none">Window > Open Perspective > Other > Seam</property> </emphasis> or you can also access it through the button in the right top corner.</para> <figure float="0"> @@ -250,8 +251,8 @@ </mediaobject> </figure> <para>Also the <emphasis> - <property moreinfo="none">Open Web Browser</property></emphasis><diffmk:wrapper diffmk:change="changed"> action is directly available in the - </diffmk:wrapper><property moreinfo="none">Seam perspective</property>.</para> + <property moreinfo="none">Open Web Browser</property></emphasis> action is directly available in the + <property moreinfo="none">Seam perspective</property>.</para> <figure float="0"> <title>Embedded Web Browser Button</title> <mediaobject> @@ -262,8 +263,8 @@ </figure> <section id="standaloneSeam" role="updated"> <title>Create standalone Seam Web Project</title> - <para><diffmk:wrapper diffmk:change="changed">The best way to get started with Seam is to create a simple Seam Project and - experiment with it.</diffmk:wrapper></para> + <para>The best way to get started with Seam is to create a simple Seam Project and + experiment with it.</para> <para>Thus, you should select <emphasis> <property moreinfo="none">File > New > Seam Web Project</property> </emphasis> to run the <property moreinfo="none">New Seam Project</property> wizard. The wizard form @@ -272,8 +273,8 @@ <para>Seam Web Project wizard has an option for selecting the actual Server (not just WTP runtime) that will be used for the project. This allows the wizard to identify correctly where the required datasource and driver libraries need to go.</para> - <para><diffmk:wrapper diffmk:change="changed">Let's get through the wizard step-by-step. First, you should enter a name and a - location directory for your new project.</diffmk:wrapper></para> + <para>Let's get through the wizard step-by-step. First, you should enter a name and a + location directory for your new project.</para> <figure float="0" id="figure_create_seam1"> <title>New Seam Project Wizard</title> <mediaobject> @@ -285,10 +286,10 @@ <para>On the figure above you can see the runtime and the server already created.</para> <para>If you need to create a new runtime, click on the <emphasis> <property moreinfo="none">New...</property> - </emphasis> button in the <property moreinfo="none">Target Runtime</property><diffmk:wrapper diffmk:change="changed"> section. It brings up the + </emphasis> button in the <property moreinfo="none">Target Runtime</property> section. It brings up the wizard where you can specify a new JBoss Server Runtime environment or the other type of runtime appropriate for your project configuration. Let's create one more JBoss 4.2 - Runtime. Hence, after choosing it click on </diffmk:wrapper><emphasis> + Runtime. Hence, after choosing it click on <emphasis> <property moreinfo="none">Next</property> </emphasis> button.</para> <figure float="0"> @@ -314,15 +315,15 @@ </figure> <para> Clicking on <emphasis> <property moreinfo="none">Finish</property> - </emphasis> returns you to the <link linkend="figure_create_seam1"><diffmk:wrapper diffmk:change="changed">New Seam Project - wizard page</diffmk:wrapper></link>.</para> - <para><diffmk:wrapper diffmk:change="changed">The next step is to define a Server by clicking on </diffmk:wrapper><emphasis> + </emphasis> returns you to the <link linkend="figure_create_seam1">New Seam Project + wizard page</link>.</para> + <para>The next step is to define a Server by clicking on <emphasis> <property moreinfo="none">New...</property> </emphasis> button in the <property moreinfo="none">Target Server</property> section. In appeared <property moreinfo="none">New Server dialog</property> the last server which matches the runtime will be selected.</para> - <para><diffmk:wrapper diffmk:change="changed">All declared runtimes are listed in the combo-box under the servers view. Here, you - can indicate a server runtime that you need. Click </diffmk:wrapper><emphasis> + <para>All declared runtimes are listed in the combo-box under the servers view. Here, you + can indicate a server runtime that you need. Click <emphasis> <property moreinfo="none">Add</property> </emphasis> if you want to add a new Server Runtime.</para> <figure float="0"> @@ -333,8 +334,8 @@ </imageobject> </mediaobject> </figure> - <para><diffmk:wrapper diffmk:change="changed">Next page allows you to verify the information for a chosen server. Leave everything as - it is and click on </diffmk:wrapper><emphasis> + <para>Next page allows you to verify the information for a chosen server. Leave everything + as it is and click on <emphasis> <property moreinfo="none">Next</property> </emphasis>.</para> <figure float="0"> @@ -361,8 +362,8 @@ wizard</property>.</para> <tip> <title>Tip:</title> - <para><diffmk:wrapper diffmk:change="changed">We suggest that you look through </diffmk:wrapper><ulink url="../../as/html_single/index.html">AS manager - guide</ulink> to find out more about runtimes and servers.</para> + <para>We suggest that you look through <ulink url="../../as/html_single/index.html">AS manager guide</ulink> to + find out more about runtimes and servers.</para> </tip> <figure float="0"> <title>Completion of Runtime and Server Configuration</title> @@ -382,11 +383,11 @@ <para>Pass to the next section to find out more details on this dialog.</para> </section> <section id="projectFacets"> - <title><diffmk:wrapper diffmk:change="changed">Selecting the Project Facets</diffmk:wrapper></title> - <para>The <property moreinfo="none">Project Facets wizard</property><diffmk:wrapper diffmk:change="changed"> allows you to enable or disable - specific facets which define necessary features for the project. When you - switch to this wizard form, all critical facets are already checked for the chosen - Configuration.</diffmk:wrapper></para> + <title>Selecting the Project Facets</title> + <para>The <property moreinfo="none">Project Facets wizard</property> allows you to enable or disable + specific facets which define necessary features for the project. When you switch to this + wizard form, all critical facets are already checked for the chosen + Configuration.</para> <para>Notice that this page of the wizard also allows you to set the necessary version for any facet. </para> <figure float="0"> @@ -412,12 +413,12 @@ <para>To see all available Server runtimes click on <property moreinfo="none">Runtimes</property> tab on the left. You can create a new one using the <emphasis> <property moreinfo="none">New</property> - </emphasis><diffmk:wrapper diffmk:change="changed"> button. If more than one runtime is checked here, the </diffmk:wrapper><emphasis> + </emphasis> button. If more than one runtime is checked here, the <emphasis> <property moreinfo="none">Make Primary</property> - </emphasis><diffmk:wrapper diffmk:change="changed"> button won't be dimmed yet. Thus, you can make use of it to mark primary - runtime.</diffmk:wrapper></para> + </emphasis> button won't be dimmed yet. Thus, you can make use of it to mark + primary runtime.</para> <figure float="0"> - <title><diffmk:wrapper diffmk:change="changed">Setting Runtime</diffmk:wrapper></title> + <title>Setting Runtime</title> <mediaobject> <imageobject> <imagedata fileref="images/create_new_seam/create_seam_16.png"></imagedata> @@ -428,28 +429,53 @@ <property moreinfo="none">Ok</property> </emphasis> button will bring you to the <property moreinfo="none">Web Module</property> wizard form again.</para> + <section id="seamWithJPA"> + <title>Seam project with JPA facets</title> + <para>For creating Seam project with JPA support you need to select<property moreinfo="none"> Java + Persistent</property> facet on <property moreinfo="none">Project Facets</property> page and + click <property moreinfo="none">OK</property>.</para> + <para>Then you should press <property moreinfo="none">Next</property> and may leave the default value on + <property moreinfo="none">Java application building</property> page and <property moreinfo="none">Web Module + Settings</property> page.</para> + <para>After that you will see <property moreinfo="none">JPA facet</property> page.</para> + <figure float="0"> + <title>JPA Facet page</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/create_new_seam/create_seam_16b.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>On this page you can choose <property moreinfo="none">Platform</property> (vendor-specific JPA + implementation) for your project, type of JPA Implementation, and configure the + <property moreinfo="none">Connection</property> to database in the <property moreinfo="none">Connection</property> area.</para> + <para>More about <property moreinfo="none">JPA facet</property> page you can read in <ulink url="http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.jpt.doc.user...">Eclipse documentation</ulink>. </para> + <para>On the next step you will see <property moreinfo="none">JSF Capabilities</property> and <property moreinfo="none">Seam + facet</property> pages, which are mostly the same as in general Seam + project.</para> + </section> </section> - <section diffmk:change="added" id="configureJava"> - <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">Java application building configuration</diffmk:wrapper></title> - <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">With this wizard you can define Java source directories which will be generated on + <section id="configureJava"> + <title>Java application building configuration</title> + <para>With this wizard you can define Java source directories which will be generated on build path. Also you can specify a default output folder. If you are agree with default - values, press </diffmk:wrapper><property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">Next</diffmk:wrapper></property></para> - <figure diffmk:change="added" float="0"> - <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">Java application building Wizard</diffmk:wrapper></title> - <mediaobject diffmk:change="added"> - <imageobject diffmk:change="added"> - <imagedata diffmk:change="added" fileref="images/create_new_seam/create_seam_16a.png"></imagedata> + values, press <property moreinfo="none">Next</property></para> + <figure float="0"> + <title>Java application building Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/create_new_seam/create_seam_16a.png"></imagedata> </imageobject> </mediaobject> </figure> </section> <section id="configureWebModule"> <title>How to Configure Web Module Settings</title> - <para><diffmk:wrapper diffmk:change="changed"> As we deal with a Dynamic Web Application, we should at first specify the top level + <para> As we deal with a Dynamic Web Application, we should at first specify the top level directory of our application for deploying it to a server afterwards. You know, this kind of application contains Web resources. Thus, it's important to indicate the content directory. The wizard will put all those values itself, so you can leave everything as - is.</diffmk:wrapper></para> + is.</para> <figure float="0"> <title>Web Module Settings</title> <mediaobject> @@ -464,11 +490,11 @@ </section> <section id="addJSFCapab"> <title>Adding JSF Capabilities</title> - <para><diffmk:wrapper diffmk:change="changed">This wizard helps you to add JSF capabilities to your project. </diffmk:wrapper></para> - <para><diffmk:wrapper diffmk:change="changed">Choose </diffmk:wrapper><emphasis> - <property moreinfo="none"><diffmk:wrapper diffmk:change="changed">Library provided by Target Runtime</diffmk:wrapper></property> - </emphasis><diffmk:wrapper diffmk:change="changed"> from Library Type list if you'd like to use a default JSF implementation - given by the present runtime.</diffmk:wrapper></para> + <para>This wizard helps you to add JSF capabilities to your project. </para> + <para>Choose <emphasis> + <property moreinfo="none">Library provided by Target Runtime</property> + </emphasis> from Library Type list if you'd like to use a default JSF implementation + given by the present runtime.</para> <figure float="0"> <title>Adding JSF Capabilities to Web Project</title> <mediaobject> @@ -477,56 +503,58 @@ </imageobject> </mediaobject> </figure> - <para><diffmk:wrapper diffmk:change="added">In case if you prefer to use your custom JSF implementation, choose </diffmk:wrapper><property moreinfo="none"><diffmk:wrapper diffmk:change="changed">User - Library</diffmk:wrapper></property><diffmk:wrapper diffmk:change="added"> Item from Library Type list. In User Library list you can check - required library.</diffmk:wrapper></para> - <figure diffmk:change="added" float="0"> - <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">Using Custom JSF implementation Library </diffmk:wrapper></title> - <mediaobject diffmk:change="added"> - <imageobject diffmk:change="added"> - <imagedata diffmk:change="added" fileref="images/create_new_seam/create_seam_17.png"></imagedata> + <para>In case if you prefer to use your custom JSF implementation, choose <property moreinfo="none">User + Library</property> Item from Library Type list. In User Library list you can check + required library.</para> + <figure float="0"> + <title>Using Custom JSF implementation Library </title> + <mediaobject> + <imageobject> + <imagedata fileref="images/create_new_seam/create_seam_17.png"></imagedata> </imageobject> </mediaobject> </figure> - <para><diffmk:wrapper diffmk:change="added"> If a new library is required, click </diffmk:wrapper><property moreinfo="none"><diffmk:wrapper diffmk:change="changed">Manage libraries...</diffmk:wrapper></property><diffmk:wrapper diffmk:change="added"> ( </diffmk:wrapper><inlinemediaobject diffmk:change="added"> - <imageobject diffmk:change="added"> - <imagedata diffmk:change="added" fileref="images/create_new_seam/create_seam_17a.png"></imagedata> + <para> If a new library is required, click <property moreinfo="none">Manage libraries...</property> ( + <inlinemediaobject> + <imageobject> + <imagedata fileref="images/create_new_seam/create_seam_17a.png"></imagedata> </imageobject> - </inlinemediaobject><diffmk:wrapper diffmk:change="added">) button. Then you should click </diffmk:wrapper><property moreinfo="none"><diffmk:wrapper diffmk:change="changed">New</diffmk:wrapper></property><diffmk:wrapper diffmk:change="added">.</diffmk:wrapper></para> - <figure diffmk:change="added" float="0"> - <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">Using Custom JSF implementation Library </diffmk:wrapper></title> - <mediaobject diffmk:change="added"> - <imageobject diffmk:change="added"> - <imagedata diffmk:change="added" fileref="images/create_new_seam/create_seam_18.png"></imagedata> + </inlinemediaobject>) button. Then you should click <property moreinfo="none">New</property>.</para> + <figure float="0"> + <title>Using Custom JSF implementation Library </title> + <mediaobject> + <imageobject> + <imagedata fileref="images/create_new_seam/create_seam_18.png"></imagedata> </imageobject> </mediaobject> </figure> - <para diffmk:change="added"><diffmk:wrapper diffmk:change="added"> Here, it's necessary to type a </diffmk:wrapper><property moreinfo="none"><diffmk:wrapper diffmk:change="changed">Library Name</diffmk:wrapper></property><diffmk:wrapper diffmk:change="added">. </diffmk:wrapper></para> + <para> Here, it's necessary to type a <property moreinfo="none">Library Name</property>. </para> <figure float="0"> - <title><diffmk:wrapper diffmk:change="changed">Entering New User Library Name</diffmk:wrapper></title> + <title>Entering New User Library Name</title> <mediaobject> <imageobject> <imagedata fileref="images/create_new_seam/create_seam_23.png"></imagedata> </imageobject> </mediaobject> </figure> - <para><diffmk:wrapper diffmk:change="changed">To add proper </diffmk:wrapper><property moreinfo="none"><diffmk:wrapper diffmk:change="changed">Library JARs</diffmk:wrapper></property><diffmk:wrapper diffmk:change="added">, click </diffmk:wrapper><property moreinfo="none"><diffmk:wrapper diffmk:change="changed">Add JARs...</diffmk:wrapper></property><diffmk:wrapper diffmk:change="added"> - button and select the JARs on your hard drive. </diffmk:wrapper></para> - <figure diffmk:change="added" float="0"> - <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">Selection Library JARs</diffmk:wrapper></title> - <mediaobject diffmk:change="added"> - <imageobject diffmk:change="added"> - <imagedata diffmk:change="added" fileref="images/create_new_seam/create_seam_25.png"></imagedata> + <para>To add proper <property moreinfo="none">Library JARs</property>, click <property moreinfo="none">Add + JARs...</property> button and select the JARs on your hard drive. </para> + <figure float="0"> + <title>Selection Library JARs</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/create_new_seam/create_seam_25.png"></imagedata> </imageobject> </mediaobject> </figure> - <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">You can download necessary JSF implementation libraries provided by Sun and Apache Foundation as well. Click </diffmk:wrapper><property moreinfo="none"><diffmk:wrapper diffmk:change="changed">Download...</diffmk:wrapper></property><diffmk:wrapper diffmk:change="added"> (</diffmk:wrapper><inlinemediaobject diffmk:change="added"> - <imageobject diffmk:change="added"> - <imagedata diffmk:change="added" fileref="images/create_new_seam/create_seam_23a.png"></imagedata> - </imageobject> - </inlinemediaobject><diffmk:wrapper diffmk:change="added">) button and choose one of proposed libraries.</diffmk:wrapper></para> + <para>You can download necessary JSF implementation libraries provided by Sun and Apache + Foundation as well. Click <property moreinfo="none">Download...</property> (<inlinemediaobject> + <imageobject> + <imagedata fileref="images/create_new_seam/create_seam_23a.png"></imagedata> + </imageobject> + </inlinemediaobject>) button and choose one of proposed libraries.</para> <figure float="0"> - <title><diffmk:wrapper diffmk:change="changed">Download JSF Implementation Library</diffmk:wrapper></title> + <title>Download JSF Implementation Library</title> <mediaobject> <imageobject> <imagedata fileref="images/create_new_seam/create_seam_24.png"></imagedata> @@ -544,8 +572,8 @@ </imageobject> </mediaobject> </figure> - <para><diffmk:wrapper diffmk:change="changed">Since we are arranging the Seam Web project, the last step we should do is to - adjust project configurations associated with the Seam.</diffmk:wrapper></para> + <para>Since we are arranging the Seam Web project, the last step we should do is to adjust + project configurations associated with the Seam.</para> </section> <section id="seamFacet"> <title>Configure Seam Facet Settings</title> @@ -566,10 +594,10 @@ </itemizedlist> <para>For that click on <emphasis> <property moreinfo="none">Add</property> - </emphasis> button in the <property moreinfo="none">General</property><diffmk:wrapper diffmk:change="changed"> section. Note, in the - wizard shown below you can create a Seam runtime only for the version that was - selected in the </diffmk:wrapper><link linkend="projectFacets">Project Facets</link> wizard (version 1.2 - in our case).</para> + </emphasis> button in the <property moreinfo="none">General</property> section. Note, in the wizard + shown below you can create a Seam runtime only for the version that was selected in the + <link linkend="projectFacets">Project Facets</link> wizard (version 1.2 in our + case).</para> <figure float="0"> <title>Seam Runtime Creation</title> <mediaobject> @@ -624,8 +652,8 @@ </imageobject> </mediaobject> </figure> - <para><diffmk:wrapper diffmk:change="changed">On the dialog you'll be asked to enter its name and description. And then - you should select a proper driver and adjust connection details. Press </diffmk:wrapper><emphasis> + <para>On the dialog you'll be asked to enter its name and description. And then you + should select a proper driver and adjust connection details. Press <emphasis> <property moreinfo="none">Next</property> </emphasis> to preview all the adjusted settings and complete the creation of the new profile.</para> @@ -639,10 +667,10 @@ </figure> <para>The next block of settings in the Seam Facet wizard are describing a Database and a connection to it.</para> - <para>In the <property moreinfo="none">Code Generation</property><diffmk:wrapper diffmk:change="changed"> section the wizard has already provided the - names for your </diffmk:wrapper><property moreinfo="none">Session Bean</property>, <property moreinfo="none">Entity Bean</property> and - <property moreinfo="none">Test</property><diffmk:wrapper diffmk:change="changed"> packages. Of course, you can change them on others - of your choice.</diffmk:wrapper></para> + <para>In the <property moreinfo="none">Code Generation</property> section the wizard has already provided + the names for your <property moreinfo="none">Session Bean</property>, <property moreinfo="none">Entity Bean</property> + and <property moreinfo="none">Test</property> packages generation (optional). Of course, you can change + them on others of your choice.</para> <figure float="0"> <title>Code Generation Section</title> <mediaobject> @@ -659,7 +687,7 @@ </chapter> -<chapter id="mavenized_seam" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/seam/docs/reference/en/modules/creating_mavenized_seam.xml" xreflabel="mavenized_seam"> +<chapter id="mavenized_seam" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/seam/docs/reference/en/modules/creating_mavenized_seam.xml" xreflabel="mavenized_seam"> <?dbhtml filename="create_mavenized_seam.html"?> <chapterinfo> <keywordset> @@ -668,136 +696,149 @@ <keyword>JBDS</keyword> </keywordset> </chapterinfo> - <title>Maven Integration for Seam Projects</title> - <para>Starting from 3.1 M2 version <property moreinfo="none">JBoss Tools</property> includes new Jboss Maven Integration plug-in which for now allows - to create mavenized Seam projects and enable Seam tools support for imported Maven projects.</para> - + <para>Starting from 3.1 M2 version <property moreinfo="none">JBoss Tools</property> includes new Jboss Maven + Integration plug-in which for now allows to create mavenized Seam projects and enable Seam + tools support for imported Maven projects.</para> <para>The Jboss Maven Integration requires <ulink url="http://m2eclipse.sonatype.org/">m2eclipse</ulink> to be installed.</para> - <note> <title>Note:</title> - <para>For M2 release of <property moreinfo="none">Jboss Tools</property> it is important to use m2eclipse <ulink url="http://m2eclipse.sonatype.org/update/">stable updatesite</ulink> or the <ulink url="http://m2eclipse.sonatype.org/releases/0.9.9.200906081351">latest integration build</ulink> that M2 was - developed against. If you want to use the latest development release of m2eclipse you need to use the <ulink url="http://download.jboss.org/jbosstools/updates/nightly/trunk/">nightly builds</ulink> of - <property moreinfo="none">JBoss Tools</property>.</para> + <para>For M2 release of <property moreinfo="none">Jboss Tools</property> it is important to use m2eclipse + <ulink url="http://m2eclipse.sonatype.org/update/">stable updatesite</ulink> or the + <ulink url="http://m2eclipse.sonatype.org/releases/0.9.9.200906081351">latest + integration build</ulink> that M2 was developed against. If you want to use the + latest development release of m2eclipse you need to use the <ulink url="http://download.jboss.org/jbosstools/updates/nightly/trunk/">nightly + builds</ulink> of <property moreinfo="none">JBoss Tools</property>.</para> </note> - <section id="create_mavenized_project"> - <title>Creating Maven ready Seam project</title> - - <para>Maven Integration makes the Seam Wizard capable of creating - Maven ready projects to let Maven get the libraries instead of using the Seam runtime.</para> - - <para>To create a mavenized Seam project you should perform the following steps:</para> - - <itemizedlist> - <listitem> - <para>Navigate to <emphasis> - <property moreinfo="none">File > New Seam Project</property>.</emphasis> Give the project a meaningful name, specify a target runtime and server - and select the proper configuration for your Seam project:</para> - - <figure float="0"> - <title>Starting the Mavenized Seam Project</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/create_mavenized_seam/createMavenizedSeamProject.png"></imagedata> - </imageobject> - </mediaobject> - </figure> - </listitem> - - <listitem> - <para>Click the <emphasis> - <property moreinfo="none">Modify</property></emphasis> button to enable the <emphasis> - <property moreinfo="none">Jboss Maven Integration</property></emphasis> facet:</para> - - <figure float="0"> - <title>Enabling the Jboss Maven Integration Facet</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/create_mavenized_seam/jbossMavenIntegrationFacet.png"></imagedata> - </imageobject> - </mediaobject> - </figure> - </listitem> - - <listitem> - <para>On the <property moreinfo="none">JBoss M2 capabilities</property> page you'll be prompted to add the following maven properties: - groupId, artifactId, version, packaging, name and description. Here it's possible to set a maven version of Seam - and also decide whether to remove WTP classpath containers (where the path starts with org.eclipse.jst). - </para> - - <figure float="0"> - <title>Adjusting JBoss M2 Capabilities</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/create_mavenized_seam/jbossM2capabilities.png"></imagedata> - </imageobject> - </mediaobject> - </figure> - </listitem> - - <listitem> - <para>On the <property moreinfo="none">Seam Facet</property> page configure the Seam Facet settings and click <emphasis> - <property moreinfo="none">Finish</property>:</emphasis></para> - - <figure float="0"> - <title>Seam Facet Settings</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/create_mavenized_seam/seamFacetPage.png"></imagedata> - </imageobject> - </mediaobject> - </figure> - </listitem> - </itemizedlist> - - <para>The organized Seam project contains five projects with the Maven nature, builder, Maven classpath and the <emphasis> - <property moreinfo="none">pom.xml</property></emphasis> files added: - projectname, projectname-ear, projectname-ejb, projectname-parent and projectname-test.</para> - - <figure float="0"> - <title>Mavenized Seam Project</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/create_mavenized_seam/mavenizedProjectStructure.png"></imagedata> - </imageobject> - </mediaobject> - </figure> + <title>Creating Maven ready Seam project</title> + <para>Maven Integration makes the Seam Wizard capable of creating Maven ready projects to + let Maven get the libraries instead of using the Seam runtime.</para> + <para>To create a mavenized Seam project you should perform the following steps:</para> + <itemizedlist> + <listitem> + <para>Navigate to <emphasis> + <property moreinfo="none">File > New Seam Project</property>.</emphasis> Give the project + a meaningful name, specify a target runtime and server and select the proper + configuration for your Seam project:</para> + <figure float="0"> + <title>Starting the Mavenized Seam Project</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/create_mavenized_seam/createMavenizedSeamProject.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Click the <emphasis> + <property moreinfo="none">Modify</property></emphasis> button to enable the <emphasis> + <property moreinfo="none">Jboss Maven Integration</property></emphasis> facet:</para> + <figure float="0"> + <title>Enabling the Jboss Maven Integration Facet</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/create_mavenized_seam/jbossMavenIntegrationFacet.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>On the <property moreinfo="none">JBoss M2 capabilities</property> page you'll be prompted + to add the following maven properties: groupId, artifactId, version, packaging, + name and description. Here it's possible to set a maven version of Seam and + also decide whether to remove WTP classpath containers (where the path starts + with org.eclipse.jst). </para> + <figure float="0"> + <title>Adjusting JBoss M2 Capabilities</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/create_mavenized_seam/jbossM2capabilities.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para> On the <property moreinfo="none">JSF Capabilities</property> page you can choose Maven as + libraries provider. This is possible when you use Maven JSF 1.2 Libraries as + type of JSF Implementing Library. Also it gives you capability to edit + Dependencies and Exclusions for the mavenized Seam project directly from the + wizard. </para> + <figure float="0"> + <title>Using JSF Implementation libraries provided by Maven</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/create_mavenized_seam/seamJSFImplementation.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>On the <property moreinfo="none">Seam Facet</property> page configure the Seam Facet settings + and click <emphasis> + <property moreinfo="none">Finish</property>:</emphasis></para> + <figure float="0"> + <title>Seam Facet Settings</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/create_mavenized_seam/seamFacetPage.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + <para>The organized Seam project contains five projects with the Maven nature, builder, + Maven classpath and the <emphasis> + <property moreinfo="none">pom.xml</property></emphasis> files added: projectname, projectname-ear, + projectname-ejb, projectname-parent and projectname-test.</para> + <figure float="0"> + <title>Mavenized Seam Project</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/create_mavenized_seam/mavenizedProjectStructure.png"></imagedata> + </imageobject> + </mediaobject> + </figure> </section> - <section id="import_maven_project"> <title>Existing Maven Projects Import</title> - - <para>Maven Integration includes the Seam Maven configurator which is called when importing a project, changing - <emphasis> + <para>Maven Integration includes the Seam Maven configurator which is called when importing + a project, changing <emphasis> <property moreinfo="none">pom.xml</property></emphasis> and/or calling <emphasis> - <property moreinfo="none">Maven > Update Project Configuration</property>.</emphasis> When importing a Maven Seam project, the Seam Maven configurator - picks up the settings set up in <emphasis> - <property moreinfo="none">pom.xml</property></emphasis> and adds to the project the following:</para> - + <property moreinfo="none">Maven > Update Project Configuration</property>.</emphasis> When + importing a Maven Seam project, the Seam Maven configurator picks up the settings set up + in <emphasis> + <property moreinfo="none">pom.xml</property></emphasis> and adds to the project the + following:</para> <itemizedlist> - <listitem><para>Seam nature</para></listitem> - <listitem><para>Seam facet and dependent facets to the EJB, EAR and WAR projects</para></listitem> - <listitem><para>JBoss Maven Integration facet if the Maven project contains a dependency with the - org.jboss.seam groupId and an artifactId starting with 'jboss-seam'</para></listitem> - <listitem><para>other required facets (Web Module, Java, JSF, etc.)</para></listitem> + <listitem> + <para>Seam nature</para> + </listitem> + <listitem> + <para>Seam facet and dependent facets to the EJB, EAR and WAR projects</para> + </listitem> + <listitem> + <para>JBoss Maven Integration facet if the Maven project contains a dependency with + the org.jboss.seam groupId and an artifactId starting with 'jboss-seam'</para> + </listitem> + <listitem> + <para>other required facets (Web Module, Java, JSF, etc.)</para> + </listitem> </itemizedlist> - <para>If the Seam version from <emphasis> - <property moreinfo="none">pom.xml</property></emphasis> matches a version of a Seam runtime configured in the workspace, - Seam configurator will set that runtime, otherwise no Seam runtime will be set and you'll have to set it manually under - <link linkend="project_pref">Seam Settings in the project preferences</link>.</para> - - <para>Seam configurator recognizes the Seam artifacts in the following way: the view folder is a web content folder from the WAR project, - the source folder is the first Eclipse source folder. If there is a folder containing "hot" in the name, it will be chosen as the action source folder. - Package is the first package that has children or doesn't have any subpackage. - </para> - - <para>Configuring the Seam when importing a Maven project as well as a Seam Runtime, Seam artifacts and some facets could be suspended - in the JBoss Maven Integration preferences (<emphasis> - <property moreinfo="none">Window > Preferences > JBoss Tools > JBoss Maven Integration</property></emphasis>).</para> - + <property moreinfo="none">pom.xml</property></emphasis> matches a version of a Seam runtime + configured in the workspace, Seam configurator will set that runtime, otherwise no Seam + runtime will be set and you'll have to set it manually under <link linkend="project_pref">Seam Settings in the project preferences</link>.</para> + <para>Seam configurator recognizes the Seam artifacts in the following way: the view folder + is a web content folder from the WAR project, the source folder is the first Eclipse + source folder. If there is a folder containing "hot" in the name, it will be + chosen as the action source folder. Package is the first package that has children or + doesn't have any subpackage. </para> + <para>Configuring the Seam when importing a Maven project as well as a Seam Runtime, Seam + artifacts and some facets could be suspended in the JBoss Maven Integration preferences + (<emphasis> + <property moreinfo="none">Window > Preferences > JBoss Tools > JBoss Maven + Integration</property></emphasis>).</para> <figure float="0"> <title>JBoss Maven Integration Preferences</title> <mediaobject> @@ -807,18 +848,17 @@ </mediaobject> </figure> </section> - <section> <title>Relevant Resources Links</title> - - <para>In the <ulink url="http://in.relation.to/Bloggers/UsingMavenWithJBossTools">Using Maven with JBoss Tools</ulink> - article written by Max Andersen you'll find references to the - screencasts on how to use the examples of mavenized Seam projects provided by <property moreinfo="none">JBoss Tools</property>.</para> + <para>In the <ulink url="http://in.relation.to/Bloggers/UsingMavenWithJBossTools">Using + Maven with JBoss Tools</ulink> article written by Max Andersen you'll find + references to the screencasts on how to use the examples of mavenized Seam projects + provided by <property moreinfo="none">JBoss Tools</property>.</para> </section> </chapter> -<chapter id="directory_str" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/seam/docs/reference/en/modules/directory_structure.xml" xreflabel="directory_str"> +<chapter id="directory_str" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/seam/docs/reference/en/modules/directory_structure.xml" xreflabel="directory_str"> <?dbhtml filename="directory_structure.html"?> <chapterinfo> <keywordset> @@ -911,8 +951,8 @@ <title>Changing the Seam Version</title> - <para>To upgrade or downgrade your projects Seam version use the facet preferences. You - should right-click your project and choose <emphasis> + <para><diffmk:wrapper diffmk:change="added">To upgrade or downgrade your projects Seam version use the facet preferences. You + should right-click your project, open its </diffmk:wrapper><property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">Properties</diffmk:wrapper></property><diffmk:wrapper diffmk:change="added"> and choose </diffmk:wrapper><emphasis> <property moreinfo="none">Project Facets</property> </emphasis> category. Next select <emphasis> <property moreinfo="none">Seam</property> @@ -1022,7 +1062,7 @@ </chapter> -<chapter id="menus_and_actions" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/seam/docs/reference/en/modules/seam_menus_and_actions.xml" xreflabel="menus_and_actions"> +<chapter id="menus_and_actions" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/seam/docs/reference/en/modules/seam_menus_and_actions.xml" xreflabel="menus_and_actions"> <?dbhtml filename="seam_menus_and_actions.html"?> <chapterinfo> <keywordset> @@ -1385,7 +1425,7 @@ </chapter> -<chapter id="seam_wizards" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/seam/docs/reference/en/modules/seam_wizards.xml" xreflabel="seam_wizards"> +<chapter id="seam_wizards" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/seam/docs/reference/en/modules/seam_wizards.xml" xreflabel="seam_wizards"> <?dbhtml filename="seam_wizards.html"?> <chapterinfo> <keywordset> @@ -1727,7 +1767,7 @@ </chapter> -<chapter id="generate_entities" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/seam/docs/reference/en/modules/generate_entities.xml" xreflabel="generate_entities"> +<chapter id="generate_entities" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/seam/docs/reference/en/modules/generate_entities.xml" xreflabel="generate_entities"> <?dbhtml filename="generate_entities.html"?> <chapterinfo> <keywordset> @@ -1740,8 +1780,8 @@ <title>Seam Generate Entities</title> <para>The main purpose of this chapter is to tell you about Seam Generate Entities.</para> - <para><diffmk:wrapper diffmk:change="changed">Generate Entities is available directly from Eclipse using Hibernate Tools plugin for the standard seam-gen generation.</diffmk:wrapper></para> - <para><diffmk:wrapper diffmk:change="changed">The wizard generates a set of CRUD Seam components and web pages based on existing tables in a database or on existing entities in your application.</diffmk:wrapper></para> + <para>Generate Entities is available directly from Eclipse using Hibernate Tools plugin for the standard seam-gen generation.</para> + <para>The wizard generates a set of CRUD Seam components and web pages based on existing tables in a database or on existing entities in your application.</para> <figure float="0"> @@ -1753,37 +1793,37 @@ </mediaobject> </figure> - <para><diffmk:wrapper diffmk:change="added">By default, the generation mode is set to </diffmk:wrapper><emphasis diffmk:change="added"><property moreinfo="none"><diffmk:wrapper diffmk:change="changed">Reverse engineer from database</diffmk:wrapper></property><diffmk:wrapper diffmk:change="added">.</diffmk:wrapper></emphasis><diffmk:wrapper diffmk:change="added"> - The reverse engineering from a database could be described in four steps:</diffmk:wrapper></para> + <para>By default, the generation mode is set to <emphasis><property moreinfo="none">Reverse engineer from database</property>.</emphasis> + The reverse engineering from a database could be described in four steps:</para> <orderedlist continuation="restarts" inheritnum="ignore"> <listitem><para>The wizard gets in database, extracts the tables and their connections</para></listitem> - <listitem><para><diffmk:wrapper diffmk:change="added">On basis of this metainfomation the Entity classes are generated into - </diffmk:wrapper><literal diffmk:change="added" moreinfo="none">org.domain.project.entity</literal> package</para></listitem> - <listitem><para>For the entities from step 2 the classes <property moreinfo="none">EntityList</property> and <property moreinfo="none">EntityHome</property><diffmk:wrapper diffmk:change="added"> are generated - into </diffmk:wrapper><literal diffmk:change="added" moreinfo="none">org.domain.project.session</literal> package</para></listitem> + <listitem><para>On basis of this metainfomation the Entity classes are generated into + <literal moreinfo="none">org.domain.project.entity</literal> package</para></listitem> + <listitem><para>For the entities from step 2 the classes <property moreinfo="none">EntityList</property> and <property moreinfo="none">EntityHome</property> are generated + into <literal moreinfo="none">org.domain.project.session</literal> package</para></listitem> <listitem><para>The xhtml pages are generated.</para></listitem> </orderedlist> - <note diffmk:change="added"> - <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">Note:</diffmk:wrapper></title> - <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">The entities are generated from a database based on the console configuration that is created automatically during a Seam project creation. - (Read more about </diffmk:wrapper><ulink diffmk:change="added" url="../../hibernatetools/html_single/index.html#console_conf"><diffmk:wrapper diffmk:change="added">console configuration</diffmk:wrapper></ulink><diffmk:wrapper diffmk:change="added">). The created console configuration is based on the - connection profile set on the </diffmk:wrapper><link diffmk:change="added" linkend="seamFacet"><diffmk:wrapper diffmk:change="added">Seam Facets wizard page</diffmk:wrapper></link><diffmk:wrapper diffmk:change="added"> while creating a project. - Configured connection profile settings are hold in the generated </diffmk:wrapper><literal diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">hibernate-console.properties</diffmk:wrapper></literal><diffmk:wrapper diffmk:change="added">. To change the connection - profile, double-click the console configuration. It could be found in the </diffmk:wrapper><property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">Hibernate Configurations</diffmk:wrapper></property><diffmk:wrapper diffmk:change="added"> view - (</diffmk:wrapper><emphasis diffmk:change="added"><property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">Window > Show view > Other > Hibernate > Hibernate Configurations</diffmk:wrapper></property></emphasis><diffmk:wrapper diffmk:change="added"> - or just switch to the </diffmk:wrapper><property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">Hibernate</diffmk:wrapper></property><diffmk:wrapper diffmk:change="added"> perspective).</diffmk:wrapper></para> + <note> + <title>Note:</title> + <para>The entities are generated from a database based on the console configuration that is created automatically during a Seam project creation. + (Read more about <ulink url="../../hibernatetools/html_single/index.html#console_conf">console configuration</ulink>). The created console configuration is based on the + connection profile set on the <link linkend="seamFacet">Seam Facets wizard page</link> while creating a project. + Configured connection profile settings are hold in the generated <literal moreinfo="none">hibernate-console.properties</literal>. To change the connection + profile, double-click the console configuration. It could be found in the <property moreinfo="none">Hibernate Configurations</property> view + (<emphasis><property moreinfo="none">Window > Show view > Other > Hibernate > Hibernate Configurations</property></emphasis> + or just switch to the <property moreinfo="none">Hibernate</property> perspective).</para> </note> - <para><diffmk:wrapper diffmk:change="added"> - Checking the </diffmk:wrapper><emphasis diffmk:change="added"><property moreinfo="none">Use existing entities</property></emphasis> mode the wizard executes only 3 and 4 steps. It generates missing classes and + <para> + Checking the <emphasis><property moreinfo="none">Use existing entities</property></emphasis> mode the wizard executes only 3 and 4 steps. It generates missing classes and xhtml pages. </para> <para>Read the <link linkend="crud_database_application">Generate a CRUD Database Application</link> chapter in order to see how the <property moreinfo="none">Generate Seam Entities</property> wizard can be used.</para> </chapter> - <chapter id="seam_editors" role="updated" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/seam/docs/reference/en/modules/seam_editors.xml" xreflabel="seam_editors"> +<chapter id="seam_editors" role="updated" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/seam/docs/reference/en/modules/seam_editors.xml" xreflabel="seam_editors"> <?dbhtml filename="seam_editors.html"?> <chapterinfo> <keywordset> @@ -1794,40 +1834,40 @@ </chapterinfo> <title>Seam Editors</title> - - + + <para>This chapter tells about Seam Editors and their features.</para> - + <section> <title>Visual Page Editor</title> <para>Visual Page Editor fits perfectly for authoring view Seam pages. The major features of VPE are listed in <link linkend="SeamEditors">Main Features of Seam Editors</link> </para> <para>You can also read more about Visual Page Editor in <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/jsf/html/editors.htm...">Visual Page Editor</ulink> chapter of "Visual Web Tools Reference Guide".</para> </section> - - - - + + + + <section> <title>Seam Pages Editor</title> - - + + <para> <property moreinfo="none">Seam Pages Editor</property> provides a handy way to edit the <property moreinfo="none">pages.xml</property> file. - + </para> - + <para> You can edit the pages.xml file in three modes: Graphical, Tree and Source. - + </para> <para> Seam Pages Editor supports synchronization with Package Explorer.This means that while renaming files in the Package Explorer all the changes immediately affect the pages.xml file. - + </para> <section> <title>Graphical Mode</title> - - + + <para>Graphical mode provides you with a set of visual tools to organize your project pageflow, exception handling etc.</para> <figure float="0"> <title>Seam Pages Editor: Graphical View</title> @@ -1837,22 +1877,22 @@ </imageobject> </mediaobject> </figure> - + <para>The Graphical part of the editor has some visual elements. The table below shows graphical representation of the elements and explains their meanings. </para> <table> - <title>Pages Editor: Graphical View. Visual elements</title> + <title>Pages Editor: Graphical View. Visual elements</title> <tgroup cols="2"> <thead> <row> <entry>Element</entry> - + <entry>Description</entry> </row> </thead> <tbody> <row> - <entry> + <entry> <mediaobject> <imageobject> <imagedata fileref="images/seam_editors/element_page.png"></imagedata> @@ -1863,9 +1903,9 @@ <page> </code> element. </para></entry> - </row> + </row> <row> - <entry> + <entry> <mediaobject> <imageobject> <imagedata fileref="images/seam_editors/element_param.png"></imagedata> @@ -1877,26 +1917,26 @@ <imagedata fileref="images/seam_editors/icon_plus.png"></imagedata> </imageobject> </inlinemediaobject>) - - + + on the <code> <page> </code> element reveals a box that lists the parameters for the page.</para> </entry> - - </row> - + + </row> + <row> <entry> <mediaobject> <imageobject> <imagedata fileref="images/seam_editors/element_page2.png"></imagedata> </imageobject> </mediaobject></entry> - <entry> + <entry> <para>A red cross in the upper left corner of the page box indicates that the view-id is not found in the project.</para> </entry> - </row> - + </row> + <row> <entry><mediaobject> <imageobject> @@ -1904,12 +1944,12 @@ </imageobject> </mediaobject></entry> <entry> <para> - A gray box with a dashed border represents a page that has navigation + A gray box with a dashed border represents a page that has navigation (navigation rule) to but the page is not defined in the page.xml file. </para></entry> - </row> - - + </row> + + <row> <entry> <mediaobject> <imageobject> @@ -1917,30 +1957,30 @@ </imageobject> </mediaobject></entry> <entry> <para>An <code><exception></code> is represented by a blue box with a orange diamond.</para></entry> - </row> - - - - - + </row> + + + + + </tbody> </tgroup> </table> + + + <para>Pageflow relations are shown with gray arrows, when you select a relationship the arrow is changed to orange. </para> + + + + <para>On the lefthand side of the Graphical view of <property moreinfo="none">Seam Page Editor</property> you can find a toolbar with a set of icons for the most frequently used commands. </para> - - <para>Pageflow relations are shown with gray arrows, when you select a relationship the arrow is changed to orange. </para> - - - - <para>On the lefthand side of the Graphical view of <property moreinfo="none">Seam Page Editor</property> you can find a toolbar with a set of icons for the most frequently used commands. </para> - <table> - <title>Pages Editor: Graphical View. Commands Icons</title> + <title>Pages Editor: Graphical View. Commands Icons</title> <tgroup cols="2"> <thead> <row> <entry>Icon Image</entry> - + <entry>Command</entry> </row> </thead> @@ -1952,12 +1992,12 @@ <imagedata fileref="images/seam_editors/icon_select.png"></imagedata> </imageobject> </inlinemediaobject> - + </entry> <entry>Select a page element</entry> - - </row> - + + </row> + <row> <entry><inlinemediaobject> <imageobject> @@ -1965,9 +2005,9 @@ </imageobject> </inlinemediaobject></entry> <entry>Marquee a page item</entry> - </row> - - + </row> + + <row> <entry> <inlinemediaobject> @@ -1975,31 +2015,31 @@ <imagedata fileref="images/seam_editors/icon_new_link.png"></imagedata> </imageobject> </inlinemediaobject> - + </entry> <entry>Add a page relationship</entry> - </row> - - + </row> + + <row> <entry> <inlinemediaobject> <imageobject> <imagedata fileref="images/seam_editors/icon_exception.png"></imagedata> </imageobject> - </inlinemediaobject> - + </inlinemediaobject> + </entry> <entry>Add an exception rule</entry> - </row> - + </row> + </tbody> </tgroup> - </table> - + </table> + <para>Context menus are also available when you click either on an item or a blank space.</para> - - + + <para>A context menu called on a blank space of the diagram provides the following options:</para> <itemizedlist> <listitem><para><emphasis role="bold">Page</emphasis> creates a new page element on the diagram</para></listitem> @@ -2010,28 +2050,28 @@ <para>Rightclicking on a selected <code><page></code> element calls a context menu where you can choose the following options if you click on the <emphasis role="bold">New</emphasis> menu item: </para> - - - + + + <itemizedlist> <listitem><para><emphasis role="bold">Rule</emphasis> opens the <property moreinfo="none">Add Navigation Rule</property> dialog in which you can browse your project for a view page to set the view-id in the navigation rule and specify <emphasis role="bold">render</emphasis> or <emphasis role="bold">redirect</emphasis> navigation options </para></listitem> - <listitem><para><emphasis role="bold">Param</emphasis> calls a dialog box where you can define a parameter (using the - <code><param></code> - tag) for the + <listitem><para><emphasis role="bold">Param</emphasis> calls a dialog box where you can define a parameter (using the + <code><param></code> + tag) for the <code><page></code> element</para></listitem> </itemizedlist> - - + + <section> <title>Seam Pages Diagram Preferences</title> - - - - <para>In order to customize the layout of Diagram you can go to + + + + <para>In order to customize the layout of Diagram you can go to <property moreinfo="none">Window > Preferences > JBoss Tools > Web > Seam > Editors > Seam Pages Diagram</property>. </para> - + <figure float="0"> <title>Preferences of Seam Pages Diagram</title> <mediaobject> @@ -2042,15 +2082,15 @@ </figure> </section> </section> - - + + <section> <title>Tree Mode</title> - + <para>Tree Mode provides a wider range of options and way to edit and modify the pages.xml file.</para> - - - + + + <figure float="0"> <title>Seam Pages Editor: Tree View</title> <mediaobject> @@ -2059,19 +2099,19 @@ </imageobject> </mediaobject> </figure> - + <para> In this mode all elements and attributes of the page.xml file can be viewed and edited in a visual, user friendly way. </para> - + </section> - - + + <section> <title>Outline Support for Seam Pages Editor</title> - - + + <para>Seam Pages Editor provides <property moreinfo="none">Outline</property> view support. You can explore the pages.xml using Outline view in two modes: <property moreinfo="none">Tree</property> ( <inlinemediaobject> <imageobject> @@ -2082,11 +2122,11 @@ <imagedata fileref="images/seam_editors/outline_navigation.png"></imagedata> </imageobject> </inlinemediaobject> ).</para> - + <para> - The Diagram Navigation mode of Outline view gives a birds-view of the layout to allow quick navigation for large-scale applications. + The Diagram Navigation mode of Outline view gives a birds-view of the layout to allow quick navigation for large-scale applications. </para> - + <figure float="0"> <title>Outline view: Diagram Navigation mode</title> <mediaobject> @@ -2095,12 +2135,12 @@ </imageobject> </mediaobject> </figure> - - + + <para>The Tree mode shows a tree for every element in the pages.xml file. You can get a quick overview of the whole file. When selecting an element in the Outline view the related element is highlighted in the Graphical, Tree or Source page of Seam Pages Editor.</para> - - - + + + <figure float="0"> <title>Outline view: Tree mode</title> <mediaobject> @@ -2109,28 +2149,28 @@ </imageobject> </mediaobject> </figure> - - - - + + + + </section> - - + + </section> - - - - + + + + <section> - - + + <title>Seam Components Editor</title> - + <para>When editing <property moreinfo="none">components.xml</property> a structured tree editor is available in addition to pure source editing. It has a graphical view (Tree tab) and source (Source tab).</para> - + <figure float="0"> <title>component.xml Editor</title> <mediaobject> @@ -2139,10 +2179,10 @@ </imageobject> </mediaobject> </figure> - + <note> <title>Note:</title> - + <para>You can view and edit <property moreinfo="none">components.xml</property> and other xml files directly in the Project Explorer and Properties sheet without opening the components.xml editor.</para> @@ -2155,11 +2195,11 @@ </imageobject> </mediaobject> </figure> - + </section> - - - + + + <section id="SeamEditors"> <title>Main Features of Seam Editors</title> @@ -2243,18 +2283,18 @@ </figure> </section> - + </section> <section> <title>Content Assist for Page Descriptors</title> - - <para>Content Assist ( CA ) is available for Page Descriptors, - <property moreinfo="none">.page.xml</property> and <property moreinfo="none">page.xml</property> files. - Content Assist lets you easily compose a Page Descriptor file by suggesting elements and attributes. The suggestions are context dependent, which means that CA provides only the elements, attributes and in some cases values for the attributes, suitable in a particular place of your Page Descriptor. - + + <para>Content Assist ( CA ) is available for Page Descriptors, + <property moreinfo="none">.page.xml</property> and <property moreinfo="none">page.xml</property> files. + Content Assist lets you easily compose a Page Descriptor file by suggesting elements and attributes. The suggestions are context dependent, which means that CA provides only the elements, attributes and in some cases values for the attributes, suitable in a particular place of your Page Descriptor. + </para> <para> - Seam Pages Editor also supports code completion in EL-expressions suggesting you possible bean properties and methods. + Seam Pages Editor also supports code completion in EL-expressions suggesting you possible bean properties and methods. </para> </section> <section id="OpenOn"> @@ -2291,7 +2331,7 @@ </itemizedlist> <note> <title>Note:</title> - + <para>In this section were described only use cases special for Seam applications.For general information please read <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/jsf/html/editors.htm...">OpenOn section in Visual Web Tools Reference Guide</ulink>.</para> </note> @@ -2300,12 +2340,12 @@ <itemizedlist> <listitem><para>components or properties resolved using an EL expression;</para></listitem> <listitem><para>all actions described in pages.xml;</para></listitem> - <listitem><para>other .xhtml files that paths are specified in a current file;</para></listitem> + <listitem><para>other .xhtml files that paths are specified in a current file;</para></listitem> <listitem><para>image files that paths are set in the <emphasis> - <property moreinfo="none">value</property></emphasis> property.The files will be opened in the default system graphical editor.</para></listitem> + <property moreinfo="none">value</property></emphasis> property.The files will be opened in the default system graphical editor.</para></listitem> </itemizedlist> </listitem> - <listitem id="xmlFiles"> + <listitem id="xmlFiles"> <para>OpenOn is also supported in Page Descriptors (<property moreinfo="none">.page.xml</property> and <property moreinfo="none">pages.xml</property>). OpenOn allows you to navigate to Java beans as well as to view pages. You can <property moreinfo="none">Ctrl + left click</property> on a bean or on view page file (e.g. XTML file) to navigate to the file you clicked on. </para> @@ -2317,7 +2357,7 @@ </imageobject> </mediaobject> </figure> - <para>If you use Rule-based authorization with Drools in your Seam application you can apply OpenOn + <para>If you use Rule-based authorization with Drools in your Seam application you can apply OpenOn in <emphasis> <property moreinfo="none">components.xml</property></emphasis> to open the files containing rule definitions in the <emphasis> <property moreinfo="none">"rule-files"</property></emphasis> tag. @@ -2331,7 +2371,7 @@ </mediaobject> </figure> <para>You can also use OpenOn to open jBPM components that are described in Seam component descriptor. - Two places where it works are available: </para> + Two places where it works are available: </para> <itemizedlist> <listitem><para>inside <emphasis> <property moreinfo="none"><component></property></emphasis> definition;</para> @@ -2354,19 +2394,19 @@ </mediaobject> </figure></listitem> </itemizedlist> - </listitem> - <listitem id="javaFiles"> + </listitem> + <listitem id="javaFiles"> <para> OpenOn is also supported in seam components where <property moreinfo="none"> In annotation</property> is presented. - After pressing <property moreinfo="none">Ctrl + left click</property> on the seam component specified in <code>@In </code> you will get the possibility to open the file where the component is declarated as well as + After pressing <property moreinfo="none">Ctrl + left click</property> on the seam component specified in <code>@In </code> you will get the possibility to open the file where the component is declarated as well as all of the seam components where it is used in the next declarations:</para> <itemizedlist> <listitem><para>@Out</para></listitem> <listitem><para>@DataModel</para></listitem> <listitem><para>@Role</para></listitem> - <listitem><para>@Roles</para></listitem> + <listitem><para>@Roles</para></listitem> </itemizedlist> - + <figure float="0"> <title>OpenOn in Seam Component</title> <mediaobject> @@ -2421,7 +2461,7 @@ on normal Java projects you will have to go and add the Validation builder of your project . It is available in the properties of your project under <emphasis><property moreinfo="none">Validation</property>.</emphasis></para> - + <figure float="0"> <title>Enabling the Validation Builder</title> <mediaobject> @@ -2430,16 +2470,16 @@ </imageobject> </mediaobject> </figure> - + <para>The validations can be run manually by clicking <emphasis><property moreinfo="none">Validate</property></emphasis> via the context menu on your project (folder or file inside your project) which will execute all the active WTP validations. Following to the project's preferences under <emphasis> - <property moreinfo="none">Validation</property></emphasis> it's possible to enable/disable any validator. + <property moreinfo="none">Validation</property></emphasis> it's possible to enable/disable any validator. </para> - + <para>It's also possible to turn off the validation for some resource (a file, folder) inside your project via the <emphasis> <property moreinfo="none">Exclude Validation</property></emphasis> context menu option.</para> - + <figure float="0"> <title>Excluding Validation for the WebContent Folder</title> <mediaobject> @@ -2448,9 +2488,9 @@ </imageobject> </mediaobject> </figure> - + <para>As a result, if you've turned off the validation for a folder (or file), it is put to the excluded group of the Validation filters and be ignored during the validation.</para> - + <figure float="0"> <title>Validation Filters</title> <mediaobject> @@ -2465,7 +2505,7 @@ </chapter> -<chapter id="seam_view" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/seam/docs/reference/en/modules/seam_view.xml" xreflabel="seam_view"> +<chapter id="seam_view" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/seam/docs/reference/en/modules/seam_view.xml" xreflabel="seam_view"> <?dbhtml filename="seam_view.html"?> <chapterinfo> <keywordset> @@ -2474,126 +2514,126 @@ <keyword>JBDS</keyword> </keywordset> </chapterinfo> - + <title>Seam Views</title> - + <section> <title>Seam Components View</title> - + <para>This chapter introduces you with Seam Components View.</para> <para>The <property moreinfo="none">Seam Components View</property> is available from Seam perspective. It provides a list of seam components found in a project.</para> - + <figure float="0"> <title>Seam Components View</title> - <mediaobject> + <mediaobject> <imageobject> <imagedata fileref="images/seam_view/seam_view_1.png"></imagedata> </imageobject> </mediaobject> </figure> - + <para>The Seam Components View can show a components default scope in two ways:</para> - + <itemizedlist> <listitem><para>as labels on each component (click on the triangular symbol at the top of the Seam Components View page and select <emphasis><property moreinfo="none">Scope Presentation > Label</property></emphasis>)</para></listitem> </itemizedlist> - + <figure float="0"> <title>Label Scope Presentation of Seam Components</title> - <mediaobject> + <mediaobject> <imageobject> <imagedata fileref="images/seam_view/seam_view_2.png"></imagedata> </imageobject> </mediaobject> </figure> - + <itemizedlist> <listitem><para>as a node per scope where the components are grouped under a node representing its default scope.</para></listitem> </itemizedlist> - + <figure float="0"> <title>Node Scope Presentation of Seam Components</title> - <mediaobject> + <mediaobject> <imageobject> <imagedata fileref="images/seam_view/seam_view_3.png"></imagedata> </imageobject> </mediaobject> </figure> - + <para>The Seam Packages can be presented in two ways:</para> - + <itemizedlist> <listitem><para>Flat</para></listitem> </itemizedlist> - + <figure float="0"> <title>Flat Presentation of Seam Packages</title> - <mediaobject> + <mediaobject> <imageobject> <imagedata fileref="images/seam_view/seam_view_4.png"></imagedata> </imageobject> </mediaobject> </figure> - + <itemizedlist> <listitem><para>Hierarchical</para></listitem> </itemizedlist> - + <figure float="0"> <title>Hierarchical Presentation of Seam Packages</title> - <mediaobject> + <mediaobject> <imageobject> <imagedata fileref="images/seam_view/seam_view_5.png"></imagedata> </imageobject> </mediaobject> </figure> - + <para>The Seam Component View can be filtered by choosing <property moreinfo="none">Customize View</property>.</para> - + <figure float="0"> <title>Customize View</title> - <mediaobject> + <mediaobject> <imageobject> <imagedata fileref="images/seam_view/seam_view_6.png"></imagedata> </imageobject> </mediaobject> </figure> - - <para>Select the <emphasis><property moreinfo="none">Seam Components from Libraries</property></emphasis> under the Filters tab. + + <para>Select the <emphasis><property moreinfo="none">Seam Components from Libraries</property></emphasis> under the Filters tab. This will make the view ignore components defined in jars. This will hide the many built-in Seam components and leave only those that are actually defined in the project or have been actively configured via components.xml. Therefore, deselecting the filter will show you all available components.</para> <para>Selecting the <emphasis><property moreinfo="none">Seam Components from Referenced Projects</property></emphasis> will hide the components that dependent on other project.</para> - + <figure float="0"> <title>Available Seam Component View Customizations</title> - <mediaobject> + <mediaobject> <imageobject> <imagedata fileref="images/seam_view/seam_view_7.png"></imagedata> </imageobject> </mediaobject> </figure> - + </section> - + <section> <title>Project Explorer integration</title> - + <para>If you don't like to have a view for every piece of information in Eclipse, the content of the Seam Components view is also available as a node in the built-in Project Explorer (not Package Explorer!) view in Eclipse.</para> - + <figure float="0"> <title>Seam Components in Project Explorer</title> - <mediaobject> + <mediaobject> <imageobject> <imagedata fileref="images/seam_view/seam_view_8.png"></imagedata> </imageobject> </mediaobject> </figure> - + </section> - + </chapter> -<chapter id="seam_preferences" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/seam/docs/reference/en/modules/seam_preferences.xml" xreflabel="seam_preferences"> +<chapter id="seam_preferences" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/seam/docs/reference/en/modules/seam_preferences.xml" xreflabel="seam_preferences">  <?dbhtml filename="seam_preferences.html"?> <chapterinfo> @@ -2676,8 +2716,8 @@ can select whether the Seam validator displays an error, a warning or just ignore the EL Syntax error.</para> <note><para>There are references made between each EL and variable name, so you can revalidate a particular EL if a context variable was changed. This makes parsing of each resource with referenced ELs much faster.</para></note> - - + + <figure float="0"> <title>Severity Preference for EL Syntax</title> <mediaobject> @@ -2686,9 +2726,9 @@ </imageobject> </mediaobject> </figure> - + <para>The <emphasis> - <property moreinfo="none">Revalidate unresolved ELs automatically</property></emphasis> option is enabled by default. + <property moreinfo="none">Revalidate unresolved ELs automatically</property></emphasis> option is enabled by default. If necessary, you can uncheck it. It may increase a performance for big complex projects.</para> <para>In the upper right corner of the Seam Validator preferences page there is a <emphasis><property moreinfo="none">Configure Project @@ -2775,8 +2815,8 @@ <tip> <title>Tip:</title> - <para><diffmk:wrapper diffmk:change="changed">On the figure above fields for configuring Seam artifacts are unavailable because Seam - Runtime is not selected.</diffmk:wrapper></para> + <para>On the figure above fields for configuring Seam artifacts are unavailable because Seam + Runtime is not selected.</para> </tip> <para>In Seam Wizards (New Action, Form, Entity, Conversation, Generate Entities) you can @@ -2806,7 +2846,7 @@ <para>To enable it, you should call the context menu for a Seam project and select <emphasis><property moreinfo="none">JBoss Tools > Add Custom Capabilities</property>.</emphasis> Then check the needed modules and press <emphasis><property moreinfo="none">Finish</property>.</emphasis></para> - + <figure float="0"> <title> Custom Capabilities be added to Seam Project</title> <mediaobject> @@ -2817,7 +2857,7 @@ </figure> <para>The next page displays all the updates that have been made to the project.</para> - + <figure float="0"> <title>Adding Custom Capabilities to Seam Project</title> <mediaobject> @@ -2826,13 +2866,13 @@ </imageobject> </mediaobject> </figure> - + </section> </chapter> -<chapter id="seam_refactoring" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/seam/docs/reference/en/modules/seam_refactoring.xml" xreflabel="seam_refactoring"> +<chapter id="seam_refactoring" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/seam/docs/reference/en/modules/seam_refactoring.xml" xreflabel="seam_refactoring"> <?dbhtml filename="seam_refactoring.html"?> <chapterinfo> <keywordset> @@ -2842,70 +2882,71 @@ <keyword>rename</keyword> </keywordset> </chapterinfo> - <title><diffmk:wrapper diffmk:change="changed">Seam Refactoring Tools</diffmk:wrapper></title> - <para><diffmk:wrapper diffmk:change="added">The goal of Seam components refactoring is to make system-wide code changes without affecting the behavior of the program. - The Seam module of </diffmk:wrapper><property moreinfo="none"><diffmk:wrapper diffmk:change="changed">JBoss Tools</diffmk:wrapper></property><diffmk:wrapper diffmk:change="added"> provides assistance in easily code refactoring.</diffmk:wrapper></para> - - <para><diffmk:wrapper diffmk:change="changed">Starting from Jboss Tools M4 refactoring functionality became also available for managed beans, method and properties used in ELs. - Thus now Seam refactoring tools include the next refactoring operations:</diffmk:wrapper></para> - + <title>Seam Refactoring Tools</title> + <para>The goal of Seam components refactoring is to make system-wide code changes without affecting the behavior of the program. + The Seam module of <property moreinfo="none">JBoss Tools</property> provides assistance in easily code refactoring.</para> + + <para>Starting from Jboss Tools M4 refactoring functionality became also available for managed beans, method and properties used in ELs. + Thus now Seam refactoring tools include the next refactoring operations:</para> + <itemizedlist> - <listitem><para><link diffmk:change="added" linkend="renaming_seam_components"><diffmk:wrapper diffmk:change="added">Renaming Seam components</diffmk:wrapper></link></para></listitem> - <listitem><para><link diffmk:change="added" linkend="renaming_seam_context_vars"><diffmk:wrapper diffmk:change="added">Renaming Seam context variables in EL</diffmk:wrapper></link></para></listitem> + <listitem><para><link linkend="renaming_seam_components">Renaming Seam components</link></para></listitem> + <listitem><para><link linkend="renaming_seam_context_vars">Renaming Seam context variables in EL</link></para></listitem> </itemizedlist> - - <para><diffmk:wrapper diffmk:change="added">Refactoring commands are available from the context menus of several views and editors and use a standard Eclipse refactoring wizard. - For details, see </diffmk:wrapper><link diffmk:change="added" linkend="RefactornigWizard"><diffmk:wrapper diffmk:change="added">"Using the Refactoring Wizard"</diffmk:wrapper></link><diffmk:wrapper diffmk:change="added"> later in this chapter.</diffmk:wrapper></para> - - <note diffmk:change="added"> - <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">Note:</diffmk:wrapper></title> - <para><diffmk:wrapper diffmk:change="added">Seam refactoring could be only performed in the file that is not marked as </diffmk:wrapper><emphasis diffmk:change="added"><property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">Read only</diffmk:wrapper></property></emphasis><diffmk:wrapper diffmk:change="added"> in its properties.</diffmk:wrapper></para> + + <para>Refactoring commands are available from the context menus of several views and editors and use a standard Eclipse refactoring wizard. + For details, see <link linkend="RefactornigWizard">"Using the Refactoring Wizard"</link> later in this chapter.</para> + + <note> + <title>Note:</title> + <para>Seam refactoring could be only performed in the file that is not marked as <emphasis><property moreinfo="none">Read only</property></emphasis> in its properties.</para> </note> - - <figure diffmk:change="added" float="0"> - <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">Properties View for Java File</diffmk:wrapper></title> - <mediaobject diffmk:change="added"> - <imageobject diffmk:change="added"> - <imagedata diffmk:change="added" fileref="images/seam_refactoring/seam_refactor10.png"></imagedata> + + <figure float="0"> + <title>Properties View for Java File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/seam_refactoring/seam_refactor10.png"></imagedata> </imageobject> </mediaobject> </figure> - + <section id="RefactornigWizard"> - <title><diffmk:wrapper diffmk:change="changed">Using the Refactorinig Wizard</diffmk:wrapper></title> - <para>This wizard is opened always when the user clicks <property moreinfo="none">Rename Seam Component</property>/<property moreinfo="none">Rename Seam Context Variable</property>/<property moreinfo="none">Rename</property> command in any - of the mentioned views. + <title>Using the Refactorinig Wizard</title> + <para>This wizard is opened always when the user clicks the <emphasis><property moreinfo="none">Rename Seam Component</property>,</emphasis> + <emphasis><property moreinfo="none">Rename Seam Context Variable</property></emphasis> + or <emphasis><property moreinfo="none">Rename</property></emphasis> command in any of the views/editors mentioned later in this chapter. </para> - + <figure float="0"> - <title>Refactoring Seam wizard</title> + <title>Refactoring Wizard</title> <mediaobject> <imageobject> <imagedata fileref="images/seam_refactoring/seam_refactor2.png"></imagedata> </imageobject> </mediaobject> </figure> - - <para>In the <property moreinfo="none"><diffmk:wrapper diffmk:change="changed">Seam Components name</diffmk:wrapper></property><diffmk:wrapper diffmk:change="changed"> field you should enter a new name of the component, - then click </diffmk:wrapper><property moreinfo="none">Next</property> and follow the next wizard steps: + + <para>In the <property moreinfo="none">Seam Components name</property> field you should enter a new name of the component, + then click <property moreinfo="none">Next</property> and follow the next wizard steps: </para> - + <figure float="0"> - <title>Navigating between the differences</title> + <title>Navigating Between the Differences</title> <mediaobject> <imageobject> <imagedata fileref="images/seam_refactoring/seam_refactor3.png"></imagedata> </imageobject> </mediaobject> </figure> - - <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">As you see, when performing a refactoring operation, you can preview all of the changes resulting from a refactoring - action before you choose to carry them out.</diffmk:wrapper></para> - - <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">The view represents two windows: one with the original source code and the other with refactored one.</diffmk:wrapper></para> - - <para><diffmk:wrapper diffmk:change="changed">With the help of - </diffmk:wrapper><inlinemediaobject> <imageobject> + + <para>As you see, when performing a refactoring operation, you can preview all of the changes resulting from a refactoring + action before you choose to carry them out.</para> + + <para>The view represents two windows: one with the original source code and the other with refactored one.</para> + + <para>With the help of + <inlinemediaobject> <imageobject> <imagedata fileref="images/seam_refactoring/butt1.png"></imagedata> </imageobject></inlinemediaobject>, <inlinemediaobject> <imageobject> @@ -2916,10 +2957,10 @@ </imageobject></inlinemediaobject>, <inlinemediaobject> <imageobject> <imagedata fileref="images/seam_refactoring/butt4.png"></imagedata> - </imageobject></inlinemediaobject><diffmk:wrapper diffmk:change="changed"> buttons you can quickly navigate between the differences in the code. - If you don't agree with some changes you can't undo them but you can remove the class from the list of classes that need refactoring. - </diffmk:wrapper></para> - + </imageobject></inlinemediaobject> buttons you can quickly navigate between the differences in the code. + If you don't agree with some changes you can't undo them but you can remove the class from the list of classes that need refactoring. + </para> + <figure float="0"> <title>List of classes that need refactoring </title> @@ -2929,111 +2970,265 @@ </imageobject> </mediaobject> </figure> - - <para>To apply the changes click <emphasis><property moreinfo="none">Finish</property><diffmk:wrapper diffmk:change="added">.</diffmk:wrapper></emphasis></para> - - <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">Renaming the selected seam component also corrects all references to the + + <para>To apply the changes click <emphasis><property moreinfo="none">Finish</property>.</emphasis></para> + + <para>Renaming the selected seam component corrects all references to the component (also in other files in the project). Renaming a type doesn't allow to rename similarly named variables and methods. - </diffmk:wrapper></para> + </para> </section> - - <section id="renaming_seam_components"> - <title><diffmk:wrapper diffmk:change="changed">Renaming Seam Components</diffmk:wrapper></title> - + + <section id="renaming_seam_components"> + <title>Renaming Seam Components</title> + <para>Renaming a Seam component could be performed in the:</para> - + <itemizedlist> <listitem><para><link linkend="JavaEditor">Java editor</link></para></listitem> <listitem><para><link linkend="SeamComponents">Seam Components view</link></para></listitem> <listitem><para><link linkend="components_xml_editor">Tree view of the components.xml editor</link></para></listitem> </itemizedlist> - + <section id="JavaEditor"> - <title><diffmk:wrapper diffmk:change="changed">Renaming Seam Components in the Java Editor</diffmk:wrapper></title> - <para><diffmk:wrapper diffmk:change="changed">If you want to rename certain seam component using Java Editor,first of all it's necessary to open it. - If you don't know ,where the seam component is declared,use </diffmk:wrapper><link linkend="open_seam_component">Open Seam Components icon</link><diffmk:wrapper diffmk:change="changed">. - - </diffmk:wrapper></para> - <para>To open the rename Seam Component command in Java Editor it's necessary to left click the file <emphasis><property moreinfo="none">>Seam Refactor>Rename Seam Component</property></emphasis><diffmk:wrapper diffmk:change="changed">. - </diffmk:wrapper></para> + <title>Renaming Seam Components in the Java Editor</title> + <para>If you want to rename certain seam component using Java editor, first of all it's necessary to open it. + If you don't know, where the seam component is declared, use <link linkend="open_seam_component">Open Seam Components</link> icon.</para> + <para>To rename a Seam component in the Java editor it's necessary to select the component, left click the file and then select + <emphasis><property moreinfo="none">Seam Refactor > Rename Seam Component</property>.</emphasis> + </para> <figure float="0"> - <title>Opening Refactoring wizard in Java Editor</title> + <title>Opening Refactoring Wizard in Java Editor</title> <mediaobject> <imageobject> <imagedata fileref="images/seam_refactoring/seam_refactor1.png"></imagedata> </imageobject> </mediaobject> </figure> + + <para>For details, see also the movie, + <ulink url="http://docs.jboss.org/tools/movies/demos/rename_seam_components_java/rena...">"Renaming a Seam component in the Java Editor"</ulink>.</para> </section> - + <section id="SeamComponents"> - <title><diffmk:wrapper diffmk:change="changed">Renaming Seam Components in the Seam Components View</diffmk:wrapper></title> - <para>To open <property moreinfo="none"><diffmk:wrapper diffmk:change="changed">Refactoring</diffmk:wrapper></property><diffmk:wrapper diffmk:change="changed"> wizard in the </diffmk:wrapper><property moreinfo="none">Seam Components</property><diffmk:wrapper diffmk:change="changed"> view - you should left click the component you wants to open and choose </diffmk:wrapper><property moreinfo="none">Rename Seam Component</property> option.</para> - + <title>Renaming Seam Components in the Seam Components View</title> + <para>To open the <property moreinfo="none">Refactoring</property> wizard in the <property moreinfo="none">Seam Components</property> view + you should left click the component you want to open and choose <property moreinfo="none">Rename Seam Component</property> option.</para> + <figure float="0"> - <title><diffmk:wrapper diffmk:change="changed">Opening Refactoring Wizard in Seam Components View</diffmk:wrapper></title> + <title>Opening Refactoring Wizard in Seam Components View</title> <mediaobject> <imageobject> <imagedata fileref="images/seam_refactoring/seam_refactor5.png"></imagedata> </imageobject> </mediaobject> </figure> + + <para>For details, see also the movie, + <ulink url="http://docs.jboss.org/tools/movies/demos/rename_seam_components_comp_view...">"Renaming a Seam component in the Seam Components view"</ulink>.</para> </section> - - <section id="components_xml_editor"> - <title><diffmk:wrapper diffmk:change="changed">Renaming Seam Components in the Seam Components Editor</diffmk:wrapper></title> - <para>When you open <literal diffmk:change="added" moreinfo="none">components.xml</literal><diffmk:wrapper diffmk:change="added"> file using </diffmk:wrapper><property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">JBossTools XML Editor</diffmk:wrapper></property><diffmk:wrapper diffmk:change="changed">, open the - </diffmk:wrapper><property moreinfo="none"><diffmk:wrapper diffmk:change="changed">Refactoring</diffmk:wrapper></property><diffmk:wrapper diffmk:change="added"> wizard in the Tree tab by left-clicking the component in - </diffmk:wrapper><property moreinfo="none">components</property><diffmk:wrapper diffmk:change="changed"> area and choosing </diffmk:wrapper><property moreinfo="none">Rename</property><diffmk:wrapper diffmk:change="changed"> option.</diffmk:wrapper></para> - + + <section id="components_xml_editor"> + <title>Renaming Seam Components in the Seam Components Editor</title> + <para>When you open <literal moreinfo="none">components.xml</literal> file using <property moreinfo="none">JBoss Tools XML Editor</property>, open the + <property moreinfo="none">Refactoring</property> wizard in the Tree tab by left-clicking the component in + <property moreinfo="none">components</property> area and choosing <property moreinfo="none">Rename</property> option.</para> + <figure float="0"> - <title><diffmk:wrapper diffmk:change="changed">Opening Refactoring Wizard in </diffmk:wrapper><emphasis><property moreinfo="none">components.xml</property></emphasis><diffmk:wrapper diffmk:change="changed"> File</diffmk:wrapper></title> + <title>Opening Refactoring Wizard in <emphasis><property moreinfo="none">components.xml</property></emphasis> File</title> <mediaobject> <imageobject> <imagedata fileref="images/seam_refactoring/seam_refactor6.png"></imagedata> </imageobject> </mediaobject> </figure> - </section> - </section> - <section diffmk:change="added" id="renaming_seam_context_vars"> - <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">Renaming Seam Context Variables in EL</diffmk:wrapper></title> + + <para>For details, see also the movie, + <ulink url="http://docs.jboss.org/tools/movies/demos/rename_seam_components_comp_xml/...">"Renaming a Seam component in the components.xml file"</ulink>.</para> + </section> + + </section> + + <section id="renaming_seam_context_vars"> + <title>Renaming Seam Context Variables in EL</title> + + <para>Renaming a Seam context variables in EL could be executed in <literal moreinfo="none">.java</literal>, <literal moreinfo="none">.xml</literal>, <literal moreinfo="none">.jsp</literal>, + <literal moreinfo="none">.xhtml</literal> and <literal moreinfo="none">.properties</literal> files in Seam projects using + the context menu command <emphasis><property moreinfo="none">Seam Refactor > Rename Seam Context Variable</property>.</emphasis></para> - <para><diffmk:wrapper diffmk:change="added">Renaming a Seam context variables in EL could be executed in </diffmk:wrapper><literal diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">.java</diffmk:wrapper></literal><diffmk:wrapper diffmk:change="added">, </diffmk:wrapper><literal diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">.xml</diffmk:wrapper></literal><diffmk:wrapper diffmk:change="added">, </diffmk:wrapper><literal diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">.jsp</diffmk:wrapper></literal><diffmk:wrapper diffmk:change="added">, - </diffmk:wrapper><literal diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">.xhtml</diffmk:wrapper></literal><diffmk:wrapper diffmk:change="added"> and </diffmk:wrapper><literal diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">.properties</diffmk:wrapper></literal><diffmk:wrapper diffmk:change="added"> files in Seam projects using - the context menu command </diffmk:wrapper><emphasis diffmk:change="added"><property moreinfo="none"><diffmk:wrapper diffmk:change="changed">Seam Refactor > Rename Seam Context Variable</diffmk:wrapper></property><diffmk:wrapper diffmk:change="added">.</diffmk:wrapper></emphasis></para> - <figure float="0"> - <title><diffmk:wrapper diffmk:change="changed">Refactoring Seam Context Variable in .properties File</diffmk:wrapper></title> + <title>Refactoring Seam Context Variable in .properties File</title> <mediaobject> <imageobject> - <imagedata fileref="images/seam_refactoring/seam_refactor9.png"/> + <imagedata fileref="images/seam_refactoring/seam_refactor9.png"></imagedata> </imageobject> </mediaobject> </figure> <figure float="0"> - <title><diffmk:wrapper diffmk:change="changed">Opening Refactoring wizard in components.xml file</diffmk:wrapper></title> + <title>Opening Refactoring wizard in components.xml file</title> <mediaobject> <imageobject> - <imagedata fileref="images/seam_refactoring/seam_refactor7.png"/> + <imagedata fileref="images/seam_refactoring/seam_refactor7.png"></imagedata> </imageobject> </mediaobject> </figure> - + <figure float="0"> - <title><diffmk:wrapper diffmk:change="changed">Opening Refactoring wizard in .html file</diffmk:wrapper></title> + <title>Opening Refactoring wizard in .html file</title> <mediaobject> <imageobject> - <imagedata fileref="images/seam_refactoring/seam_refactor8.png"/> + <imagedata fileref="images/seam_refactoring/seam_refactor8.png"></imagedata> </imageobject> </mediaobject> </figure> + + <para>For details, see also a set of movies about renaming Seam context variables in EL in different locations:</para> + <itemizedlist> + <listitem> + <para><ulink url="http://docs.jboss.org/tools/movies/demos/rename_context_variables_java/re...">In the Java editor</ulink></para> + </listitem> + <listitem> + <para><ulink url="http://docs.jboss.org/tools/movies/demos/rename_context_variables_propert...">In the JBoss Tools Properties Editor</ulink></para> + </listitem> + <listitem> + <para><ulink url="http://docs.jboss.org/tools/movies/demos/rename_context_variables_xml/ren...">In the XML editor</ulink></para> + </listitem> + <listitem> + <para><ulink url="http://docs.jboss.org/tools/movies/demos/rename_context_variables_vpe/ren...">In the Visual Page Editor</ulink></para> + </listitem> + </itemizedlist> </section> </chapter> -<chapter id="crud_database_application" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/seam/docs/reference/en/modules/crud_database_application.xml" xreflabel="crud_database_application"> + + + + +<chapter id="adding_seam_support_to_ear_project" role="new" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/seam/docs/reference/en/modules/adding_seam_support_to_ear_project.xml" xreflabel="adding_seam_support_to _ear_project"> + <?dbhtml filename="adding_seam_support_to _ear_project.html"?> + <chapterinfo> + <keywordset> + <keyword>EAR</keyword> + <keyword>Seam</keyword> + <keyword></keyword> + <keyword></keyword> + </keywordset> + </chapterinfo> + + <title>Adding Seam support to EAR project</title> + <para>From this chapter you will find out how to add Seam support to EAR project</para> + <para>For example you have several WTP projects:</para> + + <itemizedlist> + <listitem><para> seamproject-ear (You can create WTP EAR project using New -> Project -> Java EE -> Enterprise Application Project wizard)</para></listitem> + <listitem><para> seamproject-ejb (You can create WTP EJB project using New -> Project -> EJB -> EJB Project wizard)</para></listitem> + <listitem><para> seamproject-war (You can create WTP WEB project using New -> Project -> Web -> Dynamic Web Project wizard)</para></listitem> + </itemizedlist> + + <tip><title>Tip</title> + <para>You can add as many EJBs modules as you want just doing the same for each EJB project.</para></tip> + + <figure float="0"> + <title>WTP Projects</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/adding_seam_support_to_project/wtp_projects.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>Make sure EJB and WAR are included in EAR as modules (Properties for seamproject-ear -> Java EE Module Dependencies)</para> + + <figure float="0"> + <title>Java EE Module Dependencies</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/adding_seam_support_to_project/java_ee_module_dependencies.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>Make sure there is jboss-seam.jar in application.xml as well:</para> + + <figure float="0"> + <title>Java EE Module Dependencies</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/adding_seam_support_to_project/application_xml_with_jboss-seam_jar.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + + <para>Then include libs from EAR to EJB Manifest Class-Path (Properties for seamproject-ejb -> Java EE Module Dependencies)</para> + + <figure float="0"> + <title>Including Libs from EAR to EJB Manifest Class-Path</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/adding_seam_support_to_project/including_libs_from_ear_to_ejb_manifest_class-path.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>Include libs from EAR and seamproject-ejb.jar to WAR Manifest Class-Path (Properties for seamproject-war -> Java EE Module Dependencies)</para> + + <figure float="0"> + <title>Including Libs from EAR and seamproject-ejb.jar to WAR Manifest Class-Path</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/adding_seam_support_to_project/including_libs_from_ear_to_war_manifest_class-path.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>Thus we have set our WTP EAR/EJB/WAR projects and now we are ready to add Seam support to them:</para> + + <para>First you have to add Seam support to WAR project: Properties for seamproject-war -> Seam Settings</para> + + + <figure float="0"> + <title>Adding Seam Support to WAR Project</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/adding_seam_support_to_project/adding_seam_support_to_war_project.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + + <para>Set seamproject-war as Main Seam project. All other settings mostly are used by New Seam Entity/Action/Form/Conversation/... Wizards. Thus you can set them as you wish.</para> + + <para>Then you can add Seam support to EJB project: Properties for seamproject-war -> Seam Settings</para> + + <figure float="0"> + <title>Adding Seam Support to EJB Project</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/adding_seam_support_to_project/adding_seam_support_to_ejb_project.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>It&s important to set seamproject-war project as main Seam project there.</para> + <para>It will allow Seam Tools to use one common Seam model for seamproject-ejb and seamproject-war projects.</para> + + <para>The last step is to clean/build the projects</para> + + <para>That is all. You have added Seam support to your EAR project. </para> + + <figure float="0"> + <title>Added Seam Support to EAR Project</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/adding_seam_support_to_project/added_seam_support_to_ear_project.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + +</chapter> + +<chapter id="crud_database_application" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/seam/docs/reference/en/modules/crud_database_application.xml" xreflabel="crud_database_application"> <?dbhtml filename="crud_database_application.html"?> <chapterinfo> <keywordset> @@ -3516,7 +3711,8 @@ </chapter> -<chapter id="crud_application_walkthrough" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/seam/docs/reference/en/modules/crud_application_walkthrough.xml" xreflabel="crud_application_walkthrough"> + +<chapter id="crud_application_walkthrough" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/seam/docs/reference/en/modules/crud_application_walkthrough.xml" xreflabel="crud_application_walkthrough"> <?dbhtml filename="crud_application_walkthrough.html"?> <chapterinfo> <keywordset> @@ -3647,7 +3843,7 @@ </chapter> -<chapter id="testNG" xml:base="file:///home/ochikvina/WORK/for_compare/jbosstools-3.1.0.CR1/seam/docs/reference/en/modules/testng.xml" xreflabel="testNG"> +<chapter id="testNG" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/seam/docs/reference/en/modules/testng.xml" xreflabel="testNG"> <?dbhtml filename="testNG.html"?> <chapterinfo> <keywordset> @@ -3742,27 +3938,27 @@ </listitem> </itemizedlist> - <figure> + <figure float="0"> <title>Seam-test Project</title> <mediaobject> <imageobject> - <imagedata fileref="images/testng/testng_5.png"/> + <imagedata fileref="images/testng/testng_5.png"></imagedata> </imageobject> </mediaobject> </figure> <itemizedlist> <listitem> - <para>Add Seam Action to your project via <emphasis><property>File > New > Seam + <para>Add Seam Action to your project via <emphasis><property moreinfo="none">File > New > Seam Action</property>.</emphasis></para> </listitem> </itemizedlist> - <figure> + <figure float="0"> <title>Seam Action Creation</title> <mediaobject> <imageobject> - <imagedata fileref="images/testng/testng_6.png"/> + <imagedata fileref="images/testng/testng_6.png"></imagedata> </imageobject> </mediaobject> </figure> @@ -3774,28 +3970,28 @@ </listitem> </itemizedlist> - <figure> + <figure float="0"> <title>New Seam Action Wizard</title> <mediaobject> <imageobject> - <imagedata fileref="images/testng/testng_7.png"/> + <imagedata fileref="images/testng/testng_7.png"></imagedata> </imageobject> </mediaobject> </figure> <itemizedlist> <listitem> - <para>When Action is created you will see <property>actionPage.xhtml</property> in - Package Explorer view. <property>ActionBean.java</property> will be + <para>When Action is created you will see <property moreinfo="none">actionPage.xhtml</property> in + Package Explorer view. <property moreinfo="none">ActionBean.java</property> will be automatically opened in Java Editor.</para> </listitem> </itemizedlist> - <figure> + <figure float="0"> <title>Created Action</title> <mediaobject> <imageobject> - <imagedata fileref="images/testng/testng_8.png" scale="70"/> + <imagedata fileref="images/testng/testng_8.png" scale="70"></imagedata> </imageobject> </mediaobject> </figure> @@ -3803,28 +3999,28 @@ <itemizedlist> <listitem> - <para>Select <property>ActionLocalTest.xml</property> in Seam-test project and run - the test with right click <emphasis><property>Run As > TestNG + <para>Select <property moreinfo="none">ActionLocalTest.xml</property> in Seam-test project and run + the test with right click <emphasis><property moreinfo="none">Run As > TestNG Suite</property>.</emphasis></para> </listitem> </itemizedlist> <tip><para>OpenOn is available in testNG XML files opened in JBoss XML Editor</para></tip> - <figure> + <figure float="0"> <title>Running TestNG</title> <mediaobject> <imageobject> - <imagedata fileref="images/testng/testng_9.png"/> + <imagedata fileref="images/testng/testng_9.png"></imagedata> </imageobject> </mediaobject> </figure> <para>The test process will start and its output will be written in Console View.</para> - <figure> + <figure float="0"> <title>Test is Finished</title> <mediaobject> <imageobject> - <imagedata fileref="images/testng/testng_10.png" scale="70"/> + <imagedata fileref="images/testng/testng_10.png" scale="70"></imagedata> </imageobject> </mediaobject> </figure> @@ -3833,20 +4029,20 @@ <itemizedlist> <listitem> <para>After running TestNG you will have the test results in <emphasis> - <property>test-output</property> + <property moreinfo="none">test-output</property> </emphasis> folder in Seam-test project (press F5 to refresh the Package - Explorer view). Open <property>index.html</property> file with Web Browser or + Explorer view). Open <property moreinfo="none">index.html</property> file with Web Browser or simply use the TestNG view.</para> </listitem> </itemizedlist> <para>The below view shows a successful run of the test.</para> - <figure> + <figure float="0"> <title>Viewing the Test Results</title> <mediaobject> <imageobject> - <imagedata fileref="images/testng/testng_11.png" scale="70"/> + <imagedata fileref="images/testng/testng_11.png" scale="70"></imagedata> </imageobject> </mediaobject> </figure> @@ -3854,24 +4050,24 @@ <para>You can see the test results in Web Browser.</para> - <figure> + <figure float="0"> <title>Test Results in Browser</title> <mediaobject> <imageobject> - <imagedata fileref="images/testng/testng_12.png" scale="70"/> + <imagedata fileref="images/testng/testng_12.png" scale="70"></imagedata> </imageobject> </mediaobject> </figure> <para>After clicking on <emphasis> - <property>ActionLocal Tests</property> + <property moreinfo="none">ActionLocal Tests</property> </emphasis> link you will see the Results for ActionLocal Tests.</para> - <figure> + <figure float="0"> <title>Test Information</title> <mediaobject> <imageobject> - <imagedata fileref="images/testng/testng_13.png" scale="70"/> + <imagedata fileref="images/testng/testng_13.png" scale="70"></imagedata> </imageobject> </mediaobject> </figure> @@ -3879,11 +4075,11 @@ <para>Select a result on the left-hand pane and its details will be displayed on the right-hand one.</para> - <figure> + <figure float="0"> <title>ActionLocal Test Details</title> <mediaobject> <imageobject> - <imagedata fileref="images/testng/testng_14.png"/> + <imagedata fileref="images/testng/testng_14.png"></imagedata> </imageobject> </mediaobject> </figure> @@ -3891,80 +4087,83 @@ <para>Thus with Seam tooling you can easily take advantage of TestNG framework. As you can see, it generates its own TestNG project as a separate module within which you can easily monitor the tests execution and their output.</para> - + </section> </chapter> -<chapter id="seam_faq" xreflabel="seam_faq"> + + +<chapter id="seam_faq" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/seam/docs/reference/en/modules/seam_faq.xml" xreflabel="seam_faq"> <?dbhtml filename="vwt_faq.html"?> <title>FAQ</title> - + <section id="seam_question_1"> <title>How to get Code Assist for Seam specific resources in an externally generated project?</title> - + <para>To get Code Assist for Seam specific resources in an externally generated project, you should enable Seam features in Project Preferences. Right click an imported project and navigate <emphasis> - <property>Properties > Seam Settings</property>.</emphasis> Check <emphasis> - <property>Seam support</property> + <property moreinfo="none">Properties > Seam Settings</property>.</emphasis> Check <emphasis> + <property moreinfo="none">Seam support</property> </emphasis> box to enable all available <link linkend="project_pref">Seam Settings</link>.</para> </section> - + <section id="seam_question_2"> <title>How to import an example Seam project from jboss-eap directory?</title> - + <para>To import an example Seam project from <emphasis> - <property>jboss-eap</property> + <property moreinfo="none">jboss-eap</property> </emphasis> into your working directory, you should perform the following steps:</para> - + <itemizedlist> <listitem> <para>Go to <emphasis> - <property>New > Other > Java Project from Existing Buildfile</property> + <property moreinfo="none">New > Other > Java Project from Existing Buildfile</property> </emphasis></para> </listitem> - + <listitem> <para>Point to the <emphasis> - <property>build.xml</property> + <property moreinfo="none">build.xml</property> </emphasis> of any chosen project by pressing <emphasis> - <property>Browse</property> + <property moreinfo="none">Browse</property> </emphasis> button</para> </listitem> - + <listitem> <para>Hit <emphasis> - <property>Finish</property> + <property moreinfo="none">Finish</property> </emphasis> to open the project</para> </listitem> </itemizedlist> - + <para>As these seam examples are non WTP projects, next you should enable Seam support for them. To do that, right click the project and go to <emphasis> - <property>Properties > Seam Settings</property>.</emphasis></para> + <property moreinfo="none">Properties > Seam Settings</property>.</emphasis></para> </section> - + <section id="seam_question_3"> <title>How to change the deploy folders for Seam source code from src/hot and src/main?</title> - + <para>You should right-click the project, select <emphasis> - <property>Properties > Java Build Path</property>,</emphasis> then switch to the <emphasis> - <property>Source tab</property>,</emphasis> select the output folder for <emphasis> - <property>src/hot</property></emphasis> (<emphasis> - <property>src/main</property>)</emphasis> and click <emphasis> - <property>Edit</property></emphasis> to change their output location.</para> - + <property moreinfo="none">Properties > Java Build Path</property>,</emphasis> then switch to the <emphasis> + <property moreinfo="none">Source tab</property>,</emphasis> select the output folder for <emphasis> + <property moreinfo="none">src/hot</property></emphasis> (<emphasis> + <property moreinfo="none">src/main</property>)</emphasis> and click <emphasis> + <property moreinfo="none">Edit</property></emphasis> to change their output location.</para> + <para>In conclusion, the main goal of this document is to get you know with a full featureset - that <property>JBoss Tools</property> provides to support Seam development. Thus if you have - some questions, comments or suggestions on the topic, please fell free to ask in the <ulink - url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss + that <property moreinfo="none">JBoss Tools</property> provides to support Seam development. Thus if you have + some questions, comments or suggestions on the topic, please fell free to ask in the + <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss Tools Forum</ulink>. You can also influence on how you want to see JBoss Tools docs in - future leaving your vote on the article <ulink - url="http://wiki.jboss.org/wiki/JBossToolsDocsFuture" - >Overview of the improvements required by JBossTools/JBDS Docs users</ulink>. </para> - + future leaving your vote on the article <ulink url="http://wiki.jboss.org/wiki/JBossToolsDocsFuture">Overview of the improvements required by JBossTools/JBDS Docs users</ulink>. </para> + <para>A set of movies on Seam tooling is available on <ulink url="http://docs.jboss.org/tools/movies">Seam movies page</ulink>.</para> </section> </chapter> -</book> \ No newline at end of file + +  + +</book> Modified: branches/jbosstools-3.1.x/seam/docs/reference/en/modules/directory_structure.xml =================================================================== --- branches/jbosstools-3.1.x/seam/docs/reference/en/modules/directory_structure.xml 2010-03-03 12:38:25 UTC (rev 20604) +++ branches/jbosstools-3.1.x/seam/docs/reference/en/modules/directory_structure.xml 2010-03-03 13:15:19 UTC (rev 20605) @@ -95,7 +95,7 @@ <title>Changing the Seam Version</title> <para>To upgrade or downgrade your projects Seam version use the facet preferences. You - should right-click your project and choose <emphasis> + should right-click your project, open its <property>Properties</property> and choose <emphasis> <property>Project Facets</property> </emphasis> category. Next select <emphasis> <property>Seam</property> Modified: branches/jbosstools-3.1.x/seam/docs/reference/pom.xml =================================================================== --- branches/jbosstools-3.1.x/seam/docs/reference/pom.xml 2010-03-03 12:38:25 UTC (rev 20604) +++ branches/jbosstools-3.1.x/seam/docs/reference/pom.xml 2010-03-03 13:15:19 UTC (rev 20605) @@ -23,7 +23,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
0 / 0

JBoss Tools SVN: r20604 - branches/jbosstools-3.1.x/hibernatetools/plugins/org.hibernate.eclipse/lib/tools.

by jbosstools-commits＠lists.jboss.org

Author: dgeraskov Date: 2010-03-03 07:38:25 -0500 (Wed, 03 Mar 2010) New Revision: 20604 Modified: branches/jbosstools-3.1.x/hibernatetools/plugins/org.hibernate.eclipse/lib/tools/hibernate-tools.jar Log: Update hibernate-tools Modified: branches/jbosstools-3.1.x/hibernatetools/plugins/org.hibernate.eclipse/lib/tools/hibernate-tools.jar =================================================================== (Binary files differ)

14 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r20603 - in trunk/hibernatetools: tests/org.hibernate.eclipse.console.test/lib and 1 other directory.

by jbosstools-commits＠lists.jboss.org

Author: dgeraskov Date: 2010-03-03 07:38:05 -0500 (Wed, 03 Mar 2010) New Revision: 20603 Modified: trunk/hibernatetools/plugins/org.hibernate.eclipse/lib/tools/hibernate-tools.jar trunk/hibernatetools/tests/org.hibernate.eclipse.console.test/lib/hibernate-tools-tests.jar Log: Update hibernate-tools Modified: trunk/hibernatetools/plugins/org.hibernate.eclipse/lib/tools/hibernate-tools.jar =================================================================== (Binary files differ) Modified: trunk/hibernatetools/tests/org.hibernate.eclipse.console.test/lib/hibernate-tools-tests.jar =================================================================== (Binary files differ)

14 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r20602 - branches/jbosstools-3.1.x/hibernatetools/tests/org.hibernate.eclipse.console.test/lib.

by jbosstools-commits＠lists.jboss.org

Author: dgeraskov Date: 2010-03-03 07:37:54 -0500 (Wed, 03 Mar 2010) New Revision: 20602 Modified: branches/jbosstools-3.1.x/hibernatetools/tests/org.hibernate.eclipse.console.test/lib/hibernate-tools-tests.jar Log: Update hibernate-tools Modified: branches/jbosstools-3.1.x/hibernatetools/tests/org.hibernate.eclipse.console.test/lib/hibernate-tools-tests.jar =================================================================== (Binary files differ)

14 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r20601 - branches/jbosstools-3.1.x/jsf/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/web/validation.

by jbosstools-commits＠lists.jboss.org

Author: vrubezhny Date: 2010-03-03 07:19:02 -0500 (Wed, 03 Mar 2010) New Revision: 20601 Modified: branches/jbosstools-3.1.x/jsf/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/web/validation/XHTMLEntityResolver.java Log: EPL License comment is added Modified: branches/jbosstools-3.1.x/jsf/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/web/validation/XHTMLEntityResolver.java =================================================================== --- branches/jbosstools-3.1.x/jsf/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/web/validation/XHTMLEntityResolver.java 2010-03-03 12:10:25 UTC (rev 20600) +++ branches/jbosstools-3.1.x/jsf/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/web/validation/XHTMLEntityResolver.java 2010-03-03 12:19:02 UTC (rev 20601) @@ -1,3 +1,20 @@ +/******************************************************************************* + * Copyright (c) 2001, 2009 IBM Corporation and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * IBM Corporation - initial API and implementation + * David Carver - STAR - [205989] - [validation] validate XML after XInclude resolution + * + * + * The class is partially copied from WTP because of its poor visibility + * org.eclipse.wst.xml.core.internal.validation.XMLValidator.MyEntityResolver + * + *******************************************************************************/ + package org.jboss.tools.jsf.web.validation; import java.io.FileNotFoundException;

14 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r20600 - trunk/jsf/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/web/validation.

by jbosstools-commits＠lists.jboss.org

Author: vrubezhny Date: 2010-03-03 07:10:25 -0500 (Wed, 03 Mar 2010) New Revision: 20600 Modified: trunk/jsf/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/web/validation/XHTMLEntityResolver.java Log: EPL License comment is added Modified: trunk/jsf/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/web/validation/XHTMLEntityResolver.java =================================================================== --- trunk/jsf/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/web/validation/XHTMLEntityResolver.java 2010-03-03 12:09:12 UTC (rev 20599) +++ trunk/jsf/plugins/org.jboss.tools.jsf/src/org/jboss/tools/jsf/web/validation/XHTMLEntityResolver.java 2010-03-03 12:10:25 UTC (rev 20600) @@ -1,3 +1,20 @@ +/******************************************************************************* + * Copyright (c) 2001, 2009 IBM Corporation and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * IBM Corporation - initial API and implementation + * David Carver - STAR - [205989] - [validation] validate XML after XInclude resolution + * + * + * The class is partially copied from WTP because of its poor visibility + * org.eclipse.wst.xml.core.internal.validation.XMLValidator.MyEntityResolver + * + *******************************************************************************/ + package org.jboss.tools.jsf.web.validation; import java.io.FileNotFoundException;

14 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbosstools-commits March 2010