Attachment #159902 for bug #241667

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




<dl>
<dt class="dlterm">State type</dt>

<dd>There are three types of session beans: stateless, stateful and singleton. <dl>
stateful session beans.<dl>
<dt class="dlterm">Stateless session beans</dt>

<dd>A stateless session bean is a collection of related services, each represented

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>


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. 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

<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>





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. There are 
three types of session beans: stateless, stateful and singleton. </p>
beans.</p>
<ul>
<li><b>Stateless session beans</b> <p>A stateless session bean is pooled by
the container to handle multiple requests from multiple clients and does not

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.</p> </li>
<li> <b>Singleton session beans</b> <p>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.</p> </li>
</ul>
</conbody>
</concept>




</steps>
<postreq><p><b>General Information</b></p><dl><dlentry>
<dt>State type</dt>
<dd>There are three types of session beans: stateless, stateful and singleton. <dl><dlentry>
stateful session beans.<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

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>

<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>




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. There are 
three types of session beans: stateless, stateful and singleton. </p>
beans.</p>

<ul>
<li><strong>Stateless session beans</strong> <p>A stateless session bean is pooled by

conversational state) across multiple method calls and transactions. It exists
for the duration of a single client/server session.</p>
 </li>
 
<li> <strong>Singleton session beans</strong> <p>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.</p>
 </li>

</ul>


Lines 13-25 Link Here

(-)SessionBeanWizContext.xml (-5 / +8 lines)
13	In the field <b>Superclass</b> specify the superclass for the session bean, only if it is derived from one. Click <b>Browse</b> to choose from the available, already existing or created, superclasses. (This field is optional).	13	In the field <b>Superclass</b> specify the superclass for the session bean, only if it is derived from one. Click <b>Browse</b> to choose from the available, already existing or created, superclasses. (This field is optional).
14		14
15	In the field <b>State type</b> choose the type of the session bean that you create:	15	In the field <b>State type</b> choose the type of the session bean that you create:
16	<b>- Stateful</b> 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.	16	<b>- Stateless</b> – the session bean instances contain no conversational state between methods; any instance can be used for any client.
17	<b>- Stateless</b> session bean is pooled by the container to handle multiple requests from multiple clients and does not maintain any conversational state.	17	<b>- Stateful</b> – the session bean instances contain conversational state which must be retained across methods and transactions.
		18	<b>- Singleton</b> – a single session bean instance is shared between clients and supports concurrent access.
18		19
19	In the section <b>Create business interface</b>, check the business interface that you want to create:	20	In the section <b>Create business interface</b>, check the business interface that you want to create:
20	<b>- Remote Interface</b> – 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.	21	<b>- Remote</b> – 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.
21	<b>- Local Interface</b> – 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.	22	<b>- Local</b> – 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.
22	Note: You can check both interfaces, so that your session bean will have local and remote interfaces.	23	<b>- No-interface</b> – 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.
		24
		25	<b>Note:</b> It is valid to check all of the above options.
23	</description>	26	</description>
24	<topic label="Creating Session Beans" href="../org.eclipse.jst.ejb.doc.user/topics/sessbwiz.html"/>	27	<topic label="Creating Session Beans" href="../org.eclipse.jst.ejb.doc.user/topics/sessbwiz.html"/>
25	<topic label="EJB 2.x architecture" href="../org.eclipse.jst.ejb.doc.user/topics/cearch.html"/>	28	<topic label="EJB 2.x architecture" href="../org.eclipse.jst.ejb.doc.user/topics/cearch.html"/>

Return to bug 241667

Lines 55-62 Link Here

(-)topics/sessbwiz.html (-3 / +17 lines)
55	<dl>	55	<dl>
56	<dt class="dlterm">State type</dt>	56	<dt class="dlterm">State type</dt>
57		57
58	<dd>A session beans are divided in two types: stateless session beans and	58	<dd>There are three types of session beans: stateless, stateful and singleton. <dl>
59	stateful session beans.<dl>
60	<dt class="dlterm">Stateless session beans</dt>	59	<dt class="dlterm">Stateless session beans</dt>
61		60
62	<dd>A stateless session bean is a collection of related services, each represented	61	<dd>A stateless session bean is a collection of related services, each represented
Lines 76-81 Link Here
76	data to and from this conversational state, which is shared among all methods	75	data to and from this conversational state, which is shared among all methods
77	in the bean. Stateful session beans have timeout periods.</dd>	76	in the bean. Stateful session beans have timeout periods.</dd>
78		77
		78	<dt class="dlterm">Singleton session beans</dt>
		79
		80	<dd>A Singleton session bean is a session bean component that is instantiated
		81	once per application. In cases where the container is distributed over many virtual
		82	machines, each application will have one bean instance of the Singleton for each JVM.
		83	Once instantiated, a Singleton session bean instance lives for the duration of the
		84	application in which it is created. It maintains its state between client invocations
		85	but that state is not required to survive container shutdown or crash. A Singleton
		86	session bean is intended to be shared and supports concurrent access.</dd>
		87
79	</dl>	88	</dl>
80	</dd>	89	</dd>
81		90
Lines 88-94 Link Here
88	bean's business interface can be passed as a parameter or as a return value	97	bean's business interface can be passed as a parameter or as a return value
89	of a business interface method. It contains methods to initialize a session	98	of a business interface method. It contains methods to initialize a session
90	bean's state and to notify the EJB container when the reference is no more	99	bean's state and to notify the EJB container when the reference is no more
91	needed and can be removed. The business interfaces are two types:<dl>	100	needed and can be removed. There are several options available:<dl>
92	<dt class="dlterm">Remote business interface:</dt>	101	<dt class="dlterm">Remote business interface:</dt>
93		102
94	<dd>The client can run on a different machine or different Java virtual	103	<dd>The client can run on a different machine or different Java virtual
Lines 101-106 Link Here
101	<dd>The client must run on the same Java virtual machine as the bean it accesses	110	<dd>The client must run on the same Java virtual machine as the bean it accesses
102	and the location of the enterprise bean is not transparent.</dd>	111	and the location of the enterprise bean is not transparent.</dd>
103		112
		113	<dt class="dlterm">No-interface:</dt>
		114
		115	<dd>This is a variation of the Local view that exposes the public methods of the
		116	bean class without the use of a separate business interface.</dd>
		117
104	</dl>	118	</dl>
105	</dd>	119	</dd>
106		120

Lines 38-46 Link Here

(-)topics/sessb.html (-3 / +8 lines)
38	in the database, but they can access data, so we can use session beans to	38	in the database, but they can access data, so we can use session beans to
39	read, update, and insert data in a business process. Session beans access	39	read, update, and insert data in a business process. Session beans access
40	data that spans concepts, is not shared, and is usually read-only. Session	40	data that spans concepts, is not shared, and is usually read-only. Session
41	beans contain business logic, and entities model persistent data. Session	41	beans contain business logic, and entities model persistent data. There are
42	beans are divided in two types: stateless session beans and stateful session	42	three types of session beans: stateless, stateful and singleton. </p>
43	beans.</p>
44		43
45	<ul>	44	<ul>
46	<li><strong>Stateless session beans</strong> <p>A stateless session bean is pooled by	45	<li><strong>Stateless session beans</strong> <p>A stateless session bean is pooled by
Lines 53-58 Link Here
53	conversational state) across multiple method calls and transactions. It exists	52	conversational state) across multiple method calls and transactions. It exists
54	for the duration of a single client/server session.</p>	53	for the duration of a single client/server session.</p>
55	</li>	54	</li>
		55
		56	<li> <strong>Singleton session beans</strong> <p>A Singleton session bean is a session
		57	bean component that is instantiated once per application. In cases where the container
		58	is distributed over many virtual machines, each application will have one bean instance
		59	of the Singleton for each JVM.</p>
		60	</li>
56		61
57	</ul>	62	</ul>
58		63

Lines 18-26 Link Here

(-)topics/sessb.dita (-3 / +6 lines)
18	in the database, but they can access data, so we can use session beans to	18	in the database, but they can access data, so we can use session beans to
19	read, update, and insert data in a business process. Session beans access	19	read, update, and insert data in a business process. Session beans access
20	data that spans concepts, is not shared, and is usually read-only. Session	20	data that spans concepts, is not shared, and is usually read-only. Session
21	beans contain business logic, and entities model persistent data. Session	21	beans contain business logic, and entities model persistent data. There are
22	beans are divided in two types: stateless session beans and stateful session	22	three types of session beans: stateless, stateful and singleton. </p>
23	beans.</p>
24	<ul>	23	<ul>
25	<li><b>Stateless session beans</b> <p>A stateless session bean is pooled by	24	<li><b>Stateless session beans</b> <p>A stateless session bean is pooled by
26	the container to handle multiple requests from multiple clients and does not	25	the container to handle multiple requests from multiple clients and does not
Lines 29-34 Link Here
29	of a single client and maintains client-specific session information (called	28	of a single client and maintains client-specific session information (called
30	conversational state) across multiple method calls and transactions. It exists	29	conversational state) across multiple method calls and transactions. It exists
31	for the duration of a single client/server session.</p> </li>	30	for the duration of a single client/server session.</p> </li>
		31	<li> <b>Singleton session beans</b> <p>A Singleton session bean is a session
		32	bean component that is instantiated once per application. In cases where the container
		33	is distributed over many virtual machines, each application will have one bean instance
		34	of the Singleton for each JVM.</p> </li>
32	</ul>	35	</ul>
33	</conbody>	36	</conbody>
34	</concept>	37	</concept>

Lines 27-34 Link Here

(-)topics/sessbwiz.dita (-2 / +14 lines)
27	</steps>	27	</steps>
28	<postreq><p><b>General Information</b></p><dl><dlentry>	28	<postreq><p><b>General Information</b></p><dl><dlentry>
29	<dt>State type</dt>	29	<dt>State type</dt>
30	<dd>A session beans are divided in two types: stateless session beans and	30	<dd>There are three types of session beans: stateless, stateful and singleton. <dl><dlentry>
31	stateful session beans.<dl><dlentry>
32	<dt>Stateless session beans</dt>	31	<dt>Stateless session beans</dt>
33	<dd>A stateless session bean is a collection of related services, each represented	32	<dd>A stateless session bean is a collection of related services, each represented
34	by a method; the bean maintains no state from one method invocation to the	33	by a method; the bean maintains no state from one method invocation to the
Lines 44-49 Link Here
44	and the client. Methods invoked on a stateful session bean can write and read	43	and the client. Methods invoked on a stateful session bean can write and read
45	data to and from this conversational state, which is shared among all methods	44	data to and from this conversational state, which is shared among all methods
46	in the bean. Stateful session beans have timeout periods.</dd>	45	in the bean. Stateful session beans have timeout periods.</dd>
		46	</dlentry><dlentry>
		47	<dt>Singleton session beans</dt>
		48	<dd>A Singleton session bean is a session bean component that is instantiated
		49	once per application. In cases where the container is distributed over many virtual
		50	machines, each application will have one bean instance of the Singleton for each JVM.
		51	Once instantiated, a Singleton session bean instance lives for the duration of the
		52	application in which it is created. It maintains its state between client invocations
		53	but that state is not required to survive container shutdown or crash. A Singleton
		54	session bean is intended to be shared and supports concurrent access.</dd>
47	</dlentry></dl></dd>	55	</dlentry></dl></dd>
48	</dlentry></dl> <dl><dlentry>	56	</dlentry></dl> <dl><dlentry>
49	<dt>Business interface</dt>	57	<dt>Business interface</dt>
Lines 64-69 Link Here
64	<dd>The client must run on the same <tm tmclass="special" tmowner="Sun Microsystems, Inc."	72	<dd>The client must run on the same <tm tmclass="special" tmowner="Sun Microsystems, Inc."
65	tmtype="tm" trademark="Java">Java</tm> virtual machine as the bean it accesses	73	tmtype="tm" trademark="Java">Java</tm> virtual machine as the bean it accesses
66	and the location of the enterprise bean is not transparent.</dd>	74	and the location of the enterprise bean is not transparent.</dd>
		75	</dlentry><dlentry>
		76	<dt>No-interface:</dt>
		77	<dd>This is a variation of the Local view that exposes the public methods of the
		78	bean class without the use of a separate business interface.</dd>
67	</dlentry></dl></dd>	79	</dlentry></dl></dd>
68	</dlentry></dl> <dl><dlentry>	80	</dlentry></dl> <dl><dlentry>
69	<dt>Mapped name</dt>	81	<dt>Mapped name</dt>