3:10 a.m.
Author: Grid.Qian
Date: 2009-09-22 04:10:46 -0400 (Tue, 22 Sep 2009)
New Revision: 17688
Added:
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/.classpath
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/.project
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/.settings/
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/.settings/org.eclipse.jdt.core.prefs
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/META-INF/
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/META-INF/MANIFEST.MF
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/bin/
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/bin/org/
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/bin/org/jboss/
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/bin/org/jboss/tools/
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/bin/org/jboss/tools/bpel/
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/bin/org/jboss/tools/bpel/cheatsheet/
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/bin/org/jboss/tools/bpel/cheatsheet/Activator.class
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/build.properties
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/cheatsheets/
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/cheatsheets/bpel.xml
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/plugin.xml
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/src/
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/src/org/
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/src/org/jboss/
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/src/org/jboss/tools/
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/src/org/jboss/tools/bpel/
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/src/org/jboss/tools/bpel/cheatsheet/
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/src/org/jboss/tools/bpel/cheatsheet/Activator.java
Log:
add cheatsheet for bpel
Added: trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/.classpath
===================================================================
--- trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/.classpath
(rev 0)
+++ trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/.classpath 2009-09-22 08:10:46 UTC
(rev 17688)
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<classpath>
+ <classpathentry kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5"/>
+ <classpathentry kind="con"
path="org.eclipse.pde.core.requiredPlugins"/>
+ <classpathentry kind="src" path="src"/>
+ <classpathentry kind="output" path="bin"/>
+</classpath>
Added: trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/.project
===================================================================
--- trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/.project
(rev 0)
+++ trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/.project 2009-09-22 08:10:46 UTC
(rev 17688)
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.jboss.tools.bpel.cheatsheet</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.jdt.core.javabuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.ManifestBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.SchemaBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.PluginNature</nature>
+ <nature>org.eclipse.jdt.core.javanature</nature>
+ </natures>
+</projectDescription>
Added:
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/.settings/org.eclipse.jdt.core.prefs
===================================================================
---
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/.settings/org.eclipse.jdt.core.prefs
(rev 0)
+++
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/.settings/org.eclipse.jdt.core.prefs 2009-09-22
08:10:46 UTC (rev 17688)
@@ -0,0 +1,8 @@
+#Thu Sep 17 15:54:11 CST 2009
+eclipse.preferences.version=1
+org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=enabled
+org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.5
+org.eclipse.jdt.core.compiler.compliance=1.5
+org.eclipse.jdt.core.compiler.problem.assertIdentifier=error
+org.eclipse.jdt.core.compiler.problem.enumIdentifier=error
+org.eclipse.jdt.core.compiler.source=1.5
Added: trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/META-INF/MANIFEST.MF
===================================================================
--- trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/META-INF/MANIFEST.MF
(rev 0)
+++ trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/META-INF/MANIFEST.MF 2009-09-22
08:10:46 UTC (rev 17688)
@@ -0,0 +1,11 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: Cheatsheet
+Bundle-SymbolicName: org.jboss.tools.bpel.cheatsheet;singleton:=true
+Bundle-Version: 1.0.0
+Bundle-Activator: org.jboss.tools.bpel.cheatsheet.Activator
+Require-Bundle: org.eclipse.ui,
+ org.eclipse.core.runtime,
+ org.eclipse.ui.cheatsheets
+Bundle-ActivationPolicy: lazy
+Bundle-RequiredExecutionEnvironment: J2SE-1.5
Added:
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/bin/org/jboss/tools/bpel/cheatsheet/Activator.class
===================================================================
(Binary files differ)
Property changes on:
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/bin/org/jboss/tools/bpel/cheatsheet/Activator.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/build.properties
===================================================================
--- trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/build.properties
(rev 0)
+++ trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/build.properties 2009-09-22
08:10:46 UTC (rev 17688)
@@ -0,0 +1,4 @@
+source.. = src/
+output.. = bin/
+bin.includes = META-INF/,\
+ .
Added: trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/cheatsheets/bpel.xml
===================================================================
--- trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/cheatsheets/bpel.xml
(rev 0)
+++ trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/cheatsheets/bpel.xml 2009-09-22
08:10:46 UTC (rev 17688)
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8" ?>
+<cheatsheet title="JBoss BPEL Tutorial">
+
+ <intro>
+ <description>
+ Learn how to use JBoss BPEL editor.
+ </description>
+ </intro>
+
+ <item title="Create a BPEL Project" skip="true">
+ <description>
+ If you want to deploy a bpel staff into JBoss BPEL server, the first step, you need
create a BPEL project.
+Of course, if you only need to draw a BPEL process, you don't need to do the
step.
+ </description>
+ <subitem
+ label="Create a BPEL project by selecting "File > New
> Project... > BPEL 2.0 > BPEL Project" from the menu
bar."
+ skip="false">
+ </subitem>
+ <subitem label="On the first page of the "New BPEL
Project" Wizard enter a project name in the "Project Name"
field. Click "Finish" button.">
+ </subitem>
+ </item>
+
+ <item title="Create a BPEL Process" skip="true">
+ <description>
+ After create a BPEL project, you can create a BPEL process file in the project.
+ </description>
+ <subitem
+ label="Create a BPEL process file by selecting "File >
New > Others... > BPEL 2.0 > New BPEL Process File" from the
menu bar.">
+ </subitem>
+ <subitem label="On the first page of the "Create a BPEL Process
File" Wizard enter a process name in the "BPEL Process Name"
field, a process's namesapce in the "Namespace" field, and a
process's template in the "Template" field. Click
"Next" button.">
+ </subitem>
+ <subitem label="On the second page of the "Create a BPEL Process
File" Wizard select the "bpel" folder of the BPEL project.
Click "Finish" button.">
+ </subitem>
+ </item>
+
+ <item title="Edit the BPEL Process file" skip="true">
+ <description>
+ For getting a useful BPEL process, you need to edit the BPEL process file by
adding some BPEL elements.<br/><br/>
+From the "Palette" view, you can add a BPEL element to the BPEL process
by dragging and dropping it.<br/><br/>
+From the "Properties" view, you can edit the attributes of a BPEL
element.<br/><br/>
+From the "Tray of the BPEL editor", you can add a Partner link,
Variable, Correlation Set or Message Exchange to the BPEL process.<br/><br/>
+If the "Properties" view and "Palette" view are not
opened, you can open the views by right-clicking the BPEL editor and selecting
"Show in Properties", "Show Palette in Palette view".
+
+ </description>
+ </item>
+
+ <item title="Edit the WSDL file" skip="true">
+ <description>
+ For getting a runnable BPEL staff, beside the BPEL process file, you need a WSDL to
describe how to use the BPEL process. As default, the system has genereted a WSDL for the
BPEL staff. You need to edit it to support your BPEL project. <br/><br/>
+Open the WSDL using the WSDL editor, add "Service" and
"Binding" by right-clicking on the WSDL editor, and set the attributes
of them in the "Properties" view.
+ </description>
+ </item>
+
+ <item title="Create a bpel-deploy.xml file" skip="true">
+ <description>
+ If you want to deploy a BPEL project to JBoss BPEL Runtime, you need to create a
bpel-deploy.xml file.
+ </description>
+ <subitem label="Create a bpel-deploy.xml by selecting "File
> New > Other... > BPEL 2.0 > Apache ODE Deployment
Descriptor" from the menu bar.">
+ </subitem>
+ <subitem label="On the first page of the "Apache ODE Deployment
Descriptor" Wizard choose the "bpel" folder of a bpel project
in the "BPEL Project" field and enter
"bpel-deploy.xml" in the "File name" field. Click
"Finish" button.">
+ </subitem>
+ <subitem label="Double-click the bpel-deploy.xml file to open it in ODE
Descriptor Deployment Editor. In the "Inbound Interfaces" section, click
the "Associated Port" column and in the dropdown box select a BPEL port
that is defined in the WSDL file.The Related Service and Binding Used columns should be
automatically filled in. Save the bpel-deploy.xml file.">
+ </subitem>
+ </item>
+
+ <item title="Create a JBoss BPEL Server" skip="true">
+ <description>
+ Suppose you have installed the JBoss BPEL Runtime-RiftSaw into a JBoss server,
you can create a server in JBoss Tools for JBoss BPEL runtime.
+ </description>
+ <subitem label="Open the "JBoss Server" view by selecting
"Windows > Show View > Other... > Server > JBoss
Server view" in the menu bar.">
+ </subitem>
+ <subitem label="Right-click the JBoss Server view and select "New
> Server" to open the New Server Wizard">
+ </subitem>
+ <subitem label="On the first page of the "New Server"
Wizard select "JBoss AS 5.1" in the "Select the server
type" field, input a server name in the "Server name" field
and select a runtime in the "Server runtime environment" field. Click
"Next" button.">
+ </subitem>
+ <subitem label="On the second page of the "New Server"
Wizard input your JBoss AS location in the "JBoss AS Location" field.
Click "Next" button.">
+ </subitem>
+ <subitem label="On the third page of the "New Server"
Wizard select a BPEL resource in the left column, click "Add >"
button to add the BPEL resource to the right column. Click "Finish"
button.">
+ </subitem>
+ </item>
+
+ <item title="Deploy the BPEL Process into the JBoss BPEL Server"
skip="true">
+ <description>
+ If you don't add a BPEL resource into the server in the third step of
"Create a JBoss BPEL Server", you can right-click on the server item in
the "JBoss Server" view and select the "Add and
Removes...", then you can do the step as the third step of "Create a
JBoss BPEL Server".
+<br/><br/>
+After these steps, you can start the server to test your BPEL staff.
+ </description>
+ </item>
+</cheatsheet>
Added: trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/plugin.xml
===================================================================
--- trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/plugin.xml
(rev 0)
+++ trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/plugin.xml 2009-09-22 08:10:46 UTC
(rev 17688)
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.5"?>
+<plugin>
+ <extension
+ point="org.eclipse.ui.cheatsheets.cheatSheetContent">
+ <category
+ id="org.jboss.tools.bpel.cheatsheet"
+ name="JBoss BPEL Tutorial">
+ </category>
+ <cheatsheet
+ category="org.jboss.tools.bpel.cheatsheet"
+ contentFile="$nl$/cheatsheets/bpel.xml"
+ id="org.jboss.tools.bpel.cheatsheet.bpel"
+ name="JBoss BPEL Tutorial">
+ <description>
+ Learn how to use JBoss BPEL editor
+ </description>
+ </cheatsheet>
+ </extension>
+
+</plugin>
\ No newline at end of file
Added:
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/src/org/jboss/tools/bpel/cheatsheet/Activator.java
===================================================================
---
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/src/org/jboss/tools/bpel/cheatsheet/Activator.java
(rev 0)
+++
trunk/bpel/plugins/org.jboss.tools.bpel.cheatsheet/src/org/jboss/tools/bpel/cheatsheet/Activator.java 2009-09-22
08:10:46 UTC (rev 17688)
@@ -0,0 +1,50 @@
+package org.jboss.tools.bpel.cheatsheet;
+
+import org.eclipse.ui.plugin.AbstractUIPlugin;
+import org.osgi.framework.BundleContext;
+
+/**
+ * The activator class controls the plug-in life cycle
+ */
+public class Activator extends AbstractUIPlugin {
+
+ // The plug-in ID
+ public static final String PLUGIN_ID = "org.jboss.tools.bpel.cheatsheet";
+
+ // The shared instance
+ private static Activator plugin;
+
+ /**
+ * The constructor
+ */
+ public Activator() {
+ }
+
+ /*
+ * (non-Javadoc)
+ * @see org.eclipse.ui.plugin.AbstractUIPlugin#start(org.osgi.framework.BundleContext)
+ */
+ public void start(BundleContext context) throws Exception {
+ super.start(context);
+ plugin = this;
+ }
+
+ /*
+ * (non-Javadoc)
+ * @see org.eclipse.ui.plugin.AbstractUIPlugin#stop(org.osgi.framework.BundleContext)
+ */
+ public void stop(BundleContext context) throws Exception {
+ plugin = null;
+ super.stop(context);
+ }
+
+ /**
+ * Returns the shared instance
+ *
+ * @return the shared instance
+ */
+ public static Activator getDefault() {
+ return plugin;
+ }
+
+}