Attachment 159902 Details for Bug 241667 – Context help documentation

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

[patch] Context help documentation

241667_patch_doc.txt (text/plain), 10.82 KB, created by Kaloyan Raev

on 2010-02-23 05:10:55 EST

(hide)

Description:

Filename:

MIME Type:

Creator: Kaloyan Raev

Created: 2010-02-23 05:10:55 EST

Size: 10.82 KB

patch

obsolete

>### Eclipse Workspace Patch 1.0
>#P org.eclipse.jst.ejb.doc.user
>Index: topics/sessbwiz.html
>===================================================================
>RCS file: /cvsroot/webtools/ejbtools/docs/org.eclipse.jst.ejb.doc.user/topics/sessbwiz.html,v
>retrieving revision 1.3
>diff -u -r1.3 sessbwiz.html
>--- topics/sessbwiz.html	14 May 2008 01:36:43 -0000	1.3
>+++ topics/sessbwiz.html	23 Feb 2010 10:03:31 -0000
>@@ -55,8 +55,7 @@
> <dl>
> <dt class="dlterm">State type</dt>
> 
>-<dd>A session beans are divided in two types: stateless session beans and
>-stateful session beans.<dl>
>+<dd>There are three types of session beans: stateless, stateful and singleton. <dl>
> <dt class="dlterm">Stateless session beans</dt>
> 
> <dd>A stateless session bean is a collection of related services, each represented
>@@ -76,6 +75,16 @@
> data to and from this conversational state, which is shared among all methods
> in the bean. Stateful session beans have timeout periods.</dd>
> 
>+<dt class="dlterm">Singleton session beans</dt>
>+
>+<dd>A Singleton session bean is a session bean component that is instantiated 
>+once per application. In cases where the container is distributed over many virtual 
>+machines, each application will have one bean instance of the Singleton for each JVM. 
>+Once instantiated, a Singleton session bean instance lives for the duration of the 
>+application in which it is created. It maintains its state between client invocations 
>+but that state is not required to survive container shutdown or crash. A Singleton 
>+session bean is intended to be shared and supports concurrent access.</dd>
>+
> </dl>
> </dd>
> 
>@@ -88,7 +97,7 @@
> bean's business interface can be passed as a parameter or as a return value
> of a business interface method. It contains methods to initialize a session
> bean's state and to notify the EJB container when the reference is no more
>-needed and can be removed. The business interfaces are two types:<dl>
>+needed and can be removed. There are several options available:<dl>
> <dt class="dlterm">Remote business interface:</dt>
> 
> <dd>The client can run on a different machine or different Java virtual
>@@ -101,6 +110,11 @@
> <dd>The client must run on the same Java virtual machine as the bean it accesses
> and the location of the enterprise bean is not transparent.</dd>
> 
>+<dt class="dlterm">No-interface:</dt>
>+
>+<dd>This is a variation of the Local view that exposes the public methods of the 
>+bean class without the use of a separate business interface.</dd>
>+
> </dl>
> </dd>
> 
>Index: topics/sessb.dita
>===================================================================
>RCS file: /cvsroot/webtools/ejbtools/docs/org.eclipse.jst.ejb.doc.user/topics/sessb.dita,v
>retrieving revision 1.3
>diff -u -r1.3 sessb.dita
>--- topics/sessb.dita	14 May 2008 01:36:43 -0000	1.3
>+++ topics/sessb.dita	23 Feb 2010 10:03:31 -0000
>@@ -18,9 +18,8 @@
> in the database, but they can access data, so we can use session beans to
> read, update, and insert data in a business process. Session beans access
> data that spans concepts, is not shared, and is usually read-only. Session
>-beans contain business logic, and entities model persistent data. Session
>-beans are divided in two types: stateless session beans and stateful session
>-beans.
>+beans contain business logic, and entities model persistent data. There are 
>+three types of session beans: stateless, stateful and singleton. 
> <ul>
> <li>Stateless session beans A stateless session bean is pooled by
> the container to handle multiple requests from multiple clients and does not
>@@ -29,6 +28,10 @@
> of a single client and maintains client-specific session information (called
> conversational state) across multiple method calls and transactions. It exists
> for the duration of a single client/server session. </li>
>+<li> Singleton session beans A Singleton session bean is a session 
>+bean component that is instantiated once per application. In cases where the container 
>+is distributed over many virtual machines, each application will have one bean instance 
>+of the Singleton for each JVM. </li>
> </ul>
> </conbody>
> </concept>
>Index: topics/sessbwiz.dita
>===================================================================
>RCS file: /cvsroot/webtools/ejbtools/docs/org.eclipse.jst.ejb.doc.user/topics/sessbwiz.dita,v
>retrieving revision 1.3
>diff -u -r1.3 sessbwiz.dita
>--- topics/sessbwiz.dita	14 May 2008 01:36:43 -0000	1.3
>+++ topics/sessbwiz.dita	23 Feb 2010 10:03:31 -0000
>@@ -27,8 +27,7 @@
> </steps>
> <postreq>General Information<dl><dlentry>
> <dt>State type</dt>
>-<dd>A session beans are divided in two types: stateless session beans and
>-stateful session beans.<dl><dlentry>
>+<dd>There are three types of session beans: stateless, stateful and singleton. <dl><dlentry>
> <dt>Stateless session beans</dt>
> <dd>A stateless session bean is a collection of related services, each represented
> by a method; the bean maintains no state from one method invocation to the
>@@ -44,6 +43,15 @@
> and the client. Methods invoked on a stateful session bean can write and read
> data to and from this conversational state, which is shared among all methods
> in the bean. Stateful session beans have timeout periods.</dd>
>+</dlentry><dlentry>
>+<dt>Singleton session beans</dt>
>+<dd>A Singleton session bean is a session bean component that is instantiated 
>+once per application. In cases where the container is distributed over many virtual 
>+machines, each application will have one bean instance of the Singleton for each JVM. 
>+Once instantiated, a Singleton session bean instance lives for the duration of the 
>+application in which it is created. It maintains its state between client invocations 
>+but that state is not required to survive container shutdown or crash. A Singleton 
>+session bean is intended to be shared and supports concurrent access.</dd>
> </dlentry></dl></dd>
> </dlentry></dl> <dl><dlentry>
> <dt>Business interface</dt>
>@@ -64,6 +72,10 @@
> <dd>The client must run on the same <tm tmclass="special" tmowner="Sun Microsystems, Inc."
> tmtype="tm" trademark="Java">Java</tm> virtual machine as the bean it accesses
> and the location of the enterprise bean is not transparent.</dd>
>+</dlentry><dlentry>
>+<dt>No-interface:</dt>
>+<dd>This is a variation of the Local view that exposes the public methods of the 
>+bean class without the use of a separate business interface.</dd>
> </dlentry></dl></dd>
> </dlentry></dl> <dl><dlentry>
> <dt>Mapped name</dt>
>Index: topics/sessb.html
>===================================================================
>RCS file: /cvsroot/webtools/ejbtools/docs/org.eclipse.jst.ejb.doc.user/topics/sessb.html,v
>retrieving revision 1.3
>diff -u -r1.3 sessb.html
>--- topics/sessb.html	14 May 2008 01:36:43 -0000	1.3
>+++ topics/sessb.html	23 Feb 2010 10:03:31 -0000
>@@ -38,9 +38,8 @@
> in the database, but they can access data, so we can use session beans to
> read, update, and insert data in a business process. Session beans access
> data that spans concepts, is not shared, and is usually read-only. Session
>-beans contain business logic, and entities model persistent data. Session
>-beans are divided in two types: stateless session beans and stateful session
>-beans.
>+beans contain business logic, and entities model persistent data. There are 
>+three types of session beans: stateless, stateful and singleton. 
> 
> <ul>
> <li>Stateless session beans A stateless session bean is pooled by
>@@ -53,6 +52,12 @@
> conversational state) across multiple method calls and transactions. It exists
> for the duration of a single client/server session.
> </li>
>+ 
>+<li> Singleton session beans A Singleton session bean is a session 
>+bean component that is instantiated once per application. In cases where the container 
>+is distributed over many virtual machines, each application will have one bean instance 
>+of the Singleton for each JVM.
>+ </li>
> 
> </ul>
> 
>#P org.eclipse.jst.ejb.ui.infopop
>Index: SessionBeanWizContext.xml
>===================================================================
>RCS file: /cvsroot/webtools/ejbtools/docs/org.eclipse.jst.ejb.ui.infopop/SessionBeanWizContext.xml,v
>retrieving revision 1.2
>diff -u -r1.2 SessionBeanWizContext.xml
>--- SessionBeanWizContext.xml	29 Jun 2009 15:09:24 -0000	1.2
>+++ SessionBeanWizContext.xml	23 Feb 2010 10:03:39 -0000
>@@ -13,13 +13,16 @@
> In the field Superclass specify the superclass for the session bean, only if it is derived from one. Click Browse to choose from the available, already existing or created, superclasses. (This field is optional).
> 
> In the field State type choose the type of the session bean that you create: 
>- - Stateful session bean acts on behalf of a single client and maintains client-specific session information (called conversational state) across multiple method calls and transactions. It exists for the duration of a single client/server session.
>- - Stateless session bean is pooled by the container to handle multiple requests from multiple clients and does not maintain any conversational state.
>+ - Stateless â the session bean instances contain no conversational state between methods; any instance can be used for any client. 
>+ - Stateful â the session bean instances contain conversational state which must be retained across methods and transactions. 
>+ - Singleton â a single session bean instance is shared between clients and supports concurrent access. 
> 
> In the section Create business interface, check the business interface that you want to create:
>- - Remote Interface â the client can run on a different machine or different Java virtual machine than the enterprise bean it accesses and the location of the bean is transparent.
>- - Local Interface â the client must run on the same Java virtual machine as the bean it accesses and the location of the enterprise bean is not transparent.
>-Note: You can check both interfaces, so that your session bean will have local and remote interfaces.
>+ - Remote â the client can run on a different machine or different Java virtual machine than the enterprise bean it accesses and the location of the bean is transparent.
>+ - Local â the client must run on the same Java virtual machine as the bean it accesses and the location of the enterprise bean is not transparent.
>+ - No-interface â this is a variation of the Local view that exposes the public methods of the bean class without the use of a separate business interface.
>+ 
>+Note: It is valid to check all of the above options. 
> </description>
> <topic label="Creating Session Beans" href="../org.eclipse.jst.ejb.doc.user/topics/sessbwiz.html"/>
> <topic label="EJB 2.x architecture" href="../org.eclipse.jst.ejb.doc.user/topics/cearch.html"/>

Actions: View | Diff

Attachments on bug 241667: 154964 | 159894 | 159902