[218957] Infopops for EJB 3.0 bean wizards

15 files changed, 835 insertions, 0 deletions

diff --git a/docs/org.eclipse.jst.ejb.doc.user/ejb_toc.ditamap b/docs/org.eclipse.jst.ejb.doc.user/ejb_toc.ditamap
index af36ed66a..cfa8c4eb6 100644
--- a/docs/org.eclipse.jst.ejb.doc.user/ejb_toc.ditamap
+++ b/docs/org.eclipse.jst.ejb.doc.user/ejb_toc.ditamap
@@ -29,6 +29,17 @@ type="task">
 type="task"></topicref>

 <topicref href="topics/txdocletconf.dita" navtitle="Configuring XDoclet annotation support"

 type="task"></topicref>

+<topicref href="topics/ejbarch.dita" navtitle="EJB 3.0 architecture"

+type="concept">

+<topicref href="topics/sessbwiz.dita" navtitle="Creating session beans" type="task">

+<topicref href="topics/sessb.dita" navtitle="Session beans" type="concept">

+</topicref>

+</topicref>

+<topicref href="topics/messbwiz.dita" navtitle="Creating message-driven beans" type="task">

+<topicref href="topics/messb.dita" navtitle="Message-driven beans"

+type="concept"></topicref>

+</topicref>

+</topicref>

 </topicref>

 </map>

 <?Pub *0000001550?>

diff --git a/docs/org.eclipse.jst.ejb.doc.user/ejb_toc.xml b/docs/org.eclipse.jst.ejb.doc.user/ejb_toc.xml
index 4abf4301a..25f8d0d1b 100644
--- a/docs/org.eclipse.jst.ejb.doc.user/ejb_toc.xml
+++ b/docs/org.eclipse.jst.ejb.doc.user/ejb_toc.xml
@@ -18,4 +18,14 @@
 <topic label="Creating message-driven beans with XDoclet annotation support" href="topics/temessb.html"/>
 <topic label="Configuring XDoclet annotation support" href="topics/txdocletconf.html"/>
 </topic>
+<topic href="topics/ejbarch.html" label="EJB 3.0 architecture">
+   <topic href="topics/sessbwiz.html" label="Creating session beans">
+      <topic href="topics/sessb.html" label="Session beans">
+      </topic>
+   </topic>
+   <topic href="topics/messbwiz.html" label="Creating message-driven beans">
+      <topic href="topics/messb.html" label="Message-driven beans">
+      </topic>
+   </topic>
+</topic>
 </toc>
diff --git a/docs/org.eclipse.jst.ejb.doc.user/index/indexed_docs b/docs/org.eclipse.jst.ejb.doc.user/index/indexed_docs
index db294cda8..c7ba3e0b6 100644
--- a/docs/org.eclipse.jst.ejb.doc.user/index/indexed_docs
+++ b/docs/org.eclipse.jst.ejb.doc.user/index/indexed_docs
@@ -12,3 +12,8 @@
 /org.eclipse.jst.ejb.doc.user/topics/tecrte.html=0

 /org.eclipse.jst.ejb.doc.user/topics/txdocletconf.html=0

 /org.eclipse.jst.ejb.doc.user/topics/ceresrc.html=0

+/org.eclipse.jst.ejb.doc.user/topics/ejbarch.html=0

+/org.eclipse.jst.ejb.doc.user/topics/sessbwiz.html=0

+/org.eclipse.jst.ejb.doc.user/topics/messbwiz.html=0

+/org.eclipse.jst.ejb.doc.user/topics/sessb.html=0

+/org.eclipse.jst.ejb.doc.user/topics/messb.html=0

diff --git a/docs/org.eclipse.jst.ejb.doc.user/org.eclipse.jst.ejb.doc.userindex.html b/docs/org.eclipse.jst.ejb.doc.user/org.eclipse.jst.ejb.doc.userindex.html
index f470c46cd..a25d00cda 100644
--- a/docs/org.eclipse.jst.ejb.doc.user/org.eclipse.jst.ejb.doc.userindex.html
+++ b/docs/org.eclipse.jst.ejb.doc.user/org.eclipse.jst.ejb.doc.userindex.html
@@ -30,6 +30,8 @@
 <ul class="indexlist">
 <li><a href="topics/cearch.html#cearch">EJB</a>
 </li>
+<li><a href="topics/ejbarch.html#ejbarch">EJB 3.0</a>
+</li>
 </ul>
 </li>
 </ul>
@@ -48,6 +50,8 @@
 <ul class="indexlist">
 <li><a href="topics/cearch.html#cearch">architecture overview</a>
 </li>
+<li><a href="topics/ejbarch.html#ejbarch">3.0 architecture overview</a>
+</li>
 <li><a href="topics/ceclientjars.html#ceclientjars">cleint JAR projects</a>
 </li>
 <li><a href="topics/tecrte.html#tecrte">creating with XDoclet annotation support</a>
@@ -100,6 +104,10 @@
 <ul class="indexlist">
 <li><a href="topics/temessb.html#temessb">XDoclet annotation support</a>
 </li>
+<li><a href="topics/messb.html#messb">overview</a>
+</li>
+<li><a href="topics/messbwiz.html#messbwiz">creating</a>
+</li>
 </ul>
 </li>
 </ul>
@@ -118,6 +126,10 @@
 <ul class="indexlist">
 <li><a href="topics/tesessb.html#tesessb">creating with XDoclet annotation support</a>
 </li>
+<li><a href="topics/sessb.html#sessb">overview</a>
+</li>
+<li><a href="topics/sessbwiz.html#sessbwiz">creating</a>
+</li>
 </ul>
 </li>
 </ul>
diff --git a/docs/org.eclipse.jst.ejb.doc.user/org.eclipse.jst.ejb.doc.userindex.xml b/docs/org.eclipse.jst.ejb.doc.user/org.eclipse.jst.ejb.doc.userindex.xml
index 91d269088..10dd28adf 100644
--- a/docs/org.eclipse.jst.ejb.doc.user/org.eclipse.jst.ejb.doc.userindex.xml
+++ b/docs/org.eclipse.jst.ejb.doc.user/org.eclipse.jst.ejb.doc.userindex.xml
@@ -16,6 +16,7 @@
     </entry>
     <entry keyword="architecture overview">
       <topic href="topics/cearch.html#cearch" title="EJB architecture"/>
+      <topic href="topics/ejbarch.html#ejbarch" title="EJB 3.0 architecture"/>
     </entry>
     <entry keyword="projects">
       <entry keyword="creating">
@@ -43,6 +44,7 @@
   <entry keyword="architecture">
     <entry keyword="EJB">
       <topic href="topics/cearch.html#cearch" title="EJB architecture"/>
+      <topic href="topics/ejbarch.html#ejbarch" title="EJB 3.0 architecture"/>
     </entry>
   </entry>
   <entry keyword="resources">
@@ -61,12 +63,14 @@
     </entry>
     <entry keyword="creating session beans">
       <topic href="topics/tesessb.html#tesessb" title="Creating session beans with XDoclet annotation support"/>
+      <topic href="topics/sessbwiz.html#sessbwiz" title="Creating session beans"/>
     </entry>
     <entry keyword="creating entity beans">
       <topic href="topics/teentityb.html#temessb" title="Creating container-managed persistence (CMP) entity beans with XDoclet annotation support"/>
     </entry>
     <entry keyword="creating message-driven beans">
       <topic href="topics/temessb.html#temessb" title="Creating message-driven beans with XDoclet annotation support"/>
+      <topic href="topics/messbwiz.html#messbwiz" title="Creating message-driven beans"/>
     </entry>
     <entry keyword="configuring">
       <topic href="topics/txdocletconf.html#configuringxdocletannotationsupport" title="Configuring XDoclet annotation support"/>
@@ -75,6 +79,8 @@
   <entry keyword="session beans">
     <entry keyword="creating with XDoclet annotation support">
       <topic href="topics/tesessb.html#tesessb" title="Creating session beans with XDoclet annotation support"/>
+      <topic href="topics/sessbwiz.html#sessbwiz" title="Creating session beans"/>
+      <topic href="topics/sessb.html#sessb" title="Session beans"/>
     </entry>
   </entry>
   <entry keyword="CMP entity beans">
@@ -85,6 +91,8 @@
   <entry keyword="message-driven beans">
     <entry keyword="XDoclet annotation support">
       <topic href="topics/temessb.html#temessb" title="Creating message-driven beans with XDoclet annotation support"/>
+      <topic href="topics/messbwiz.html#messbwiz" title="Creating message-driven beans"/>
+      <topic href="topics/messb.html#messb" title="Message-driven beans"/>
     </entry>
   </entry>
   <entry keyword="Java annotation">
diff --git a/docs/org.eclipse.jst.ejb.doc.user/topics/ejbarch.dita b/docs/org.eclipse.jst.ejb.doc.user/topics/ejbarch.dita
new file mode 100644
index 000000000..6a943f50a
--- /dev/null
+++ b/docs/org.eclipse.jst.ejb.doc.user/topics/ejbarch.dita
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!--Arbortext, Inc., 1988-2006, v.4002-->
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
+ "concept.dtd">
+<concept id="ejbarch" xml:lang="en-us">
+<title>EJB 3.0 architecture</title>
+<shortdesc>This topic provides a high-level overview of the distributed component
+architecture defined in the Sun Microsystems Enterprise <tm tmclass="special"
+tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="JavaBeans">JavaBeans</tm> (EJB)
+version 3.0 architecture specification.</shortdesc>
+<prolog><metadata>
+<keywords><indexterm>architecture<indexterm>EJB</indexterm></indexterm><indexterm>EJB<indexterm>architecture
+overview</indexterm></indexterm></keywords>
+</metadata></prolog>
+<conbody>
+<p><b>Enterprise JavaBeans</b> is a standard server-side component model
+for distributed business applications. The EJB specification is part of the <b>Java Platform Enterprise Edition</b>.</p>
+<p><b>EJB 3.0</b> makes it much easier to develop EJBs, using
+annotations rather than the complex deployment descriptors used in
+version 2.x. The use of home and remote interfaces and the <i>ejb-jar.xml</i> file are also no longer required in this release. They are replaced
+with a business interface and a bean class that implements the interface.</p>
+<p>In this release there are several types of Enterprise JavaBeans:</p>
+<p>For more information about EJB 3.0 specification go to <xref format="html" href="http://java.sun.com/products/ejb/docs.html#specs"
+scope="external">java.sun.com<desc></desc></xref> Web site.</p>
+</conbody>
+</concept>
diff --git a/docs/org.eclipse.jst.ejb.doc.user/topics/ejbarch.html b/docs/org.eclipse.jst.ejb.doc.user/topics/ejbarch.html
new file mode 100644
index 000000000..68f8ac824
--- /dev/null
+++ b/docs/org.eclipse.jst.ejb.doc.user/topics/ejbarch.html
@@ -0,0 +1,59 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="concept" name="DC.Type" />
+<meta name="DC.Title" content="EJB 3.0 architecture" />
+<meta name="abstract" content="This topic provides a high-level overview of the distributed component architecture defined in the Sun Microsystems Enterprise JavaBeans (EJB) version 3.0 architecture specification." />
+<meta name="description" content="This topic provides a high-level overview of the distributed component architecture defined in the Sun Microsystems Enterprise JavaBeans (EJB) version 3.0 architecture specification." />
+<meta content="architecture, EJB, architecture overview" name="DC.subject" />
+<meta content="architecture, EJB, architecture overview" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/sessb.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/messb.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="ejbarch" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>EJB 3.0 architecture</title>
+</head>
+<body id="ejbarch"><a name="ejbarch"><!-- --></a>
+
+
+<h1 class="topictitle1">EJB 3.0 architecture</h1>
+
+
+
+<div><p>This topic provides a high-level overview of the distributed component
+architecture defined in the Sun Microsystems Enterprise JavaBeans?„? (EJB)
+version 3.0 architecture specification.</p>
+
+<p><b>Enterprise JavaBeans</b> is a standard server-side component model
+for distributed business applications. The EJB specification is part of
+the <b>Java Platform Enterprise Edition</b>.</p>
+
+<p><b>EJB 3.0</b> makes it much easier to develop EJBs, using
+annotations rather than the complex deployment descriptors used in
+version 2.x. The use of home and remote interfaces and the <i>ejb-jar.xml</i>
+file are also no longer required in this release. They are replaced with
+a business interface and a bean class that implements the interface.</p>
+
+<p>In this release there are several types of Enterprise JavaBeans:</p>
+
+<ul class="ullinks">
+<li><strong>Entities</strong></li>
+<li class="ulchildlink"><strong><a href="../topics/sessb.html">Session Beans</a></strong></li>
+<li class="ulchildlink"><strong><a href="../topics/messb.html">Message-driven Beans</a></strong></li>
+</ul>
+</div>
+
+<div>For more information about EJB 3.0 specification go to <a
+	href="http://java.sun.com/products/ejb/docs.html#specs" target="_blank"
+	title="">java.sun.com</a> Web site.</div>
+
+</body>
+</html>
diff --git a/docs/org.eclipse.jst.ejb.doc.user/topics/messb.dita b/docs/org.eclipse.jst.ejb.doc.user/topics/messb.dita
new file mode 100644
index 000000000..2fcedecd9
--- /dev/null
+++ b/docs/org.eclipse.jst.ejb.doc.user/topics/messb.dita
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!--Arbortext, Inc., 1988-2006, v.4002-->
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
+ "concept.dtd">
+<concept id="messb" xml:lang="en-us">
+<title>Message-driven Beans</title>
+<shortdesc></shortdesc>
+<prolog><metadata>
+<keywords><indexterm>message-driven beans</indexterm>
+</metadata></prolog>
+<conbody>
+<p>A <b>message-driven bean</b> is an enterprise bean that allows Java EE
+applications to process messages asynchronously. It acts as a Java Message Service (JMS)
+message listener, which is similar to an event listener except that it
+receives messages instead of events. The messages may be sent by any Java EE
+component - an application client, another enterprise bean, or a Web
+component - or by a JMS application or system that does not use Java EE
+technology.</p>
+<p>In JMS, a message is a Java object with two parts: a <b>header</b>
+and a <b>body</b>. The header is composed of delivery
+information and metadata. The message body carries the application
+data, which can take several forms: text, serializable objects, byte
+streams, etc. The JMS API defines several message types (<b>TextMessage,
+MapMessage, ObjectMessage</b>, and others) and provides methods for
+delivering messages to and receiving messages from other applications.</p>
+</conbody>
+</concept>
diff --git a/docs/org.eclipse.jst.ejb.doc.user/topics/messb.html b/docs/org.eclipse.jst.ejb.doc.user/topics/messb.html
new file mode 100644
index 000000000..e89dc8a3a
--- /dev/null
+++ b/docs/org.eclipse.jst.ejb.doc.user/topics/messb.html
@@ -0,0 +1,56 @@
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright" content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="concept" name="DC.Type" />
+<meta name="DC.Title" content="Message-driven beans" />
+<meta name="abstract" content="" />
+<meta name="description" content="" />
+<meta content="message-driven beans" name="DC.subject" />
+<meta content="message-driven beans" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/ejbarch.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="messb" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" />
+<title>Message-driven Beans</title>
+</head>
+<body id="messb"><a name="messb"><!-- --></a>
+
+
+<h1 class="topictitle1">Message-driven Beans</h1>
+
+
+
+<div><p>A <b>message-driven bean</b> is an enterprise bean that allows Java EE
+applications to process messages asynchronously. It acts as a Java Message Service (JMS)
+message listener, which is similar to an event listener except that it
+receives messages instead of events. The messages may be sent by any Java EE
+component - an application client, another enterprise bean, or a Web
+component - or by a JMS application or system that does not use Java EE
+technology.</p>
+
+<p>In JMS, a message is a Java object with two parts: a <b>header</b>
+and a <b>body</b>. The header is composed of delivery
+information and metadata. The message body carries the application
+data, which can take several forms: text, serializable objects, byte
+streams, etc. The JMS API defines several message types (<b>TextMessage,
+MapMessage, ObjectMessage</b>, and others) and provides methods for
+delivering messages to and receiving messages from other applications.</p>
+
+</div>
+
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a
+	href="../topics/messbwiz.html">Creating Message-driven Beans</a></div>
+</div>
+</div>
+
+</body>
+</html>
diff --git a/docs/org.eclipse.jst.ejb.doc.user/topics/messbwiz.dita b/docs/org.eclipse.jst.ejb.doc.user/topics/messbwiz.dita
new file mode 100644
index 000000000..69c78dfcf
--- /dev/null
+++ b/docs/org.eclipse.jst.ejb.doc.user/topics/messbwiz.dita
@@ -0,0 +1,81 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!--Arbortext, Inc., 1988-2006, v.4002-->
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
+ "task.dtd">
+<task id="messbwiz" xml:lang="en-us">
+<title>Creating Message-driven Beans</title>
+<shortdesc>You can use a wizard to create a message-driven bean and add it to your
+project.</shortdesc>
+<prolog><metadata>
+<keywords><indexterm>message-driven beans</indexterm><indexterm>creating
+message-driven beans</keywords>
+</metadata></prolog>
+<taskbody>
+<context><p>The message-driven bean wizard helps you create an Enterprise message-driven bean by
+walking you through the creation process and by providing you with
+output files that you can use or that you can modify for use with your
+application.</p>
+<p>To create a message-driven bean, complete the following steps:</p></context>
+<steps>
+<step><cmd>From the J2EE perspective, expand your  EJB project in the Project Explorer view.</cmd></step>
+<step><cmd>Right click on the <b>Message-Driven Bean</b> icon, and select <menucascade>
+<uicontrol>New</uicontrol><uicontrol>Message-Driven Bean</uicontrol></menucascade> from
+the pop-up menu.</cmd><stepresult> The <uicontrol>Create Message-Driven Bean</uicontrol> wizard
+appears.</stepresult></step>
+<step><cmd>Follow the project wizard prompts.</cmd></step>
+</steps>
+<postreq><p><b>General Information</b></p><dl><dlentry>
+<dt><b>Destination name</b></dt>
+<dd>This field provides the attribute <b>mappedName</b> to the <b>@MessageDriven</b>
+	annotation. This attribute specifies the product-specific name to which
+	the message-driven bean should be mapped. You can also use this
+	attribute to specify the JNDI name of the destination from
+	which the bean will consume messages.</dd>
+</dlentry></dl>
+<dl><dlentry>
+<dt><b>Destination type</b></dt>
+<dd>To send a JMS message, we need a connection to the JMS
+	provider and a destination address for the message. A JMS connection
+	factory makes the connection to the provider possible. In JMS, messages
+	are not sent directly to applications; they are sent to topics or queues:<p> <ul>
+<li><b>Queue:</b><br />
+ Queue is used as a destination for point–to–point messaging. The <b>point-to-point</b>
+		messaging model allows JMS clients to send and receive messages both
+		synchronously and asynchronously via virtual channels known as <i>queues</i>.
+		The p2p messaging model has traditionally been a pull- or
+		polling-based model, where messages are requested from the queue
+		instead of being pushed to the client automatically. A queue may have
+		multiple receivers, but only one receiver may receive each message.
+		Messages holding this queue are of <b>MapMessages</b> type, which stores
+		the information about the email as name/value pair.</li>
+<li><b>Topic:</b><br />
+Topic is used as a destination for publish/subscribe messaging. In <b>publish-and-subscribe</b>
+		messaging, one producer can send a message to many consumers through a
+		virtual channel called a <i>topic</i>. Consumers can choose to subscribe to a
+		topic. Any messages addressed to a topic are delivered to all the
+		topic's consumers. Every consumer receives a copy of each message. The
+		pub/sub messaging model is a push-based model, where
+		messages are automatically broadcast to consumers without them having
+		to request or poll the topic for new messages. In the pub/sub messaging
+		model, the producer sending the message is not dependent on the
+		consumers receiving the message. Optionally, JMS clients that use
+		pub/sub can establish durable subscriptions that allow consumers to
+		disconnect and later reconnect and collect messages that were
+		published while they were disconnected.</li>
+</ul></p></dd>
+</dlentry></dl>
+<dl><dlentry>
+<dt><b>Transaction type</b></dt>
+<dd>The <b>Transaction type</b> field is used to specify
+	whether the transaction is handled by the <b>Container</b> or the <b>Bean</b>.</dd>
+</dlentry></dl>
+<dl><dlentry>
+<dt><b>Interfaces</b></dt>
+<dd>Message-driven beans usually implement the <b>javax.jms.MessageListener</b>
+	interface. A <i>MessageListener object</i> is used to receive
+	asynchronously delivered messages. This interface defines the <b>onMessage()</b>
+	method. This method processes the JMS messages received by a bean.</dd>
+</dlentry></dl></postreq>
+</steps>
+</taskbody>
+</task>
diff --git a/docs/org.eclipse.jst.ejb.doc.user/topics/messbwiz.html b/docs/org.eclipse.jst.ejb.doc.user/topics/messbwiz.html
new file mode 100644
index 000000000..0ca4a296e
--- /dev/null
+++ b/docs/org.eclipse.jst.ejb.doc.user/topics/messbwiz.html
@@ -0,0 +1,152 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright"
+	content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label"
+	content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="Creating session beans" />
+<meta name="abstract"
+	content="You can use a wizard to create a message-driven bean and add it to your
+project." />
+<meta name="description"
+	content="You can use a wizard to create a message-driven bean and add it to your
+project." />
+<meta content="message-driven beans, creating message-driven beans" name="DC.subject" />
+<meta content="message-driven beans, creating message-driven beans" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/ejbarch.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/messb.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="messbwiz" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../../org.eclipse.wst.doc.user/common.css"
+	type="text/css" rel="stylesheet" />
+<title>Creating Message-driven Beans</title>
+</head>
+<body id="messbwiz">
+<a name="messbwiz"><!-- --></a>
+
+
+<h1 class="topictitle1">Creating Message-driven Beans</h1>
+
+
+
+<div>
+<p>You can use a wizard to create a message-driven bean and add it to your
+project.</p>
+
+<p>The message-driven bean wizard helps you create an Enterprise message-driven bean by
+walking you through the creation process and by providing you with
+output files that you can use or that you can modify for use with your
+application.</p>
+
+<div class="section">
+<p>To create a message-driven bean, complete the following steps:</p>
+</div>
+
+<ol>
+	<li class="stepexpand"><span>In the Java EE perspective,
+	expand your EJB project in the Project Explorer view.</span></li>
+
+	<li class="stepexpand"><span>Right click on the <strong>Message-Driven
+	Bean</strong> icon, and select <span class="menucascade"> <span
+		class="uicontrol">New</span> &gt; <span class="uicontrol">Message-Driven
+	Bean</span></span> from the pop-up menu.</span> The <span class="uicontrol">Create
+	Message-Driven Bean</span> wizard appears.</li>
+
+	<li class="stepexpand"><span>Follow the project wizard
+	prompts.</span></li>
+
+</ol>
+
+<div class="section">
+<p><strong>General Information</strong></p>
+<dl>
+	<dt class="dlterm"><b>Destination name</b></dt>
+
+
+	<dd>This field provides the attribute <b>mappedName</b> to the <b>@MessageDriven</b>
+	annotation. This attribute specifies the product-specific name to which
+	the message-driven bean should be mapped. You can also use this
+	attribute to specify the JNDI name of the destination from
+	which the bean will consume messages.</dd>
+</dl>
+
+<dl>
+	<dt class="dlterm"><strong>Destination type</strong></dt>
+
+	<dd>To send a JMS message, we need a connection to the JMS
+	provider and a destination address for the message. A JMS connection
+	factory makes the connection to the provider possible. In JMS, messages
+	are not sent directly to applications; they are sent to topics or queues:
+	<div class="p">
+	<ul>
+		<li><strong>Queue:</strong><br />
+		Queue is used as a destination for point–to–point messaging. The <b>point-to-point</b>
+		messaging model allows JMS clients to send and receive messages both
+		synchronously and asynchronously via virtual channels known as <i>queues</i>.
+		The p2p messaging model has traditionally been a pull- or
+		polling-based model, where messages are requested from the queue
+		instead of being pushed to the client automatically. A queue may have
+		multiple receivers, but only one receiver may receive each message.
+		Messages holding this queue are of <b>MapMessages</b> type, which stores
+		the information about the email as name/value pair.</li>
+		<li><strong>Topic:</strong><br />
+		Topic is used as a destination for publish/subscribe messaging. In <b>publish-and-subscribe</b>
+		messaging, one producer can send a message to many consumers through a
+		virtual channel called a <i>topic</i>. Consumers can choose to subscribe to a
+		topic. Any messages addressed to a topic are delivered to all the
+		topic's consumers. Every consumer receives a copy of each message. The
+		pub/sub messaging model is a push-based model, where
+		messages are automatically broadcast to consumers without them having
+		to request or poll the topic for new messages. In the pub/sub messaging
+		model, the producer sending the message is not dependent on the
+		consumers receiving the message. Optionally, JMS clients that use
+		pub/sub can establish durable subscriptions that allow consumers to
+		disconnect and later reconnect and collect messages that were
+		published while they were disconnected.</li>
+
+	</ul>
+	</div>
+	</dd>
+</dl>
+
+<dl>
+	<dt class="dlterm"><b>Transaction type</b></dt>
+
+	<dd>The <b>Transaction type</b> field is used to specify
+	whether the transaction is handled by the <b>Container</b> or the <b>Bean</b>.</dd>
+</dl>
+
+
+
+<dl>
+	<dt class="dlterm"><strong>Interfaces</strong></dt>
+
+	<dd>Message-driven beans usually implement the <b>javax.jms.MessageListener</b>
+	interface. A <i>MessageListener</i> object is used to receive
+	asynchronously delivered messages. This interface defines the <b>onMessage()</b>
+	method. This method processes the JMS messages received by a bean.</dd>
+</dl>
+
+</div>
+
+</div>
+
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a
+	href="../topics/ejbarch.html">EJB 3.0 architecture</a></div>
+<div class="childlink"><strong>Child topic:</strong> <a
+	href="../topics/messb.html">Message-driven Beans</a></div>
+</div>
+</div>
+
+</body>
+</html>
diff --git a/docs/org.eclipse.jst.ejb.doc.user/topics/sessb.dita b/docs/org.eclipse.jst.ejb.doc.user/topics/sessb.dita
new file mode 100644
index 000000000..09b67158f
--- /dev/null
+++ b/docs/org.eclipse.jst.ejb.doc.user/topics/sessb.dita
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!--Arbortext, Inc., 1988-2006, v.4002-->
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
+ "concept.dtd">
+<concept id="sessb" xml:lang="en-us">
+<title>Session Beans</title>
+<shortdesc></shortdesc>
+<prolog><metadata>
+<keywords><indexterm>session beans</indexterm>
+</metadata></prolog>
+<conbody>
+<p>A <b>session bean</b> is a type of enterprise bean. It is created by a
+client and usually exists only for the duration of a single
+client-server session.</p>
+<p>Session beans are useful for describing interactions between other
+beans (taskflow) and for implementing particular tasks. They do not
+represent data 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.</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 maintain any
+	conversational state.</p>
+</li>
+<li>
+<b>Stateful session beans</b>
+<p>A 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.</p>
+</li>
+</ul>
+</conbody>
+</concept>
diff --git a/docs/org.eclipse.jst.ejb.doc.user/topics/sessb.html b/docs/org.eclipse.jst.ejb.doc.user/topics/sessb.html
new file mode 100644
index 000000000..a17bec6db
--- /dev/null
+++ b/docs/org.eclipse.jst.ejb.doc.user/topics/sessb.html
@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright"
+	content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label"
+	content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="concept" name="DC.Type" />
+<meta name="DC.Title" content="Session beans" />
+<meta name="abstract" content="" />
+<meta name="description" content="" />
+<meta content="session beans" name="DC.subject" />
+<meta content="session beans" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/sessbwiz.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="sessb" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../../org.eclipse.wst.doc.user/common.css"
+	type="text/css" rel="stylesheet" />
+<title>Session Beans</title>
+</head>
+<body id="sessb">
+<a name="sessb"><!-- --></a>
+
+
+<h1 class="topictitle1">Session Beans</h1>
+
+
+
+<div>
+<p>A <b>session bean</b> is a type of enterprise bean. It is created
+by a client and usually exists only for the duration of a single
+client-server session.</p>
+
+<p>Session beans are useful for describing interactions between
+other beans (taskflow) and for implementing particular tasks. They do
+not represent data 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.</p>
+
+
+<ul>
+	<li><strong>Stateless session beans</strong>
+
+	<p>A stateless session bean is pooled by the container to handle
+	multiple requests from multiple clients and does not maintain any
+	conversational state.</p>
+
+	</li>
+	<li><strong>Stateful session beans</strong>
+
+	<p>A 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.</p>
+
+	</li>
+</ul>
+
+</div>
+
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a
+	href="../topics/sessbwiz.html">Creating Session Beans</a></div>
+</div>
+
+</div>
+
+</body>
+</html>
diff --git a/docs/org.eclipse.jst.ejb.doc.user/topics/sessbwiz.dita b/docs/org.eclipse.jst.ejb.doc.user/topics/sessbwiz.dita
new file mode 100644
index 000000000..e475f1066
--- /dev/null
+++ b/docs/org.eclipse.jst.ejb.doc.user/topics/sessbwiz.dita
@@ -0,0 +1,93 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!--Arbortext, Inc., 1988-2006, v.4002-->
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
+ "task.dtd">
+<task id="sessbwiz" xml:lang="en-us">
+<title>Creating Session Beans</title>
+<shortdesc>You can use a wizard to create a session bean and add it to your
+project.</shortdesc>
+<prolog><metadata>
+<keywords><indexterm>session beans</indexterm><indexterm>creating
+session beans</keywords>
+</metadata></prolog>
+<taskbody>
+<context><p>The session bean wizard helps you create an Enterprise session bean by
+walking you through the creation process and by providing you with
+output files that you can use or that you can modify for use with your
+application.</p>
+<p>To create a session bean, complete the following steps:</p></context>
+<steps>
+<step><cmd>From the J2EE perspective, expand your  EJB project in the Project Explorer view.</cmd></step>
+<step><cmd>Right click on the <b>Session Bean</b> icon, and select <menucascade>
+<uicontrol>New</uicontrol><uicontrol>Session Bean</uicontrol></menucascade> from
+the pop-up menu.</cmd><stepresult> The <uicontrol>Create Session Bean</uicontrol> wizard
+appears.</stepresult></step>
+<step><cmd>Follow the project wizard prompts.</cmd></step>
+</steps>
+<postreq><p><b>General Information</b></p><dl><dlentry>
+<dt><b>State type</b></dt>
+<dd>A session beans are divided in two types: stateless session
+	beans and stateful session beans.<p> <ul>
+<li><b>Stateless session beans</b><br />
+ 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 next. When you invoke a method on a stateless
+		session bean, it executes the method and returns the result without
+		knowing or caring what other requests have gone before or might
+		follow. Stateless session beans have longer lives because they do
+		not maintain any conversational state.</li>
+<li><b>Stateful session beans</b><br />
+A stateful session bean performs tasks on behalf of a client and
+		maintains state related to that client. This state is called
+		conversational state because it represents a continuing conversation
+		between the stateful session bean 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.</li>
+</ul></p></dd>
+</dlentry></dl>
+<dl><dlentry>
+<dt><b>Business interface</b></dt>
+<dd>A business interface of a session bean is an ordinary Java
+	interface that contains the business methods for the bean. A reference
+	to a session 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:<p> <ul>
+<li><b>Remote business interface:</b><br />
+ 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.</li>
+<li><b>Local business interface:</b><br />
+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.</li>
+</ul></p></dd>
+</dlentry></dl>
+<dl><dlentry>
+<dt><b>Mapped name</b></dt>
+<dd>Specifies the bean's global JNDI name. The use of mappedName
+	attribute allows you to assign names which you can use to search the
+	EJB bean through the remote client.</dd>
+</dlentry></dl>
+<dl><dlentry>
+<dt><b>Transaction type</b></dt>
+<dd>The <b>Transaction type</b> field is used to specify
+	whether the transaction is handled by the <b>Container</b> or the <b>Bean</b>.</dd>
+</dlentry></dl>
+<dl><dlentry>
+<dt><b>Home and Components Interfaces</b></dt>
+<dd>Home and component interfaces are used only for EJB 2.x
+	session beans.<p> <ul>
+<li><b>Home interface:</b><br />
+ The home interface allows a client to create, remove and find
+		existing instances of enterprise beans.</li>
+<li><b>Component interface:</b><br />
+The component interface allows a client to access the business
+		methods of the enterprise bean.</li>
+</ul></p></dd>
+</dlentry></dl></postreq>
+</steps>
+</taskbody>
+</task>
+
diff --git a/docs/org.eclipse.jst.ejb.doc.user/topics/sessbwiz.html b/docs/org.eclipse.jst.ejb.doc.user/topics/sessbwiz.html
new file mode 100644
index 000000000..d6e12a319
--- /dev/null
+++ b/docs/org.eclipse.jst.ejb.doc.user/topics/sessbwiz.html
@@ -0,0 +1,178 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
+<meta name="copyright"
+	content="Copyright (c) 2000, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" />
+<meta name="DC.rights.owner" content="(C) Copyright 2000, 2008" />
+<meta content="public" name="security" />
+<meta content="index,follow" name="Robots" />
+<meta http-equiv="PICS-Label"
+	content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
+<meta content="task" name="DC.Type" />
+<meta name="DC.Title" content="Creating session beans" />
+<meta name="abstract"
+	content="You can use a wizard to create a session bean and add it to your project." />
+<meta name="description"
+	content="You can use a wizard to create a session bean and add it to your project." />
+<meta content="session beans, creating session beans" name="DC.subject" />
+<meta content="session beans, creating session beans" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/ejbarch.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/sessb.html" />
+<meta content="XHTML" name="DC.Format" />
+<meta content="sessbwiz" name="DC.Identifier" />
+<meta content="en-us" name="DC.Language" />
+<link href="../../../org.eclipse.wst.doc.user/common.css"
+	type="text/css" rel="stylesheet" />
+<title>Creating Session Beans</title>
+</head>
+<body id="sessbwiz">
+<a name="sessbwiz"><!-- --></a>
+
+
+<h1 class="topictitle1">Creating Session Beans</h1>
+
+
+
+<div>
+<p>You can use a wizard to create a session bean and add it to your
+project.</p>
+
+<p>The session bean wizard helps you create an Enterprise session bean by
+walking you through the creation process and by providing you with
+output files that you can use or that you can modify for use with your
+application.</p>
+
+<div class="section">
+<p>To create a session bean, complete the following steps:</p>
+</div>
+
+<ol>
+	<li class="stepexpand"><span>In the Java EE perspective,
+	expand your EJB project in the Project Explorer view.</span></li>
+
+	<li class="stepexpand"><span>Right click on the <strong>Session
+	Bean</strong> icon, and select <span class="menucascade"> <span
+		class="uicontrol">New</span> &gt; <span class="uicontrol">Session
+	Bean</span></span> from the pop-up menu.</span> The <span class="uicontrol">Create
+	Session Bean</span> wizard appears.</li>
+
+	<li class="stepexpand"><span>Follow the project wizard
+	prompts.</span></li>
+
+</ol>
+
+<div class="section">
+<p><strong>General Information</strong></p>
+<dl>
+	<dt class="dlterm"><strong>State type:</strong></dt>
+
+	<dd>A session beans are divided in two types: stateless session
+	beans and stateful session beans.
+	<div class="p">
+	<ul>
+		<li><strong>Stateless session beans</strong><br />
+		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 next. When you invoke a method on a stateless
+		session bean, it executes the method and returns the result without
+		knowing or caring what other requests have gone before or might
+		follow. Stateless session beans have longer lives because they do
+		not maintain any conversational state.</li>
+		<li><strong>Stateful session beans</strong><br />
+		A stateful session bean performs tasks on behalf of a client and
+		maintains state related to that client. This state is called
+		conversational state because it represents a continuing conversation
+		between the stateful session bean 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.</li>
+
+	</ul>
+	</div>
+	</dd>
+</dl>
+
+<dl>
+	<dt class="dlterm"><strong>Business interface</strong></dt>
+
+	<dd>A business interface of a session bean is an ordinary Java
+	interface that contains the business methods for the bean. A reference
+	to a session bean&apos;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&apos;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:
+	<div class="p">
+	<ul>
+		<li><strong>Remote business interface:</strong><br />
+		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.</li>
+		<li><strong>Local business interface:</strong><br />
+		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.</li>
+
+	</ul>
+	</div>
+	</dd>
+</dl>
+
+
+
+
+<dl>
+	<dt class="dlterm"><b>Mapped name</b></dt>
+
+
+	<dd>Specifies the bean&apos;s global JNDI name. The use of mappedName
+	attribute allows you to assign names which you can use to search the
+	EJB bean through the remote client.</dd>
+</dl>
+
+
+
+<dl>
+	<dt class="dlterm"><b>Transaction type</b></dt>
+
+	<dd>The <b>Transaction type</b> field is used to specify
+	whether the transaction is handled by the <b>Container</b> or the <b>Bean</b>.</dd>
+</dl>
+
+
+<dl>
+	<dt class="dlterm"><strong>Home and Components Interfaces</strong></dt>
+
+	<dd>Home and component interfaces are used only for EJB 2.x
+	session beans.
+	<div class="p">
+	<ul>
+		<li><strong>Home interface:</strong><br />
+		The home interface allows a client to create, remove and find
+		existing instances of enterprise beans.</li>
+		<li><strong>Component interface:</strong><br />
+		The component interface allows a client to access the business
+		methods of the enterprise bean.</li>
+	</ul>
+	</div>
+	</dd>
+
+</dl>
+
+</div>
+
+</div>
+
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a
+	href="../topics/ejbarch.html">EJB 3.0 architecture</a></div>
+<div class="childlink"><strong>Child topic:</strong> <a
+	href="../topics/sessb.html">Session Beans</a></div>
+</div>
+</div>
+
+
+</body>
+</html>