[jboss-cvs] jboss-seam/doc/reference/en/modules ...
Gavin King
gavin.king at jboss.com
Tue Jun 26 16:52:00 EDT 2007
User: gavin
Date: 07/06/26 16:52:00
Modified: doc/reference/en/modules annotations.xml components.xml
concepts.xml i18n.xml xml.xml
Log:
update to new packaging
Revision Changes Path
1.69 +6 -6 jboss-seam/doc/reference/en/modules/annotations.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: annotations.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/annotations.xml,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -b -r1.68 -r1.69
--- annotations.xml 26 Jun 2007 20:33:41 -0000 1.68
+++ annotations.xml 26 Jun 2007 20:52:00 -0000 1.69
@@ -109,7 +109,7 @@
<literal>@Startup</literal>
</term>
<listitem>
- <programlisting><![CDATA[@Scope(APPLICATION) @Startup(depends={"org.jboss.core.jndi", "org.jboss.core.jta"})]]></programlisting>
+ <programlisting><![CDATA[@Scope(APPLICATION) @Startup(depends="org.jboss.seam.bpm.jbpm")]]></programlisting>
<para> Specifies that an application scope component is started immediately at initialization time.
This is mainly used for certain built-in components that bootstrap critical infrastructure such
as JNDI, datasources, etc. </para>
@@ -134,7 +134,7 @@
Specifies whether or not a component should be installed by default. The lack of an @Install
annotation indicates a component should be installed.
</para>
- <programlisting><![CDATA[@Install(dependencies="org.jboss.seam.core.jbpm")]]></programlisting>
+ <programlisting><![CDATA[@Install(dependencies="org.jboss.seam.bpm.jbpm")]]></programlisting>
<para>
Specifies that a component should only be stalled if the components listed as dependencies
are also installed.
@@ -523,7 +523,7 @@
<listitem>
<para>
<literal>pageflow</literal> — a process definition name of a jBPM process
- definition deployed via <literal>org.jboss.seam.core.jbpm.pageflowDefinitions.</literal>
+ definition deployed via <literal>org.jboss.seam.bpm.jbpm.pageflowDefinitions.</literal>
</para>
</listitem>
</itemizedlist>
@@ -659,7 +659,7 @@
<listitem>
<para>
<literal>definition</literal> — the name of the jBPM process definition
- deployed via <literal>org.jboss.seam.core.jbpm.processDefinitions</literal>. </para>
+ deployed via <literal>org.jboss.seam.bpm.jbpm.processDefinitions</literal>. </para>
</listitem>
</itemizedlist>
</listitem>
@@ -1083,9 +1083,9 @@
<programlisting><![CDATA[@Namespace(value="http://jboss.com/products/seam/core", prefix="org.jboss.seam.core")]]></programlisting>
<para>Specifies a namespace to associate with a given package. Additionally, it specifies a
component name prefix to be applied to component names specified in the XML file. For example,
- an XML element named <literal>microcontainer</literal> that is associated with this namespace
+ an XML element named <literal>init</literal> that is associated with this namespace
would be understood to actually refere to a component named
- <literal>org.jboss.seam.core.microcontainer</literal>. </para>
+ <literal>org.jboss.seam.core.init</literal>. </para>
</listitem>
</varlistentry>
1.63 +22 -79 jboss-seam/doc/reference/en/modules/components.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: components.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/components.xml,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -b -r1.62 -r1.63
--- components.xml 20 Jun 2007 06:05:06 -0000 1.62
+++ components.xml 26 Jun 2007 20:52:00 -0000 1.63
@@ -36,58 +36,11 @@
<variablelist spacing="compact">
<varlistentry>
- <term><literal>org.jboss.seam.core.eventContext</literal></term>
+ <term><literal>org.jboss.seam.core.contexts</literal></term>
<listitem>
<para>
- Manager component for the event context object
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><literal>org.jboss.seam.core.pageContext</literal></term>
- <listitem>
- <para>
- Manager component for the page context object
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><literal>org.jboss.seam.core.conversationContext</literal></term>
- <listitem>
- <para>
- Manager component for the conversation context object
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><literal>org.jboss.seam.core.sessionContext</literal></term>
- <listitem>
- <para>
- Manager component for the session context object
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><literal>org.jboss.seam.core.applicationContext</literal></term>
- <listitem>
- <para>
- Manager component for the application context object
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><literal>org.jboss.seam.core.methodContext</literal></term>
- <listitem>
- <para>
- Manager component for the method context object
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><literal>org.jboss.seam.core.businessProcessContext</literal></term>
- <listitem>
- <para>
- Manager component for the business process context object
+ Component that provides access to Seam Context objects, for
+ example <literal>org.jboss.seam.core.contexts.sessionContext['user']</literal>.
</para>
</listitem>
</varlistentry>
@@ -314,16 +267,6 @@
</itemizedlist>
</listitem>
</varlistentry>
- <varlistentry>
- <term><literal>org.jboss.seam.core.uiComponent</literal></term>
- <listitem>
- <para>
- Allows access to a JSF <literal>UIComponent</literal> by its id
- from the EL. For example, we can write
- <literal>@In("#{uiComponent['myForm:address'].value}")</literal>.
- </para>
- </listitem>
- </varlistentry>
</variablelist>
<para>
@@ -340,7 +283,7 @@
<variablelist spacing="compact">
<varlistentry>
- <term><literal>org.jboss.seam.core.locale</literal></term>
+ <term><literal>org.jboss.seam.international.locale</literal></term>
<listitem>
<para>
The Seam locale. The locale is session scoped.
@@ -348,7 +291,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>org.jboss.seam.core.timezone</literal></term>
+ <term><literal>org.jboss.seam.international.timezone</literal></term>
<listitem>
<para>
The Seam timezone. The timezone is session scoped.
@@ -374,7 +317,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>org.jboss.seam.core.localeSelector</literal></term>
+ <term><literal>org.jboss.seam.international.localeSelector</literal></term>
<listitem>
<para>
Supports selection of the locale either at configuration time,
@@ -433,7 +376,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>org.jboss.seam.core.timezoneSelector</literal></term>
+ <term><literal>org.jboss.seam.international.timezoneSelector</literal></term>
<listitem>
<para>
Supports selection of the timezone either at configuration time,
@@ -467,7 +410,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>org.jboss.seam.core.messages</literal></term>
+ <term><literal>org.jboss.seam.international.messages</literal></term>
<listitem>
<para>
A map containing internationalized messages rendered from message
@@ -670,7 +613,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>org.jboss.seam.core.switcher</literal></term>
+ <term><literal>org.jboss.seam.faces.switcher</literal></term>
<listitem>
<para>
The conversation switcher.
@@ -916,7 +859,7 @@
<para>
All of these components are installed whenever the component
- <literal>org.jboss.seam.core.jbpm</literal> is installed.
+ <literal>org.jboss.seam.bpm.jbpm</literal> is installed.
</para>
</section>
@@ -929,7 +872,7 @@
<variablelist spacing="compact">
<varlistentry>
- <term><literal>org.jboss.seam.core.userPrincipal</literal></term>
+ <term><literal>org.jboss.seam.web.userPrincipal</literal></term>
<listitem>
<para>
Manager component for the current user <literal>Principal</literal>.
@@ -937,7 +880,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>org.jboss.seam.core.isUserInRole</literal></term>
+ <term><literal>org.jboss.seam.web.isUserInRole</literal></term>
<listitem>
<para>
Allows JSF pages to choose to render a control, depending upon
@@ -1127,7 +1070,7 @@
<itemizedlist>
<listitem>
<para>
- <literal>org.jboss.seam.core.pages.noConversationViewId</literal>
+ <literal>org.jboss.seam.navigation.pages.noConversationViewId</literal>
— global setting for the view id to redirect to when a
conversation entry is not found on the server side.
</para>
@@ -1140,19 +1083,19 @@
<listitem>
<para>
Bootstraps a <literal>JbpmConfiguration</literal>. Install as class
- <literal>org.jboss.seam.core.Jbpm</literal>.
+ <literal>org.jboss.seam.bpm.Jbpm</literal>.
</para>
<itemizedlist>
<listitem>
<para>
- <literal>org.jboss.seam.core.jbpm.processDefinitions</literal> —
+ <literal>org.jboss.seam.bpm.jbpm.processDefinitions</literal> —
a list of resource names of jPDL files to be used for orchestration
of business processes.
</para>
</listitem>
<listitem>
<para>
- <literal>org.jboss.seam.core.jbpm.pageflowDefinitions</literal> —
+ <literal>org.jboss.seam.bpm.jbpm.pageflowDefinitions</literal> —
a list of resource names of jPDL files to be used for orchestration
of conversation page flows.
</para>
@@ -1235,7 +1178,7 @@
<term><literal>org.jboss.seam.core.validators</literal></term>
<listitem>
<para>
- Caches instances of Hibernate Validator ClassValidator.
+ Caches instances of Hibernate Validator <literal>ClassValidator</literal>.
</para>
</listitem>
</varlistentry>
@@ -1265,7 +1208,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>org.jboss.seam.exceptions.exceptions</literal></term>
+ <term><literal>org.jboss.seam.exception.exceptions</literal></term>
<listitem>
<para>
Internal component for exception handling.
@@ -1273,12 +1216,12 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>org.jboss.seam.core.transactionListener</literal></term>
+ <term><literal>org.jboss.seam.transaction.transaction</literal></term>
<listitem>
<para>
- Temporary solution for getting JTA transaction lifecycle
- callbacks. Once all appservers support the new EE5 APIs,
- this will be removed.
+ API for controlling transactions and abstracting the underlying
+ transaction management implementation behind a JTA-compatible
+ interface.
</para>
</listitem>
</varlistentry>
1.62 +0 -20 jboss-seam/doc/reference/en/modules/concepts.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: concepts.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/concepts.xml,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -b -r1.61 -r1.62
--- concepts.xml 26 Jun 2007 20:33:41 -0000 1.61
+++ concepts.xml 26 Jun 2007 20:52:00 -0000 1.62
@@ -584,26 +584,6 @@
convenient static <literal>instance()</literal> methods:
</para>
<programlisting><![CDATA[FacesMessages.instance().add("Welcome back, #{user.name}!");]]></programlisting>
- <para>
- Seam was designed to integrate tightly in a Java EE 5 environment. However, we understand that there
- are many projects which are not running in a full EE environment. We also realize the critical
- importance of easy unit and integration testing using frameworks such as TestNG and JUnit. So, we've
- made it easy to run Seam in Java SE environments by allowing you to boostrap certain critical
- infrastructure normally only found in EE environments by installing built-in Seam components.
- </para>
- <para>
- For example, you can run your EJB3 components in Tomcat or an integration test suite just by
- installing the built-in component <literal>org.jboss.seam.core.ejb</literal>, which automatically
- bootstraps the JBoss Embeddable EJB3 container and deploys your EJB components.
- </para>
- <para>
- Or, if you're not quite ready for the Brave New World of EJB 3.0, you can write a Seam application
- that uses only JavaBean components, together with Hibernate3 for persistence, by installing a built-in
- component that manages a Hibernate <literal>SessionFactory</literal>. When using Hibernate outside of a J2EE
- environment, you will also probably need a JTA transaction manager and JNDI server, which are available
- via the built-in component <literal>org.jboss.seam.core.microcontainer</literal>. This lets you use the
- bulletproof JTA/JCA pooling datasource from JBoss application server in an SE environment like Tomcat!
- </para>
</sect2>
</sect1>
1.18 +5 -5 jboss-seam/doc/reference/en/modules/i18n.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: i18n.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/i18n.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
--- i18n.xml 26 Jun 2007 02:23:11 -0000 1.17
+++ i18n.xml 26 Jun 2007 20:52:00 -0000 1.18
@@ -38,9 +38,9 @@
<para>
It is <emphasis>possible</emphasis> to set the locale
manually via the Seam configuration properties
- <literal>org.jboss.seam.core.localeSelector.language</literal>,
- <literal>org.jboss.seam.core.localeSelector.country</literal> and
- <literal>org.jboss.seam.core.localeSelector.variant</literal>, but
+ <literal>org.jboss.seam.international.localeSelector.language</literal>,
+ <literal>org.jboss.seam.international.localeSelector.country</literal> and
+ <literal>org.jboss.seam.international.localeSelector.variant</literal>, but
we can't think of any good reason to ever do this.
</para>
@@ -216,8 +216,8 @@
<title>Timezones</title>
<para>
There is also a session-scoped instance of <literal>java.util.Timezone</literal>,
- named <literal>org.jboss.seam.core.timezone</literal>, and a Seam component for changing
- the timezone named <literal>org.jboss.seam.core.timezoneSelector</literal>. By default,
+ named <literal>org.jboss.seam.international.timezone</literal>, and a Seam component for changing
+ the timezone named <literal>org.jboss.seam.international.timezoneSelector</literal>. By default,
the timezone is the default timezone of the server. Unfortunately, the JSF specification
says that all dates and times should be assumed to be UTC, and displayed as UTC, unless
a timezone is explicitly specified using <literal><f:convertDateTime></literal>.
1.13 +4 -4 jboss-seam/doc/reference/en/modules/xml.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: xml.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/xml.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- xml.xml 21 Jun 2007 22:16:37 -0000 1.12
+++ xml.xml 26 Jun 2007 20:52:00 -0000 1.13
@@ -92,7 +92,7 @@
</para>
<para>
- For example, the following <literal>components.xml</literal> file installs the jBPM:
+ For example, the following <literal>components.xml</literal> file installs jBPM:
</para>
<programlisting><![CDATA[<components xmlns="http://jboss.com/products/seam/components"
@@ -106,7 +106,7 @@
</para>
<programlisting><![CDATA[<components>
- <component class="org.jboss.seam.core.Ejb"/>
+ <component class="org.jboss.seam.bpm.Jbpm"/>
</components>]]></programlisting>
<para>
@@ -302,7 +302,7 @@
Arrays, sets and lists of strings or primitives are also supported:
</para>
- <programlisting><![CDATA[org.jboss.seam.core.jbpm.processDefinitions order.jpdl.xml, return.jpdl.xml, inventory.jpdl.xml]]></programlisting>
+ <programlisting><![CDATA[org.jboss.seam.bpm.jbpm.processDefinitions order.jpdl.xml, return.jpdl.xml, inventory.jpdl.xml]]></programlisting>
<programlisting><![CDATA[<core:jbpm>
<core:process-definitions>
@@ -312,7 +312,7 @@
</core:process-definitions>
</core:jbpm>]]></programlisting>
- <programlisting><![CDATA[<component name="org.jboss.seam.core.jbpm">
+ <programlisting><![CDATA[<component name="org.jboss.seam.bpm.jbpm">
<property name="processDefinitions">
<value>order.jpdl.xml</value>
<value>return.jpdl.xml</value>
More information about the jboss-cvs-commits
mailing list