October 2011 - gatein-commits - Jboss List Archives

gatein SVN: r7693 - in epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US: modules/Advanced and 5 other directories.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-10-09 21:25:25 -0400 (Sun, 09 Oct 2011) New Revision: 7693 Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/extras/Authentication_Identity_SSO/default102.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/extras/Authentication_Identity_SSO/default109.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/extras/Authentication_Identity_SSO/default115.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/extras/Authentication_Identity_SSO/default122.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Advanced_Concepts.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Config_Retrieval.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Configuring_Containers.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Configuring_Services.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Extensions_And_Multiple_Portals.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Kernel.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Profiles.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Requests.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/System_Properties.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/data-container.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/protocols/ftp.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/protocols/webdav.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/kernel.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/AuthenticationAndIdentity/SSO.xml Log: Edits to new JCR1.14 content and updated images Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/extras/Authentication_Identity_SSO/default102.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/extras/Authentication_Identity_SSO/default102.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/extras/Authentication_Identity_SSO/default102.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -22,4 +22,4 @@ <bean class="org.jasig.cas.authentication.handler.support.SimpleTestUsernamePasswordAuthenticationHandler" /> </list> - </property> + </property> \ No newline at end of file Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/extras/Authentication_Identity_SSO/default109.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/extras/Authentication_Identity_SSO/default109.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/extras/Authentication_Identity_SSO/default109.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -1,30 +1,58 @@ <filter> - <filter-name>LoginRedirectFilter</filter-name> - <filter-class>org.gatein.sso.agent.filter.LoginRedirectFilter</filter-class> - <init-param> -  - <param-name>LOGIN_URL</param-name> -  - <param-value>http://localhost:8888/cas/login?service=http://localhost:8080/portal/priv...</param-value> -  -  - </init-param> - </filter> - <filter> - <filter-name>CASLogoutFilter</filter-name> - <filter-class>org.gatein.sso.agent.filter.CASLogoutFilter</filter-class> - <init-param> -  - <param-name>LOGOUT_URL</param-name> - <param-value>http://localhost:8888/cas/logout</param-value> - </init-param> - </filter> -  - <filter-mapping> - <filter-name>LoginRedirectFilter</filter-name> - <url-pattern>/*</url-pattern> - </filter-mapping> - <filter-mapping> - <filter-name>CASLogoutFilter</filter-name> - <url-pattern>/*</url-pattern> - </filter-mapping> \ No newline at end of file + <filter-name>LoginRedirectFilter</filter-name> + <filter-class>org.gatein.sso.agent.filter.LoginRedirectFilter</filter-class> + <init-param> +  + <param-name>LOGIN_URL</param-name> +  + <param-value>http://localhost:8888/cas/login?service= + http://localhost:8080/portal/initiatessologin</param-value> +  +  + </init-param> + </filter> + <filter> + <filter-name>CASLogoutFilter</filter-name> + <filter-class>org.gatein.sso.agent.filter.CASLogoutFilter</filter-class> + <init-param> +  + <param-name>LOGOUT_URL</param-name> + <param-value>http://localhost:8888/cas/logout</param-value> + </init-param> + </filter> + <filter> + <filter-name>InitiateLoginFilter</filter-name> + <filter-class>org.gatein.sso.agent.filter.InitiateLoginFilter</filter-class> + <init-param> + <param-name>ssoServerUrl</param-name> + <param-value>http://localhost:8888/cas</param-value> + </init-param> + <init-param> + <param-name>casRenewTicket</param-name> + <param-value>false</param-value> + </init-param> + <init-param> + <param-name>casServiceUrl</param-name> + <param-value>http://localhost:8080/portal/initiatessologin</param-value> + </init-param> + <init-param> + <param-name>loginUrl</param-name> + <param-value>http://localhost:8080/portal/dologin</param-value> + </init-param> + </filter> + +  + <filter-mapping> + <filter-name>LoginRedirectFilter</filter-name> + <url-pattern>/*</url-pattern> + </filter-mapping> + <filter-mapping> + <filter-name>CASLogoutFilter</filter-name> + <url-pattern>/*</url-pattern> + </filter-mapping> + <filter-mapping> + <filter-name>InitiateLoginFilter</filter-name> + <url-pattern>/initiatessologin</url-pattern> + </filter-mapping> \ No newline at end of file Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/extras/Authentication_Identity_SSO/default115.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/extras/Authentication_Identity_SSO/default115.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/extras/Authentication_Identity_SSO/default115.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -1,27 +1,44 @@ <filter> - <filter-name>LoginRedirectFilter</filter-name> - <filter-class>org.gatein.sso.agent.filter.LoginRedirectFilter</filter-class> - <init-param> -  - <param-name>LOGIN_URL</param-name> - <param-value>http://localhost:8888/josso/signon/login.do?josso_back_to=http://localhos...</param-value> - </init-param> + <filter-name>LoginRedirectFilter</filter-name> + <filter-class>org.gatein.sso.agent.filter.LoginRedirectFilter</filter-class> + <init-param> +  + <param-name>LOGIN_URL</param-name> + <param-value>http://localhost:8888/josso/signon/login.do? + josso_back_to=http://localhost:8080/portal/initiatessologin</param-value> + </init-param> </filter> <filter> - <filter-name>JOSSOLogoutFilter</filter-name> - <filter-class>org.gatein.sso.agent.filter.JOSSOLogoutFilter</filter-class> - <init-param> -  - <param-name>LOGOUT_URL</param-name> - <param-value>http://localhost:8888/josso/signon/logout.do</param-value> - </init-param> + <filter-name>JOSSOLogoutFilter</filter-name> + <filter-class>org.gatein.sso.agent.filter.JOSSOLogoutFilter</filter-class> + <init-param> +  + <param-name>LOGOUT_URL</param-name> + <param-value>http://localhost:8888/josso/signon/logout.do</param-value> + </init-param> </filter> + <filter> + <filter-name>InitiateLoginFilter</filter-name> + <filter-class>org.gatein.sso.agent.filter.InitiateLoginFilter</filter-class> + <init-param> + <param-name>ssoServerUrl</param-name> + <param-value>http://localhost:8888/josso/signon/login.do</param-value> + </init-param> + <init-param> + <param-name>loginUrl</param-name> + <param-value>http://localhost:8080/portal/dologin</param-value> + </init-param> + </filter>  <filter-mapping> - <filter-name>LoginRedirectFilter</filter-name> - <url-pattern>/*</url-pattern> + <filter-name>LoginRedirectFilter</filter-name> + <url-pattern>/*</url-pattern> </filter-mapping> <filter-mapping> - <filter-name>JOSSOLogoutFilter</filter-name> - <url-pattern>/*</url-pattern> + <filter-name>JOSSOLogoutFilter</filter-name> + <url-pattern>/*</url-pattern> + </filter-mapping> + <filter-mapping> + <filter-name>InitiateLoginFilter</filter-name> + <url-pattern>/initiatessologin</url-pattern> </filter-mapping> \ No newline at end of file Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/extras/Authentication_Identity_SSO/default122.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/extras/Authentication_Identity_SSO/default122.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/extras/Authentication_Identity_SSO/default122.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -1,27 +1,49 @@ <filter> <filter-name>LoginRedirectFilter</filter-name> <filter-class>org.gatein.sso.agent.filter.LoginRedirectFilter</filter-class> - <init-param> -  - <param-name>LOGIN_URL</param-name> - <param-value>http://localhost:8888/opensso/UI/Login?realm=gatein&amp;goto=http://l...</param-value> - </init-param> + <init-param> +  + <param-name>LOGIN_URL</param-name> + <param-value>http://localhost:8888/opensso/UI/Login? + realm=gatein&goto=http://localhost:8080/portal/initiatessologin</param-value> + </init-param> </filter> - <filter> - <filter-name>OpenSSOLogoutFilter</filter-name> - <filter-class>org.gatein.sso.agent.filter.OpenSSOLogoutFilter</filter-class> - <init-param> -  - <param-name>LOGOUT_URL</param-name> - <param-value>http://localhost:8888/opensso/UI/Logout</param-value> - </init-param> - </filter> + <filter> + <filter-name>OpenSSOLogoutFilter</filter-name> + <filter-class>org.gatein.sso.agent.filter.OpenSSOLogoutFilter</filter-class> + <init-param> +  + <param-name>LOGOUT_URL</param-name> + <param-value>http://localhost:8888/opensso/UI/Logout</param-value> + </init-param> + </filter> + <filter> + <filter-name>InitiateLoginFilter</filter-name> + <filter-class>org.gatein.sso.agent.filter.InitiateLoginFilter</filter-class> + <init-param> + <param-name>ssoServerUrl</param-name> + <param-value>hhttp://localhost:8888/opensso</param-value> + </init-param> + <init-param> + <param-name>loginUrl</param-name> + <param-value>http://localhost:8080/portal/dologin</param-value> + </init-param> + <init-param> + <param-name>ssoCookieName</param-name> + <param-value>iPlanetDirectoryPro</param-value> + </init-param> + </filter> +  <filter-mapping> - <filter-name>LoginRedirectFilter</filter-name> - <url-pattern>/*</url-pattern> + <filter-name>LoginRedirectFilter</filter-name> + <url-pattern>/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>OpenSSOLogoutFilter</filter-name> <url-pattern>/*</url-pattern> + </filter-mapping> + <filter-mapping> + <filter-name>InitiateLoginFilter</filter-name> + <url-pattern>/initiatessologin</url-pattern> </filter-mapping> \ No newline at end of file Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Advanced_Concepts.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Advanced_Concepts.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Advanced_Concepts.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -1,9 +1,8 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Book_Name.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> - <section id="sect-Reference_Guide-Understanding_how_configuration_files_are_loaded-Advanced_concepts_for_the_PortalContainers"> <title>Advanced concepts for the <emphasis>PortalContainers</emphasis></title> <para> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Config_Retrieval.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Config_Retrieval.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Config_Retrieval.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -1,6 +1,6 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Book_Name.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Configuring_Containers.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Configuring_Containers.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Configuring_Containers.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -1,6 +1,6 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Book_Name.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Configuring_Services.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Configuring_Services.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Configuring_Services.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -1,6 +1,6 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Book_Name.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> @@ -47,6 +47,82 @@ <para> The configuration you find inside the jar file is considered as the default configuration. If you want to override this default configuration you can do it in different places outside the jar. When the container finds several configurations for the same service, the configuration which is found later replaces completely the one found previously. Let's call this the <emphasis>configuration override mechanism</emphasis>. </para> + <para> + After deploying you find the configuration.xml file in webapps/portal/WEB-INF/conf Use component registration tags. Let's look at the key tag that defines the interface and the type tag that defines the implementation. Note that the key tag is not mandatory, but it improves performance. + </para> + <programlisting language="XML" role="XML"> + <component> + <key>org.exoplatform.services.portletcontainer.persistence.PortletPreferencesPersister</key> + <type>org.exoplatform.services.portal.impl.PortletPreferencesPersisterImpl</type> + </component></programlisting> + <para> + Register plugins that can act as listeners or external plugin to bundle some plugin classes in other jar modules. The usual example is the hibernate service to which we can add hbm mapping files even if those are deployed in an other maven artifact. + </para> + +<programlisting language="XML" role="XML"><external-component-plugins> + <target-component>org.exoplatform.services.database.HibernateService</target-component> + <component-plugin> + <name>add.hibernate.mapping</name> + <set-method>addPlugin</set-method> + <type>org.exoplatform.services.database.impl.AddHibernateMappingPlugin</type> + <init-params> + <values-param> + <name>hibernate.mapping</name> + <value>org/exoplatform/services/portal/impl/PortalConfigData.hbm.xml</value> + <value>org/exoplatform/services/portal/impl/PageData.hbm.xml</value> + <value>org/exoplatform/services/portal/impl/NodeNavigationData.hbm.xml</value> + </values-param> + </init-params> + </component-plugin> +</external-component-plugins></programlisting> + <para> + In that sample we target the HibernateService and we will call its addPlugin() method with an argument of the type AddHibernateMappingPlugin. That object will first have been filled with the init parameters. + </para> + <para> + Therefore, it is possible to define services that will be able to receive plugins without implementing any framework interface. + </para> + <para> + Another example of use is the case of listeners as in the following code where a listener is added to the OrganisationService and will be called each time a new user is created: + </para> + +<programlisting language="XML" role="XML"><external-component-plugins> + <target-component>org.exoplatform.services.organization.OrganizationService</target-component> + <component-plugin> + <name>portal.new.user.event.listener</name> + <set-method>addListenerPlugin</set-method> + <type>org.exoplatform.services.portal.impl.PortalUserEventListenerImpl</type> + <description>this listener create the portal configuration for the new user</description> + <init-params> + <object-param> + <name>configuration</name> + <description>description</description> + <object type="org.exoplatform.services.portal.impl.NewPortalConfig"> + <field name="predefinedUser"> + <collection type="java.util.HashSet"> + <value><string>admin</string></value> + <value><string>exo</string></value> + <value><string>company</string></value> + <value><string>community</string></value> + <value><string>portal</string></value> + <value><string>exotest</string></value> + </collection> + </field> + <field name="templateUser"><string>template</string></field> + <field name="templateLocation"><string>war:/conf/users</string></field> + </object> + </object-param> + </init-params> + </component-plugin> +...</programlisting> + <para> + In the previous XML configuration, we refer the organization service and we will call its method addListenerPlugin with an object of type PortalUserEventListenerImpl. Each time a new user will be created (apart the predefined ones in the list above) methods of the PortalUserEventListenerImpl will be called by the service. + </para> + <para> + As you can see, there are several types of init parameters, from a simple value param which binds a key with a value to a more complex object mapping that fills a JavaBean with the info defined in the XML. + </para> + <para> + Many other examples exist such as for the Scheduler Service where you can add a job with a simple XML configuration or the JCR Service where you can add a NodeType from your own configuration.xml file. + </para> <section id="sect-Reference_Guide-Configuration_Retrieval-RootContainer"> <title>RootContainer</title> <para> @@ -94,6 +170,8 @@ <para> The further configuration retrieval depends on the container type. </para> + </section> + <section id="sect-Reference_Guide-Configuration_Retrieval-PortalContainer"> <title>PortalContainer</title> <para> @@ -147,7 +225,6 @@ </para> </note> - </section> </section> <section id="sect-Reference_Guide-Configuration_syntax-External_Plug_ins"> @@ -622,6 +699,55 @@ </para> </section> </section> + <section id="sect-Reference_Guide-Component_Plugin_Priority"> + <title>Component Plugin Priority</title> + <para> + Since kernel version 2.0.6 it is possible to setup order of loading for ComponentPlugin. Use the ' <emphasis role="bold">priority</emphasis>' tag to define plugin's load priority. By <emphasis role="bold">default</emphasis> all plugins get <emphasis role="bold">priority '0'</emphasis>; they will be loaded in the container's natural way. If you want one plugin to be loaded later than the others then just set priority for it <emphasis role="bold">higher than zero</emphasis>. + </para> + <para> + Simple example of fragment of a <emphasis role="bold">configuration.xml</emphasis>. + </para> + +<programlisting language="XML" role="XML">... +<component> + <type>org.exoplatform.services.Component1</type> +</component> + +<external-component-plugins> + <target-component>org.exoplatform.services.Component1</target-component> + + <component-plugin> + <name>Plugin1</name> + <set-method>addPlugin</set-method> + <type>org.exoplatform.services.plugins.Plugin1</type> + <description>description</description> + <priority>1</priority> + </component-plugin> + + <component-plugin> + <name>Plugin2</name> + <set-method>addPlugin</set-method> + <type>org.exoplatform.services.plugins.Plugin2</type> + <description>description</description> + <priority>2</priority> + </component-plugin> + +</external-component-plugins> + +<external-component-plugins> + <target-component>org.exoplatform.services.Component1</target-component> + <component-plugin> + <name>Plugin3</name> + <set-method>addPlugin</set-method> + <type>org.exoplatform.services.plugins.Plugin3</type> + <description>description</description> + </component-plugin> +</external-component-plugins> +...</programlisting> + <para> + In the above example plugin 'Plugin3' will be loaded first because it has the default priority '0'. Then, plugin 'Plugin1' will be loaded and last one is plugin 'Plugin2'. + </para> +</section> <section id="sect-Reference_Guide-Miscellaneous-Configuration_Logging"> <title>Configuration Logging</title> <para> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Extensions_And_Multiple_Portals.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Extensions_And_Multiple_Portals.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Extensions_And_Multiple_Portals.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -1,9 +1,8 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Book_Name.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> - <section id="sect-Reference_Guide-Foundations-The_Extension_Mechanism_and_Portal_Extensions"> <title>The Extension Mechanism and Portal Extensions</title> <para> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Kernel.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Kernel.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Kernel.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -1,6 +1,6 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Book_Name.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> @@ -43,7 +43,19 @@ <programlisting language="Java" role="Java">public ServiceA(){ this.serviceB =Container.getSInstance().getService(ServiceB.class); }</programlisting> -<para> + <para> + The container package is responsible of building a hierarchy of containers. Each service will then be registered in one container or the other according to the XML configuration file it is defined in. It is important to understand that there can be several PortalContainer instances that all are children of the RootContainer. + </para> + <para> + The behavior of the hierarchy is similar to a class loader one, hence when you will lookup a service that depends on another one, the container will look for it in the current container and if it cannot be found, then it will look in the parent container. That way you can load all the reusable business logic components in the same container (here the RootContainer) and differentiate the service implementation from one portal instance to the other by just loading different service implementations in two sibling PortalContainers. + </para> + <para> + Therefore, if you look at the Portal Container as a service repository for all the business logic in a portal instance, then you understand why several PortalContainers allows you to manage several portals (each one deployed as a single war) in the same server by just changing XML configuration files. + </para> + <para> + The default configuration XML files are packaged in the service jar. There are three configuration.xml files, one for each container type. In that XML file, we define the list of services and their init parameters that will be loaded in the corresponding container. + </para> + <para> Service components exist in two scopes. The first scope is represented by the <literal>RootContainer</literal>. It contains services that exist independently of any portal, and can be accessed by all portals. </para> <para> @@ -72,6 +84,9 @@ </mediaobject> </para> + <para> + As there can be several portal container instances per JVM. it is important to be able to configure the loaded services per instance. Therefore all the default configuration files located in the service impl jar can be overridden from the portal war. + </para> <para> Whenever a specific service is looked up through the <literal>PortalContainer</literal>, and the service is not available, the lookup is delegated further up to the <literal>RootContainer</literal>. </para> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Profiles.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Profiles.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Profiles.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -1,6 +1,6 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Book_Name.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Requests.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Requests.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Requests.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -1,6 +1,6 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Book_Name.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/System_Properties.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/System_Properties.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/System_Properties.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -1,6 +1,6 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Book_Name.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -5,16 +5,19 @@ %BOOK_ENTITIES; ]> <chapter id="chap-Reference_Guide-Foundations"> - <title>Foundations</title> + <title><remark>Foundations</remark></title> <xi:include href="Foundations/Kernel.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Foundations/JNDI_Naming.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Foundations/Config_Retrieval.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Foundations/Advanced_Concepts.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Foundations/Profiles.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Foundations/Requests.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Foundations/Configuring_Services.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Foundations/Specific_Services.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Foundations/Configuring_Containers.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Foundations/System_Properties.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Foundations/Extensions_And_Multiple_Portals.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Foundations/Management.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </chapter> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/data-container.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/data-container.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/data-container.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -1,612 +1,478 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "../../../../Reference_Guide_eXo_JCR_1.14.ent"> %BOOK_ENTITIES; ]> <section id="sect-Reference_Guide-JCR_Workspace_Data_Container_architecture_contract"> - <title>JCR Workspace Data Container (architecture contract)</title> - <section id="sect-Reference_Guide-JCR_Workspace_Data_Container_architecture_contract-Goals"> - <title>Goals</title> + <title>JCR Workspace Data Container</title> + <para> + The JCR Workspace Data Container: + </para> <itemizedlist> <listitem> <para> - Cover the requirements on Workspace Data Container implementation + Covers the requirements on Workspace Data Container implementation </para> </listitem> <listitem> <para> - Describe container life cycle + Describes container life cycle. </para> </listitem> <listitem> <para> - Describe relations between container and high-level DataManagers + Describes relations between container and high-level DataManagers </para> - </listitem> - </itemizedlist> - - </section> - <section id="sect-Reference_Guide-JCR_Workspace_Data_Container_architecture_contract-Concepts"> - <title>Concepts</title> - <section id="sect-Reference_Guide-Concepts-Container_and_connection"> - <title>Container and connection</title> - <para> - Workspace Data Container (container) serves Repository Workspace persistent storage. WorkspacePersistentDataManager (data manager) uses container to perform CRUD operation on the persistent storage. Accessing to the storage in the data manager is implemented via storage connection obtained from the container (WorkspaceDataContainer interface implementation). Each connection represents a transaction on the storage. Storage Connection (connection) should be an implementation of WorkspaceStorageConnection. - </para> - <itemizedlist> - <listitem> - <para> - Container acts as a factory of a new storage connections. Usually, this method is designed to be synchronized to avoid possible concurrent issues. - </para> - - </listitem> - - </itemizedlist> - + <variablelist> + <title>Concepts</title> + <varlistentry> + <term>Container and connection</term> + <listitem> + <para> + The Workspace Data Container (container) serves Repository Workspace persistent storage. + </para> + <para> + <literal>WorkspacePersistentDataManager</literal> (data manager) uses the container to perform <abbrev>CRUD</abbrev> (Create, Read, Update and Delete) operations on the persistent storage. + </para> + <para> + Access to the storage in the data manager is implemented via a storage connection obtained from the container (<literal>WorkspaceDataContainer</literal> interface implementation). + </para> + <para> + Each connection represents a transaction on the storage. Storage Connection (connection) should be an implementation of <literal>WorkspaceStorageConnection</literal>. + </para> + <itemizedlist> + <listitem> + <para> + The Container acts as a factory of a new storage connections. Usually, this method is designed to be synchronized to avoid possible concurrent issues. + </para> <programlisting language="Java" role="Java">WorkspaceStorageConnection openConnection() throws RepositoryException; </programlisting> - <itemizedlist> - <listitem> - <para> - Open read-only WorkspaceStorageConnection. Read-only connections can be potentially a bit faster in some cases. - </para> - - </listitem> - - </itemizedlist> - -<programlisting language="Java" role="Java">WorkspaceStorageConnection openConnection(boolean readOnly) throws RepositoryException; -</programlisting> - <note> - <title>*EXPERIMENTAL*</title> - <para> - Read-only WorkspaceStorageConnection is experimental feature and not currently handled in JCR. Actually, such connections didn't prove their performance, so JCR Core doesn't use them. - </para> - - </note> - <itemizedlist> - <listitem> - <para> - Storage connection might also be reused. This means reuse of physical resource (e.g. JDBC Connection) allocated by one connection in another. This feature is used in a data manager for saving ordinary and system changes on the system Workspace. But the reuse is an optional feature and it can work, otherwise a new connection will open. - </para> - - </listitem> - - </itemizedlist> - + </listitem> + <listitem> + <para> + The Storage connection might also be reused. This means reuse of a physical resource (JDBC Connection, for example) allocated by one connection in another. + </para> + <para> + This feature is used in a data manager for saving ordinary and system changes on the system Workspace. But the reuse is an optional feature. If it is not used, a new connection will open. + </para> <programlisting language="Java" role="Java">WorkspaceStorageConnection reuseConnection(WorkspaceStorageConnection original) throws RepositoryException; </programlisting> - <itemizedlist> - <listitem> - <para> - When checking Same-Name Siblings (SNS) existence, JCR Core can use new connection or not. This is defined via Workspace Data Container configuration and retrieved by using a special method. - </para> - - </listitem> - - </itemizedlist> - + </listitem> + <listitem> + <para> + When checking for the existence of <literal>Same-Name Siblings</literal> (SNS), JCR Core can use either a new connection or an existing one. This behaviour is defined via the Workspace Data Container configuration and is retrieved by using the special method: + </para> <programlisting language="Java" role="Java">boolean isCheckSNSNewConnection(); </programlisting> - <para> - Container initialization is only based on a configuration. After the container has been created, it's not possible to change parameters. Configuration consists of implementation class and set of properties and Value Storages configuration. - </para> - - </section> - - <section id="sect-Reference_Guide-Concepts-Value_storages"> - <title>Value storages</title> - <para> - Container provides optional special mechanism for Value storing. It's possible to configure external Value Storages via container configuration (available only via configuration). Value Storage works as fully independent pluggable storage. All required parameters storage obtains from its configuration. Some storages are possible for one container. Configuration describes such parameters as ValueStoragePluginimplementation class, set of implementation specific properties and filters. The filters declares criteria for Value matching to the storage. Only matched Property Values will be stored. So, in common case, the storage might contains only the part of the Workspace content. Value Storages are very useful for BLOB storing. E.g. storing on the File System instead of a database. - </para> - <para> - Container obtains Values Storages from ValueStoragePluginProvider component. Provider acts as a factory of Value channels (ValueIOChannel). Channel provides all CRUD operation for Value Storage respecting the transaction manner of work (how it can be possible due to implementation specifics of the storages). - </para> - - </section> - - <section id="sect-Reference_Guide-Concepts-Lifecycle"> - <title>Lifecycle</title> - <para> - Container is used for read and write operations by data manager. Read operations (getters) uses connection once and close it on the finally. Write operations performs in commit method as a sequence of creating/ updating calls and final commit (or rollback on error). Writes uses one connection (or two - another for system workspace) per commit call. One connection guaranties transaction support for write operations. Commit or rollback should free/clean all resources consumed by the container (connection). - </para> - - </section> - - <section id="sect-Reference_Guide-Concepts-Value_storage_lifecycle"> - <title>Value storage lifecycle</title> - <para> - Value storage is used from the container inside. Reads are related to a container reads. Writes are commit-related. Container (connection) implementation should use transaction capabilities of the storages in the same way as for other operations. - </para> - - </section> - - - </section> - + </listitem> + <listitem> + <para> + As container initialization is based soley on a written configuration, it is not possible to change a container's parameters after it has been created. This configuration consists of implementation class(s) and a set of properties and Value Storages configuration. + </para> + </listitem> + </itemizedlist> + </listitem> + </varlistentry> + <varlistentry> + <term>Value storages</term> + <listitem> + <para> + The container provides an optional special mechanism for <emphasis role="bold">Value</emphasis> storing. It is possible to configure external Value Storages via the container configuration. + </para> + <para> + Value Storage works as fully independent pluggable storage (however some storages are possible for a single container). All required parameters are obtained from the configuration, including the <literal>ValueStoragePluginimplementation</literal> class and a set of implementation specific properties and filters. + </para> + <para> + Filters declare criteria which dictate what Values are stored. This means that the storage might only contain some of the Workspace content. + </para> + <para> + The container obtains Values from Storages with the <literal>ValueStoragePluginProvider</literal> component. This component acts as a factory of Value channels (<literal>ValueIOChannel</literal>). Value Channels provide all CRUD operations for Value Storage, while respecting the transaction manner of work (based on implementation specifics of the storages). + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Lifecycle</term> + <listitem> + <para> + The Container is used for <emphasis>read</emphasis> and <emphasis>write</emphasis> operations by the data manager. + </para> + <para> + Read operations (<emphasis>getters</emphasis>) use the connection once and then closes it. + </para> + <para> + Write operations use the commit method as a sequence of creating and/or updating calls and the final commit (or rollback if an error is encountered). Writes use one connection (plus one for the system workspace) per commit call. One connection guarantees transaction support for write operations. The commit or rollback action should free and/or clean all resources consumed by the container (connection). + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Value storage lifecycle</term> + <listitem> + <para> + Value storage is used from within the container. <emphasis>Read</emphasis> actions are related to container reads while <emphasis>write</emphasis> actions are commit-related. The container (connection) implementation should use transaction capabilities of the storages in the same way as for other operations. + </para> + </listitem> + </varlistentry> + </variablelist> + <section id="sect-Reference_Guide-JCR_Workspace_Data_Container_architecture_contract-Requirements"> <title>Requirements</title> <para> - Connection creation and reuse should be a thread safe operation. Connection provides CRUD operations support on the storage. + Connection creation and reuse should be a thread safe operation. The connection provides <abbrev>CRUD</abbrev> operations support on the storage. </para> - <section id="sect-Reference_Guide-Requirements-Read_operations"> + <itemizedlist> <title>Read operations</title> - <itemizedlist> <listitem> <para> - Read ItemData from the storage by item identifier. + Read <literal>ItemData</literal> from the storage by item identifier. </para> - - </listitem> - - </itemizedlist> - <programlisting language="Java" role="Java">ItemData getItemData(String identifier) throws RepositoryException, IllegalStateException; </programlisting> - <itemizedlist> + </listitem> <listitem> <para> - Read ItemData from the storage by using the parent and name of the item, related to the parent location. + Read <literal>ItemData</literal> from the storage by using the parent and name of the item, related to the parent location. </para> - - </listitem> - - </itemizedlist> - <programlisting language="Java" role="Java">ItemData getItemData(NodeData parentData, QPathEntry name) throws RepositoryException,IllegalStateException; </programlisting> - <itemizedlist> + </listitem> <listitem> <para> - Read List of NodeData from the storage by using the parent location of the item. + Read List of <literal>NodeData</literal> from the storage by using the parent location of the item. </para> - - </listitem> - - </itemizedlist> - <programlisting language="Java" role="Java">List<NodeData> getChildNodesData(NodeData parent) throws RepositoryException, IllegalStateException; </programlisting> - <itemizedlist> + </listitem> <listitem> <para> - Reads List of PropertyData from the storage by using the parent location of the item. + Read List of <literal>PropertyData</literal> from the storage by using the parent location of the item. </para> - - </listitem> - - </itemizedlist> - <programlisting language="Java" role="Java">List<PropertyData> getChildPropertiesData(NodeData parent) throws RepositoryException, IllegalStateException; </programlisting> - <itemizedlist> + </listitem> <listitem> <para> - Reads List of PropertyData with empty ValueData from the storage by using the parent location of the item. + Read List of <literal>PropertyData</literal> with empty <literal>ValueData</literal> from the storage by using the parent location of the item. </para> - - </listitem> - - </itemizedlist> - <para> - This method specially dedicated for non-content modification operations (e.g. Items delete). - </para> - + <para> + This method is specifically dedicated to non-content modification operations (Items delete, for example). + </para> <programlisting language="Java" role="Java">List<PropertyData> listChildPropertiesData(NodeData parent) throws RepositoryException, IllegalStateException; </programlisting> - <itemizedlist> + </listitem> <listitem> <para> - Reads List of PropertyData from the storage by using the parent location of the item. + Read List of <literal>PropertyData</literal> from the storage by using the parent location of the item. </para> - - </listitem> - - </itemizedlist> - <para> - It's REFERENCE type: Properties referencing Node with given nodeIdentifier. See more in javax.jcr.Node.getReferences() - </para> - + <para> + It's REFERENCE type: Properties referencing Node with given <literal>nodeIdentifier</literal>. See more in <literal>javax.jcr.Node.getReferences()</literal> + </para> <programlisting language="Java" role="Java">List<PropertyData> getReferencesData(String nodeIdentifier) throws RepositoryException,IllegalStateException,UnsupportedOperationException; </programlisting> - - </section> + </listitem> + </itemizedlist> - <section id="sect-Reference_Guide-Requirements-Write_operations"> + <itemizedlist> <title>Write operations</title> - <itemizedlist> <listitem> <para> - Add single NodeData. + Add single <literal>NodeData</literal>. </para> - - </listitem> - - </itemizedlist> - <programlisting language="Java" role="Java">void add(NodeData data) throws RepositoryException,UnsupportedOperationException,InvalidItemStateException,IllegalStateException; </programlisting> - <itemizedlist> + </listitem> <listitem> <para> - Add single PropertyData. + Add single <literal>PropertyData</literal>. </para> - - </listitem> - - </itemizedlist> - <programlisting language="Java" role="Java">void add(PropertyData data) throws RepositoryException,UnsupportedOperationException,InvalidItemStateException,IllegalStateException; </programlisting> - <itemizedlist> + </listitem> <listitem> <para> - Update NodeData. + Update <literal>NodeData</literal>. </para> - - </listitem> - - </itemizedlist> - <programlisting language="Java" role="Java">void update(NodeData data) throws RepositoryException,UnsupportedOperationException,InvalidItemStateException,IllegalStateException; </programlisting> - <itemizedlist> + </listitem> <listitem> <para> - Update PropertyData. + Update <literal>PropertyData</literal>. </para> - - </listitem> - - </itemizedlist> - <programlisting language="Java" role="Java">void update(PropertyData data) throws RepositoryException,UnsupportedOperationException,InvalidItemStateException,IllegalStateException; </programlisting> - <itemizedlist> + </listitem> <listitem> <para> - Rename NodeData by using Node identifier and new name and indexing from the data. + Rename <literal>NodeData</literal> by using Node identifier and new name and indexing from the data. </para> - - </listitem> - - </itemizedlist> - <programlisting language="Java" role="Java">void rename(NodeData data) throws RepositoryException,UnsupportedOperationException,InvalidItemStateException,IllegalStateException; </programlisting> - <itemizedlist> + </listitem> <listitem> <para> - Delete NodeData. + Delete <literal>NodeData</literal>. </para> - - </listitem> - - </itemizedlist> - <programlisting language="Java" role="Java">void delete(NodeData data) throws RepositoryException,UnsupportedOperationException,InvalidItemStateException,IllegalStateException; </programlisting> - <itemizedlist> + </listitem> <listitem> <para> - Delete PropertyData. + Delete <literal>PropertyData</literal>. </para> - - </listitem> - - </itemizedlist> - <programlisting language="Java" role="Java">void delete(PropertyData data) throws RepositoryException,UnsupportedOperationException,InvalidItemStateException,IllegalStateException; </programlisting> - <itemizedlist> + </listitem> <listitem> <para> Persist changes and closes connection. It can be database transaction commit for instance etc. </para> - - </listitem> - - </itemizedlist> - <programlisting language="Java" role="Java">void commit() throws IllegalStateException, RepositoryException; </programlisting> - <itemizedlist> + </listitem> <listitem> <para> Refuse persistent changes and closes connection. It can be database transaction rollback for instance etc. </para> - +<programlisting language="Java" role="Java">void rollback() throws IllegalStateException, RepositoryException; +</programlisting> + <para> + All methods throw <literal>IllegalStateException</literal> if the connection is closed, <literal>UnsupportedOperationException</literal> if the method is not supported and <literal>RepositoryException</literal> if some errors occur during preparation, validation or persistence. + </para> </listitem> - </itemizedlist> -<programlisting language="Java" role="Java">void rollback() throws IllegalStateException, RepositoryException; -</programlisting> - <para> - All methods throw IllegalStateException if connection is closed. UnsupportedOperationException if the method is not supported (e.g. JCR Level 1 implementation etc). RepositoryException if some errors occur during preparation, validation or persistence. - </para> - - </section> - - <section id="sect-Reference_Guide-Requirements-State_operations"> + <itemizedlist> <title>State operations</title> - <itemizedlist> <listitem> <para> Return true if connection can be used. </para> - +<programlisting language="Java" role="Java">boolean isOpened(); +</programlisting> </listitem> </itemizedlist> - -<programlisting language="Java" role="Java">boolean isOpened(); -</programlisting> - </section> - - <section id="sect-Reference_Guide-Requirements-Validation_of_write_operations"> + <itemizedlist> <title>Validation of write operations</title> - <para> - Container has to care about storage consistency (JCR constraints) on write operations: (InvalidItemStateException should be thrown according the spec). At least, the following checks should be performed: - </para> - <itemizedlist> <listitem> <para> - On ADD errors + As the container has to care about storage consistency (JCR constraints) on write operations: (InvalidItemStateException should be thrown according the spec). At least, the following checks should be performed: </para> - <itemizedlist> - <listitem> - <para> - Parent not found. Condition: Parent ID (Item with ID is not exists). - </para> + </listitem> + <listitem> + <itemizedlist> + <title>On ADD errors</title> + <listitem> + <itemizedlist> + <listitem> + <para> + Parent not found. Condition: Parent ID (Item with ID is not exists). + </para> - </listitem> - <listitem> - <para> - Item already exists. Condition: ID (Item with ID already exists). - </para> + </listitem> + <listitem> + <para> + Item already exists. Condition: ID (Item with ID already exists). + </para> + </listitem> + <listitem> + <para> + Item already exists. Condition: Parent ID, Name, Index (Item with parent ID, name and index already exists). + </para> + </listitem> + </itemizedlist> </listitem> - <listitem> - <para> - Item already exists. Condition: Parent ID, Name, Index (Item with parent ID, name and index already exists). - </para> - - </listitem> - </itemizedlist> - </listitem> - - </itemizedlist> - <itemizedlist> <listitem> - <para> - On DELETE errors - </para> <itemizedlist> + <title>On DELETE errors</title> <listitem> - <para> - Item not found. Condition ID. - </para> + <itemizedlist> + <listitem> + <para> + Item not found. Condition ID. + </para> - </listitem> - <listitem> - <para> - Can not delete parent till children exists. - </para> + </listitem> + <listitem> + <para> + Can not delete parent till children exists. + </para> + </listitem> + </itemizedlist> </listitem> - </itemizedlist> - </listitem> - - </itemizedlist> - <itemizedlist> <listitem> - <para> - On UPDATE errors - </para> <itemizedlist> + <title>On UPDATE errors</title> <listitem> - <para> - Item not found. Condition ID. - </para> + <itemizedlist> + <listitem> + <para> + Item not found. Condition ID. + </para> + </listitem> + <listitem> + <para> + Item already exists with higher Version. Condition: ID, Version (Some Session had updated Item with ID prior this update). + </para> + </listitem> + </itemizedlist> </listitem> - <listitem> - <para> - Item already exists with higher Version. Condition: ID, Version (Some Session had updated Item with ID prior this update). - </para> - - </listitem> - - </itemizedlist> - - </listitem> - - </itemizedlist> - - </section> - - <section id="sect-Reference_Guide-Requirements-Consistency_of_save"> + </itemizedlist> + </listitem> + </itemizedlist> + <itemizedlist> <title>Consistency of save</title> - <para> - The container (connection) should implement consistency of Commit (Rollback) in <emphasis role="bold">transaction manner</emphasis>. I.e. If a set of operations was performed <emphasis role="bold">before</emphasis> the future <emphasis role="bold">Commit</emphasis> and another next operation <emphasis role="bold">fails</emphasis>. <emphasis role="bold">It should be possible to</emphasis> rollback applied changes using <emphasis role="bold">Rollback</emphasis> command. - </para> - - </section> + <listitem> + <para> + The container (connection) should implement consistency of Commit (Rollback) in <emphasis role="bold">transaction manner</emphasis>. I.e. If a set of operations was performed <emphasis role="bold">before</emphasis> the future <emphasis role="bold">Commit</emphasis> and another next operation <emphasis role="bold">fails</emphasis>. <emphasis role="bold">It should be possible to</emphasis> rollback applied changes using <emphasis role="bold">Rollback</emphasis> command. + </para> + </listitem> + </itemizedlist> - - </section> - - <section id="sect-Reference_Guide-JCR_Workspace_Data_Container_architecture_contract-Value_storages_API"> - <title>Value storages API</title> - <section id="sect-Reference_Guide-Value_storages_API-Storages_provider"> - <title>Storages provider:</title> - <para> - Container implementation obtains Values Storages option via ValueStoragePluginProvider component. Provider acts as a factory of Value channels (ValueIOChannel) and has two methods for this purpose: - </para> + <itemizedlist> + <title>Value storages API</title> + <listitem> <itemizedlist> - <listitem> - <para> - Return ValueIOChannel matched this property and valueOrderNumer. Null will be returned if no channel matches. - </para> - - </listitem> - - </itemizedlist> - + <title>Storages provider:</title> + <listitem> + <para> + Container implementation obtains Values Storages option via ValueStoragePluginProvider component. Provider acts as a factory of Value channels (ValueIOChannel) and has two methods for this purpose: + </para> + <itemizedlist> + <listitem> + <para> + Return ValueIOChannel matched this property and valueOrderNumer. Null will be returned if no channel matches. + </para> <programlisting language="Java" role="Java">ValueIOChannel getApplicableChannel(PropertyData property, int valueOrderNumer) throws IOException; </programlisting> - <itemizedlist> - <listitem> - <para> - Return ValueIOChannel associated with given storageId. - </para> - - </listitem> - - </itemizedlist> - + </listitem> + <listitem> + <para> + Return ValueIOChannel associated with given storageId. + </para> <programlisting language="Java" role="Java">ValueIOChannel getChannel(String storageId) throws IOException, ValueStorageNotFoundException; </programlisting> - <para> - There is also method for consistency check, but this method doesn't used anywhere and storage implementations has it empty. - </para> - - </section> - - <section id="sect-Reference_Guide-Value_storages_API-Value_storage_plugin"> - <title>Value storage plugin</title> - <para> - Provider implementation should use ValueStoragePlugin abstract class as a base for all storage implementations. Plugin provides support for provider implementation methods. Plugin's methods should be implemented: - </para> - <itemizedlist> - <listitem> - <para> - Initialize this plugin. Used at start time in ValueStoragePluginProvider. - </para> - - </listitem> - + </listitem> + </itemizedlist> + </listitem> + <listitem> + <para> + There is also method for consistency check, but this method doesn't used anywhere and storage implementations has it empty. + </para> + </listitem> </itemizedlist> - + </listitem> + <listitem> + <itemizedlist> + <title>Value storage plugin</title> + <listitem> + <para> + Provider implementation should use ValueStoragePlugin abstract class as a base for all storage implementations. Plugin provides support for provider implementation methods. Plugin's methods should be implemented: + </para> + </listitem> + <listitem> + <itemizedlist> + <listitem> + <para> + Initialize this plugin. Used at start time in ValueStoragePluginProvider. + </para> <programlisting language="Java" role="Java">public abstract void init(Properties props, ValueDataResourceHolder resources) throws RepositoryConfigurationException, IOException; </programlisting> - <itemizedlist> - <listitem> - <para> - Open ValueIOChannel.Used in ValueStoragePluginProvider.getApplicableChannel(PropertyData, int) and getChannel(String) - </para> - - </listitem> - - </itemizedlist> - + </listitem> + <listitem> + <para> + Open ValueIOChannel.Used in ValueStoragePluginProvider.getApplicableChannel(PropertyData, int) and getChannel(String) + </para> <programlisting language="Java" role="Java">public abstract ValueIOChannel openIOChannel() throws IOException; </programlisting> - <itemizedlist> - <listitem> - <para> - Return true if this storage has the same storageId. - </para> - - </listitem> - - </itemizedlist> - + </listitem> + <listitem> + <para> + Return true if this storage has the same storageId. + </para> <programlisting language="Java" role="Java">public abstract boolean isSame(String valueDataDescriptor); </programlisting> - - </section> - - <section id="sect-Reference_Guide-Value_storages_API-Value_IO_channel"> - <title>Value I/O channel</title> - <para> - Channel should implement ValueIOChannel interface. CRUD operation for Value Storage: - </para> - <itemizedlist> - <listitem> + </listitem> + </itemizedlist> + </listitem> + </itemizedlist> + </listitem> + <listitem> + <itemizedlist> + <title>Value I/O channel</title> + <listitem> <para> - Read Property value. + Channel should implement ValueIOChannel interface. CRUD operation for Value Storage: </para> - - </listitem> - - </itemizedlist> - + </listitem> + <listitem> + <itemizedlist> + <listitem> + <para> + Read Property value. + </para> <programlisting language="Java" role="Java">ValueData read(String propertyId, int orderNumber, int maxBufferSize) throws IOException; </programlisting> - <itemizedlist> - <listitem> - <para> - Add or update Property value. - </para> - - </listitem> - - </itemizedlist> - + </listitem> + <listitem> + <para> + Add or update Property value. + </para> <programlisting language="Java" role="Java">void write(String propertyId, ValueData data) throws IOException; </programlisting> - <itemizedlist> - <listitem> - <para> - Delete Property all values. - </para> - - </listitem> - - </itemizedlist> - + </listitem> + <listitem> + <para> + Delete Property all values. + </para> <programlisting language="Java" role="Java">void delete(String propertyId) throws IOException; </programlisting> - - </section> - - <section id="sect-Reference_Guide-Value_storages_API-Transaction_support_via_channel"> - <title>Transaction support via channel</title> - <para> - Modification operations should be applied only when committing. Rollback is required for data created cleanup. - </para> - <itemizedlist> - <listitem> - <para> - Commit channel changes. - </para> - - </listitem> - + </listitem> + </itemizedlist> + </listitem> </itemizedlist> - + </listitem> + <listitem> + <itemizedlist> + <title>Transaction support via channel</title> + <listitem> + <para> + Modification operations should be applied only when committing. Rollback is required for data created cleanup. + </para> + </listitem> + <listitem> + <itemizedlist> + <listitem> + <para> + Commit channel changes. + </para> <programlisting language="Java" role="Java">void commit() throws IOException; </programlisting> - <itemizedlist> - <listitem> - <para> - Rollback channel changes. - </para> - - </listitem> - - </itemizedlist> - + </listitem> + <listitem> + <para> + Rollback channel changes. + </para> <programlisting language="Java" role="Java">void rollback() throws IOException; </programlisting> - - </section> - - - </section> - -</section> - - + </listitem> + </itemizedlist> + </listitem> + </itemizedlist> + </listitem> + </itemizedlist> + </section> +</section> \ No newline at end of file Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/protocols/ftp.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/protocols/ftp.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/protocols/ftp.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -6,34 +6,35 @@ <section id="sect-Reference_Guide-FTP"> <title>FTP</title> <section id="sect-Reference_Guide-FTP-Introduction"> - <title>Introdution</title> + <title>Introduction</title> <para> - The JCR-FTP Server represents the standard eXo service, operates as an FTP server with an access to a content stored in JCR repositories in the form of <emphasis role="bold">nt:file/nt:folder</emphasis> nodes or their successors. The client of an executed Server can be any FTP client. The FTP server is supported by a standard configuration which can be changed as required. + The JCR-FTP Server operates as an FTP server with access to a content stored in JCR repositories in the form of <emphasis role="bold">nt:file/nt:folder</emphasis> nodes or their successors. The client of an executed Server can be any FTP client. The FTP server is supported by a standard configuration which can be changed as required. </para> </section> <section id="sect-Reference_Guide-FTP-Configuration_Parameters"> <title>Configuration Parameters</title> - <section id="sect-Reference_Guide-Configuration_Parameters-command_port"> - <title>command-port:</title> - + <variablelist> + <title>Parameters</title> + <varlistentry> + <term>command-port:</term> + <listitem> <programlisting language="XML" role="XML"><value-param> <name>command-port</name> <value>21</value> </value-param></programlisting> - <para> - The value of the command channel port. The value '21' is default. - </para> - <para> - When you have already some FTP server installed in your system , this parameter needs to be changed (2121 for example) to avoid conflicts or if the port is protected. - </para> - - </section> - - <section id="sect-Reference_Guide-Configuration_Parameters-data_min_port_amp_data_max_port"> - <title>data-min-port & data-max-port</title> - + <para> + The value of the command channel port. The value '<literal>21</literal>' is default. + </para> + <para> + If you have already other FTP server installed in your system, this parameter needs to be changed (to <literal>2121</literal>, for example) to avoid conflicts or if the port is protected. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>data-min-port & data-max-port</term> + <listitem> <programlisting language="XML" role="XML"><value-param> <name>data-min-port</name> <value>52000</value> @@ -43,15 +44,14 @@ <name>data-max-port</name> <value>53000</value> </value-param></programlisting> - <para> - These two parameters indicate the minimal and maximal values of the range of ports, used by the server. The usage of the additional data channel is required by the FTP - protocol, which is used to transfer the contents of files and the listing of catalogues. This range of ports should be free from listening by other server-programs. - </para> - - </section> - - <section id="sect-Reference_Guide-Configuration_Parameters-system"> - <title>system</title> - + <para> + These two parameters indicate the minimum and maximum values of the range of ports, used by the server. The usage of the additional data channel is required by the FTP protocol, which is used to transfer the contents of files and the listing of catalogues. This range of ports should be free from listening by other server-programs. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>system</term> + <listitem> <programlisting language="XML" role="XML"><value-param> <name>system</name> @@ -59,15 +59,14 @@ or <value>UNIX Type: L8</value> </value-param></programlisting> - <para> - Types of formats of listing of catalogues which are supported. - </para> - - </section> - - <section id="sect-Reference_Guide-Configuration_Parameters-client_side_encoding"> - <title>client-side-encoding</title> - + <para> + Types of formats of listing of catalogues which are supported. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>client-side-encoding</term> + <listitem> <programlisting language="XML" role="XML"><value-param> <name>client-side-encoding</name> @@ -76,104 +75,97 @@ <value>KOI8-R</value> </value-param></programlisting> - <para> - This parameter specifies the coding which is used for dialogue with the client. - </para> - - </section> - - <section id="sect-Reference_Guide-Configuration_Parameters-def_folder_node_type"> - <title>def-folder-node-type</title> - + <para> + This parameter specifies the coding which is used for dialogue with the client. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>def-folder-node-type</term> + <listitem> <programlisting language="XML" role="XML"><value-param> <name>def-folder-node-type</name> <value>nt:folder</value> </value-param></programlisting> - <para> - This parameter specifies the type of a node, when an FTP-folder is created. - </para> - - </section> - - <section id="sect-Reference_Guide-Configuration_Parameters-def_file_node_type"> - <title>def-file-node-type</title> - + <para> + This parameter specifies the type of a node, when an FTP-folder is created. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>def-file-node-type</term> + <listitem> <programlisting language="XML" role="XML"><value-param> <name>def-file-node-type</name> <value>nt:file</value> </value-param></programlisting> - <para> - This parameter specifies the type of a node, when an FTP - file is created. - </para> - - </section> - - <section id="sect-Reference_Guide-Configuration_Parameters-def_file_mime_type"> - <title>def-file-mime-type</title> - + <para> + This parameter specifies the type of a node, when an FTP-file is created. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>def-file-mime-type</term> + <listitem> <programlisting language="XML" role="XML"><value-param> <name>def-file-mime-type</name> <value>application/zip</value> </value-param></programlisting> - <para> - The mime type of a created file is chosen by using its file extention. In case, a server cannot find the corresponding mime type, this value is used. - </para> - - </section> - - <section id="sect-Reference_Guide-Configuration_Parameters-cache_folder_name"> - <title>cache-folder-name</title> - + <para> + The mime type of a created file is chosen by using its file extention. In case, a server cannot find the corresponding mime type, this value is used. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>cache-folder-name</term> + <listitem> <programlisting language="XML" role="XML"><value-param> <name>cache-folder-name</name> <value>../temp/ftp_cache</value> </value-param></programlisting> - <para> - The Path of the cache folder. - </para> - - </section> - - <section id="sect-Reference_Guide-Configuration_Parameters-upload_speed_limit"> - <title>upload-speed-limit</title> - + <para> + The Path of the cache folder. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>upload-speed-limit</term> + <listitem> <programlisting language="XML" role="XML"><value-param> <name>upload-speed-limit</name> <value>20480</value> </value-param></programlisting> - <para> - Restriction of the upload speed. It is measured in bytes. - </para> - - </section> - - <section id="sect-Reference_Guide-Configuration_Parameters-download_speed_limit"> - <title>download-speed-limit</title> - + <para> + Restriction of the upload speed. It is measured in bytes. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>download-speed-limit</term> + <listitem> <programlisting language="XML" role="XML"><value-param> <name>download-speed-limit</name> <value>20480</value> </value-param></programlisting> - <para> - Restriction of the download speed. It is measured in bytes. - </para> - - </section> - - <section id="sect-Reference_Guide-Configuration_Parameters-timeout"> - <title>timeout</title> - + <para> + Restriction of the download speed. It is measured in bytes. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>timeout</term> + <listitem> <programlisting language="XML" role="XML"><value-param> <name>timeout</name> <value>60</value> </value-param></programlisting> - <para> - Defines the value of a timeout. - </para> + <para> + Defines the value of a timeout. + </para> + </listitem> + </varlistentry> + </variablelist> - </section> - - </section> </section> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/protocols/webdav.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/protocols/webdav.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/protocols/webdav.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -6,28 +6,17 @@ <section id="sect-Reference_Guide-WebDAV">  <title>WebDAV</title> - <section id="sect-Reference_Guide-WebDAV-Related_documents"> - <title>Related documents</title> - <itemizedlist> - <listitem> - <para> - <xref linkend="sect-Reference_Guide-Link_Producer_Service" /> - </para> - </listitem> - </itemizedlist> - - </section> - + <section id="sect-Reference_Guide-WebDAV-Introduction"> <title>Introduction</title> <para> - The <application>WebDAV</application> protocol enables you to use third party tools to communicate with hierarchical content servers via HTTP. It is possible to add and remove documents or a set of documents from a path on the server. + The <application>WebDAV</application> protocol enables you to use third party tools to communicate with hierarchical content servers via the HTTP protocol. It is possible to add and remove documents or a set of documents from a path on the server. </para> <para> - <application>DeltaV</application> is an extension of the WebDav protocol that allows managing document versioning. Locking guarantees protection against multiple access when writing resources. The ordering support allows changing the position of the resource in the list and sort the directory to make the directory tree viewed conveniently. The full-text search makes it easy to find the necessary documents. You can search by using two languages: SQL and XPATH. + <application>DeltaV</application> is an extension of the WebDav protocol that allows managing document versioning. The <emphasis>Locking</emphasis> feature guarantees protection against multiple access when writing resources. The ordering support allows changing the position of the resource in the list and sort the directory to make the directory tree viewed conveniently. The full-text search makes it easy to find the necessary documents. You can search by using two languages: SQL and XPATH. </para> <para> - In the eXo JCR, the WebDAV layer (based on the code taken from the extension modules of the reference implementation) is plugged in on top of our JCR implementation. This makes it possible to browse a workspace using the third party tools regardless of operating system environments. You can use a Java WebDAV client, such as DAVExplorer or Internet Explorer using <menuchoice><guimenu>File</guimenu><guimenuitem>Open</guimenuitem></menuchoice> as a Web Folder. + In the eXo JCR, the WebDAV layer (based on the code taken from the extension modules of the reference implementation) is plugged in on top of our JCR implementation. This makes it possible to browse a workspace using the third party tools regardless of operating system environments. You can use a Java WebDAV client, such as <application>DAVExplorer</application> or <application>Internet Explorer</application> using <menuchoice><guimenu>File</guimenu><guimenuitem>Open as a Web Folder</guimenuitem></menuchoice>. </para> <para> WebDav is an extension of the REST service. To get the WebDav server ready, you must deploy the REST application. Then, you can access any workspaces of your repository by using the following URL: @@ -39,14 +28,14 @@ When accessing the WebDAV server via <ulink type="http" url="http://localhost:8080/rest/jcr/repository/production"></ulink>, you can substitute <ulink type="http" url="http://localhost:8080/rest/jcr/repository/production">production</ulink> with <ulink type="http" url="http://localhost:8080/rest/jcr/repository/collaboration">collaboration</ulink>. </para> <para> - You will be asked to enter your login and password. Those will then be checked by using the organization service that can be implemented thanks to an InMemory (dummy) module or a DB module or an LDAP one and the JCR user session will be created with the correct JCR Credentials. + You will be asked to enter your login credentials. These will then be checked by using the organization service that can be implemented thanks to an InMemory (dummy) module or a DB module or an LDAP one and the JCR user session will be created with the correct JCR Credentials. </para> <note> <title>Note:</title> + <remark>DOCS NOTE: I have no idea what this means!</remark> <para> If you try the "in ECM" option, add "@ecm" to the user's password. Alternatively, you may modify jaas.conf by adding the <emphasis role="bold">domain=ecm</emphasis> option as follows: </para> - <remark>DOCS NOTE: I have no idea what this means!</remark> <programlisting>exo-domain { org.exoplatform.services.security.jaas.BasicLoginModule required domain=ecm; };</programlisting> @@ -145,76 +134,6 @@ </section> -  - <section id="sect-Reference_Guide-WebDAV-Comparison_table_of_WebDav_and_JCR_commands"> <title>Corresponding WebDav and JCR actions</title> <table> @@ -411,13 +330,14 @@ <section id="sect-Reference_Guide-WebDAV-WebDAV_Considerations"> <title>WebDAV Considerations</title> <para> - There are some restrictions for WebDAV in different Operating systems. + There are some restrictions for WebDAV in different operating systems. </para> - <section id="sect-Reference_Guide-Restrictions-Windows_7"> + <formalpara> <title>Windows 7</title> <para> When attemping to set up a web folder through <guilabel>Add a Network Location</guilabel> or <guilabel>Map a Network Drive</guilabel> through <guilabel>My Computer</guilabel>, an error message stating <guilabel>The folder you entered does not appear to be valid. Please choose another</guilabel> or <guilabel>Windows cannot access … Check the spelling of the name. Otherwise, there might be …</guilabel> may be encountered. These errors may appear when you are using SSL or non-SSL. - </para> + </para> + </formalpara> <para> To fix this, do as follows: </para> @@ -440,32 +360,32 @@ </para> </listitem> </orderedlist> - </section> - <section id="sect-Reference_Guide-Restrictions-Microsoft_Office_2010"> + <formalpara> <title>Microsoft Office 2010</title> <para> If you have: </para> + </formalpara> <itemizedlist> <listitem> <para> - Microsoft Office 2007/2010 applications installed on a client computer and... + Microsoft Office 2007/2010 applications installed on a client computer AND... </para> </listitem> <listitem> <para> - The client computer is connected to a web server configured for Basic authentication via... + The client computer is connected to a web server configured for Basic authentication VIA... </para> </listitem> <listitem> <para> - A connection that does not use Secure Sockets Layer (SSL) and... + A connection that does not use Secure Sockets Layer (SSL) AND... </para> </listitem> <listitem> <para> - You try to access an Office file that is stored on the remote server. + You try to access an Office file that is stored on the remote server... </para> </listitem> <listitem> @@ -501,7 +421,7 @@ <orderedlist> <listitem> <para> - Click Start, type regedit in the Start Search box, and then press Enter. + Click Start, type <literal>regedit</literal> in the Start Search box, and then press Enter. </para> </listitem> @@ -510,31 +430,31 @@ Locate and then click the following registry subkey: </para> <para> - HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\Internet + <envar>HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\Internet</envar> </para> </listitem> <listitem> <para> - On the Edit menu, point to New, and then click DWORD Value. + On the <guilabel>Edit</guilabel> menu, point to <guilabel>New</guilabel>, and then click <guilabel>DWORD Value</guilabel>. </para> </listitem> <listitem> <para> - Type BasicAuthLevel, and then press Enter. + Type <literal>BasicAuthLevel</literal>, and then press <keycap>Enter</keycap>. </para> </listitem> <listitem> <para> - Right-click BasicAuthLevel, and then click Modify. + Right-click <literal>BasicAuthLevel</literal>, and then click <guilabel>Modify</guilabel>. </para> </listitem> <listitem> <para> - In the Value data box, type 2, and then click OK. + In the Value data box, type <literal>2</literal>, and then click <guilabel>OK</guilabel>. </para> </listitem> @@ -542,10 +462,5 @@ </orderedlist> </section> - - </section> - -</section> - - +</section> \ No newline at end of file Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/kernel.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/kernel.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/kernel.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -11,19 +11,19 @@    - <xi:include href="kernel/services-wiring.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="kernel/component-plugin-priority.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="kernel/understanding-listnerservice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="kernel/initialcontext-binder-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="kernel/job-scheduler-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="kernel/cache.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="kernel/transaction-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="kernel/data-source-provider.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="kernel/jndi-naming.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="kernel/logging.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="kernel/manageability.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="kernel/listener-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="kernel/rpc-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> +  +  +  +  +  +  +  +  +  +  +  +  +  </section> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -4,7 +4,7 @@ %BOOK_ENTITIES; ]> <chapter id="chap-Reference_Guide-eXo_JCR"> - <title>eXo JCR</title> + <title><remark>eXo JCR</remark></title> <xi:include href="eXoJCR/jcr.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />   Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/AuthenticationAndIdentity/SSO.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-10-10 01:24:38 UTC (rev 7692) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-10-10 01:25:25 UTC (rev 7693) @@ -4,7 +4,7 @@ %BOOK_ENTITIES; ]> <section id="sect-Reference_Guide-SSO_Single_Sign_On"> - <title>SSO - Single Sign On</title> + <title><remark>SSO - Single Sign On</remark></title> <section id="sect-Reference_Guide-SSO_Single_Sign_On-Overview"> <title>Overview</title> <para> @@ -548,12 +548,13 @@ <para> Tomcat should start without issue and should be accessible at <ulink type="http" url="http://localhost:8888/cas">http://localhost:8888/cas</ulink>. </para> +  <mediaobject> <imageobject> <imagedata fileref="images/AuthenticationAndIdentity/SSO/cas.png" format="PNG" scale="100" width="444" /> @@ -562,9 +563,23 @@ </mediaobject> </step> - </procedure> - +  + <note> + <remark>Added in gatein commit r7620</remark> + <para> + By default on logout the CAS server will display the CAS logout page with a link to return to the portal. To make the CAS server redirect to the portal page after a logout, modify the + <filename>cas.war/WEB-INF/cas-servlet.xml</filename> to include the follow line : + </para> +<programlisting> +<bean id="logoutController" class="org.jasig.cas.web.LogoutController" + p:centralAuthenticationService-ref="centralAuthenticationService" + p:logoutView="casLogoutView" + p:warnCookieGenerator-ref="warnCookieGenerator" + p:ticketGrantingTicketCookieGenerator-ref="ticketGrantingTicketCookieGenerator" + p:followServiceRedirects="true"/> +</programlisting> + </note> <procedure id="proc-Reference_Guide-CAS_Central_Authentication_Service-Setup_the_CAS_client"> <title>Setup the CAS client</title> <step> @@ -645,15 +660,15 @@ <para> Add the following Filters at the top of the filter chain in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename>: </para> - +<remark>DOC NOTE: Please check code sample as updated according to gatein r7620</remark> <programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default109.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> </step> <step> - <para> - Replace the <literal>InitiateLoginServlet</literal> declaration in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename> with: - </para> - + <remark> This step removed in gatein r7620. Should it be removed here?</remark> + <para> + Replace the <literal>InitiateLoginServlet</literal> declaration in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename> with: + </para> <programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default110.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> </step> @@ -841,11 +856,12 @@ <para> Add the following Filters to the top of the filter chain in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename>: </para> - +<remark>DOC NOTE: Please check code sample as updated according to gatein r7647</remark> <programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default115.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> </step> <step> + <remark> This step removed in gatein r7647. Should it be removed here?</remark> <para> Replace the <literal>InitiateLoginServlet</literal> declaration in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename> with: </para> @@ -880,17 +896,15 @@ <title>Obtaining OpenSSO</title> <step> <para> - Download OpenSSO from <ulink type="http" url="https://opensso.dev.java.net/public/use/index.html">https://opensso.dev.java.net/public/use/index.html</ulink>. + OpenSSO must be purchased from Oracle. </para> </step> - <step> +  </procedure> <para> @@ -1194,11 +1208,12 @@ <para> Add the following Filters to the top of the filter chain in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename>: </para> - +<remark>DOC NOTE: Please check code sample as updated according to gatein r7620</remark> <programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default122.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> </step> <step> + <remark> This step removed in gatein r7647. Should it be removed here?</remark> <para> Replace the <literal>InitiateLoginServlet</literal> declaration in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename> with: </para>

13 years, 3 months

1
0
0 / 0

gatein SVN: r7692 - in epp/docs/branches/5.2/Reference_Guide/en-US: extras/Authentication_Identity_SSO and 5 other directories.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-10-09 21:24:38 -0400 (Sun, 09 Oct 2011) New Revision: 7692 Modified: epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_SSO/default109.xml epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_SSO/default115.xml epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_SSO/default122.xml epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_SSO/default128.xml epp/docs/branches/5.2/Reference_Guide/en-US/images/Advanced/Foundations/PortalContainers.png epp/docs/branches/5.2/Reference_Guide/en-US/images/PortalDevelopment/Skinning/leftMarginPattern.png epp/docs/branches/5.2/Reference_Guide/en-US/images/PortletDevelopment/Standard/SpecPortalDef.png epp/docs/branches/5.2/Reference_Guide/en-US/images/PortletDevelopment/Standard/jsp_portlet/process.png epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml Log: Edits to new JCR1.14 content and updated images Modified: epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml 2011-10-10 01:23:11 UTC (rev 7691) +++ epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml 2011-10-10 01:24:38 UTC (rev 7692) @@ -9,7 +9,7 @@ <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> <edition>5.2.0</edition> - <pubsnumber>5</pubsnumber> + <pubsnumber>6</pubsnumber> <abstract> <para> This Reference Guide is a high-level usage document. It deals with more advanced topics than the Installation and User Guides, adding new content or taking concepts discussed in the earlier documents further. It aims to provide supporting documentation for advanced users of the JBoss Enterprise Portal Platform product. Its primary focus is on advanced use of the product and it assumes an intermediate or advanced knowledge of the technology and terms. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml 2011-10-10 01:23:11 UTC (rev 7691) +++ epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml 2011-10-10 01:24:38 UTC (rev 7692) @@ -8,6 +8,20 @@ <simpara> <revhistory> <revision> + <revnumber>5.2.0-6</revnumber> + <date>Wed Oct 5 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>Updated SSO section with changes from GateIn r7620 and r7647.</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>5.2.0-5</revnumber> <date>Wed Sep 14 2011</date> <author> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_SSO/default109.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_SSO/default109.xml 2011-10-10 01:23:11 UTC (rev 7691) +++ epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_SSO/default109.xml 2011-10-10 01:24:38 UTC (rev 7692) @@ -1,30 +1,58 @@ <filter> - <filter-name>LoginRedirectFilter</filter-name> - <filter-class>org.gatein.sso.agent.filter.LoginRedirectFilter</filter-class> - <init-param> -  - <param-name>LOGIN_URL</param-name> -  - <param-value>http://localhost:8888/cas/login?service=http://localhost:8080/portal/priv...</param-value> -  -  - </init-param> - </filter> - <filter> - <filter-name>CASLogoutFilter</filter-name> - <filter-class>org.gatein.sso.agent.filter.CASLogoutFilter</filter-class> - <init-param> -  - <param-name>LOGOUT_URL</param-name> - <param-value>http://localhost:8888/cas/logout</param-value> - </init-param> - </filter> -  - <filter-mapping> - <filter-name>LoginRedirectFilter</filter-name> - <url-pattern>/*</url-pattern> - </filter-mapping> - <filter-mapping> - <filter-name>CASLogoutFilter</filter-name> - <url-pattern>/*</url-pattern> - </filter-mapping> \ No newline at end of file + <filter-name>LoginRedirectFilter</filter-name> + <filter-class>org.gatein.sso.agent.filter.LoginRedirectFilter</filter-class> + <init-param> +  + <param-name>LOGIN_URL</param-name> +  + <param-value>http://localhost:8888/cas/login?service= + http://localhost:8080/portal/initiatessologin</param-value> +  +  + </init-param> + </filter> + <filter> + <filter-name>CASLogoutFilter</filter-name> + <filter-class>org.gatein.sso.agent.filter.CASLogoutFilter</filter-class> + <init-param> +  + <param-name>LOGOUT_URL</param-name> + <param-value>http://localhost:8888/cas/logout</param-value> + </init-param> + </filter> + <filter> + <filter-name>InitiateLoginFilter</filter-name> + <filter-class>org.gatein.sso.agent.filter.InitiateLoginFilter</filter-class> + <init-param> + <param-name>ssoServerUrl</param-name> + <param-value>http://localhost:8888/cas</param-value> + </init-param> + <init-param> + <param-name>casRenewTicket</param-name> + <param-value>false</param-value> + </init-param> + <init-param> + <param-name>casServiceUrl</param-name> + <param-value>http://localhost:8080/portal/initiatessologin</param-value> + </init-param> + <init-param> + <param-name>loginUrl</param-name> + <param-value>http://localhost:8080/portal/dologin</param-value> + </init-param> + </filter> + +  + <filter-mapping> + <filter-name>LoginRedirectFilter</filter-name> + <url-pattern>/*</url-pattern> + </filter-mapping> + <filter-mapping> + <filter-name>CASLogoutFilter</filter-name> + <url-pattern>/*</url-pattern> + </filter-mapping> + <filter-mapping> + <filter-name>InitiateLoginFilter</filter-name> + <url-pattern>/initiatessologin</url-pattern> + </filter-mapping> \ No newline at end of file Modified: epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_SSO/default115.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_SSO/default115.xml 2011-10-10 01:23:11 UTC (rev 7691) +++ epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_SSO/default115.xml 2011-10-10 01:24:38 UTC (rev 7692) @@ -1,27 +1,44 @@ <filter> - <filter-name>LoginRedirectFilter</filter-name> - <filter-class>org.gatein.sso.agent.filter.LoginRedirectFilter</filter-class> - <init-param> -  - <param-name>LOGIN_URL</param-name> - <param-value>http://localhost:8888/josso/signon/login.do?josso_back_to=http://localhos...</param-value> - </init-param> + <filter-name>LoginRedirectFilter</filter-name> + <filter-class>org.gatein.sso.agent.filter.LoginRedirectFilter</filter-class> + <init-param> +  + <param-name>LOGIN_URL</param-name> + <param-value>http://localhost:8888/josso/signon/login.do? + josso_back_to=http://localhost:8080/portal/initiatessologin</param-value> + </init-param> </filter> <filter> - <filter-name>JOSSOLogoutFilter</filter-name> - <filter-class>org.gatein.sso.agent.filter.JOSSOLogoutFilter</filter-class> - <init-param> -  - <param-name>LOGOUT_URL</param-name> - <param-value>http://localhost:8888/josso/signon/logout.do</param-value> - </init-param> + <filter-name>JOSSOLogoutFilter</filter-name> + <filter-class>org.gatein.sso.agent.filter.JOSSOLogoutFilter</filter-class> + <init-param> +  + <param-name>LOGOUT_URL</param-name> + <param-value>http://localhost:8888/josso/signon/logout.do</param-value> + </init-param> </filter> + <filter> + <filter-name>InitiateLoginFilter</filter-name> + <filter-class>org.gatein.sso.agent.filter.InitiateLoginFilter</filter-class> + <init-param> + <param-name>ssoServerUrl</param-name> + <param-value>http://localhost:8888/josso/signon/login.do</param-value> + </init-param> + <init-param> + <param-name>loginUrl</param-name> + <param-value>http://localhost:8080/portal/dologin</param-value> + </init-param> + </filter>  <filter-mapping> - <filter-name>LoginRedirectFilter</filter-name> - <url-pattern>/*</url-pattern> + <filter-name>LoginRedirectFilter</filter-name> + <url-pattern>/*</url-pattern> </filter-mapping> <filter-mapping> - <filter-name>JOSSOLogoutFilter</filter-name> - <url-pattern>/*</url-pattern> + <filter-name>JOSSOLogoutFilter</filter-name> + <url-pattern>/*</url-pattern> + </filter-mapping> + <filter-mapping> + <filter-name>InitiateLoginFilter</filter-name> + <url-pattern>/initiatessologin</url-pattern> </filter-mapping> \ No newline at end of file Modified: epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_SSO/default122.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_SSO/default122.xml 2011-10-10 01:23:11 UTC (rev 7691) +++ epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_SSO/default122.xml 2011-10-10 01:24:38 UTC (rev 7692) @@ -1,27 +1,49 @@ <filter> <filter-name>LoginRedirectFilter</filter-name> <filter-class>org.gatein.sso.agent.filter.LoginRedirectFilter</filter-class> - <init-param> -  - <param-name>LOGIN_URL</param-name> - <param-value>http://localhost:8888/opensso/UI/Login?realm=gatein&amp;goto=http://l...</param-value> - </init-param> + <init-param> +  + <param-name>LOGIN_URL</param-name> + <param-value>http://localhost:8888/opensso/UI/Login? + realm=gatein&goto=http://localhost:8080/portal/initiatessologin</param-value> + </init-param> </filter> - <filter> - <filter-name>OpenSSOLogoutFilter</filter-name> - <filter-class>org.gatein.sso.agent.filter.OpenSSOLogoutFilter</filter-class> - <init-param> -  - <param-name>LOGOUT_URL</param-name> - <param-value>http://localhost:8888/opensso/UI/Logout</param-value> - </init-param> - </filter> + <filter> + <filter-name>OpenSSOLogoutFilter</filter-name> + <filter-class>org.gatein.sso.agent.filter.OpenSSOLogoutFilter</filter-class> + <init-param> +  + <param-name>LOGOUT_URL</param-name> + <param-value>http://localhost:8888/opensso/UI/Logout</param-value> + </init-param> + </filter> + <filter> + <filter-name>InitiateLoginFilter</filter-name> + <filter-class>org.gatein.sso.agent.filter.InitiateLoginFilter</filter-class> + <init-param> + <param-name>ssoServerUrl</param-name> + <param-value>hhttp://localhost:8888/opensso</param-value> + </init-param> + <init-param> + <param-name>loginUrl</param-name> + <param-value>http://localhost:8080/portal/dologin</param-value> + </init-param> + <init-param> + <param-name>ssoCookieName</param-name> + <param-value>iPlanetDirectoryPro</param-value> + </init-param> + </filter> +  <filter-mapping> - <filter-name>LoginRedirectFilter</filter-name> - <url-pattern>/*</url-pattern> + <filter-name>LoginRedirectFilter</filter-name> + <url-pattern>/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>OpenSSOLogoutFilter</filter-name> <url-pattern>/*</url-pattern> + </filter-mapping> + <filter-mapping> + <filter-name>InitiateLoginFilter</filter-name> + <url-pattern>/initiatessologin</url-pattern> </filter-mapping> \ No newline at end of file Modified: epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_SSO/default128.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_SSO/default128.xml 2011-10-10 01:23:11 UTC (rev 7691) +++ epp/docs/branches/5.2/Reference_Guide/en-US/extras/Authentication_Identity_SSO/default128.xml 2011-10-10 01:24:38 UTC (rev 7692) @@ -1,20 +1,13 @@ - <filter> - <filter-name>LoginRedirectFilter</filter-name> - <filter-class>org.gatein.sso.agent.filter.LoginRedirectFilter</filter-class> - <init-param> -  - <param-name>LOGIN_URL</param-name> - <param-value>/portal/private/classic</param-value> - </filter> - <filter> - <filter-name>SPNEGOFilter</filter-name> - <filter-class>org.gatein.sso.agent.filter.SPNEGOFilter</filter-class> - </filter> - <filter-mapping> - <filter-name>LoginRedirectFilter</filter-name> - <url-pattern>/*</url-pattern> - </filter-mapping> - <filter-mapping> - <filter-name>SPNEGOFilter</filter-name> - <url-pattern>/*</url-pattern> - </filter-mapping> \ No newline at end of file +<filter> + <filter-name>LoginRedirectFilter</filter-name> + <filter-class>org.gatein.sso.agent.filter.LoginRedirectFilter</filter-class> + <init-param> +  + <param-name>LOGIN_URL</param-name> + <param-value>/portal/private/classic</param-value> + </init-param> +</filter> +<filter-mapping> + <filter-name>LoginRedirectFilter</filter-name> + <url-pattern>/*</url-pattern> +</filter-mapping> \ No newline at end of file Modified: epp/docs/branches/5.2/Reference_Guide/en-US/images/Advanced/Foundations/PortalContainers.png =================================================================== (Binary files differ) Modified: epp/docs/branches/5.2/Reference_Guide/en-US/images/PortalDevelopment/Skinning/leftMarginPattern.png =================================================================== (Binary files differ) Modified: epp/docs/branches/5.2/Reference_Guide/en-US/images/PortletDevelopment/Standard/SpecPortalDef.png =================================================================== (Binary files differ) Modified: epp/docs/branches/5.2/Reference_Guide/en-US/images/PortletDevelopment/Standard/jsp_portlet/process.png =================================================================== (Binary files differ) Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-10-10 01:23:11 UTC (rev 7691) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-10-10 01:24:38 UTC (rev 7692) @@ -4,7 +4,7 @@ %BOOK_ENTITIES; ]> <section id="sect-Reference_Guide-SSO_Single_Sign_On"> - <title>SSO - Single Sign On</title> + <title><remark>SSO - Single Sign On</remark></title> <section id="sect-Reference_Guide-SSO_Single_Sign_On-Overview"> <title>Overview</title> <para> @@ -461,18 +461,38 @@ <para> Tomcat should start without issue and should be accessible at <ulink type="http" url="http://localhost:8888/cas">http://localhost:8888/cas</ulink>. </para> - <note> +  + <mediaobject> <imageobject> <imagedata fileref="images/AuthenticationAndIdentity/SSO/cas.png" format="PNG" scale="100" width="444" /> </imageobject> + </mediaobject> + </step> </procedure> +  + <note> + <remark>Added in gatein commit r7620</remark> + <para> + By default on logout the CAS server will display the CAS logout page with a link to return to the portal. To make the CAS server redirect to the portal page after a logout, modify the + <filename>cas.war/WEB-INF/cas-servlet.xml</filename> to include the follow line : + </para> +<programlisting> +<bean id="logoutController" class="org.jasig.cas.web.LogoutController" + p:centralAuthenticationService-ref="centralAuthenticationService" + p:logoutView="casLogoutView" + p:warnCookieGenerator-ref="warnCookieGenerator" + p:ticketGrantingTicketCookieGenerator-ref="ticketGrantingTicketCookieGenerator" + p:followServiceRedirects="true"/> +</programlisting> + </note> <procedure id="proc-Reference_Guide-CAS_Central_Authentication_Service-Setup_the_CAS_client"> <title>Setup the CAS client</title> @@ -543,15 +563,16 @@ <para> Add the following Filters at the top of the filter chain in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename>: </para> - +<remark>DOC NOTE: Please check code sample as updated according to gatein r7620</remark> <programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default109.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> </step> <step> - <para> - Replace the <literal>InitiateLoginServlet</literal> declaration in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename> with: - </para> - + <remark> This step removed in gatein r7620. Should it be removed here?</remark> + <para> + Replace the <literal>InitiateLoginServlet</literal> declaration in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename> with: + </para> <programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default110.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + </step> </procedure> @@ -709,10 +730,11 @@ <para> Add the following Filters to the top of the filter chain in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename>: </para> - +<remark>DOC NOTE: Please check code sample as updated according to gatein r7647</remark> <programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default115.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> </step> <step> + <remark> This step removed in gatein r7647. Should it be removed here?</remark> <para> Replace the <literal>InitiateLoginServlet</literal> declaration in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename> with: </para> @@ -742,16 +764,17 @@ </para> <procedure id="proc-Reference_Guide-OpenSSO_The_Open_Web_SSO_project-Obtaining_OpenSSO"> <title>Obtaining OpenSSO</title> - <step> + <step> <para> - Download OpenSSO from <ulink type="http" url="https://opensso.dev.java.net/public/use/index.html">https://opensso.dev.java.net/public/use/index.html</ulink>. + OpenSSO must be purchased from Oracle. </para> + </step> - <step> +  </procedure> <para> @@ -1009,10 +1032,11 @@ <para> Add the following Filters to the top of the filter chain in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename>: </para> - +<remark>DOC NOTE: Please check code sample as updated according to gatein r7620</remark> <programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default122.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> </step> <step> + <remark> This step removed in gatein r7647. Should it be removed here?</remark> <para> Replace the <literal>InitiateLoginServlet</literal> declaration in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename> with: </para>

13 years, 3 months

1
0
0 / 0

gatein SVN: r7691 - epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-10-09 21:23:11 -0400 (Sun, 09 Oct 2011) New Revision: 7691 Added: epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Create_A_Site.xml Log: Added in-progress conversion of Create-a-site (with ecmdemo) content Added: epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Create_A_Site.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Create_A_Site.xml (rev 0) +++ epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Create_A_Site.xml 2011-10-10 01:23:11 UTC (rev 7691) @@ -0,0 +1,1272 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!ENTITY % BOOK_ENTITIES SYSTEM "Site_Publisher_Installation_Guide.ent"> +%BOOK_ENTITIES; +]> +<chapter id="chap-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo"> + <title>Create a Site Using The Demo</title> + <para> + It is possible to use the source files of the <literal>ecmdemo</literal> example site as a basis for a new site within your portal deployment. + </para> + <para> + <remark>Does it have to be the sources that get modified to do this? Can the changes be made in the <filename>ecmdemo</filename>.ear that is part of the SP download?</remark> + + </para> + <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Pre_requisites"> + <title>Pre-requisites</title> + <para> + In order to use the demonstration portal to create a new site, you will need the following tools: + </para> + <itemizedlist> + <listitem> + <para> + The <application>Subversion</application> version management tool. + </para> + + </listitem> + <listitem> + <para> + The <application>Maven</application> build tool. + </para> + + </listitem> + <listitem> + <para> + A subscription to JBoss Enterprise Portal Platform Site Publisher and the <filename>jboss-eppsp-<version>-exo-<version>-GA.zip</filename> package available from the JBoss Customer Service Portal. + </para> + + </listitem> + + </itemizedlist> + + </section> + + <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Get_Started"> + <title>Get Started</title> + <procedure> + <title></title> + <step id="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Execution-Get_Started-step_1"> + <title>Get the sources</title> + <para> + Obtain the <literal>ecmdemo</literal> source files with the following command: + </para> + +<programlisting>svn export http://svn.exoplatform.org/projects/ecms/tags/2.1.4/packaging/ecmdemo/ EXT_NAME</programlisting> + <para> + (In this instance, and throughout the rest of this guide, EXT_NAME will be used to denote the name of your new site.) + </para> + <note> + <title>SVN Export</title> + <para> + Using the <command>svn export</command> command allows you to check out the source files without creating a local working copy of the repository. + </para> + + </note> + + </step> + + </procedure> + + + </section> + + <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Customize_the_extension"> + <title>Customize the extension</title> + <para> + The <literal>ecmdemo</literal> project uses the extension mechanism to create a new portal container. This portal container is separate from the default deployment; it uses its own IDM implementation, JCR datasources and URL context. All services required by the new site area configured independently, meaning the default portal instance in not affected in any way. + </para> + <para> + The <literal>ecmdemo</literal> portal container includes two portals; <emphasis role="bold">Classic</emphasis> and <emphasis role="bold">Acme</emphasis>. The <emphasis role="bold">Classic</emphasis> portal is a presentation of the JBoss Enterprise Portal Platform product while the <emphasis role="bold">Acme</emphasis> site serves as a demonstration of Site Publisher's features. + </para> + <para> + The following procedures will guide you through renaming the extension to whatever you intend to call your new portal. + </para> + <procedure id="proc-Site_Publisher_Installation_Guide-Customize_the_extension-Renaming_In_POM_Files"> + <title>Renaming In POM Files</title> + <step id="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_1"> + <para> + Files to be modified in this section: + </para> + <programlistingco> + <areaspec> + <area coords="1 20" id="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-EXT_NAME" /> + <area coords="2 20" id="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-pom" /> + <area coords="3 20" id="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-config" /> + <area coords="5 20" id="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-webapp" /> + <area coords="7 20" id="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-rest" /> + <area coords="9 20" id="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-ear" /> + + </areaspec> + +<programlisting><replaceable>EXT_NAME</replaceable> +├── pom.xml +├── config +│ └── pom.xml +├── webapp +│ └── pom.xml +├── rest-webapp +│ └── pom.xml +└── ear + └── pom.xml +</programlisting> + <calloutlist> + <callout arearefs="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-EXT_NAME"> + <para> + The parent project. + </para> + + </callout> + <callout arearefs="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-pom"> + <para> + The extension's <filename>pom</filename> file. + </para> + <para> + Refer to <xref linkend="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_2" /> for information on how to edit the <filename>pom.xml</filename>. + </para> + + </callout> + <callout arearefs="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-config"> + <para> + The configuration JAR. <remark>This is a normal directory in my copy (not a JAR)</remark> + + </para> + <para> + Refer to <xref linkend="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_3" /> for information on how to edit the <filename>pom.xml</filename>. + </para> + + </callout> + <callout arearefs="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-webapp"> + <para> + The configuration WAR. <remark>This is a normal directory in my copy (not a WAR)</remark> + + </para> + <para> + Refer to <xref linkend="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_4" /> for information on how to edit the <filename>pom.xml</filename>. + </para> + + </callout> + <callout arearefs="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-rest"> + <para> + The REST configuration WAR. <remark>This is a normal directory in my copy (not a WAR)</remark> + + </para> + <para> + Refer to <xref linkend="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_5" /> for information on how to edit the <filename>pom.xml</filename>. + </para> + + </callout> + <callout arearefs="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-ear"> + <para> + The deployable EAR archive. <remark>This is a normal directory in my copy (not an EAR)</remark> + + </para> + <para> + Refer to <xref linkend="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_6" /> for information on how to edit the <filename>pom.xml</filename>. + </para> + + </callout> + + </calloutlist> + + </programlistingco> + + + </step> + <step id="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_2"> + <para> + Remove references to the original project from the extension's <filename>pom.xml</filename> file. + </para> + +<programlisting language="XML" role="XML">... + <groupId>org.myorg</groupId> + <artifactId>EXT_NAME</artifactId> + <version>1.0.0</version> + <packaging>pom</packaging> + <name>EXT NAME</name> + <description/> +...</programlisting> + + </step> + <step id="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_3"> + <para> + Remove references to the original project from the <filename>config/pom.xml</filename> file. + </para> + +<programlisting language="XML" role="XML">... + <parent> + <groupId>org.myorg</groupId> + <artifactId>EXT_NAME</artifactId> + <version>1.0.0</version> + </parent> + <artifactId>EXT_NAME-config</artifactId> + <name>EXT NAME configuration jar</name> +...</programlisting> + <para> + (You may also remove the <literal>src/main/java</literal> resource folder definition because the <literal>EXT_NAME-config</literal> project only contains one configuration file which is located in the <filename>src/main/resources</filename> folder.) + </para> + + </step> + <step id="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_4"> + <para> + Remove references to the original project from the <filename>webapp/pom.xml</filename> file. + </para> + +<programlisting language="XML" role="XML">... + <parent> + <groupId>org.myorg</groupId> + <artifactId>EXT_NAME</artifactId> + <version>1.0.0</version> + </parent> + <artifactId>EXT_NAME-webapp</artifactId> + <packaging>war</packaging> + <name>EXT_NAME configuration war</name> + ...</programlisting> + + </step> + <step id="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_5"> + <para> + Remove references to the original project from the <filename>rest-webapp/pom.xml</filename> file. + </para> + +<programlisting language="XML" role="XML">... +<parent> + <groupId>org.myorg</groupId> + <artifactId>EXT_NAME</artifactId> + <version>1.0.0</version> +</parent> +<artifactId>EXT_NAME-rest-webapp</artifactId> +<packaging>war</packaging> +<name>EXT NAME Portal REST war</name> +...</programlisting> + <para> + Remove or comment-out the <parameter>finalName</parameter> tag from the build definition. + </para> + + </step> + <step id="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_6"> + <para> + Remove references to the original project from the <filename>ear/pom.xml</filename> file. + </para> + +<programlisting language="XML" role="XML">... +<parent> + <groupId>org.myorg</groupId> + <artifactId>EXT_NAME</artifactId> + <version>1.0.0</version> +</parent> +<artifactId>EXT_NAME-ear</artifactId> +<packaging>ear</packaging> +<name>EXT_NAME EAR for GateIn</name> +...</programlisting> + <para> + Rename the <parameter>dependencies</parameter> to match the renamed projects. + </para> + +<programlisting language="XML" role="XML">... +<dependencies> +<dependency> + <groupId>org.myorg</groupId> + <artifactId>EXT_NAME-config</artifactId> + <version>${project.version}</version> +</dependency> +...</programlisting> + <para> + Rename the artifacts in <parameter>maven-ear-plugin</parameter> configuration. + </para> + +<programlisting language="XML" role="XML">... +<configuration> + <displayName>EXT_NAME</displayName> + <defaultLibBundleDir>lib</defaultLibBundleDir> + <modules> + <jarModule> + <groupId>org.myorg</groupId> + <artifactId>EXT_NAME-config</artifactId> + <includeInApplicationXml>true</includeInApplicationXml> + </jarModule> + <webModule> + <groupId>org.myorg</groupId> + <artifactId>EXT_NAME-webapp</artifactId> + <contextRoot>EXT_NAME</contextRoot> + <bundleFileName>EXT_NAME.war</bundleFileName> + </webModule> + <webModule> + <groupId>org.myorg</groupId> + <artifactId>EXT_NAME-rest-webapp</artifactId> + <contextRoot>rest-EXT_NAME</contextRoot> + <bundleFileName>rest-EXT_NAME.war</bundleFileName> + </webModule> + </modules> +</configuration> +... +</programlisting> + <para> + Add the <parameter>finalName</parameter> tag to the build element so the result EAR will be <filename>EXT_NAME.ear</filename>. + </para> + +<programlisting language="XML" role="XML">... +<build> + <finalName>EXT_NAME</finalName> + ...</programlisting> + + </step> + + </procedure> + + + </section> + + <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Renaming_Configuration_Files"> + <title>Renaming Configuration Files</title> + <para> + The <literal>ecmdemo</literal> string is present in the following configuration files within the project: + </para> + +<screen>EXT_NAME/ +├── pom.xml +├── config +│ └── src +│ └── main +│ └── resources +│ └── conf +│ └── configuration.xml +├── webapp +│ └── src +│ └── main +│ └── webapp +│ └── WEB-INF +│ ├── conf +│ │ └── sample-portal +│ │ ├── portal +│ │ │ └── portal +│ │ │ └── acme +│ │ │ └── pages.xml +│ │ └── wcm +│ │ ├── artifacts +│ │ │ └── site-resources +│ │ │ └── newsletter +│ │ │ └── newsletterBasicTemplate.xml +│ │ └── friendly-configuration.xml +│ ├── jboss-web.xml +│ └── web.xml +├── rest-webapp +│ └── src +│ └── main +│ └── webapp +│ └── WEB-INF +│ ├── jboss-web.xml +│ └── web.xml +└── ear + └── src + └── main + └── application + ├── ecmdemo.xml + └── META-INF + └── gatein-jboss-beans.xml +</screen> + <para> + To completely rename the extension project all occurences of the <literal>ecmdemo</literal> string must be replaced with your <replaceable>EXT_NAME</replaceable>. + </para> + <para> + Additionally, the <filename>ecmdemo.xml</filename> file must be renamed <filename><replaceable>EXT_NAME</replaceable>.xml</filename>. + </para> + + </section> + + <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Deploy_the_application"> + <title>Deploy the application</title> + <para> + After the project is completely renamed, you must build it and deploy it00 into JBoss Enterprise Portal Platform portal. + </para> + <procedure> + <step> + <para> + Build the application with the following commands: + </para> + <substeps> + <step> + <para> + <command>cd <replaceable>EXT_NAME</replaceable>/</command> + </para> + + </step> + <step> + <para> + <command>mvn clean install</command> + </para> + + </step> + + </substeps> + <para> + The above commands will create an <filename><replaceable>EXT_NAME</replaceable>.ear</filename> file in a new <filename>ear/target/</filename> directory. + </para> + + </step> + <step> + <para> + Copy the <filename><replaceable>EXT_NAME</replaceable>.ear</filename> to the <filename>deploy</filename> directory of your JBoss Enterprise Portal Platform profile: + </para> + +<programlisting><command>cp ear/target/<filename><replaceable>EXT_NAME</replaceable>.ear</filename> <replaceable>JBOSS_HOME</replaceable>/jboss-as/server/<<replaceable>PROFILE</replaceable>>/deploy/</command></programlisting> + + </step> + <step> + <para> + As the extension also creates a new portal container, a separate datasource config file must be deployed as well. + </para> + <substeps> + <step> + <para> + Copy the <filename>gatein-ds.xml</filename> file from the <filename>jboss-eppsp-<version>-exo-<version>-GA.zip</filename> distribution package. + </para> + + </step> + <step> + <para> + Edit the file to replace instances of the <emphasis>portal</emphasis> JNDI name with your <replaceable>EXT_NAME</replaceable>. + </para> + +<programlisting language="XML" role="XML"><datasources> +<no-tx-datasource> + <jndi-name>gatein-idm_spdemo</jndi-name> + <connection-url>jdbc:hsqldb:${jboss.server.data.dir}${/}gatein${/}hypersonic${/}gatein-idm_spdemo-localDB</connection-url> + ... +</programlisting> + <para> + + </para> + + </step> + + </substeps> + + </step> + <step> + <para> + Ensure you have also deployed at least the <filename>gatein-wcm-extension-<replaceable><version></replaceable>-GA.ear</filename> and <filename>gatein-ds.xml</filename> artifacts from the Site Publisher disribution package. + </para> + <para> + + </para> + <para> + Refer to the <emphasis role="bold">Installation</emphasis> chapter of the Site Publisher Installation Guide for more information about the other files in the distribution and their deployment. + </para> + + </step> + <step> + <para> + Start the server using the configuration profile you deployed your new portal to. + </para> + <itemizedlist> + <listitem> + <para> + For Linux (or other Unix-based) systems: + </para> + +<programlisting><command>sh <replaceable>JBOSS_HOME</replaceable>/jboss-as/bin/run.sh -c <replaceable>EXT_NAME</replaceable></command></programlisting> + + </listitem> + <listitem> + <para> + For Microsoft Windows systems: + </para> + +<programlisting><command><replaceable>JBOSS_HOME</replaceable>/jboss-as/bin/run.bat -c <replaceable>EXT_NAME</replaceable></command></programlisting> + + </listitem> + + </itemizedlist> + <para> + (The commands above assume that you have created a profile with the same name as the portal you are creating) + </para> + + </step> + <step> + <para> + Access the new portal at <ulink type="http" url="http://localhost:8080/EXT_NAME" /> + </para> + + </step> + + </procedure> + + <note> + <title>Portal Content</title> + <para> + At this point the new portal container will have the same content as the original <literal>ecmdemo</literal>. As a result, much of the web content (stylesheets, links, etc.) will still use the <ulink type="http" url="/ecmdemo" /> context and may not be displayed properly (unless the original site is deployed as well). + </para> + <para> + Also, as the the portals in <literal>ecmdemo</literal> use separate <literal>SingleContentViewer</literal> portlets to display the <guilabel>Login</guilabel>, <guilabel>Register</guilabel> and <guilabel>Language</guilabel> links and not the <literal>BannerPortlet</literal> (as they do in the default <ulink type="http" url="/portal" /> container URL context), the links will not work in your new portal context. + </para> + + </note> + + </section> + + <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Add_a_new_portalwebsite"> + <title>Add a new portal/website</title> + <para> + Within the <filename>webapp/WEB-INF/CONF</filename> directory is the main configuration entry point for the portal container; <filename>configuration.xml</filename>. This file imports all the required configurations from the <filename>sample-portal</filename> subdirectory. + </para> + +<screen>EXT_NAME/ +└── webapp + └── src + └── main + └── webapp + └── WEB-INF + └── conf + ├── configuration.xml + └── sample-portal + ├── portal + │ └── portal-configuration.xml + └── wcm + └── ... +</screen> + <para> + The <filename>configuration.xml</filename> file defines all the portals and websites in the portal container with the <literal>UserPortalConfigService</literal>. + </para> + <para> + To add a new portal/website to the container follow the steps below: + </para> + <procedure id="proc-Site_Publisher_Installation_Guide-Add_a_new_portalwebsite-Create_a_new_portal"> + <title>Create a new portal</title> + <step> + <para> + Register the new site in the <filename>portal-configuration.xml</filename> file: + </para> + <para> + In this example the new site will be called <emphasis role="bold">demo</emphasis>. + </para> + +<programlisting language="XML" role="XML"><object-param> + <name>portal.configuration</name> + <description>description</description> + <object type="org.exoplatform.portal.config.NewPortalConfig"> + <field name="predefinedOwner"> + <collection type="java.util.HashSet"> + <value> + <string>demo</string> + </value> + <value> + <string>classic</string> + </value> + <value> + <string>acme</string> + </value> + </collection> + </field> + ... +</object-param></programlisting> + + </step> + <step> + <para> + Set the <emphasis role="bold">demo</emphasis> portal as the default. JBoss Enterprise Portal Platform will then redirect to this portal when users access the <ulink type="http" url="EXT_NAME/" /> URL context. + </para> + +<programlisting language="XML" role="XML"><value-param> + <name>default.portal</name> + <description>The default portal for checking db is empty or not</description> + <value>demo</value> +</value-param></programlisting> + + </step> + <step> + <para> + Add the configuration of the portal layout, navigation and pages. These configurations are set in <filename>portal.xml</filename>, <filename>navigation.xml</filename> and <filename>pages.xml</filename>, respectively. + </para> + +<screen>EXT_NAME/ +└── webapp + └── src + └── main + └── webapp + └── WEB-INF + └── conf + └── sample-portal + └── portal + └── portal + ├── acme + │ ├── navigation.xml + │ ├── pages.xml + │ └── portal.xml + ├── classic + │ ├── navigation.xml + │ ├── pages.xml + │ └── portal.xml + └── template + └── acme + ├── navigation.xml + ├── pages.xml + └── portal.xml + +</screen> + + </step> + + </procedure> + + <para> + The most effective way to create a new portal configuration is to copy an existing portal configuration (from the <emphasis role="bold">Classic</emphasis> portal, for example) and modify it to create a new empty portal. + </para> + <para> + This process is explained in more detail in the next section. + </para> + + </section> + + <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Define_portal_layout"> + <title>Define portal layout</title> + <procedure id="proc-Site_Publisher_Installation_Guide-Define_portal_layout-Define_portal_layout"> + <title>Define portal layout</title> + <step> + <para> + Create folder <emphasis role="bold">demo</emphasis> in the <filename>sample-portal/portal/portal/</filename> directory and copy the <filename>portal.xml</filename> file from the <emphasis role="bold">classic</emphasis> configuration. + </para> + + </step> + <step> + <para> + Edit the <filename>portal.xml</filename> file and change the portal name in the <parameter>portal-name</parameter> element to <emphasis role="bold">demo</emphasis> then replace the contents of the <parameter>portal-layout</parameter> element with the following code: + </para> + +<programlisting language="XML" role="XML"><portal-layout> + + <portlet-application> + <portlet> + <application-ref>web</application-ref> + <portlet-ref>BannerPortlet</portlet-ref> + <preferences> + <preference> + <name>template</name> + <value>par:/groovy/groovy/webui/component/UIBannerPortlet.gtmpl</value> + <read-only>false</read-only> + </preference> + </preferences> + </portlet> + <access-permissions>Everyone</access-permissions> + <show-info-bar>false</show-info-bar> + </portlet-application> + + <portlet-application> + <portlet> + <application-ref>web</application-ref> + <portlet-ref>NavigationPortlet</portlet-ref> + </portlet> + <access-permissions>Everyone</access-permissions> + <show-info-bar>false</show-info-bar> + </portlet-application> + + <container id="MainColumn" template="system:/groovy/portal/webui/container/UITableColumnContainer.gtmpl"> + <container id="PageColumn" template="system:/groovy/portal/webui/container/UIContainer.gtmpl"> + <access-permissions>Everyone</access-permissions> + <page-body/> + </container> + <container id="SideColumn" template="system:/groovy/portal/webui/container/UIContainer.gtmpl"> + <access-permissions>Everyone</access-permissions> + </container> + </container> + + <portlet-application> + <portlet> + <application-ref>web</application-ref> + <portlet-ref>FooterPortlet</portlet-ref> + <preferences> + <preference> + <name>template</name> + <value>par:/groovy/groovy/webui/component/UIFooterPortlet.gtmpl</value> + <read-only>false</read-only> + </preference> + </preferences> + </portlet> + <access-permissions>Everyone</access-permissions> + <show-info-bar>false</show-info-bar> + </portlet-application> + +</portal-layout></programlisting> + <para> + This will create a layout that contains: + </para> + <variablelist> + <title></title> + <varlistentry> + <term>BannerPortlet</term> + <listitem> + <para> + The <literal>BannerPortlet</literal> is a default portlet which is used to display the website's banner and also the Login, Register and Language quick-links on the front page. + </para> + <para> + This portlet's stylesheet can be overridden and customized to better suit your website's design. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>NavigationPortlet</term> + <listitem> + <para> + The <literal>NavigationPortlet</literal> controls portal navigation. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>MainColumn</term> + <listitem> + <para> + The <literal>MainColumn</literal> container is generated by <filename>UITableColumnContainer.gtmpl</filename> template. + </para> + <para> + This template also contains: + </para> + <variablelist> + <title></title> + <varlistentry> + <term>PageColumn</term> + <listitem> + <para> + This container holds the <emphasis role="bold">page-body</emphasis> element. During runtime this element is replaced by the currently selected selected portal page. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>SideColumn</term> + <listitem> + <para> + This container displays the <guilabel>Searchbox</guilabel> and other content elements required on every portal page. + </para> + + </listitem> + + </varlistentry> + + </variablelist> + + </listitem> + + </varlistentry> + <varlistentry> + <term>FooterPortlet</term> + <listitem> + <para> + The <literal>FooterPortlet</literal> is a default JBoss Enterprise Portal Platform portlet. It can be replaced with a custom <literal>SingleContentViewer</literal> portlet. + </para> + + </listitem> + + </varlistentry> + + </variablelist> + + </step> + + </procedure> + + + </section> + + <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Define_portal_navigation_and_pages"> + <title>Define portal navigation and pages</title> + <para> + It is recommended that portal creators use the <filename>navigation.xml</filename> and <filename>pages.xml</filename> files from the <literal>Classic</literal> portal as templates. + </para> +<programlistingco> + <areaspec> + <area coords="21" id="area-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Define_portal_navigation_and_pages-nav" /> + <area coords="22" id="area-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Define_portal_navigation_and_pages-page" /> + </areaspec> +<programlisting>EXT_NAME/ +└── webapp + └── src + └── main + └── webapp + └── WEB-INF + └── conf + └── sample-portal + └── portal + ├── portal + │ ├── acme + │ ├── navigation.xml + │ ├── pages.xml + │ └── portal.xml + ├── classic + │ ├── navigation.xml + │ ├── pages.xml + │ └── portal.xml + └── template + └── acme + ├── navigation.xml + ├── pages.xml + └── portal.xml +</programlisting> + <calloutlist> +  + <callout arearefs="area-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Define_portal_navigation_and_pages-nav"> + <para> + Edit the <filename>navigation.xml</filename> file and customize the navigational structure of your website. + </para> + <itemizedlist> + <listitem> + <para> + Change page labels from <parameter>#{portal.classic.*}</parameter> to <parameter>#{portal.demo.*}</parameter> + </para> + <para> + The <parameter>#{...}</parameter> notation means the portal will look for a localized label rather than a hardcoded string. + </para> + </listitem> + <listitem> + <para> + Change all page references from <parameter>portal::classic::*</parameter> to <parameter>portal::demo::*</parameter>. + </para> + </listitem> + <listitem> + <para> + Add two new nodes: <literal>docs</literal> and <literal>news</literal>. Other nodes remain as they are. + </para> + </listitem> + </itemizedlist> +<programlisting language="XML" role="XML"><![CDATA[<node-navigation ...> + <priority>1</priority> + <page-nodes> + <node> + <uri>home</uri> + <name>home</name> + <label>#{portal.demo.home}</label> + <visibility>DISPLAYED</visibility> + <page-reference>portal::demo::homepage</page-reference> + </node> + <node> + <uri>docs</uri> + <name>docs</name> + <label>#{portal.demo.docs}</label> + <visibility>DISPLAYED</visibility> + <page-reference>portal::demo::docs</page-reference> + </node> + <node> + <uri>news</uri> + <name>news</name> + <label>#{portal.demo.news}</label> + <visibility>DISPLAYED</visibility> + <page-reference>portal::demo::news</page-reference> + </node> + <node> + ... + </node> + ... + </page-nodes> +</node-navigation>]]></programlisting> + </callout> +  + <callout arearefs="area-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Define_portal_navigation_and_pages-page"> + <para> + Edit the <filename>pages.xml</filename> file to customize the layout and content of particular pages. + </para> + <itemizedlist> + <listitem> + <para> + Remove the content configured for the classic website's homepage by deleting the container <parameter>ClassicBody</parameter> from the homepage definition in the page-set. + </para> + </listitem> + <listitem> + <para> + Add empty pages <literal>docs</literal> and <literal>news</literal>. Other nodes remain as they are. + </para> + </listitem> + </itemizedlist> + <programlisting language="XML" role="XML"><![CDATA[<page-set ...> + <page> + <name>homepage</name> + <title>Home Page</title> + <access-permissions>Everyone</access-permissions> + <edit-permission>*:/platform/administrators</edit-permission> + +  + + </page> + <page> + <name>docs</name> + <title>Documentation</title> + <access-permissions>Everyone</access-permissions> + <edit-permission>*:/platform/administrators</edit-permission> + + </page> + <page> + <name>news</name> + <title>News</title> + <access-permissions>Everyone</access-permissions> + <edit-permission>*:/platform/administrators</edit-permission> + + </page> + <page> ... </page> + ... + </page-set>]]></programlisting> + </callout> + </calloutlist> +</programlistingco> + + <para> + This will provide a working portal configuration for the new <replaceable>demo</replaceable> portal. It defines a simple portal layout and a basic navigation. The pages will be empty, however, until some webcontent is added to the portal's JCR repository. + </para> + <para> + Later chapters in this guide will discuss how to deploy content. + </para> + </section> + + <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Localize_the_navigation"> + <title>Localize the navigation</title> + <para> + To localize navigation nodes; + </para> + <procedure> + <step> + <para> + Browse to the <filename>classes/locale/navigation/portal/</filename> folder and create an XML file called <filename>demo_<replaceable><locale></replaceable>.xml</filename> (where <replaceable><locale></replaceable> is the desired localization, <filename>demo_en.xml</filename> for example). + </para> + </step> + <step> + <para> + Populate the file with: + </para> +<programlisting language="XML" role="XML"><![CDATA[<bundle> + <portal> + <demo> + <home>Home</home> + <news>News</news> + <docs>Documentation</docs> + ... + </demo> + </portal> +</bundle>]]></programlisting> + </step> + <step> + <para> + Register your localization in the <filename>conf/sample-portlet/portal/resource-bundle-configuration.xml</filename> file by adding the <parameter>locale.navigation.portal.demo</parameter> to the <parameter>init.resources</parameter> and <parameter>portal.resources.names</parameter> parameters. + </para> + </step> + </procedure> + </section> + + <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Deploy_custom_content"> + <title>Deploy custom content</title> + <para> + All content managed by Site Publisher is stored in the portal JCR repository. For more information, refer to the <emphasis role="bold">JCR</emphasis> chapter of the JBoss Enterprise Portal Platform Reference Guide at <ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...."></ulink>. + </para> + <para> + Each node can be exported from the repository into an XML file and imported back to an arbitrary location. The export/import functionality can be used via the <application>ContentExplorer portlet</application> which is an integral part of Site Publisher's User Interface. + </para> + <para> + The content can also be imported by the <application>WCMContentInitializerServices</application> which is used to initialize content for the websites in the <emphasis role="bold">ecmodemo</emphasis> project. + </para> + <para> + The <application>TaxonomyPlugin</application> can be used to deploy a custom taxonomy. + </para> + <para> + Site Publisher enables customization of website stylesheets. To customize the styles you can put the CSS files into the <filename>css</filename> directory of the appropriate website's JCR repository. + </para> + <section> + <title>Various web content</title> + <para> + Use the following files and locations in the following procedure to deploy web content: + </para> +<programlisting>EXT_NAME/ +└── webapp + ├── pom.xml + └── src + └── main + └── webapp + └── WEB-INF + └── conf + ├── configuration.xml + └── sample-portal + └── wcm + ├── artifacts + │ └── site-resources + │ └── demo + │ ├── Logo.xml + │ └── ... + └── deployment + └── demo-deployment-configuration.xml +</programlisting> + <procedure id="proc-Site_Publisher_Installation_Guide-Deploy_custom_content-Various_web_content"> + <title>Various web content</title> + <step> + <para> + Build and deploy your application, then start the server. Refer to <xref linkend="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Deploy_the_application"/> for information on how to do this. + </para> + </step> + <step> + <para> + Access the custom portal container at <ulink type="http" url="http://localhost:8080/EXT_NAME"></ulink>. + </para> + <itemizedlist> + <listitem> + <para> + The container will also contain the <replaceable>EXT_NAME</replaceable> portal project. + </para> + </listitem> + <listitem> + <para> + You will automatically be redirected to <ulink type="http" url="http://localhost:8080/EXT_NAME/public/demo"></ulink>. + </para> + </listitem> + </itemizedlist> + </step> + <step> + <para> + Create, edit or upload content items using the <application>ContentExplorer portlet</application>. + </para> + <itemizedlist> + <listitem> + <para> + The portlet can be accessed via <menuchoice><guimenu>Group</guimenu><guimenuitem>Content Explorer</guimenuitem></menuchoice>. + </para> + </listitem> + <listitem> + <para> + To add content to your portal repository, browse to Sites Management / demo + </para> + </listitem> + <listitem> + <para> + Previously exported content call also be imported via <menuchoice><guimenu>System</guimenu><guimenuitem>Import Node</guimenuitem></menuchoice>. + </para> + </listitem> + </itemizedlist> + </step> + <step> + <para> + Use the <application>ContentExplorer</application> portlet to export the content into XML files + </para> + <itemizedlist> + <listitem> + <para> + Browse to, and open, the the item you wish to export and use the <menuchoice><guimenu>System</guimenu><guimenuitem>Export Node</guimenuitem></menuchoice>. + </para> + </listitem> + <listitem> + <para> + Both singular items and whole directories can be exported. + </para> + </listitem> + <listitem> + <para> + Version history is not required in the export as the <application>WCMContentInitializerService</application> cannot import version information. + </para> + </listitem> + </itemizedlist> + </step> + <step> + <para> + Place the exported XML files into a <emphasis role="bold">demo</emphasis> directory in <filename>webapp/WEB-INF/conf/sample-portal/wcm/artifacts/site-resources/</filename> + </para> + </step> + <step> + <para> + Configure the <application>WCMContentInitializerService</application> to feploy the content to appropriate locations in the JCR. + </para> + <substeps> + <step> + <para> + Navigate to the <filename>/sample-portal/wcm/deployment/</filename> directory. + </para> + </step> + <step> + <para> + Create a configuration file called <filename>demo-deployment-configuration.xml</filename> by making a copy of the <filename>classic-deployment-configuration.xml</filename>. + </para> + </step> + <step> + <para> + Create an entry to import the <filename>demo-deployment-configuration.xml</filename> file in the main configuration <filename>WEB-INF/conf/configuration.xml</filename>file + </para> + </step> + <step> + <para> + Edit the <filename>demo-deployment-configuration.xml</filename> to configure <application>WCMContentInitializer</application> and <application>XMLDeploymentPlugin</application> to deploy your content items to particular locations in your new portal's JCR repository. + </para> + <para> + The <filename>demo-deployment-configuration.xml</filename> contains a configuration of the <application>XMLDeploymentPlugin</application> which has several <application>DeploymentDescriptor</application> object init-params. Each deployment descriptor represents a deployment of a single XML file to a particular JCR location. + </para> + <para> + The <application>DeploymentDescriptor</application> param has the following fields: + </para> + <itemizedlist> + <listitem> + <para> + The <parameter>target</parameter> determines the location in the JCR repository to which the content will be imported. + </para> + </listitem> + <listitem> + <para> + The <parameter>sourcePath</parameter> is the path to the XML file to import. In this case the file is in the application as per <emphasis role="bold">Step 5</emphasis> above. + </para> + </listitem> + <listitem> + <para> + The <parameter>cleanupPublication</parameter> parameter is used as a workaround for a known issue with webcontent that has <emphasis>Publication State</emphasis> data not being successfully imported. + </para> + </listitem> + </itemizedlist> + </step> + </substeps> +<programlisting language="XML" role="XML"><![CDATA[... +<external-component-plugins> + <target-component>org.exoplatform.services.deployment.WCMContentInitializerService</target-component> + <component-plugin> + ... + <type>org.exoplatform.services.deployment.plugins.XMLDeploymentPlugin</type> + <init-params> + <object-param> + <name>Logo</name> + ... + <object type="org.exoplatform.services.deployment.DeploymentDescriptor"> + <field name="target">  + <object type="org.exoplatform.services.deployment.DeploymentDescriptor$Target"> + <field name="repository"><string>repository</string></field> + <field name="workspace"><string>collaboration</string></field> + <field name="nodePath"><string>/sites content/live/demo/medias/images</string></field> + </object> + </field> + <field name="sourcePath"> + <string>war:/conf/sample-portal/wcm/artifacts/site-resources/demo/Logo.xml</string>  + </field> + <field name="cleanupPublication"> + <boolean>true</boolean> + </field> + </object> + </object-param> + <object-param> + ... + </object-param> + ...]]></programlisting> + </step> + <step> + <para> + Edit <filename>/sample-portal/wcm/deployment/template-deployment-configuration.xml</filename> file to disable deployment of template contents into the <emphasis role="bold">demo</emphasis> portal by adding value <literal>demo</literal> to the <parameter>ignored.portals</parameter> list: + </para> +<programlisting language="XML" role="XML"><![CDATA[<component> + <key>org.exoplatform.services.wcm.portal.artifacts.CreatePortalArtifactsService</key> + <type>org.exoplatform.services.wcm.portal.artifacts.CreatePortalArtifactsServiceImpl</type> + <init-params> + <values-param> + <name>ignored.portals</name> + <value>demo</value> + ...]]></programlisting> + </step> + </procedure> + </section> + </section> + + <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Taxonomies"> + <title>Taxonomies</title> + <para> + + </para> + <procedure> + <step> + <para> + + </para> + + </step> + + </procedure> + + + </section> + + <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Custom_website_stylesheet"> + <title>Custom website stylesheet</title> + <para> + + </para> + <procedure> + <step> + <para> + + </para> + + </step> + + </procedure> + + + </section> + + <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Searchbox_stylesheet"> + <title>Searchbox stylesheet</title> + <para> + + </para> + <procedure> + <step> + <para> + + </para> + + </step> + + </procedure> + + + </section> + + <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Configure_content_presentation_portlets"> + <title>Configure content presentation portlets</title> + <procedure id="proc-Site_Publisher_Installation_Guide-Configure_content_presentation_portlets-SingleContentViewer_portlet_preferences"> + <title>SingleContentViewer portlet preferences</title> + <step> + <para> + + </para> + + </step> + + </procedure> + + + </section> + + <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-ContentListViewer_portlet_preferences"> + <title>ContentListViewer portlet preferences</title> + <para> + + </para> + <procedure> + <step> + <para> + + </para> + + </step> + + </procedure> + + + </section> + + <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Other_configurations"> + <title>Other configurations</title> + <procedure id="proc-Site_Publisher_Installation_Guide-Other_configurations-Newsletter_configuration"> + <title>Newsletter configuration</title> + <step> + <para> + + </para> + + </step> + + </procedure> + + + </section> + + +</chapter> +

13 years, 3 months

1
0
0 / 0

gatein SVN: r7690 - in epp/docs/branches/5.2/Site_Publisher/Installation_Guide: en-US and 1 other directories.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-10-09 21:21:48 -0400 (Sun, 09 Oct 2011) New Revision: 7690 Modified: epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Author_Group.xml epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Book_Info.xml epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Installation.xml epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Introduction.xml epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Preface.xml epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Revision_History.xml epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Site_Publisher_Installation_Guide.xml epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/fallback_content/Conventions.xml epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/fallback_content/Feedback.xml epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/fallback_content/Legal_Notice.xml epp/docs/branches/5.2/Site_Publisher/Installation_Guide/publican.cfg Log: Minor edits Modified: epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Author_Group.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Author_Group.xml 2011-10-07 21:55:02 UTC (rev 7689) +++ epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Author_Group.xml 2011-10-10 01:21:48 UTC (rev 7690) @@ -1,6 +1,6 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Site_Publisher_Installation_Guide.ent"> %BOOK_ENTITIES; ]> <authorgroup> @@ -12,6 +12,7 @@ <orgdiv>Engineering Content Services</orgdiv> </affiliation> + </author> </authorgroup> Modified: epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Book_Info.xml 2011-10-07 21:55:02 UTC (rev 7689) +++ epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Book_Info.xml 2011-10-10 01:21:48 UTC (rev 7690) @@ -1,31 +1,31 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Site_Publisher_Installation_Guide.ent"> %BOOK_ENTITIES; ]> -<bookinfo id="book-Installation_Guide-Installation_Guide"> - <title>Site Publisher Installation Guide</title> - <subtitle>A guide to installing JBoss Enterprise Portal Platform Site Publisher &VZ;</subtitle> - <productname>JBoss Enterprise Portal Platform</productname> - <productnumber>5.2</productnumber> - <edition>5.2.0</edition> - <pubsnumber>2</pubsnumber> - <abstract> - <para> - This book provides information about obtaining, installing and running the JBoss Enterprise Portal Platform Site Publisher extension. It forms the documentation suite along with the Site Publisher User Guide available at <ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Site_Publisher/index.html" /> - </para> +<bookinfo id="book-Site_Publisher_Installation_Guide-Site_Publisher_Installation_Guide"> + <title>Site Publisher Installation Guide</title> + <subtitle>A guide to installing JBoss Enterprise Portal Platform Site Publisher &VZ;</subtitle> + <productname>JBoss Enterprise Portal Platform</productname> + <productnumber>5.2</productnumber> + <edition>5.2.0</edition> + <pubsnumber>4</pubsnumber> + <abstract> + <para> + This book provides information about obtaining, installing and running the JBoss Enterprise Portal Platform Site Publisher extension. It forms the documentation suite along with the Site Publisher User Guide available at <ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Site_Publisher/index.html" /> + </para> - </abstract> - <corpauthor> - <inlinemediaobject> - <imageobject> - <imagedata fileref="Common_Content/images/title_logo.svg" format="SVG" /> - </imageobject> + </abstract> + <corpauthor> + <inlinemediaobject> + <imageobject> + <imagedata fileref="Common_Content/images/title_logo.svg" format="SVG" /> + </imageobject> - </inlinemediaobject> + </inlinemediaobject> - </corpauthor> - <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + </corpauthor> + <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </bookinfo> Modified: epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Installation.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Installation.xml 2011-10-07 21:55:02 UTC (rev 7689) +++ epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Installation.xml 2011-10-10 01:21:48 UTC (rev 7690) @@ -1,161 +1,173 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Site_Publisher_Installation_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Installation_Guide-Installation"> - <title>Installation</title> - - <section id="sect-Installation_Guide-Installation-Pre_Installation_Requirements"> - <title><emphasis role="bold">Pre-Installation Requirements</emphasis></title> - <para> - Site Publisher is an extension to the JBoss Enterprise Portal Platform product. It is not a standalone product. Therefore it needs to be installed into a working installation of JBoss Enterprise Portal Platform to function. - </para> - <para> - If you do not already have a installation of JBoss Enterprise Portal Platform you should follow the steps outlined in the JBoss Enterprise Portal Platform Installation Guide to obtain and install an instance of the Portal Platform. - </para> - <para> - The JBoss Enterprise Portal Platform Installation Guide is available at <ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." />. A User Guide and Reference Guide are also available at this location and should be reviewed to ensure your Portal Platform is configured correctly. - </para> - <important> - <title>JBoss Enterprise Portal Platform Environments</title> - <para> - The <emphasis role="bold">Site Publisher</emphasis> add-on that is part of the &VZ; release can only be installed into a <emphasis>clean</emphasis> installation of JBoss Enterprise Portal Platform version 5.1 or later. - </para> - <itemizedlist> - <listitem> - <para> - It <emphasis role="bold">cannot</emphasis> be installed into a <emphasis>pre-existing</emphasis> and configured JBoss Enterprise Portal Platform installation (that is; a deployment that contains configuration settings or data that is not standard in the release). - </para> - </listitem> - <listitem> - <para> - Likewise, Site Publisher <emphasis role="bold">cannot</emphasis> be installed onto JBoss Enterprise Portal Platform 5.0 or 5.0.1 versions (including installations that include the technical preview release of the Site Publisher extension). - </para> - <para> - You must deploy a new instance of JBoss Enterprise Portal Platform 5.1.1 in order to use the Site Publisher add-on. - </para> - </listitem> - </itemizedlist> - </important> - <note> - <title>JBoss Enterprise Portal Platform Subscriptions</title> - <para> - Subscriptions for Site Publisher are separate from JBoss Enterprise Portal Platform subscriptions. - </para> - <para> - If you do not already have a subscription to JBoss Enterprise Portal Platform you will need to obtain one in addition to your Site Publisher subscription in order to install and run Site Publisher. - </para> - </note> - </section> - - <section id="sect-Installation_Guide-Installation-Configuration_Locations"> - <title>Configuration Locations</title> - <para> - Installation of the Site Publisher add-on requires various configuration files to be copied to the configuration location of your JBoss Enterprise Portal Platform instance. - </para> - <para> - There are three possible locations for these configuration files depending on your JBoss Enterprise Portal Platform configuration setup: - </para> - <variablelist> - <varlistentry> - <term>Default</term> - <listitem> - <para> - <filename>jboss-epp-<replaceable><version></replaceable>/jboss-as/server/default/deploy</filename>. - </para> +<chapter id="chap-Site_Publisher_Installation_Guide-Installing_Site_Publisher"> + <title>Installing Site Publisher</title> + <section id="sect-Site_Publisher_Installation_Guide-Installing_Site_Publisher-Pre_Installation_Requirements"> + <title><emphasis role="bold">Pre-Installation Requirements</emphasis></title> + <para> + Site Publisher is an extension to the JBoss Enterprise Portal Platform product. It is not a standalone product. Therefore it needs to be installed into a working installation of JBoss Enterprise Portal Platform to function. + </para> + <para> + If you do not already have a installation of JBoss Enterprise Portal Platform you should follow the steps outlined in the JBoss Enterprise Portal Platform Installation Guide to obtain and install an instance of the Portal Platform. + </para> + <para> + The JBoss Enterprise Portal Platform Installation Guide is available at <ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." />. A User Guide and Reference Guide are also available at this location and should be reviewed to ensure your Portal Platform is configured correctly. + </para> + <important> + <title>JBoss Enterprise Portal Platform Environments</title> + <para> + The <emphasis role="bold">Site Publisher</emphasis> add-on that is part of the &VZ; release can only be installed into a <emphasis>clean</emphasis> installation of JBoss Enterprise Portal Platform version 5.1 or later. + </para> + <itemizedlist> + <listitem> + <para> + It <emphasis role="bold">cannot</emphasis> be installed into a <emphasis>pre-existing</emphasis> and configured JBoss Enterprise Portal Platform installation (that is; a deployment that contains configuration settings or data that is not standard in the release). + </para> - </listitem> + </listitem> + <listitem> + <para> + Likewise, Site Publisher <emphasis role="bold">cannot</emphasis> be installed onto JBoss Enterprise Portal Platform 5.0 or 5.0.1 versions (including installations that include the technical preview release of the Site Publisher extension). + </para> + <para> + You must deploy a new instance of JBoss Enterprise Portal Platform 5.1.1 in order to use the Site Publisher add-on. + </para> - </varlistentry> - <varlistentry> - <term>All</term> - <listitem> - <para> - <filename>jboss-epp-<replaceable><version></replaceable>/jboss-as/server/all/deploy</filename>. - </para> + </listitem> - </listitem> + </itemizedlist> - </varlistentry> - <varlistentry> - <term>Production</term> - <listitem> - <para> - <filename>jboss-epp-<replaceable><version></replaceable>/jboss-as/server/production/deploy</filename>. - </para> + </important> + <note> + <title>JBoss Enterprise Portal Platform Subscriptions</title> + <para> + Subscriptions for Site Publisher are separate from JBoss Enterprise Portal Platform subscriptions. + </para> + <para> + If you do not already have a subscription to JBoss Enterprise Portal Platform you will need to obtain one in addition to your Site Publisher subscription in order to install and run Site Publisher. + </para> - </listitem> + </note> - </varlistentry> + </section> + + <section id="sect-Site_Publisher_Installation_Guide-Installing_Site_Publisher-Configuration_Locations"> + <title>Configuration Locations</title> + <para> + Installation of the Site Publisher add-on requires various configuration files to be copied to the configuration location of your JBoss Enterprise Portal Platform instance. + </para> + <para> + There are three possible locations for these configuration files depending on your JBoss Enterprise Portal Platform configuration setup: + </para> + <variablelist> + <varlistentry> + <term>Default</term> + <listitem> + <para> + <filename>jboss-epp-<replaceable><version></replaceable>/jboss-as/server/default/deploy</filename>. + </para> - </variablelist> - <para> - Ensure you know which of the above configuration profiles are to be used in your JBoss Enterprise Portal Platform environment before you begin the installation. - </para> - <para> - Alternatively, the required files can be copied into each of the three locations to ensure that Site Publisher can be used with each of the three configuration profiles. - </para> - <para> - If you use a custom configuration profile, copy the files into the corresponding location of your profile. - </para> + </listitem> - </section> - - <section id="sect-Installation_Guide-Installation-Installation_Instructions"> - <title>Installation Instructions</title> - <procedure> - <step> - <para> - If you have not already done so, deploy a new installation of JBoss Enterprise Portal Platform &VX;. - </para> + </varlistentry> + <varlistentry> + <term>All</term> + <listitem> + <para> + <filename>jboss-epp-<replaceable><version></replaceable>/jboss-as/server/all/deploy</filename>. + </para> - </step> - <step> - <para> - Download the <filename>jboss-eppsp-<replaceable><version></replaceable>-exo-<replaceable><version></replaceable>-GA.zip</filename> file from the Red Hat JBoss Customer Support Portal and extract it to an easily accessible location. - </para> + </listitem> - </step> + </varlistentry> + <varlistentry> + <term>Production</term> + <listitem> + <para> + <filename>jboss-epp-<replaceable><version></replaceable>/jboss-as/server/production/deploy</filename>. + </para> + + </listitem> + + </varlistentry> + + </variablelist> + <para> + Ensure you know which of the above configuration profiles are to be used in your JBoss Enterprise Portal Platform environment before you begin the installation. + </para> + <para> + Alternatively, the required files can be copied into each of the three locations to ensure that Site Publisher can be used with each of the three configuration profiles. + </para> + <para> + If you use a custom configuration profile, copy the files into the corresponding location of your profile. + </para> + + </section> + + <section id="sect-Site_Publisher_Installation_Guide-Installing_Site_Publisher-Installation_Instructions"> + <title>Installation Instructions</title> + <procedure> + <step> + <para> + If you have not already done so, deploy a new installation of JBoss Enterprise Portal Platform &VX;. + </para> + + </step> + <step> + <para> + Download the <filename>jboss-eppsp-<replaceable><version></replaceable>-exo-<replaceable><version></replaceable>-GA.zip</filename> file from the Red Hat JBoss Customer Support Portal and extract it to an easily accessible location. + </para> + + </step> + <step> + <para> + Copy the files in the list below from the extracted location to the configuration location of your JBoss Enterprise Portal Platform installation (as discussed in <xref linkend="sect-Site_Publisher_Installation_Guide-Installing_Site_Publisher-Configuration_Locations" />): + </para> + <itemizedlist> + <listitem> + <para> + <filename>gatein-wcm-extension-<replaceable><version></replaceable>-GA.ear</filename> + </para> + + </listitem> + <listitem> + <para> + <filename>gatein-eppspdemo-portal-<replaceable><version></replaceable>-GA.ear</filename> + </para> + + </listitem> + <listitem> + <para> + <filename>gatein-ds.xml</filename> + </para> + + </listitem> + <listitem> + <para> + <filename>wcm-ds.xml</filename> + </para> + + </listitem> + + </itemizedlist> + <note> + <title>Overwriting gatein-ds.xml</title> + <para> + Be aware that a base installation of JBoss Enterprise Portal Platform already contains a <filename>gatein-ds.xml</filename> file in the <filename>deploy</filename> directory. It is recommended that this file be backed-up before copying the new Site Publisher version of the file. + </para> + <para> + This ensures that if you wish to 'uninstall' the Site Publisher add-on, you can revert to the original <filename>gatein-ds.xml</filename> file. + </para> + + </note> + + </step> +  - <step> - <para> - Start JBoss Enterprise Portal Platform using your established method, the procedures outlined in the JBoss Enterprise Portal Platform Installation Guide or by following the steps below: - </para> - <procedure> - <step> - <para> - Open a command-line terminal session and navigate to the <filename>jboss-epp-&VX;/jboss-as/bin</filename> directory in the JBoss Enterprise Portal Platform location. - </para> + </step> --> <step> + <para> + Start JBoss Enterprise Portal Platform using your established method, the procedures outlined in the JBoss Enterprise Portal Platform Installation Guide or by following the steps below: + </para> + <procedure> + <step> + <para> + Open a command-line terminal session and navigate to the <filename>jboss-epp-&VX;/jboss-as/bin</filename> directory in the JBoss Enterprise Portal Platform location. + </para> - </step> - <step> - <para> - Run the command that corresponds to your operating environment. - </para> - <itemizedlist> - <listitem> - <para> - In Windows: - </para> - + </step> + <step> + <para> + Run the command that corresponds to your operating environment. + </para> + <itemizedlist> + <listitem> + <para> + In Windows: + </para> + <programlisting>run.bat</programlisting> - </listitem> - <listitem> - <para> - In Unix/Linux/Cygwin: - </para> - + </listitem> + <listitem> + <para> + In Unix/Linux/Cygwin: + </para> + <programlisting>./run.sh</programlisting> - </listitem> + </listitem> - </itemizedlist> + </itemizedlist> - </step> + </step> - </procedure> - </step> - <step> - <para> + </procedure> + + + </step> + <step> +  <para> + Navigate to <ulink type="http" url="http://localhost:8080/ecmdemo/public/classic">http://localhost:8080/ecmdemo/public/classic</ulink>. + </para> + <para> + If your installation has been successful, you will see the following sample homepage: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata fileref="images/epp-sp-homepage.png" format="PNG" scale="90" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata contentwidth="150mm" fileref="images/epp-sp-homepage.png" format="PNG" width="444" /> + </imageobject> - </mediaobject> - <para> + </mediaobject> +  + </step> - </step> + </procedure> + + <note> + <title>JBoss Enterprise Portal Platform Installation</title> + <para> + If you have read this guide as part of a complete installation of JBoss Enterprise Portal Platform and Site Publisher, you should now return to <emphasis role="bold">Chapter 7</emphasis> of the JBoss Enterprise Portal Platform Installation Guide to test your Portal Platform environment: + </para> + <para> + <ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." /> + </para> - </procedure> - <note> - <title>JBoss Enterprise Portal Platform Installation</title> - <para> - If you have read this guide as part of a complete installation of JBoss Enterprise Portal Platform and Site Publisher, you should now return to <emphasis role="bold">Chapter 7</emphasis> of the JBoss Enterprise Portal Platform Installation Guide to test your Portal Platform environment: - </para> - <para> - <ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...."></ulink> - </para> - </note> + </note> - </section> + </section> + - </chapter> Modified: epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Introduction.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Introduction.xml 2011-10-07 21:55:02 UTC (rev 7689) +++ epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Introduction.xml 2011-10-10 01:21:48 UTC (rev 7690) @@ -1,12 +1,12 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Site_Publisher_Installation_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Installation_Guide-Introduction"> +<chapter id="chap-Site_Publisher_Installation_Guide-Introduction"> <title>Introduction</title> <para> - JBoss Site Publisher (powered by eXo) is a new add-on component for JBoss Enterprise Portal Platform. It enables users to create, edit and publish rich web content within the context of their portal installation. + JBoss Site Publisher (powered by eXo) is a new add-on component for JBoss Enterprise Portal Platform. It enables users to create, edit and publish rich web content within the context of their portal installation. </para> <para> Site Publisher simplifies the authoring and management for every website an organization needs to deploy. It includes the ability to administer sites, manage navigation, and publish content. Site Publisher delivers powerful functionality to everyone responsible for maintaining web content. Modified: epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Preface.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Preface.xml 2011-10-07 21:55:02 UTC (rev 7689) +++ epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Preface.xml 2011-10-10 01:21:48 UTC (rev 7690) @@ -1,22 +1,15 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Site_Publisher_Installation_Guide.ent"> %BOOK_ENTITIES; ]> -<preface id="pref-Installation_Guide-Preface"> +<preface id="pref-Site_Publisher_Installation_Guide-Preface"> <title>Preface</title> - - -<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Common_Content/Conventions.xml"> - - <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"> - <xi:include href="fallback_content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> - </xi:fallback> -</xi:include> - - -<xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"><xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"><xi:include href="fallback_content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - </xi:fallback> -</xi:include> + <xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"> <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"> <xi:include href="fallback_content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + </xi:fallback> + </xi:include> + <xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"><xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"><xi:include href="fallback_content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + </xi:fallback> + </xi:include> </preface> Modified: epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Revision_History.xml 2011-10-07 21:55:02 UTC (rev 7689) +++ epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Revision_History.xml 2011-10-10 01:21:48 UTC (rev 7690) @@ -1,26 +1,51 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Site_Publisher_Installation_Guide.ent"> %BOOK_ENTITIES; ]> -<appendix id="appe-Release_Notes-Revision_History"> - <title>Revision History</title> - <simpara> - <revhistory> - <revision> - <revnumber>5.2.0-2</revnumber> - <date>Mon Aug 29 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></email> - </author> - <revdescription> - <simplelist> - <member>Updating version and resetting pubs/ed numbers.</member> - </simplelist> - </revdescription> - </revision> - </revhistory> - </simpara> -</appendix> \ No newline at end of file +<appendix id="appe-Site_Publisher_Installation_Guide-Revision_History"> + <title>Revision History</title> + <simpara> + <revhistory> + <revision> + <revnumber>5.2.0-4</revnumber> + <date>Mon Sept 19 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + + </author> + <revdescription> + <simplelist> + <member>Edited Installation content about deploying ecmdemo portal.</member> + + </simplelist> + + </revdescription> + + </revision> + <revision> + <revnumber>5.2.0-2</revnumber> + <date>Mon Aug 29 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + + </author> + <revdescription> + <simplelist> + <member>Updating version and resetting pubs/ed numbers.</member> + + </simplelist> + + </revdescription> + + </revision> + + </revhistory> + + </simpara> +</appendix> + Modified: epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Site_Publisher_Installation_Guide.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Site_Publisher_Installation_Guide.xml 2011-10-07 21:55:02 UTC (rev 7689) +++ epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Site_Publisher_Installation_Guide.xml 2011-10-10 01:21:48 UTC (rev 7690) @@ -1,6 +1,6 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Site_Publisher_Installation_Guide.ent"> %BOOK_ENTITIES; ]> <book> @@ -8,6 +8,7 @@ <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Create_A_Site.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <index /> </book> Modified: epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/fallback_content/Conventions.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/fallback_content/Conventions.xml 2011-10-07 21:55:02 UTC (rev 7689) +++ epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/fallback_content/Conventions.xml 2011-10-10 01:21:48 UTC (rev 7690) @@ -1,120 +1,127 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "../Installation_Guide.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Site_Publisher_Installation_Guide.ent"> %BOOK_ENTITIES; ]> -<section> +<section id="sect-Site_Publisher_Installation_Guide-Document_Conventions"> <title>Document Conventions</title> - <para> + <para> This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information. </para> - <para> + <para> In PDF and paper editions, this manual uses typefaces drawn from the <ulink url="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</ulink> set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default. </para> - <section> + <section id="sect-Site_Publisher_Installation_Guide-Document_Conventions-Typographic_Conventions"> <title>Typographic Conventions</title> - <para> + <para> Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows. </para> - <para> + <para> <literal>Mono-spaced Bold</literal> </para> - <para> + <para> Used to highlight system input, including shell commands, file names and paths. Also used to highlight keycaps and key combinations. For example: </para> - <blockquote> + <blockquote> <para> To see the contents of the file <filename>my_next_bestselling_novel</filename> in your current working directory, enter the <command>cat my_next_bestselling_novel</command> command at the shell prompt and press <keycap>Enter</keycap> to execute the command. </para> + </blockquote> - <para> + <para> The above includes a file name, a shell command and a keycap, all presented in mono-spaced bold and all distinguishable thanks to context. </para> - <para> + <para> Key combinations can be distinguished from keycaps by the hyphen connecting each part of a key combination. For example: </para> - <blockquote> + <blockquote> <para> Press <keycap>Enter</keycap> to execute the command. </para> - <para> + <para> Press <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F1</keycap></keycombo> to switch to the first virtual terminal. Press <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F7</keycap></keycombo> to return to your X-Windows session. </para> + </blockquote> - <para> + <para> The first paragraph highlights the particular keycap to press. The second highlights two key combinations (each a set of three keycaps with each set pressed simultaneously). </para> - <para> + <para> If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in <literal>mono-spaced bold</literal>. For example: </para> - <blockquote> + <blockquote> <para> File-related classes include <classname>file system</classname> for file systems, <classname>file</classname> for files, and <classname>dir</classname> for directories. Each class has its own associated set of permissions. </para> + </blockquote> - <para> + <para> <application>Proportional Bold</application> </para> - <para> + <para> This denotes words or phrases encountered on a system, including application names; dialog box text; labeled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example: </para> - <blockquote> + <blockquote> <para> Choose <menuchoice><guimenu>System</guimenu><guisubmenu>Preferences</guisubmenu><guimenuitem>Mouse</guimenuitem></menuchoice> from the main menu bar to launch <application>Mouse Preferences</application>. In the <guilabel>Buttons</guilabel> tab, click the <guilabel>Left-handed mouse</guilabel> check box and click <guibutton>Close</guibutton> to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand). </para> - <para> + <para> To insert a special character into a <application>gedit</application> file, choose <menuchoice><guimenu>Applications</guimenu><guisubmenu>Accessories</guisubmenu><guimenuitem>Character Map</guimenuitem></menuchoice> from the main menu bar. Next, choose <menuchoice><guimenu>Search</guimenu><guimenuitem>Find…</guimenuitem></menuchoice> from the <application>Character Map</application> menu bar, type the name of the character in the <guilabel>Search</guilabel> field and click <guibutton>Next</guibutton>. The character you sought will be highlighted in the <guilabel>Character Table</guilabel>. Double-click this highlighted character to place it in the <guilabel>Text to copy</guilabel> field and then click the <guibutton>Copy</guibutton> button. Now switch back to your document and choose <menuchoice><guimenu>Edit</guimenu><guimenuitem>Paste</guimenuitem></menuchoice> from the <application>gedit</application> menu bar. </para> + </blockquote> - <para> + <para> The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all distinguishable by context. </para> - <para> + <para> <command><replaceable>Mono-spaced Bold Italic</replaceable></command> or <application><replaceable>Proportional Bold Italic</replaceable></application> </para> - <para> + <para> Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example: </para> - <blockquote> + <blockquote> <para> To connect to a remote machine using ssh, type <command>ssh <replaceable>username</replaceable>@<replaceable>domain.name</replaceable></command> at a shell prompt. If the remote machine is <filename>example.com</filename> and your username on that machine is john, type <command>ssh john(a)example.com</command>. </para> - <para> + <para> The <command>mount -o remount <replaceable>file-system</replaceable></command> command remounts the named file system. For example, to remount the <filename>/home</filename> file system, the command is <command>mount -o remount /home</command>. </para> - <para> + <para> To see the version of a currently installed package, use the <command>rpm -q <replaceable>package</replaceable></command> command. It will return a result as follows: <command><replaceable>package-version-release</replaceable></command>. </para> + </blockquote> - <para> + <para> Note the words in bold italics above — username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system. </para> - <para> + <para> Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example: </para> - <blockquote> + <blockquote> <para> Publican is a <firstterm>DocBook</firstterm> publishing system. </para> + </blockquote> + </section> - <section> + <section id="sect-Site_Publisher_Installation_Guide-Document_Conventions-Pull_quote_Conventions"> <title>Pull-quote Conventions</title> - <para> + <para> Terminal output and source code listings are set off visually from the surrounding text. </para> - <para> + <para> Output sent to a terminal is set in <computeroutput>mono-spaced roman</computeroutput> and presented thus: </para> - + <screen>books Desktop documentation drafts mss photos stuff svn books_tests Desktop1 downloads images notes scripts svgs </screen> - <para> + <para> Source-code listings are also set in <computeroutput>mono-spaced roman</computeroutput> but add syntax highlighting as follows: </para> - + <programlisting language="Java">package org.jboss.book.jca.ex1; import javax.naming.InitialContext; @@ -135,32 +142,38 @@ } } </programlisting> + </section> - <section> + <section id="sect-Site_Publisher_Installation_Guide-Document_Conventions-Notes_and_Warnings"> <title>Notes and Warnings</title> - <para> + <para> Finally, we use three visual styles to draw attention to information that might otherwise be overlooked. </para> - <note> + <note> <title>Note</title> - <para> + <para> Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier. </para> + </note> - <important> + <important> <title>Important</title> - <para> + <para> Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' will not cause data loss but may cause irritation and frustration. </para> + </important> - <warning> + <warning> <title>Warning</title> - <para> + <para> Warnings should not be ignored. Ignoring warnings will most likely cause data loss. </para> + </warning> + </section> + </section> Modified: epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/fallback_content/Feedback.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/fallback_content/Feedback.xml 2011-10-07 21:55:02 UTC (rev 7689) +++ epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/fallback_content/Feedback.xml 2011-10-10 01:21:48 UTC (rev 7690) @@ -1,21 +1,22 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "../Installation_Guide.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Site_Publisher_Installation_Guide.ent"> %BOOK_ENTITIES; ]> -<section> +<section id="sect-Site_Publisher_Installation_Guide-We_Need_Feedback"> <title>We Need Feedback!</title> - <indexterm> + <indexterm> <primary>feedback</primary> - <secondary>contact information for this manual</secondary> + <secondary>contact information for this manual</secondary> + </indexterm> - <para> + <para> If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a support ticket with your comments via the JBoss Customer Support Portal available at <ulink url="http://support.redhat.com">http://support.redhat.com</ulink> against the product <application>JBoss Enterprise Portal Platform</application>. </para> - <para> + <para> When submitting a bug report, be sure to mention the manual's identifier: <citetitle>&BOOKID;</citetitle> </para> - <para> + <para> If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily. </para> </section> Modified: epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/fallback_content/Legal_Notice.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/fallback_content/Legal_Notice.xml 2011-10-07 21:55:02 UTC (rev 7689) +++ epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/fallback_content/Legal_Notice.xml 2011-10-10 01:21:48 UTC (rev 7690) @@ -1,6 +1,6 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE legalnotice PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "../Installation_Guide.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Site_Publisher_Installation_Guide.ent"> %BOOK_ENTITIES; ]> <legalnotice> Modified: epp/docs/branches/5.2/Site_Publisher/Installation_Guide/publican.cfg =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Installation_Guide/publican.cfg 2011-10-07 21:55:02 UTC (rev 7689) +++ epp/docs/branches/5.2/Site_Publisher/Installation_Guide/publican.cfg 2011-10-10 01:21:48 UTC (rev 7690) @@ -4,7 +4,7 @@ xml_lang: en-US type: Book brand: JBoss -#show_remarks: 1 +show_remarks: 1 cvs_branch: DOCS-RHEL-6 cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist cvs_pkg: JBoss_Enterprise_Portal_Platform-Site_Publisher_Installation_Guide-5.2-web-__LANG__

13 years, 3 months

1
0
0 / 0

gatein SVN: r7689 - components/pc/trunk.

by do-not-reply＠jboss.org

Author: chris.laprun(a)jboss.com Date: 2011-10-07 17:55:02 -0400 (Fri, 07 Oct 2011) New Revision: 7689 Modified: components/pc/trunk/pom.xml Log: - Updated to use Common 2.0.4-GA. Modified: components/pc/trunk/pom.xml =================================================================== --- components/pc/trunk/pom.xml 2011-10-07 21:54:28 UTC (rev 7688) +++ components/pc/trunk/pom.xml 2011-10-07 21:55:02 UTC (rev 7689) @@ -55,7 +55,7 @@ </scm> <properties> - <version.gatein.common>2.0.4-Beta03</version.gatein.common> + <version.gatein.common>2.0.4-GA</version.gatein.common> <version.gatein.wci>2.1.0-Beta06</version.gatein.wci> <version.apache.portals.bridges>1.0.4</version.apache.portals.bridges> <version.apache.taglibs>1.1.2</version.apache.taglibs>

13 years, 3 months

1
0
0 / 0

gatein SVN: r7688 - in components/pc/trunk: federation/src/main/java/org/gatein/pc/federation/impl and 4 other directories.

by do-not-reply＠jboss.org

Author: chris.laprun(a)jboss.com Date: 2011-10-07 17:54:28 -0400 (Fri, 07 Oct 2011) New Revision: 7688 Modified: components/pc/trunk/api/src/main/java/org/gatein/pc/api/PortletInvoker.java components/pc/trunk/federation/src/main/java/org/gatein/pc/federation/impl/FederatedPortletInvokerService.java components/pc/trunk/federation/src/main/java/org/gatein/pc/federation/impl/FederatingPortletInvokerService.java components/pc/trunk/federation/src/test/java/org/gatein/pc/federation/FederatingPortletInvokerTestCase.java components/pc/trunk/portlet/src/main/java/org/gatein/pc/portlet/PortletInvokerInterceptor.java components/pc/trunk/portlet/src/main/java/org/gatein/pc/portlet/container/ContainerPortletDispatcher.java components/pc/trunk/portlet/src/test/java/org/gatein/pc/portlet/support/PortletInvokerSupport.java Log: - GTNPC-75: added isActive method on PortletInvoker and check whether an invoker is active before attempting to retrieve portlets from it. Should maybe extend active checking to other methods. Modified: components/pc/trunk/api/src/main/java/org/gatein/pc/api/PortletInvoker.java =================================================================== --- components/pc/trunk/api/src/main/java/org/gatein/pc/api/PortletInvoker.java 2011-10-07 11:37:36 UTC (rev 7687) +++ components/pc/trunk/api/src/main/java/org/gatein/pc/api/PortletInvoker.java 2011-10-07 21:54:28 UTC (rev 7688) @@ -49,8 +49,10 @@ Set<Portlet> getPortlets() throws PortletInvokerException; /** - * Get information about a specific portlet. Note that this PortletInvoker can know about more portlets than returned - * by {@link #getPortlets()}. In particular, cloned portlets wouldn't necessarily be exposed to getPortlets and still + * Get information about a specific portlet. Note that this PortletInvoker can know about more portlets than + * returned + * by {@link #getPortlets()}. In particular, cloned portlets wouldn't necessarily be exposed to getPortlets and + * still * be known by this PortletInvoker i.e. there exists PortletContexts <code>pc</code> as follows: <p> <code> assert * getPortlet(pc) != null && !getPortlets().contains(portlet);<br/> </code> </p> * @@ -161,4 +163,11 @@ * @throws PortletInvokerException */ PortletContext importPortlet(PortletStateType stateType, PortletContext contextToImport) throws PortletInvokerException; + + /** + * Returns whether this portlet invoker is active and can respond to requests. + * + * @return <code>true</code> if this portlet invoker can respond to requests, <code>false</code> otherwise + */ + boolean isActive(); } Modified: components/pc/trunk/federation/src/main/java/org/gatein/pc/federation/impl/FederatedPortletInvokerService.java =================================================================== --- components/pc/trunk/federation/src/main/java/org/gatein/pc/federation/impl/FederatedPortletInvokerService.java 2011-10-07 11:37:36 UTC (rev 7687) +++ components/pc/trunk/federation/src/main/java/org/gatein/pc/federation/impl/FederatedPortletInvokerService.java 2011-10-07 21:54:28 UTC (rev 7688) @@ -75,6 +75,11 @@ return portletInvoker; } + public boolean isActive() + { + return portletInvoker.isActive(); + } + public String getId() { return id; Modified: components/pc/trunk/federation/src/main/java/org/gatein/pc/federation/impl/FederatingPortletInvokerService.java =================================================================== --- components/pc/trunk/federation/src/main/java/org/gatein/pc/federation/impl/FederatingPortletInvokerService.java 2011-10-07 11:37:36 UTC (rev 7687) +++ components/pc/trunk/federation/src/main/java/org/gatein/pc/federation/impl/FederatingPortletInvokerService.java 2011-10-07 21:54:28 UTC (rev 7688) @@ -191,6 +191,13 @@ final FederatedPortletInvoker federated = getFederatedInvoker(invokerId); + // skip the invoker if it isn't active + if(!federated.isActive()) + { + log.info("PortletInvoker with id: " + invokerId + " was skipped because it isn't active."); + continue; + } + try { Set<Portlet> offeredPortlets = federated.getPortlets(); @@ -305,6 +312,11 @@ return federated.importPortlet(stateType, compoundPortletContext); } + public boolean isActive() + { + return true; + } + public synchronized void setPortletInvokerResolver(PortletInvokerResolver portletResolver) { if (portletResolver == null) Modified: components/pc/trunk/federation/src/test/java/org/gatein/pc/federation/FederatingPortletInvokerTestCase.java =================================================================== --- components/pc/trunk/federation/src/test/java/org/gatein/pc/federation/FederatingPortletInvokerTestCase.java 2011-10-07 11:37:36 UTC (rev 7687) +++ components/pc/trunk/federation/src/test/java/org/gatein/pc/federation/FederatingPortletInvokerTestCase.java 2011-10-07 21:54:28 UTC (rev 7688) @@ -258,5 +258,10 @@ { return null; } + + public boolean isActive() + { + return true; + } } } Modified: components/pc/trunk/portlet/src/main/java/org/gatein/pc/portlet/PortletInvokerInterceptor.java =================================================================== --- components/pc/trunk/portlet/src/main/java/org/gatein/pc/portlet/PortletInvokerInterceptor.java 2011-10-07 11:37:36 UTC (rev 7687) +++ components/pc/trunk/portlet/src/main/java/org/gatein/pc/portlet/PortletInvokerInterceptor.java 2011-10-07 21:54:28 UTC (rev 7688) @@ -149,4 +149,9 @@ { return safeGetNext().importPortlet(stateType, originalPortletContext); } + + public boolean isActive() + { + return safeGetNext().isActive(); + } } Modified: components/pc/trunk/portlet/src/main/java/org/gatein/pc/portlet/container/ContainerPortletDispatcher.java =================================================================== --- components/pc/trunk/portlet/src/main/java/org/gatein/pc/portlet/container/ContainerPortletDispatcher.java 2011-10-07 11:37:36 UTC (rev 7687) +++ components/pc/trunk/portlet/src/main/java/org/gatein/pc/portlet/container/ContainerPortletDispatcher.java 2011-10-07 21:54:28 UTC (rev 7688) @@ -41,4 +41,10 @@ // return container.dispatch(invocation); } + + @Override + public boolean isActive() + { + return true; // todo: should it be smarter than this? i.e. check if the PortletContainer is available or not? + } } Modified: components/pc/trunk/portlet/src/test/java/org/gatein/pc/portlet/support/PortletInvokerSupport.java =================================================================== --- components/pc/trunk/portlet/src/test/java/org/gatein/pc/portlet/support/PortletInvokerSupport.java 2011-10-07 11:37:36 UTC (rev 7687) +++ components/pc/trunk/portlet/src/test/java/org/gatein/pc/portlet/support/PortletInvokerSupport.java 2011-10-07 21:54:28 UTC (rev 7688) @@ -232,4 +232,9 @@ { throw new UnsupportedOperationException(); } + + public boolean isActive() + { + return true; + } }

13 years, 3 months

1
0
0 / 0

gatein SVN: r7687 - portal/trunk/webui/core/src/main/java/org/exoplatform/webui/form.

by do-not-reply＠jboss.org

Author: haint Date: 2011-10-07 07:37:36 -0400 (Fri, 07 Oct 2011) New Revision: 7687 Modified: portal/trunk/webui/core/src/main/java/org/exoplatform/webui/form/UIFormDateTimeInput.java Log: GTNPORTAL-2155 Modified: portal/trunk/webui/core/src/main/java/org/exoplatform/webui/form/UIFormDateTimeInput.java =================================================================== --- portal/trunk/webui/core/src/main/java/org/exoplatform/webui/form/UIFormDateTimeInput.java 2011-10-07 11:27:15 UTC (rev 7686) +++ portal/trunk/webui/core/src/main/java/org/exoplatform/webui/form/UIFormDateTimeInput.java 2011-10-07 11:37:36 UTC (rev 7687) @@ -66,11 +66,11 @@ public UIFormDateTimeInput(String name, String bindField, Date date, boolean isDisplayTime) { super(name, bindField, String.class); + setDisplayTime(isDisplayTime); + WebuiRequestContext requestContext = WebuiRequestContext.getCurrentInstance(); formatPattern(requestContext.getLocale()); - setDate(date); - setDisplayTime(isDisplayTime); } public UIFormDateTimeInput(String name, String bindField, Date date)

13 years, 3 months

1
0
0 / 0

gatein SVN: r7686 - portal/trunk/webui/core/src/main/java/org/exoplatform/webui/form.

by do-not-reply＠jboss.org

Author: haint Date: 2011-10-07 07:27:15 -0400 (Fri, 07 Oct 2011) New Revision: 7686 Modified: portal/trunk/webui/core/src/main/java/org/exoplatform/webui/form/UIFormDateTimeInput.java Log: GTNPORTAL-2155 NPE when creating UIFormDateTimeInput with a non-NULL value passed for Date argument Modified: portal/trunk/webui/core/src/main/java/org/exoplatform/webui/form/UIFormDateTimeInput.java =================================================================== --- portal/trunk/webui/core/src/main/java/org/exoplatform/webui/form/UIFormDateTimeInput.java 2011-10-06 18:52:54 UTC (rev 7685) +++ portal/trunk/webui/core/src/main/java/org/exoplatform/webui/form/UIFormDateTimeInput.java 2011-10-07 11:27:15 UTC (rev 7686) @@ -66,11 +66,11 @@ public UIFormDateTimeInput(String name, String bindField, Date date, boolean isDisplayTime) { super(name, bindField, String.class); + WebuiRequestContext requestContext = WebuiRequestContext.getCurrentInstance(); + formatPattern(requestContext.getLocale()); + setDate(date); setDisplayTime(isDisplayTime); - - WebuiRequestContext requestContext = WebuiRequestContext.getCurrentInstance(); - formatPattern(requestContext.getLocale()); } public UIFormDateTimeInput(String name, String bindField, Date date)

13 years, 3 months

1
0
0 / 0

gatein SVN: r7685 - epp/portal/branches/EPP_5_2_Branch.

by do-not-reply＠jboss.org

Author: theute Date: 2011-10-06 14:52:54 -0400 (Thu, 06 Oct 2011) New Revision: 7685 Modified: epp/portal/branches/EPP_5_2_Branch/pom.xml epp/portal/branches/EPP_5_2_Branch/settings-all.xml Log: Upgrading MOP Modified: epp/portal/branches/EPP_5_2_Branch/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/pom.xml 2011-10-06 16:35:19 UTC (rev 7684) +++ epp/portal/branches/EPP_5_2_Branch/pom.xml 2011-10-06 18:52:54 UTC (rev 7685) @@ -54,7 +54,7 @@ <org.gatein.pc.version>2.3.0-Beta06</org.gatein.pc.version> <org.picketlink.idm>1.3.0.Alpha08</org.picketlink.idm> <org.gatein.wsrp.version>2.1.0-Beta07-EPP520</org.gatein.wsrp.version> - <org.gatein.mop.version>1.1.0-Beta06</org.gatein.mop.version> + <org.gatein.mop.version>1.1.0-Beta07</org.gatein.mop.version> <org.gatein.mgmt.version>1.0.0-Beta04</org.gatein.mgmt.version> <org.slf4j.version>1.5.8</org.slf4j.version> <commons-pool.version>1.5.5</commons-pool.version> Modified: epp/portal/branches/EPP_5_2_Branch/settings-all.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/settings-all.xml 2011-10-06 16:35:19 UTC (rev 7684) +++ epp/portal/branches/EPP_5_2_Branch/settings-all.xml 2011-10-06 18:52:54 UTC (rev 7685) @@ -16,9 +16,7 @@  - <profiles> <profile> <id>my-jboss-maven2</id>

13 years, 3 months

1
0
0 / 0

gatein SVN: r7684 - in sandbox/as7_support/branches/gatein-as7/wci: test/servers/jboss42 and 1 other directories.

by do-not-reply＠jboss.org

Author: mstruk Date: 2011-10-06 12:35:19 -0400 (Thu, 06 Oct 2011) New Revision: 7684 Modified: sandbox/as7_support/branches/gatein-as7/wci/pom.xml sandbox/as7_support/branches/gatein-as7/wci/test/servers/jboss42/pom.xml sandbox/as7_support/branches/gatein-as7/wci/wci/pom.xml Log: Synced with wci trunk Modified: sandbox/as7_support/branches/gatein-as7/wci/pom.xml =================================================================== --- sandbox/as7_support/branches/gatein-as7/wci/pom.xml 2011-10-06 15:53:08 UTC (rev 7683) +++ sandbox/as7_support/branches/gatein-as7/wci/pom.xml 2011-10-06 16:35:19 UTC (rev 7684) @@ -149,7 +149,7 @@ </dependency> </dependencies> </dependencyManagement> - + <modules> <module>wci</module> <module>exo</module> Modified: sandbox/as7_support/branches/gatein-as7/wci/test/servers/jboss42/pom.xml =================================================================== --- sandbox/as7_support/branches/gatein-as7/wci/test/servers/jboss42/pom.xml 2011-10-06 15:53:08 UTC (rev 7683) +++ sandbox/as7_support/branches/gatein-as7/wci/test/servers/jboss42/pom.xml 2011-10-06 16:35:19 UTC (rev 7684) @@ -1,418 +1,418 @@ -<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> - <parent> - <groupId>org.gatein.wci</groupId> - <artifactId>wci-test-server-parent</artifactId> - <version>2.1.0-Beta03-SNAPSHOT</version> - </parent> - <modelVersion>4.0.0</modelVersion> - <artifactId>wci-test-jboss42</artifactId> - <packaging>jar</packaging> - <name>GateIn - WCI JBoss 4.2 test component</name> - - <dependencies> - <dependency> - <groupId>org.gatein.wci</groupId> - <artifactId>wci-wci</artifactId> - <scope>test</scope> - </dependency> - <dependency> - <groupId>org.gatein.wci</groupId> - <artifactId>wci-tomcat6</artifactId> - <scope>test</scope> - </dependency> - <dependency> - <groupId>org.gatein.wci</groupId> - <artifactId>wci-exo</artifactId> - <scope>test</scope> - </dependency> - <dependency> - <groupId>org.gatein.wci</groupId> - <artifactId>wci-test-core</artifactId> - <scope>test</scope> - </dependency> - <dependency> - <groupId>org.gatein.wci</groupId> - <artifactId>wci-test-native-portlet</artifactId> - <scope>test</scope> - <type>war</type> - </dependency> - <dependency> - <groupId>org.gatein.wci</groupId> - <artifactId>wci-test-gatein-portlet</artifactId> - <scope>test</scope> - <type>war</type> - </dependency> - <dependency> - <groupId>org.gatein.wci</groupId> - <artifactId>wci-test-exo-portlet</artifactId> - <scope>test</scope> - <type>war</type> - </dependency> - - <dependency> - <artifactId>junit</artifactId> - <groupId>junit</groupId> - <scope>test</scope> - </dependency> - <dependency> - <groupId>org.gatein.common</groupId> - <artifactId>common-common</artifactId> - <exclusions> - <exclusion> - <groupId>org.codehaus.cargo</groupId> - <artifactId>cargo-core-uberjar</artifactId> - </exclusion> - </exclusions> - </dependency> - <dependency> - <groupId>org.gatein.common</groupId> - <artifactId>common-mc</artifactId> - <scope>test</scope> - </dependency> - <dependency> - <groupId>org.gatein.common</groupId> - <artifactId>common-logging</artifactId> - <scope>test</scope> - </dependency> - <dependency> - <groupId>org.slf4j</groupId> - <artifactId>slf4j-api</artifactId> - <scope>test</scope> - </dependency> - <dependency> - <groupId>org.slf4j</groupId> - <artifactId>slf4j-simple</artifactId> - <scope>test</scope> - </dependency> -  - <dependency> - <groupId>org.jboss.unit</groupId> - <artifactId>jboss-unit</artifactId> - <scope>test</scope> - </dependency> - <dependency> - <groupId>org.jboss.unit</groupId> - <artifactId>jboss-unit-remote</artifactId> - <scope>test</scope> - <exclusions> - <exclusion> - <groupId>org.codehaus.cargo</groupId> - <artifactId>cargo-core-uberjar</artifactId> - </exclusion> - </exclusions> - </dependency> - <dependency> - <groupId>org.jboss.unit</groupId> - <artifactId>jboss-unit-mc</artifactId> - <scope>test</scope> - </dependency> - <dependency> - <groupId>org.jboss.unit</groupId> - <artifactId>jboss-unit-tooling-ant</artifactId> - <scope>test</scope> - </dependency> - <dependency> - <groupId>org.jboss.unit</groupId> - <artifactId>portal-test</artifactId> - <scope>test</scope> - <exclusions> - <exclusion> - <groupId>org.codehaus.cargo</groupId> - <artifactId>cargo-core-uberjar</artifactId> - </exclusion> - </exclusions> - </dependency> - <dependency> - <groupId>org.jboss.unit</groupId> - <artifactId>portal-test-generic</artifactId> - <scope>test</scope> - <exclusions> - <exclusion> - <groupId>org.codehaus.cargo</groupId> - <artifactId>cargo-core-uberjar</artifactId> - </exclusion> - </exclusions> - </dependency> -  - <dependency> - <groupId>org.jboss.microcontainer</groupId> - <artifactId>jboss-kernel</artifactId> - <scope>test</scope> - </dependency> - <dependency> - <groupId>org.jboss.microcontainer</groupId> - <artifactId>jboss-dependency</artifactId> - <scope>test</scope> - </dependency> - <dependency> - <groupId>org.jboss</groupId> - <artifactId>jboss-reflect</artifactId> - <scope>test</scope> - </dependency> - <dependency> - <groupId>javax.xml.bind</groupId> - <artifactId>jaxb-api</artifactId> - <scope>test</scope> - </dependency> -  - <dependency> - <groupId>log4j</groupId> - <artifactId>log4j</artifactId> - <scope>test</scope> - </dependency> - <dependency> - <groupId>concurrent</groupId> - <artifactId>concurrent</artifactId> - <scope>test</scope> - </dependency> - <dependency> - <groupId>apache-xerces</groupId> - <artifactId>xercesImpl</artifactId> - <scope>test</scope> - </dependency> - <dependency> - <groupId>apache-xerces</groupId> - <artifactId>xml-apis</artifactId> - <scope>test</scope> - </dependency> - <dependency> - <groupId>jboss</groupId> - <artifactId>jboss-serialization</artifactId> - <scope>test</scope> - </dependency> - - <dependency> - <groupId>commons-discovery</groupId> - <artifactId>commons-discovery</artifactId> - </dependency> - - <dependency> - <groupId>org.jboss.remoting</groupId> - <artifactId>jboss-remoting</artifactId> - </dependency> - - <dependency> - <groupId>org.codehaus.cargo</groupId> - <artifactId>cargo-core-uberjar</artifactId> - <version>${version.cargo}</version> - <scope>test</scope> - </dependency> - - </dependencies> - - - <build> - <plugins> - <plugin> - <artifactId>maven-dependency-plugin</artifactId> - <executions> - <execution> - <id>copy-common-build.xml</id> - <phase>process-resources</phase> - <goals> - <goal>copy</goal> - </goals> - </execution> - </executions> - </plugin> - <plugin> - <artifactId>maven-assembly-plugin</artifactId> - <configuration> - <finalName>test</finalName> - <appendAssemblyId>true</appendAssemblyId> -  - <attach>false</attach> - <outputDirectory>${project.build.directory}/test-archives</outputDirectory> - <descriptors> - <descriptor>src/assembly/spi-native-server.xml</descriptor> - <descriptor>src/assembly/spi-generic-server.xml</descriptor> - <descriptor>src/assembly/spi-exo-server.xml</descriptor> - <descriptor>src/assembly/endpoint-default-servlet-mapping.xml</descriptor> - <descriptor>src/assembly/endpoint-path-mapping.xml</descriptor> - <descriptor>src/assembly/endpoint-root-path-mapping.xml</descriptor> - </descriptors> - </configuration> - <executions> - <execution> - <id>assemble</id> - <phase>test</phase> - <goals> - <goal>single</goal> - </goals> - </execution> - </executions> - </plugin> - <plugin> - <artifactId>maven-antrun-plugin</artifactId> - <dependencies> - - <dependency> - <groupId>org.jboss.unit</groupId> - <artifactId>jboss-unit-tooling-ant</artifactId> - <version>${version.jboss.unit}</version> - </dependency> - <dependency> - <groupId>org.jboss.unit</groupId> - <artifactId>jboss-unit</artifactId> - <version>${version.jboss.unit}</version> - </dependency> - - <dependency> - <groupId>org.codehaus.cargo</groupId> - <artifactId>cargo-ant</artifactId> - <version>${version.cargo}</version> - <exclusions> - <exclusion> - <groupId>ant</groupId> - <artifactId>ant</artifactId> - </exclusion> - </exclusions> - </dependency> - <dependency> - <groupId>org.jdom</groupId> - <artifactId>jdom</artifactId> - <version>1.1</version> - </dependency> - <dependency> - <groupId>dom4j</groupId> - <artifactId>dom4j</artifactId> - <version>1.6.1</version> - </dependency> - <dependency> - <groupId>jaxen</groupId> - <artifactId>jaxen</artifactId> - <version>1.1.1</version> - </dependency> - </dependencies> - <version>1.3</version> - <executions> - <execution> - <id>integration-testing</id> - <phase>integration-test</phase> - <configuration> - <tasks> - -  - <property name="project.build.directory" value="${project.build.directory}" /> - <property name="plugin_classpath" refid="maven.plugin.classpath" /> - <property name="test_classpath" refid="maven.test.classpath" /> - -  -  - <condition property="test.generic.enable"> - <istrue value="${test.generic}" /> - </condition> - <condition property="test.native.enable"> - <istrue value="${test.native}" /> - </condition> - <condition property="test.exo.enable"> - <istrue value="${test.exo}" /> - </condition> - <condition property="test.endpoint.enable"> - <istrue value="${test.endpoint}" /> - </condition> - <condition property="cargo.debug" value="${test.cargo.debug}"> - <isset property="test.cargo.debug" /> - </condition> - <condition property="cargo.debug" value=""> - <not> - <isset property="test.cargo.debug" /> - </not> - </condition> -  - -  - <property name="dependency.jboss-logging-spi.jar" value="${maven.dependency.jboss.jboss-common-logging-spi.jar.path}" /> - <property name="dependency.jboss-logging-jdk.jar" value="${maven.dependency.jboss.jboss-common-logging-jdk.jar.path}" /> - <property name="dependency.jboss-logging-log4j.jar" value="${maven.dependency.jboss.jboss-common-logging-log4j.jar.path}" /> - <property name="dependency.gatein-common-common.jar" value="${maven.dependency.org.gatein.common.common-common.jar.path}" /> - <property name="dependency.gatein-common-logging.jar" value="${maven.dependency.org.gatein.common.common-logging.jar.path}" /> - <property name="dependency.slf4j-api.jar" value="${maven.dependency.org.slf4j.slf4j-api.jar.path}" /> - <property name="dependency.slf4j-simple.jar" value="${maven.dependency.org.slf4j.slf4j-simple.jar.path}" /> - <property name="dependency.log4j.jar" value="${maven.dependency.log4j.log4j.jar.path}" /> - <property name="dependency.activation.jar" value="${maven.dependency.javax.activation.activation.jar.path}" /> - <property name="dependency.junit.jar" value="${maven.dependency.junit.junit.jar.path}" /> - <property name="dependency.gatein-wci-core.jar" value="${maven.dependency.org.gatein.wci.wci-wci.jar.path}" /> - <property name="dependency.gatein-wci-tomcat.jar" value="${maven.dependency.org.gatein.wci.wci-tomcat6.jar.path}" /> - <property name="dependency.gatein-wci-exo.jar" value="${maven.dependency.org.gatein.wci.wci-exo.jar.path}" /> - <property name="dependency.jboss-serialization.jar" value="${maven.dependency.jboss.jboss-serialization.jar.path}" /> - -  - <property name="test.archives.directory" value="${project.build.directory}/test-archives" /> - <property name="test.generic.server.war" value="${test.archives.directory}/test-spi-generic-server.war" /> - <property name="test.native.server.war" value="${test.archives.directory}/test-spi-native-server.war" /> - <property name="test.exo.server.war" value="${test.archives.directory}/test-spi-exo-server.war" /> - - <property name="test.endpoint.default.server.mapping.server.war" value="${test.archives.directory}/test-endpoint-default-servlet-mapping.war" /> - <property name="test.endpoint.root.mapping.server.war" value="${test.archives.directory}/test-endpoint-root-path-mapping.war" /> - <property name="test.endpoint.path.mapping.server.war" value="${test.archives.directory}/test-endpoint-path-mapping.war" /> - - <property name="test.generic.portlet.war" value="${maven.dependency.org.gatein.wci.wci-test-gatein-portlet.war.path}" /> - <property name="test.native.portlet.war" value="${maven.dependency.org.gatein.wci.wci-test-native-portlet.war.path}" /> - <property name="test.exo.portlet.war" value="${maven.dependency.org.gatein.wci.wci-test-exo-portlet.war.path}" /> - -  - <property name="common.xml.file" value="${test.common.xml}" /> -  - - <ant antfile="${basedir}/src/integration-tests/build.xml" inheritRefs="true"> - <target name="tests" /> - </ant> - </tasks> - </configuration> - <goals> - <goal>run</goal> - </goals> - </execution> - </executions> - </plugin> - </plugins> - </build> - <properties> - </properties> - - <profiles> - <profile> - <id>all</id> - <activation> - <activeByDefault>true</activeByDefault> - </activation> - <properties> - <test.generic>true</test.generic> - <test.native>true</test.native> - <test.exo>true</test.exo> - <test.endpoint>true</test.endpoint> - </properties> - </profile> - <profile> - <id>generic</id> - <properties> - <test.generic>true</test.generic> - </properties> - </profile> - <profile> - <id>native</id> - <properties> - <test.native>true</test.native> - </properties> - </profile> - <profile> - <id>exo</id> - <properties> - <test.exo>true</test.exo> - </properties> - </profile> - <profile> - <id>endpoint</id> - <properties> - <test.endpoint>true</test.endpoint> - </properties> - </profile> - <profile> - <id>cargo.debug</id> - <properties> - <test.cargo.debug>-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000</test.cargo.debug> - </properties> - </profile> - </profiles> -</project> +<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> + <parent> + <groupId>org.gatein.wci</groupId> + <artifactId>wci-test-server-parent</artifactId> + <version>2.1.0-Alpha04-SNAPSHOT</version> + </parent> + <modelVersion>4.0.0</modelVersion> + <artifactId>wci-test-jboss42</artifactId> + <packaging>jar</packaging> + <name>GateIn - WCI JBoss 4.2 test component</name> + + <dependencies> + <dependency> + <groupId>org.gatein.wci</groupId> + <artifactId>wci-wci</artifactId> + <scope>test</scope> + </dependency> + <dependency> + <groupId>org.gatein.wci</groupId> + <artifactId>wci-tomcat6</artifactId> + <scope>test</scope> + </dependency> + <dependency> + <groupId>org.gatein.wci</groupId> + <artifactId>wci-exo</artifactId> + <scope>test</scope> + </dependency> + <dependency> + <groupId>org.gatein.wci</groupId> + <artifactId>wci-test-core</artifactId> + <scope>test</scope> + </dependency> + <dependency> + <groupId>org.gatein.wci</groupId> + <artifactId>wci-test-native-portlet</artifactId> + <scope>test</scope> + <type>war</type> + </dependency> + <dependency> + <groupId>org.gatein.wci</groupId> + <artifactId>wci-test-gatein-portlet</artifactId> + <scope>test</scope> + <type>war</type> + </dependency> + <dependency> + <groupId>org.gatein.wci</groupId> + <artifactId>wci-test-exo-portlet</artifactId> + <scope>test</scope> + <type>war</type> + </dependency> + + <dependency> + <artifactId>junit</artifactId> + <groupId>junit</groupId> + <scope>test</scope> + </dependency> + <dependency> + <groupId>org.gatein.common</groupId> + <artifactId>common-common</artifactId> + <exclusions> + <exclusion> + <groupId>org.codehaus.cargo</groupId> + <artifactId>cargo-core-uberjar</artifactId> + </exclusion> + </exclusions> + </dependency> + <dependency> + <groupId>org.gatein.common</groupId> + <artifactId>common-mc</artifactId> + <scope>test</scope> + </dependency> + <dependency> + <groupId>org.gatein.common</groupId> + <artifactId>common-logging</artifactId> + <scope>test</scope> + </dependency> + <dependency> + <groupId>org.slf4j</groupId> + <artifactId>slf4j-api</artifactId> + <scope>test</scope> + </dependency> + <dependency> + <groupId>org.slf4j</groupId> + <artifactId>slf4j-simple</artifactId> + <scope>test</scope> + </dependency> +  + <dependency> + <groupId>org.jboss.unit</groupId> + <artifactId>jboss-unit</artifactId> + <scope>test</scope> + </dependency> + <dependency> + <groupId>org.jboss.unit</groupId> + <artifactId>jboss-unit-remote</artifactId> + <scope>test</scope> + <exclusions> + <exclusion> + <groupId>org.codehaus.cargo</groupId> + <artifactId>cargo-core-uberjar</artifactId> + </exclusion> + </exclusions> + </dependency> + <dependency> + <groupId>org.jboss.unit</groupId> + <artifactId>jboss-unit-mc</artifactId> + <scope>test</scope> + </dependency> + <dependency> + <groupId>org.jboss.unit</groupId> + <artifactId>jboss-unit-tooling-ant</artifactId> + <scope>test</scope> + </dependency> + <dependency> + <groupId>org.jboss.unit</groupId> + <artifactId>portal-test</artifactId> + <scope>test</scope> + <exclusions> + <exclusion> + <groupId>org.codehaus.cargo</groupId> + <artifactId>cargo-core-uberjar</artifactId> + </exclusion> + </exclusions> + </dependency> + <dependency> + <groupId>org.jboss.unit</groupId> + <artifactId>portal-test-generic</artifactId> + <scope>test</scope> + <exclusions> + <exclusion> + <groupId>org.codehaus.cargo</groupId> + <artifactId>cargo-core-uberjar</artifactId> + </exclusion> + </exclusions> + </dependency> +  + <dependency> + <groupId>org.jboss.microcontainer</groupId> + <artifactId>jboss-kernel</artifactId> + <scope>test</scope> + </dependency> + <dependency> + <groupId>org.jboss.microcontainer</groupId> + <artifactId>jboss-dependency</artifactId> + <scope>test</scope> + </dependency> + <dependency> + <groupId>org.jboss</groupId> + <artifactId>jboss-reflect</artifactId> + <scope>test</scope> + </dependency> + <dependency> + <groupId>javax.xml.bind</groupId> + <artifactId>jaxb-api</artifactId> + <scope>test</scope> + </dependency> +  + <dependency> + <groupId>log4j</groupId> + <artifactId>log4j</artifactId> + <scope>test</scope> + </dependency> + <dependency> + <groupId>concurrent</groupId> + <artifactId>concurrent</artifactId> + <scope>test</scope> + </dependency> + <dependency> + <groupId>apache-xerces</groupId> + <artifactId>xercesImpl</artifactId> + <scope>test</scope> + </dependency> + <dependency> + <groupId>apache-xerces</groupId> + <artifactId>xml-apis</artifactId> + <scope>test</scope> + </dependency> + <dependency> + <groupId>jboss</groupId> + <artifactId>jboss-serialization</artifactId> + <scope>test</scope> + </dependency> + + <dependency> + <groupId>commons-discovery</groupId> + <artifactId>commons-discovery</artifactId> + </dependency> + + <dependency> + <groupId>org.jboss.remoting</groupId> + <artifactId>jboss-remoting</artifactId> + </dependency> + + <dependency> + <groupId>org.codehaus.cargo</groupId> + <artifactId>cargo-core-uberjar</artifactId> + <version>${version.cargo}</version> + <scope>test</scope> + </dependency> + + </dependencies> + + + <build> + <plugins> + <plugin> + <artifactId>maven-dependency-plugin</artifactId> + <executions> + <execution> + <id>copy-common-build.xml</id> + <phase>process-resources</phase> + <goals> + <goal>copy</goal> + </goals> + </execution> + </executions> + </plugin> + <plugin> + <artifactId>maven-assembly-plugin</artifactId> + <configuration> + <finalName>test</finalName> + <appendAssemblyId>true</appendAssemblyId> +  + <attach>false</attach> + <outputDirectory>${project.build.directory}/test-archives</outputDirectory> + <descriptors> + <descriptor>src/assembly/spi-native-server.xml</descriptor> + <descriptor>src/assembly/spi-generic-server.xml</descriptor> + <descriptor>src/assembly/spi-exo-server.xml</descriptor> + <descriptor>src/assembly/endpoint-default-servlet-mapping.xml</descriptor> + <descriptor>src/assembly/endpoint-path-mapping.xml</descriptor> + <descriptor>src/assembly/endpoint-root-path-mapping.xml</descriptor> + </descriptors> + </configuration> + <executions> + <execution> + <id>assemble</id> + <phase>test</phase> + <goals> + <goal>single</goal> + </goals> + </execution> + </executions> + </plugin> + <plugin> + <artifactId>maven-antrun-plugin</artifactId> + <dependencies> + + <dependency> + <groupId>org.jboss.unit</groupId> + <artifactId>jboss-unit-tooling-ant</artifactId> + <version>${version.jboss.unit}</version> + </dependency> + <dependency> + <groupId>org.jboss.unit</groupId> + <artifactId>jboss-unit</artifactId> + <version>${version.jboss.unit}</version> + </dependency> + + <dependency> + <groupId>org.codehaus.cargo</groupId> + <artifactId>cargo-ant</artifactId> + <version>${version.cargo}</version> + <exclusions> + <exclusion> + <groupId>ant</groupId> + <artifactId>ant</artifactId> + </exclusion> + </exclusions> + </dependency> + <dependency> + <groupId>org.jdom</groupId> + <artifactId>jdom</artifactId> + <version>1.1</version> + </dependency> + <dependency> + <groupId>dom4j</groupId> + <artifactId>dom4j</artifactId> + <version>1.6.1</version> + </dependency> + <dependency> + <groupId>jaxen</groupId> + <artifactId>jaxen</artifactId> + <version>1.1.1</version> + </dependency> + </dependencies> + <version>1.3</version> + <executions> + <execution> + <id>integration-testing</id> + <phase>integration-test</phase> + <configuration> + <tasks> + +  + <property name="project.build.directory" value="${project.build.directory}" /> + <property name="plugin_classpath" refid="maven.plugin.classpath" /> + <property name="test_classpath" refid="maven.test.classpath" /> + +  +  + <condition property="test.generic.enable"> + <istrue value="${test.generic}" /> + </condition> + <condition property="test.native.enable"> + <istrue value="${test.native}" /> + </condition> + <condition property="test.exo.enable"> + <istrue value="${test.exo}" /> + </condition> + <condition property="test.endpoint.enable"> + <istrue value="${test.endpoint}" /> + </condition> + <condition property="cargo.debug" value="${test.cargo.debug}"> + <isset property="test.cargo.debug" /> + </condition> + <condition property="cargo.debug" value=""> + <not> + <isset property="test.cargo.debug" /> + </not> + </condition> +  + +  + <property name="dependency.jboss-logging-spi.jar" value="${maven.dependency.jboss.jboss-common-logging-spi.jar.path}" /> + <property name="dependency.jboss-logging-jdk.jar" value="${maven.dependency.jboss.jboss-common-logging-jdk.jar.path}" /> + <property name="dependency.jboss-logging-log4j.jar" value="${maven.dependency.jboss.jboss-common-logging-log4j.jar.path}" /> + <property name="dependency.gatein-common-common.jar" value="${maven.dependency.org.gatein.common.common-common.jar.path}" /> + <property name="dependency.gatein-common-logging.jar" value="${maven.dependency.org.gatein.common.common-logging.jar.path}" /> + <property name="dependency.slf4j-api.jar" value="${maven.dependency.org.slf4j.slf4j-api.jar.path}" /> + <property name="dependency.slf4j-simple.jar" value="${maven.dependency.org.slf4j.slf4j-simple.jar.path}" /> + <property name="dependency.log4j.jar" value="${maven.dependency.log4j.log4j.jar.path}" /> + <property name="dependency.activation.jar" value="${maven.dependency.javax.activation.activation.jar.path}" /> + <property name="dependency.junit.jar" value="${maven.dependency.junit.junit.jar.path}" /> + <property name="dependency.gatein-wci-core.jar" value="${maven.dependency.org.gatein.wci.wci-wci.jar.path}" /> + <property name="dependency.gatein-wci-tomcat.jar" value="${maven.dependency.org.gatein.wci.wci-tomcat6.jar.path}" /> + <property name="dependency.gatein-wci-exo.jar" value="${maven.dependency.org.gatein.wci.wci-exo.jar.path}" /> + <property name="dependency.jboss-serialization.jar" value="${maven.dependency.jboss.jboss-serialization.jar.path}" /> + +  + <property name="test.archives.directory" value="${project.build.directory}/test-archives" /> + <property name="test.generic.server.war" value="${test.archives.directory}/test-spi-generic-server.war" /> + <property name="test.native.server.war" value="${test.archives.directory}/test-spi-native-server.war" /> + <property name="test.exo.server.war" value="${test.archives.directory}/test-spi-exo-server.war" /> + + <property name="test.endpoint.default.server.mapping.server.war" value="${test.archives.directory}/test-endpoint-default-servlet-mapping.war" /> + <property name="test.endpoint.root.mapping.server.war" value="${test.archives.directory}/test-endpoint-root-path-mapping.war" /> + <property name="test.endpoint.path.mapping.server.war" value="${test.archives.directory}/test-endpoint-path-mapping.war" /> + + <property name="test.generic.portlet.war" value="${maven.dependency.org.gatein.wci.wci-test-gatein-portlet.war.path}" /> + <property name="test.native.portlet.war" value="${maven.dependency.org.gatein.wci.wci-test-native-portlet.war.path}" /> + <property name="test.exo.portlet.war" value="${maven.dependency.org.gatein.wci.wci-test-exo-portlet.war.path}" /> + +  + <property name="common.xml.file" value="${test.common.xml}" /> +  + + <ant antfile="${basedir}/src/integration-tests/build.xml" inheritRefs="true"> + <target name="tests" /> + </ant> + </tasks> + </configuration> + <goals> + <goal>run</goal> + </goals> + </execution> + </executions> + </plugin> + </plugins> + </build> + <properties> + </properties> + + <profiles> + <profile> + <id>all</id> + <activation> + <activeByDefault>true</activeByDefault> + </activation> + <properties> + <test.generic>true</test.generic> + <test.native>true</test.native> + <test.exo>true</test.exo> + <test.endpoint>true</test.endpoint> + </properties> + </profile> + <profile> + <id>generic</id> + <properties> + <test.generic>true</test.generic> + </properties> + </profile> + <profile> + <id>native</id> + <properties> + <test.native>true</test.native> + </properties> + </profile> + <profile> + <id>exo</id> + <properties> + <test.exo>true</test.exo> + </properties> + </profile> + <profile> + <id>endpoint</id> + <properties> + <test.endpoint>true</test.endpoint> + </properties> + </profile> + <profile> + <id>cargo.debug</id> + <properties> + <test.cargo.debug>-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000</test.cargo.debug> + </properties> + </profile> + </profiles> +</project> Modified: sandbox/as7_support/branches/gatein-as7/wci/wci/pom.xml =================================================================== --- sandbox/as7_support/branches/gatein-as7/wci/wci/pom.xml 2011-10-06 15:53:08 UTC (rev 7683) +++ sandbox/as7_support/branches/gatein-as7/wci/wci/pom.xml 2011-10-06 16:35:19 UTC (rev 7684) @@ -6,7 +6,6 @@ </parent> <modelVersion>4.0.0</modelVersion> <artifactId>wci-wci</artifactId> - <version>2.1.0-Beta07-AS7-Beta01</version> <packaging>jar</packaging> <name>GateIn - Web Container Integration component (wci)</name>

13 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-commits October 2011