[jboss-cvs] JBossAS SVN: r101661 - projects/ejb3/components/singleton/trunk/docs/reference/en.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Mar 1 10:28:35 EST 2010
Author: jaikiran
Date: 2010-03-01 10:28:34 -0500 (Mon, 01 Mar 2010)
New Revision: 101661
Modified:
projects/ejb3/components/singleton/trunk/docs/reference/en/container.xml
projects/ejb3/components/singleton/trunk/docs/reference/en/jbremoting.xml
projects/ejb3/components/singleton/trunk/docs/reference/en/proxy.xml
Log:
Minor updates to docs
Modified: projects/ejb3/components/singleton/trunk/docs/reference/en/container.xml
===================================================================
--- projects/ejb3/components/singleton/trunk/docs/reference/en/container.xml 2010-03-01 15:25:47 UTC (rev 101660)
+++ projects/ejb3/components/singleton/trunk/docs/reference/en/container.xml 2010-03-01 15:28:34 UTC (rev 101661)
@@ -22,16 +22,17 @@
In this section we will look into the implementation available in the "impl" module of the singleton component.
</para>
<para>
- This module provides a simple <link linkend="TODO-link">SingletonContainer</link> which is an implementation of the
- new container SPI. This container uses a <link linkend="TODO-link">SingletonEJBInstanceManagerImpl</link> for managing
- the bean instances. The SingletonContainer itself acts an <link linkend="TODO-link">EJBLifecycleHandler</link>
+ This module provides a simple <ulink url="http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/components/singleton/trunk/impl/src/main/java/org/jboss/ejb3/singleton/impl/container/SingletonContainer.java">SingletonContainer</ulink>
+ which is an implementation of the
+ new container SPI. This container uses a <ulink url="http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/components/singleton/trunk/impl/src/main/java/org/jboss/ejb3/singleton/impl/container/SingletonEJBInstanceManagerImpl.java">SingletonEJBInstanceManagerImpl</ulink> for managing
+ the bean instances. The SingletonContainer itself acts an <ulink url="http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/components/container/trunk/spi/src/main/java/org/jboss/ejb3/container/spi/lifecycle/EJBLifecycleHandler.java">EJBLifecycleHandler</ulink>
</para>
</sect1>
<sect1>
<title>aop-impl module</title>
<para>
In it's current form, this acts as an integration between the "impl" module and the old containers and interceptors which
- are based on AOP and reside in the jboss-ejb3-core module. The <link linkend="TODO-link">AOPBasedSingletonContainer</link>
+ are based on AOP and reside in the jboss-ejb3-core module. The <ulink url="http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/components/singleton/trunk/aop-impl/src/main/java/org/jboss/ejb3/singleton/aop/impl/AOPBasedSingletonContainer.java">AOPBasedSingletonContainer</ulink>
*is a* org.jboss.ejb3.EJBContainer (the old jboss-ejb3-core) *as well as* a org.jboss.ejb3.container.spi.EJBContainer (new SPI based):
<programlisting>
<![CDATA[
@@ -53,10 +54,10 @@
The AOPBasedSingletonContainer is responsible for the following:
<itemizedlist>
<listitem>
- <para>Create a instance of the new SPI based <link linkend="TODO-link">SingletonContainer</link></para>
+ <para>Create a instance of the new SPI based <ulink url="http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/components/singleton/trunk/impl/src/main/java/org/jboss/ejb3/singleton/impl/container/SingletonContainer.java">SingletonContainer</ulink></para>
</listitem>
<listitem>
- <para>The SingletonContainer thus created will be passed an <link linkend="TODO-link">AOPBasedInterceptorRegistry</link>
+ <para>The SingletonContainer thus created will be passed an <ulink url="http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/components/singleton/trunk/aop-impl/src/main/java/org/jboss/ejb3/singleton/aop/impl/AOPBasedInterceptorRegistry.java">AOPBasedInterceptorRegistry</ulink>
The AOPBasedInterceptorRegistry uses a AOP backed interceptor stack for intercepting the calls to the bean instance.</para>
</listitem>
<listitem>
Modified: projects/ejb3/components/singleton/trunk/docs/reference/en/jbremoting.xml
===================================================================
--- projects/ejb3/components/singleton/trunk/docs/reference/en/jbremoting.xml 2010-03-01 15:25:47 UTC (rev 101660)
+++ projects/ejb3/components/singleton/trunk/docs/reference/en/jbremoting.xml 2010-03-01 15:28:34 UTC (rev 101661)
@@ -8,7 +8,8 @@
<title>Overview</title>
<para>The proxies created for a singleton session bean interact with client side invocation handlers.
The responsibility of these client side invocation handlers is to (somehow) pass on the control to the container which might reside on a remote server.
- The invocation handler uses the new SPI <link linkend="TODO-link">RemotingContainer</link> and just invokes the invoke() method on the RemotingContainer.
+ The invocation handler uses the new SPI <ulink url="http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/components/container/trunk/spi/src/main/java/org/jboss/ejb3/container/spi/remote/RemotingContainer.java">RemotingContainer</ulink>
+ and just invokes the invoke() method on the RemotingContainer.
Implementations of the RemotingContainer will have the necessary knowledge to (somehow) pass on the control to the container on the remote server. In this
chapter, we will look at one such implementation of RemotingContainer.
</para>
@@ -16,16 +17,18 @@
<sect1 id="jbremotingcontainer">
<title>JBoss Remoting 2.x based implementation of RemotingContainer</title>
<para>
- A JBoss Remoting 2.x based implementation of the RemotingContainer is available <link linkend="TODO-link">here</link>. Internally it uses
+ A JBoss Remoting 2.x based implementation of the RemotingContainer is available here <ulink url="http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/components/singleton/trunk/impl/src/main/java/org/jboss/ejb3/singleton/impl/remoting/JBossRemotingContainer.java">JBossRemotingContainer</ulink>.
+ Internally it uses
the default InvokerLocator URL (or the one overridden in metadata) to connect to the JBRemoting server. The important thing to notice here
is that it expects a "SIMPLE" subsystem to be available on this Remoting connector (unlike the older client side interceptors which expect
an "AOP" subsystem). The <code>JBossRemotingContainer</code> creates a <code>InvocationRequest</code> which contains the container id as well
- as a <link linkend="TODO-link">RemotableContainerInvocation</link>.
+ as a <ulink url="http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/components/singleton/trunk/impl/src/main/java/org/jboss/ejb3/singleton/impl/remoting/RemotableContainerInvocation.java">RemotableContainerInvocation</ulink>.
<note><para>Client side interceptors need to be invoked in the JBossRemotingContainer before passing on the control to the
JBRemoting server side invocation handler. This is currently a TODO</para></note>
</para>
<para>
- The "SIMPLE" subsystem is backed by a <link linkend="TODO-link">RemotingInvocationHandler</link> which is a server side
+ The "SIMPLE" subsystem is backed by a <ulink url="http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/components/singleton/trunk/impl/src/main/java/org/jboss/ejb3/singleton/impl/remoting/RemotingInvocationHandler.java">RemotingInvocationHandler</ulink>
+ which is a server side
JBRemoting invocation handler (and hence implements <code>org.jboss.remoting.ServerInvocationHandler</code>). The goal of this RemotingInvocationHandler
is to remote any AOP aspects from the client to remote container interaction. Internally, when a call reaches the <code>RemotingInvocationHandler</code>,
it obtains a container id (TODO: we need to discuss this) from the <code>InvocationRequest</code>.
Modified: projects/ejb3/components/singleton/trunk/docs/reference/en/proxy.xml
===================================================================
--- projects/ejb3/components/singleton/trunk/docs/reference/en/proxy.xml 2010-03-01 15:25:47 UTC (rev 101660)
+++ projects/ejb3/components/singleton/trunk/docs/reference/en/proxy.xml 2010-03-01 15:28:34 UTC (rev 101661)
@@ -9,9 +9,13 @@
<sect1>
<title>Invocation Handlers</title>
<para>
- These proxies use invocation handlers which interact with a <link linkend="TODO-link">RemotingContainer</link>. The implementations
+ These proxies use invocation handlers which interact with a
+ <ulink url="http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/components/container/trunk/spi/src/main/java/org/jboss/ejb3/container/spi/remote/RemotingContainer.java">RemotingContainer</ulink>.
+ The implementations
of RemotingContainer are responsible for invoking the real remote container (EJBContainer.invoke(ContainerInvocation)). An example
- implementation of the RemotingContainer is the <link linkend="TODO-link">JBossRemotingContainer</link> which uses JBoss Remoting2 to
+ implementation of the RemotingContainer is the
+ <ulink url="http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/components/singleton/trunk/impl/src/main/java/org/jboss/ejb3/singleton/impl/remoting/JBossRemotingContainer.java">JBossRemotingContainer</ulink>
+ which uses JBoss Remoting2 to
invoke on the remote container. Before doing so, it may even run the invocation past some client side interceptors.
</para>
<note>
More information about the jboss-cvs-commits
mailing list