summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2012-05-23 07:54:45 (EDT)
committer Stephan Born2012-06-15 10:41:01 (EDT)
commit265aee12863e416728399fce6ff609a9aaf57926 (patch)
tree222d633f6b3f33784ab30fec4793c477b2cb683f
parent76cea6d3772938e39dc1a9e59fa04ee8746136f8 (diff)
downloadorg.eclipse.stardust.documentation-265aee12863e416728399fce6ff609a9aaf57926.zip
org.eclipse.stardust.documentation-265aee12863e416728399fce6ff609a9aaf57926.tar.gz
org.eclipse.stardust.documentation-265aee12863e416728399fce6ff609a9aaf57926.tar.bz2
CRNT-24864 - Upgrading existing JSF app activity
git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@56516 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b
-rw-r--r--org.eclipse.stardust.docs.dev/html/handbooks/model-upgrade.html59
-rw-r--r--org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-convert-activities.html1
2 files changed, 59 insertions, 1 deletions
diff --git a/org.eclipse.stardust.docs.dev/html/handbooks/model-upgrade.html b/org.eclipse.stardust.docs.dev/html/handbooks/model-upgrade.html
index 4dcb6de..44bbc2e 100644
--- a/org.eclipse.stardust.docs.dev/html/handbooks/model-upgrade.html
+++ b/org.eclipse.stardust.docs.dev/html/handbooks/model-upgrade.html
@@ -38,6 +38,7 @@ required for specific issues.</p>
<ul>
<li><a href="#facets">Upgrading @productname@ Facets</a></li>
<li><a href="#jsf">Using JSF Managed Beans with Version 5.0.x and Earlier</a></li>
+ <li><a href="#JSFexist">Upgrading Existing JSF Application Activities in @productname@ 7.0</a></li>
<li><a href="#facOld">Upgrading Web Projects using @productname@ Facets with Versions 5.0.x and Earlier</a></li>
</ul></li>
</ul>
@@ -221,6 +222,64 @@ For details refer to chapter
<a href="modelling/mg-integration-jsf.html">Integrating JSF Applications</a>
of the
<a href="modelling/mg-integration-preface.htm">System Integration</a>.</p>
+
+<h3 id="JSFexist">Upgrading Existing JSF Application Activities in @productname@ 7.0</h3>
+<p>Existing JSF application activites need to be upgraded in @productname@ Portal 7.0 to view the new look and feel and
+features.
+The active process instances also get new look and feel and features after upgrading in @productname@ Portal 7.0.
+You need to perform some changes to:</p>
+<ul>
+ <li><a href="#JSFapp">JSF Application Activity</a> - Manually written JSF application activity</li>
+ <li><a href="#convJSF">Manual Activity Converted to JSF</a> - If JSF application is created using the <strong>Convert Manual Activity to JSF
+ </strong> option in modeler, then to view the new look and feel and features; you need to perform changes to existing one.</li>
+ <li><a href="#view">View Events</a></li>
+</ul>
+
+<h4 id="JSFapp">JSF Application Activity</h4>
+<p>You need to perform changes for In and Out data mappings:</p>
+<ul>
+ <li>Add method <tt>public void setData(HashMap&lt;String, Object&gt; data)</tt>. This method
+ receives all In Data mappings values in a <tt>HashMap</tt>
+ <ul><li>Individual setter method for each data mapping is not called by framework</li>
+ <li><tt>setData()</tt> method needs to do setting of IN data internally as appropriate</li></ul></li>
+ <li>Change return type of completion method <tt>public Map&lt;String, Object&gt; complete() </tt>
+ <ul><li>This method returns values of all Out data mappings in a <tt>Map</tt></li>
+ </ul></li>
+</ul>
+
+<h4 id="convJSF">Manual Activity Converted to JSF</h4>
+
+<p>To view the new look and feel and features of JSF activity, you need to perform the following:</p>
+<ul>
+ <li>Reconvert the manual activity to JSF application activity in the modeler. Make sure the Bean name
+ including package and XHTML name is not changed. If names are changed, you need to edit the name to be same as old names.
+ This will replace the existing backing bean and XHTML.</li>
+ <li>Redo any custom changes made on Bean and XHTML</li>
+ <li>Deploy the new artifacts (backing Bean and XHTML). You do not need to redeploy the model.</li>
+</ul>
+<p>Note that newly created Backing Bean class is an empty class because it gets all its functionality
+from super class <tt>JsfActivityPanelBean</tt>. If project has its own class hierarchy for backing bean then
+they need to copy all methods from JsfActivityPanelBean into the backing bean class.
+ </p>
+
+<h4 id="view">View Events</h4>
+<p>With new features, custom JSF backing bean is also capable of receiving <strong>View Events</strong>.
+Following changes are required:</p>
+<ul>
+ <li>Implement interface <tt>ViewEventHandler</tt> & provide method <tt>handleEvent()</tt>
+ <pre>
+ import org.eclipse.stardust.ui.web.common.event.ViewEventHandler;
+
+ public class CustomBackingBean implements ViewEventHandler
+ {
+ public void handleEvent(ViewEvent event)
+ {
+ }
+ } </pre>
+ </li>
+ <li>Also note that Backing bean receives all events except <tt>CREATED</tt> event.</li>
+
+</ul>
<h3 id="facOld">Upgrading Web Projects using @productname@ Facets with Versions 5.0.x and Earlier</h3>
<p>In case you are working with Web projects containing @productname@ Portal
facets created with a release earlier than 5.1., upgrading the @productname@ Portal facets is
diff --git a/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-convert-activities.html b/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-convert-activities.html
index f9c645d..3007703 100644
--- a/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-convert-activities.html
+++ b/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-convert-activities.html
@@ -164,7 +164,6 @@ project, after the according JSF application is deleted from the model.</p>
<li>Generated JSF beans are in session scope, so two activities of same type cannot be activated at
same time in two different views.</li>
-
</ul>