9:37 p.m.
Author: jaredmorgs
Date: 2013-01-24 22:37:08 -0500 (Thu, 24 Jan 2013)
New Revision: 9078
Modified:
epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml
epp/docs/branches/6.0/Reference_Guide/en-US/modules/Advanced/Foundations/Config_Retrieval.xml
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PasswordEncryption.xml
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/RTLFramework.xml
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml
epp/docs/branches/6.0/Reference_Guide/en-US/modules/WSRP.xml
epp/docs/branches/6.0/Reference_Guide/en-US/modules/eXoJCR/jcr-with-gtn/managed-datasources-under-jboss-as.xml
epp/docs/branches/6.0/Reference_Guide/en-US/modules/eXoJCR/jcr/cluster-config.xml
epp/docs/branches/6.0/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml
Log:
Sanitized all old file paths, and set NEEDINFO on areas that I need more advice on.
Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2013-01-25 02:15:12
UTC (rev 9077)
+++ epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2013-01-25 03:37:08
UTC (rev 9078)
@@ -8,6 +8,20 @@
<simpara>
<revhistory>
<revision>
+ <revnumber>6.0.0-36</revnumber>
+ <date>Fri Jan 25 2013</date>
+ <author>
+ <firstname>Jared</firstname>
+ <surname>Morgan</surname>
+ <email/>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Sanitized all old file paths. NEEDINFO - FILE PATH used in
remarks to flag areas where I need assistance with info.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
<revnumber>6.0.0-35</revnumber>
<date>Fri Jan 25 2013</date>
<author>
Modified:
epp/docs/branches/6.0/Reference_Guide/en-US/modules/Advanced/Foundations/Config_Retrieval.xml
===================================================================
---
epp/docs/branches/6.0/Reference_Guide/en-US/modules/Advanced/Foundations/Config_Retrieval.xml 2013-01-25
02:15:12 UTC (rev 9077)
+++
epp/docs/branches/6.0/Reference_Guide/en-US/modules/Advanced/Foundations/Config_Retrieval.xml 2013-01-25
03:37:08 UTC (rev 9078)
@@ -11,20 +11,21 @@
<para>
The container is initialized by looking into different locations. This container is
used by portal applications. Configurations are overloaded in the following lookup
sequence:
</para>
+ <remark>NEEDINFO - FILE PATHS - the file before was configuration.xml, but
I'm pretty sure all this is defined in standalone.xml now,
correct?</remark>
<procedure>
<step>
<para>
- Services default <envar>RootContainer</envar> configurations from JAR
files
<filename><replaceable>JPP_DIST/jboss-as/</replaceable>/conf/gatein/configuration.xml</filename>.
+ Services default <envar>RootContainer</envar> configurations from JAR
files
<filename><replaceable>JPP_HOME/</replaceable>/standalone/configuration/standalone.xml</filename>.
</para>
</step>
<step>
<para>
- External <envar>RootContainer</envar> configuration can be found at
<filename><replaceable>JPP_DIST/jboss-as/</replaceable>/conf/gatein/configuration.xml</filename>.
+ External <envar>RootContainer</envar> configuration can be found at
<filename><replaceable>JPP_HOME/</replaceable>/standalone/configuration/standalone.xml</filename>.
</para>
</step>
<step>
<para>
- Services default <envar>PortalContainer</envar> configurations from JAR
files
<filename><replaceable>JPP_DIST</replaceable>/jboss-as/conf/portal/configuration.xml</filename>.
+ Services default <envar>PortalContainer</envar> configurations from JAR
files
<filename><replaceable>JPP_HOME/</replaceable>/standalone/configuration/standalone.xml</filename>.
</para>
</step>
<step>
@@ -34,7 +35,7 @@
</step>
<step>
<para>
- External configuration for services of named portal can be found at
<filename><replaceable>JPP_DIST</replaceable>/jboss-as/conf/gatein/configuration.xml</filename>.
+ External configuration for services of named portal can be found at
<filename><replaceable>JPP_HOME</replaceable>/standalone/configuration/standalone.xml</filename>.
</para>
</step>
</procedure>
@@ -43,6 +44,7 @@
The search looks for a configuration file in each JAR/WAR available from the classpath
using the current thread context classloader. During the search these configurations are
added to a set. If the service was configured previously and the current JAR contains a
new configuration of that service the latest (from the current JAR/WAR) will replace the
previous one. The last one will be applied to the service during the services start
phase.
</para>
</note>
+ <remark>NEEDINFO - FILE PATHS - the file before was configuration.xml, but
I'm pretty sure all this is defined in standalone.xml now,
correct?</remark>
<warning>
<para>
Take care to have no dependencies between configurations from JAR files
(<filename>/conf/portal/configuration.xml</filename> and
<filename>/conf/configuration.xml</filename>) since we have no way to know in
advance the loading order of those configurations. In other words, if you want to overload
some configuration located in the file
<filename>/conf/portal/configuration.xml</filename> of a given JAR file, you
must not do it from the file
<filename>/conf/portal/configuration.xml</filename> of another JAR file but
from another configuration file loaded after configurations from JAR files
<filename>/conf/portal/configuration.xml.</filename>
Modified:
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml
===================================================================
---
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml 2013-01-25
02:15:12 UTC (rev 9077)
+++
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml 2013-01-25
03:37:08 UTC (rev 9078)
@@ -52,8 +52,9 @@
<para>
Authentication workflow consists of HTTP requests and redirects which include
handshakes. Currently only Servlet 3.0 containers are supported, so authentication is
triggered programmatically from Servlet API.
</para>
+ <remark>NEEDINFO - FILE PATHS - in this file, the /dologin blocks seem to be in
<servlet-mapping> directives. Is it OK for me to update to this format in
this respect?</remark>
<para>
- First you can see in
<filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/portal.war/WEB-INF/web.xml</filename>
that authentication is triggered by accessing a secured URL
<systemitem>_/dologin_</systemitem>:
+ First you can see in
<filename><replaceable>JPP_DIST</replaceable>/gatein/gatein.ear/portal.war/WEB-INF/web.xml</filename>
that authentication is triggered by accessing a secured URL
<systemitem>_/dologin_</systemitem>:
</para>
<programlisting language="XML" role="XML">
<![CDATA[
@@ -96,7 +97,7 @@
]]>
</programlisting>
<para>
- <literal>LoginServlet</literal> redirects the user to the login
page placed in
<filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/portal.war/login/jsp/login.jsp</filename>.
+ <literal>LoginServlet</literal> redirects the user to the login
page placed in
<filename><replaceable>JPP_DIST</replaceable>/gatein/gatein.ear/portal.war/login/jsp/login.jsp</filename>.
<mediaobject>
<imageobject role="html">
<imagedata align="center"
fileref="images/AuthenticationAndIdentity/Overview/loginScreen.png"
format="PNG"/>
@@ -107,7 +108,7 @@
</mediaobject>
</para>
<para>
- Changes to the appearance of this login page can be made in this JSP file.
Alternatively you can create an extension and override this page via extension if you
don't want to edit it directly. You can also change images or CSS placed in
<filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/login/skin</filename>
.
+ Changes to the appearance of this login page can be made in this JSP file.
Alternatively you can create an extension and override this page via extension if you
don't want to edit it directly. You can also change images or CSS placed in
<filename><replaceable>JPP_DIST</replaceable>/gatein/gatein.ear/login/skin</filename>
.
</para>
<para>
After a user submits the login form, they are redirected to the login URL:
<ulink
url="http://localhost:8080/portal/login?username=root&password=gtn&initialURI=/portal/classic"
type="http">http://localhost:8080/portal/login?username=root&password=gtn&initialURI=/portal/private/classic</ulink>.
@@ -119,7 +120,7 @@
<section id="sect-Authentication_Authorization_Intro-Login_Modules">
<title>Login modules</title>
<para>
-From the WCI servlet API login, the user is redirected to JAAS authentication. JBoss
Portal Platform uses its own security domain (<emphasis
role="bold">gatein-domain</emphasis>) with a set of predefined login
modules. Login module configuration for <emphasis>gatein-domain</emphasis> is
contained in the
<filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/META-INF/gatein-jboss-beans.xml</filename>
file.
+From the WCI servlet API login, the user is redirected to JAAS authentication. JBoss
Portal Platform uses its own security domain (<emphasis
role="bold">gatein-domain</emphasis>) with a set of predefined login
modules. Login module configuration for <emphasis>gatein-domain</emphasis> is
contained in the
<filename><replaceable>JPP_DIST</replaceable>/gatein/gatein.ear/META-INF/gatein-jboss-beans.xml</filename>
file.
</para>
<para>
Below is the default login modules stack:
Modified:
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PasswordEncryption.xml
===================================================================
---
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PasswordEncryption.xml 2013-01-25
02:15:12 UTC (rev 9077)
+++
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PasswordEncryption.xml 2013-01-25
03:37:08 UTC (rev 9078)
@@ -167,12 +167,12 @@
</step>
<step>
<para>
- Deploy the <filename>codec-example.jar</filename>
into your
<filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/lib/</filename>
directory.
+ Deploy the <filename>codec-example.jar</filename>
into the
<filename><replaceable>JPP_DIST</replaceable>/gatein/gatein.ear/lib/</filename>
directory.
</para>
</step>
<step>
<para>
- Start (or restart) your JBoss Portal Platform.
+ Start (or restart) JBoss Portal Platform.
</para>
<para>
Any passwords written to the JCR will now be encoded and not
plain text.
Modified:
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/RTLFramework.xml
===================================================================
---
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/RTLFramework.xml 2013-01-25
02:15:12 UTC (rev 9077)
+++
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/RTLFramework.xml 2013-01-25
03:37:08 UTC (rev 9078)
@@ -67,7 +67,7 @@
It works by appending -lt or -rt to the stylesheet name.
</para>
<para>
- For instance:
<filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/web.war/skin/portal/webui/component/UIFooterPortlet/DefaultStylesheet-rt.css</filename>
will return the same stylesheet as
<filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/web.war/skin/portal/webui/component/UIFooterPortlet/DefaultStylesheet.css</filename>
but processed for the RT orientation. The <parameter>-lt</parameter> suffix is
optional.
+ For instance:
<filename><replaceable>JPP_HOME</replaceable>/gatein/gatein.ear/portal.war/templates/skin/portal/webui/component/UIFooterPortlet/DefaultStylesheet-rt.css</filename>
will return the same stylesheet as
<filename><replaceable>JPP_HOME</replaceable>/gatein/gatein.ear/portal.war/templates/skin/portal/webui/component/UIFooterPortlet/DefaultStylesheet.css</filename>
but processed for the RT orientation. The <parameter>-lt</parameter> suffix is
optional.
</para>
<para>
Stylesheet authors can annotate their stylesheet to create content that depends on the
orientation.
@@ -112,7 +112,7 @@
The web resource filter uses the same naming pattern as the skin service. When an
image ends with the -rt suffix the portal will attempt to locate the original image and
create a mirror of it.
</para>
<para>
- For instance: requesting the image
<filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/01eXoResources.war/skin/DefaultSkin/webui/component/UITabSystem/UITabs/background/NormalTabStyle-rt.gif</filename>
returns a mirror of the image
<filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/01eXoResources.war/skin/DefaultSkin/webui/component/UITabSystem/UITabs/background/NormalTabStyle.gif</filename>.
+ For instance: requesting the image
<filename><replaceable>JPP_HOME</replaceable>/gatein/gatein.ear/eXoResources.war/skin/DefaultSkin/webui/component/UITabSystem/UITabs/background/NormalTabStyle-rt.gif</filename>
returns a mirror of the image
<filename><replaceable>JPP_HOME</replaceable>/gatein/gatein.ear/eXoResources.war/skin/DefaultSkin/webui/component/UITabSystem/UITabs/background/NormalTabStyle.gif</filename>.
</para>
<note>
<para>
Modified:
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml
===================================================================
---
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2013-01-25
02:15:12 UTC (rev 9077)
+++
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2013-01-25
03:37:08 UTC (rev 9078)
@@ -534,7 +534,7 @@
<para>
For example, the property can be passed as a JVM parameter with
<literal>-D</literal> option when running JBoss Portal Platform.
</para>
- <programlisting><command>sh jboss-as/bin/run.sh
-Dexo.product.developing=true</command></programlisting>
+ <programlisting><command>./bin/standalone.sh
-Dexo.product.developing=true</command></programlisting>
<!-- <programlisting language="Java"
role="Java"><xi:include parse="text"
href="../../extras/PortalDevelopment_Skinning/default192.java"
xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
--> <warning>
<para>
This option may cause display bugs in some browsers.
Modified:
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml
===================================================================
---
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml 2013-01-25
02:15:12 UTC (rev 9077)
+++
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml 2013-01-25
03:37:08 UTC (rev 9078)
@@ -142,12 +142,12 @@
</step>
<step>
<para>
- Copy the package file into
<literal><replaceable>JPP_DIST</replaceable>/jboss-as/server/default/deploy</literal>.
+ Copy the package file into
<literal><replaceable>JPP_HOME</replaceable>/standalone/deployments</literal>.
</para>
</step>
<step>
<para>
- Start JBoss Application Server (if it is not already
running).
+ Start the portal (if it is not already running).
</para>
</step>
<step>
@@ -159,14 +159,6 @@
<para>
Create a new portal page and add the portlet to it.
</para>
- <mediaobject>
- <imageobject role="html">
- <imagedata width="444" align="center"
scale="100"
fileref="images/PortletDevelopment/Standard/first_portlet/deployed.png"
format="PNG"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata width="444" contentwidth="120mm"
align="center"
fileref="images/PortletDevelopment/Standard/first_portlet/deployed.png"
format="PNG"/>
- </imageobject>
- </mediaobject>
</step>
</procedure>
</section>
Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/WSRP.xml
===================================================================
--- epp/docs/branches/6.0/Reference_Guide/en-US/modules/WSRP.xml 2013-01-25 02:15:12 UTC
(rev 9077)
+++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/WSRP.xml 2013-01-25 03:37:08 UTC
(rev 9078)
@@ -75,13 +75,15 @@
JBoss Portal Platform provides complete support for WSRP 1.0 and 2.0 standard interfaces,
and offers both consumer and
producer services. Starting with version 2.1.0-GA of the component, WSRP is
packaged as a JBoss Portal Platform
extension, and is self-contained in a package named
-
<filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein-wsrp-integration.ear</filename>
+
<filename><replaceable>JPP_DIST</replaceable>/gatein/extensions/gatein-wsrp-integration.ear</filename>
.
</para>
+ <remark>NEEDINFO - FILE PATHS - there don't seem to be any config
files that I can see in the directory below.</remark>
<para>The only files of interest from a user perspective
are located in the
-
<filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/conf/gatein/</filename>
+
<filename><replaceable>JPP_DIST</replaceable>/standalone/configuration/gatein/wsrp</filename>
directory.</para>
+ <remark>NEEDINFO - FILE PATHS - the wsse files are not present in the directory
structure. Where do these live now?</remark>
<itemizedlist>
<listitem>
<para><filename>gatein-wsse-consumer.xml</filename>,
which allows you to configure WS-Security support for the consumer.</para>
@@ -1038,13 +1040,14 @@
<para>While it is recommended you use the WSRP Configuration portlet to
configure Consumers, the component provides an
alternative way to configure consumers by adding an XML file called
<filename>wsrp-consumers-config.xml</filename> in the
-
<filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/conf/gatein/</filename>
directory.
+
<filename><replaceable>JPP_DIST</replaceable>/standalone/configuration/gatein/wsrp/</filename>
directory.
</para>
<note>
<title>Note</title>
+ <remark>NEEDINFO - FILE PATH - while this path is valid, there is no XSD
here any more. Should I just remove the note? Where is the XSD contained
now?</remark>
<para>An XML Schema defining which elements are available to configure
Consumers via XML can be found
in
-
<filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein-wsrp-integration.ear/lib/wsrp-integration-api-&WSRP_VERSION;.jar/xsd/gatein_wsrp_consumer_1_0.xsd
</filename>
+
<filename><replaceable>JPP_DIST</replaceable>/gatein/extensions/gatein-wsrp-integration.ear/lib/jboss7integration.jar/
</filename>
</para>
</note>
<important>
@@ -1152,13 +1155,14 @@
</section>
<section>
<title>Examples</title>
+ <remark>NEEDINFO - FILE PATHS - this file was not present at the location
specified. Where is this file now?</remark>
<para>
Here is the configuration of the
<literal>selfv1</literal>
and
<literal>selfv2</literal>
consumers as found in
-
<filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein-wsrp-integration.ear/lib/extension-component-&WSRP_VERSION;.jar/conf/wsrp-consumers-config.xml</filename>
+
<filename><replaceable>JPP_HOME</replaceable>/gatein/extensions/gatein-wsrp-integration.ear/lib/extension-component-&WSRP_VERSION;.jar/conf/wsrp-consumers-config.xml</filename>
with a cache expiring every 500 seconds and with a 50 second timeout for
web service operations.
<note>
<para>
@@ -2151,8 +2155,8 @@
</section>
</section>
<section>
-<title>Example implementation</title>
- <para>
+ <title>Example implementation</title>
+ <para>
We also provide a complete, end-to-end example to get you started, which you can
find at
<ulink
url="https://github.com/gatein/gatein-wsrp/tree/master/examples/invo...
. This example shows how
@@ -2165,15 +2169,15 @@
<code>InvocationHandlerDelegate</code>
, to establish a round-trip communication channel outside of the standard WSRP
protocol, implementing the following scenario:
</para>
- <itemizedlist>
- <listitem>
- <para>
+ <itemizedlist>
+ <listitem>
+ <para>
<code>ExampleConsumerInvocationHandlerDelegate</code>
attaches to the consumer to add the current session id as an extension to
render requests sent to the producer.
</para>
- </listitem>
- <listitem>
- <para>
+ </listitem>
+ <listitem>
+ <para>
<code>ExampleProducerInvocationHandlerDelegate</code>
provides the counterpart of
<code>ExampleConsumerInvocationHandlerDelegate</code>
@@ -2181,12 +2185,11 @@
<code>ExampleConsumerInvocationHandlerDelegate</code>
sends and adds an extension of its own to the render response so that the
consumer-side delegate can know that the information it passed was properly processed.
</para>
- </listitem>
- </itemizedlist>
- <sidebar>
- <para>To activate the InvocationHandlerDelegates on both the consumer and
producer, start your GateIn Portal instance as follows:</para>
- </sidebar>
-</section>
-
+ </listitem>
+ </itemizedlist>
+ <sidebar>
+ <para>To activate the InvocationHandlerDelegates on both the consumer and
producer, start your GateIn Portal instance as follows:</para>
+ </sidebar>
+ </section>
</section>
</chapter>
Modified:
epp/docs/branches/6.0/Reference_Guide/en-US/modules/eXoJCR/jcr/cluster-config.xml
===================================================================
---
epp/docs/branches/6.0/Reference_Guide/en-US/modules/eXoJCR/jcr/cluster-config.xml 2013-01-25
02:15:12 UTC (rev 9077)
+++
epp/docs/branches/6.0/Reference_Guide/en-US/modules/eXoJCR/jcr/cluster-config.xml 2013-01-25
03:37:08 UTC (rev 9078)
@@ -12,6 +12,7 @@
<para>
To deploy eXo JCR to the JBoss AS, do the following:
</para>
+ <remark>NEEDINFO - FILE PATHS - do we need to do this for JPP 6. JCR is
embedded isn't it?</remark>
<procedure>
<title/>
<step>
@@ -21,7 +22,7 @@
</step>
<step>
<para>
- Copy the file into
<filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/deploy</filename>
directory.
+ Copy the file into
<filename><replaceable>JPP_HOME</replaceable>/standalone/deployments</filename>
directory.
</para>
</step>
<step>
Modified:
epp/docs/branches/6.0/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml
===================================================================
---
epp/docs/branches/6.0/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml 2013-01-25
02:15:12 UTC (rev 9077)
+++
epp/docs/branches/6.0/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml 2013-01-25
03:37:08 UTC (rev 9078)
@@ -113,7 +113,7 @@
Each database software supports ANSI SQL standards but also has its own
specifics. Therefore each database has its own configuration setting in the eXo JCR as a
database dialect parameter. More detailed configuration of the database can be set by
editing the metadata SQL-script files.
</para>
<para>
- You can find SQL-scripts in <filename>conf/storage/</filename>
directory of the
<filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/lib/exo.jcr.component.core-XXX.XXX.jar</filename>
file .
+ You can find SQL-scripts in <filename>conf/storage/</filename>
directory of the
<filename><replaceable>JPP_HOME</replaceable>/modules/org/gatein/lib/main/exo.jcr.component.core-<remark>VERSION</remark>.jar</filename>
file .
</para>
<para>
The following tables show the correspondence between the scripts and
databases:
Modified:
epp/docs/branches/6.0/Reference_Guide/en-US/modules/eXoJCR/jcr-with-gtn/managed-datasources-under-jboss-as.xml
===================================================================
---
epp/docs/branches/6.0/Reference_Guide/en-US/modules/eXoJCR/jcr-with-gtn/managed-datasources-under-jboss-as.xml 2013-01-25
02:15:12 UTC (rev 9077)
+++
epp/docs/branches/6.0/Reference_Guide/en-US/modules/eXoJCR/jcr-with-gtn/managed-datasources-under-jboss-as.xml 2013-01-25
03:37:08 UTC (rev 9078)
@@ -9,6 +9,7 @@
<title>Configurations Steps</title>
<section
id="sect-Reference_Guide-Configurations_Steps-Declaring_the_datasources_in_the_AS">
<title>Declaring the datasources in the AS</title>
+ <remark>NEEDINFO - FILE PATHS - I know this isn't right. Where do
these get deployed again?</remark>
<para>
To declare the datasources using a JBoss application server, deploy a
<literal>ds</literal> file
(<filename><replaceable>XXX</replaceable>-ds.xml</filename>) into
the <emphasis>deploy</emphasis> directory of the appropriate server profile
(<filename>/server/<replaceable>PROFILE</replaceable>/deploy</filename>,
for example).
</para>
@@ -59,7 +60,9 @@
<section
id="sect-Reference_Guide-Configurations_Steps-Do_not_bind_datasources_explicitly">
<title>Do not bind datasources explicitly</title>
<para>
- Do not let the portal explicitly bind datasources. Edit the
<filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/conf/gatein/configuration.properties</filename>
and comment out the following rows in the JCR section:
+ Do not let the portal explicitly bind datasources. </para>
+ <remark>NEEDINFO - FILE PATHS - I think some of the values have changed here
when I look at the new file below. New info required?</remark>
+ <para>Edit the
<filename><replaceable>JPP_HOME</replaceable>/standalone/configuration/gatein/configuration.properties</filename>
and comment out the following rows in the JCR section:
</para>
<programlisting>#gatein.jcr.datasource.driver=org.hsqldb.jdbcDriver
#gatein.jcr.datasource.url=jdbc:hsqldb:file:${gatein.db.data.dir}/data/jdbcjcr_${name}
@@ -73,7 +76,7 @@
#gatein.idm.datasource.username=sa
#gatein.idm.datasource.password=</programlisting>
<para>
- Open the <filename>jcr-configuration.xml</filename> and
<filename>idm-configuration.xml</filename> files ans comment out references to
the plug-in <literal>InitialContextInitializer</literal>.
+ Open the <filename>jcr-configuration.xml</filename> and
<filename>idm-configuration.xml</filename> files and comment out references to
the plug-in <literal>InitialContextInitializer</literal>.
</para>
<programlisting language="XML" role="XML"><!--
Commented because, Datasources are declared and bound by AS, not in eXo -->
<!--