User: vancek
Date: 06/06/13 22:12:15
Modified: andromda-ejb3/src/site/xdoc howto3.xml howto12.xml
Log:
fixed view types for session bean/operations and service delegate
Revision Changes Path
1.7 +15 -2 cartridges/andromda-ejb3/src/site/xdoc/howto3.xml
Index: howto3.xml
===================================================================
RCS file: /cvsroot/andromdaplugins/cartridges/andromda-ejb3/src/site/xdoc/howto3.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -w -r1.6 -r1.7
--- howto3.xml 29 May 2006 01:53:36 -0000 1.6
+++ howto3.xml 14 Jun 2006 05:12:15 -0000 1.7
@@ -93,6 +93,12 @@
If you wish, you can override this feature by modelling the <code>@andromda.service.type</code>
tagged value on the session bean class.
</p>
+ <p class="highlight">
+ Stateless session beans that are JBoss Seam components do not follow the above rule. If your
+ class is modelled as a Seam component and you have modelled attributes on this class, it will not
+ be rendered as a stateful session bean, unless you specify the <code>@andromda.service.type</code>
+ tagged value.
+ </p>
</subsection>
<a name="View_Interface"/>
<subsection name="View Interfaces">
@@ -111,6 +117,10 @@
<li><p>both - This class/operations are available via the local and remote interfaces</p></li>
</ul>
</p>
+ <p>
+ If you have operations that exist in both the local and remote interfaces, your service
+ delegate class will allow you to select how you want to invoke your bean operations.
+ </p>
</subsection>
<a name="Transactions"/>
<subsection name="Transactions">
@@ -154,8 +164,11 @@
<p>
As you saw in the example in this howto, a session bean delegate class is generated for
every session bean. A client invokes the session bean's business methods via the delegate
- class, acting like a proxy via the service locator class. Both the service delegate and
- service locator classes are regenerated every time AndroMDA is run. You can find out
+ class, acting like a proxy via the service locator class.
+ </p>
+ <p>
+ Both the service delegate and
+ service locator classes are re-generated every time AndroMDA is run. You can find out
more information about session delegates from <a href="howto12.html">here</a>.
</p>
</subsection>
1.4 +2 -2 cartridges/andromda-ejb3/src/site/xdoc/howto12.xml
Index: howto12.xml
===================================================================
RCS file: /cvsroot/andromdaplugins/cartridges/andromda-ejb3/src/site/xdoc/howto12.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -w -r1.3 -r1.4
--- howto12.xml 29 May 2006 01:53:36 -0000 1.3
+++ howto12.xml 14 Jun 2006 05:12:15 -0000 1.4
@@ -45,7 +45,7 @@
</p>
<p>
The EJB3 cartridges cuts down the service delegates which references the service locator
- and provides the ability to invoke all methods available on the remote interface of
+ and provides the ability to invoke all available methods on the appropriate view interface of
the session bean.
</p>
<p>
@@ -106,7 +106,7 @@
<p>
In circumstance where you have manageable entities, a <code>ManageableServiceLocator</code>
class will also be generated with similar logic as the <code>ServiceLocator</code>
- class, except it provides the facility to get the manageable service beans remote interfaces.
+ class, except it used the remote interface of the manageable service bean.
</p>
</subsection>
<a name="Further_Reading"/>
|
