December 2012 - gatein-commits - Jboss List Archives

gatein SVN: r8985 - epp/docs/branches/6.0/Release_Notes/en-US.

by do-not-reply＠jboss.org

Author: rdickens Date: 2012-12-09 18:45:57 -0500 (Sun, 09 Dec 2012) New Revision: 8985 Removed: epp/docs/branches/6.0/Release_Notes/en-US/5.2.2_Release_Notes.ent epp/docs/branches/6.0/Release_Notes/en-US/5.2.2_Release_Notes.xml Log: Deleted unwanted files from 5.2.2 release Deleted: epp/docs/branches/6.0/Release_Notes/en-US/5.2.2_Release_Notes.ent =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/5.2.2_Release_Notes.ent 2012-12-09 23:45:51 UTC (rev 8984) +++ epp/docs/branches/6.0/Release_Notes/en-US/5.2.2_Release_Notes.ent 2012-12-09 23:45:57 UTC (rev 8985) @@ -1,14 +0,0 @@ - -<!ENTITY PRODUCT "JBoss Site Publisher"> - - -<!ENTITY BOOKID "Site Publisher Release Notes"> - - -<!ENTITY YEAR "2011"> -<!ENTITY HOLDER "Red Hat, Inc"> - - -<!ENTITY VX "5"> -<!ENTITY VY "5.2"> -<!ENTITY VZ "5.2.2"> Deleted: epp/docs/branches/6.0/Release_Notes/en-US/5.2.2_Release_Notes.xml =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/5.2.2_Release_Notes.xml 2012-12-09 23:45:51 UTC (rev 8984) +++ epp/docs/branches/6.0/Release_Notes/en-US/5.2.2_Release_Notes.xml 2012-12-09 23:45:57 UTC (rev 8985) @@ -1,278 +0,0 @@ -<?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 "5.2.2_Release_Notes.ent"> -%BOOK_ENTITIES; -]> -<book> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> - <part> - <title>General Info</title> - <chapter id="Portal_Platform_Introduction"> - <title>What is Enterprise Portal Platform </title> - <para>JBoss Enterprise Portal Platform offers an intuitive, easy to manage user interface and a proven core infrastructure to enable organizations to quickly build dynamic web sites in a highly reusable way. By bringing the principals of JBoss Open Choice to the presentation layer, JBoss Enterprise Portal Platform 5 maximizes existing skills and technology investments. - </para> - <para>By integrating open source frameworks such as JBoss Seam, Hibernate, Tomcat, and JBoss Cache, JBoss Enterprise Portal Platform takes advantage of innovations in the open source community. </para> - <para>JBoss Enterprise Portal Platform &VZ; is fully tested and supported by Red Hat, and is certified to work on many leading enterprise hardware and software products.</para> - </chapter> - <chapter id="Release_Notes-Installation"> - <title>Installation</title> - <para> - The JBoss Enterprise Portal Platform <citetitle>Installation Guide</citetitle> contains detailed installation instructions as well as environment requirements. - </para> - <para> - The Installation Guide is available in multiple formats from <ulink url="http://access.redhat.com/knowledge/docs/JBoss_Enterprise_Portal_Platform/" type="http"/>. - </para> - </chapter> - <chapter id="Release_Notes-Component_Features"> - <title>Component versions </title> - <remark>Updated table from https://docspace.corp.redhat.com/docs/DOC-68705 (version 34)</remark> - <table frame="all" pgwide="1"> - <title>Component Versions</title> - <tgroup cols="2" colsep="1"> - <colspec colnum="1"/> - <colspec colnum="2"/> - <thead> - <row> - <entry>Component</entry> - <entry>Version</entry> - </row> - </thead> - <tbody> - <row> - <entry>JBoss Enterprise Application Platform</entry> - <entry>5.1.2-GA</entry> - </row> - <row> - <entry>eXo junit</entry> - <entry>1.2.1-GA</entry> - </row> - <row> - <entry>eXo kernel</entry> - <entry>2.3.8-GA</entry> - </row> - <row> - <entry>eXo Core</entry> - <entry>2.4.8-GA</entry> - </row> - <row> - <entry>eXo WS</entry> - <entry>2.2.8-GA</entry> - </row> - <row> - <entry>eXo JCR</entry> - <entry>1.14.8-GA</entry> - </row> - <row> - <entry>Apache Shindig</entry> - <entry>2.0.2-CP01</entry> - </row> - <row> - <entry>Simple Captcha</entry> - <entry>1.1.1-GA-Patch01</entry> - </row> - <row> - <entry>GateIn Parent</entry> - <entry>1.1.0-GA</entry> - </row> - <row> - <entry>GateIn dep</entry> - <entry>1.1.0-GA</entry> - </row> - <row> - <entry>GateIn Common</entry> - <entry>2.0.4-GA</entry> - </row> - <row> - <entry>GateIn WCI</entry> - <entry>2.1.1-GA</entry> - </row> - <row> - <entry>GateIn PC</entry> - <entry>2.3.1-GA</entry> - </row> - <row> - <entry>GateIn WSRP</entry> - <entry>2.1.7-EPP522-GA</entry> - </row> - <row> - <entry>GateIn MOP</entry> - <entry>1.1.2-GA</entry> - </row> - <row> - <entry>GateIn SSO</entry> - <entry>1.1.1-GA</entry> - </row> - <row> - <entry>PicketLink IDM</entry> - <entry>1.3.2.CR01</entry> - </row> - <row> - <entry>Chromattic</entry> - <entry>1.1.3</entry> - </row> - <row> - <entry>Portlet Bridge</entry> - <entry>2.3.1.GA.EPP522</entry> - </row> - <row> - <entry>Seam</entry> - <entry>2.2.5.EAP5</entry> - </row> - <row> - <entry>Richfaces</entry> - <entry>3.3.1.SP3</entry> - </row> - <row> - <entry>Groovy</entry> - <entry>1.7.6</entry> - </row> - <row> - <entry>Commons DBCP</entry> - <entry>1.4</entry> - </row> - <row> - <entry>Commons IO</entry> - <entry>1.4</entry> - </row> - <row> - <entry>Commons Lang</entry> - <entry>2.6</entry> - </row> - <row> - <entry>HSQLDB</entry> - <entry>2.0.0</entry> - </row> - <row> - <entry>JBoss Cache</entry> - <entry>3.2.7</entry> - </row> - <row> - <entry>GateIn Management</entry> - <entry>1.0.1-GA</entry> - </row> - <row> - <entry>GateIn JBossON plug-in</entry> - <entry>1.0.1</entry> - </row> - </tbody> - </tgroup> - </table> - </chapter> - <chapter id="Release_Notes-Documentation"> - <title>Documentation</title> - <para> - An <citetitle>Installation Guide</citetitle> and a <citetitle>User Guide</citetitle> for JBoss Enterprise Portal Platform are available at <ulink url="http://access.redhat.com/knowledge/docs/JBoss_Enterprise_Portal_Platform/" type="http"/>. JBoss Enterprise Portal Platform specific documentation is also available from this location, as is Site Publisher documentation. </para> - <para>In this release, the <citetitle>Installation Guide</citetitle> has undergone heavy rework and is now presented in a task-based narrative style. Any feedback you have regarding this new format would be greatly appreciated. You can provide feedback by following the instructions in the Feedback section located in the preface of the <citetitle>Installation Guide</citetitle>.</para> - </chapter> - <chapter id="Release_Notes-_Product_Support_and_License_Website_Links_"> - <title> Product support links </title> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes"> - <title>Product Update and Support Processes</title> - <para> - <ulink url="https://access.redhat.com/support/policy/updates/jboss_notes/">https://access.redhat.com/support/policy/updates/jboss_notes/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Scope_of_Coverage_"> - <title> Developer Support Scope of Coverage, and Service Level Agreement</title> - <para><ulink url="https://access.redhat.com/support/offerings/developer/">https://access.redhat.com/support/offerings/developer/</ulink> - - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_JBoss_End_User_License_Agreement_"> - <title>Certified and Compatible Configurations</title> - <para> - <ulink url="http://www.jboss.com/products/platforms/portals/testedconfigurations/">http://www.jboss.com/products/platforms/portals/testedconfigurations/</ulink> - </para> - </formalpara> - </chapter> - </part> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="known.xml" encoding="XML"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved.xml"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="enhancement.xml" encoding="XML"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> -</book>

12 years

1
0
0 / 0

gatein SVN: r8984 - epp/docs/branches/6.0/Release_Notes/en-US.

by do-not-reply＠jboss.org

Author: rdickens Date: 2012-12-09 18:45:51 -0500 (Sun, 09 Dec 2012) New Revision: 8984 Modified: epp/docs/branches/6.0/Release_Notes/en-US/Book_Info.xml epp/docs/branches/6.0/Release_Notes/en-US/Revision_History.xml epp/docs/branches/6.0/Release_Notes/en-US/enhancement.xml epp/docs/branches/6.0/Release_Notes/en-US/known.xml epp/docs/branches/6.0/Release_Notes/en-US/resolved.xml Log: Minor changes to skeleton documents in preparation for 6.0.0 Beta Modified: epp/docs/branches/6.0/Release_Notes/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/Book_Info.xml 2012-12-09 23:45:41 UTC (rev 8983) +++ epp/docs/branches/6.0/Release_Notes/en-US/Book_Info.xml 2012-12-09 23:45:51 UTC (rev 8984) @@ -2,14 +2,14 @@ <!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> <bookinfo id="arti-Release_Notes-Release_Notes"> - <title>6.0 Release Notes</title> - <subtitle>For use with JBoss Enterprise Portal Platform &VZ;.</subtitle> - <productname>JBoss Enterprise Portal Platform</productname> - <productnumber>5.2</productnumber> - <edition>5.2.2</edition> + <title>Release Notes</title> + <subtitle>For use with JBoss Portal Platform &VZ;.</subtitle> + <productname>JBoss Portal Platform</productname> + <productnumber>6.0.0</productnumber> + <edition>6.0.0</edition> <abstract> <para> - These release notes contain important information related to JBoss Enterprise Portal Platform &VZ;, and the Site Publisher plug-in that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing the product. + These release notes contain important information related to JBoss Portal Platform &VZ;. You should read these Release Notes in their entirety before installing the product. </para> </abstract> <corpauthor> Modified: epp/docs/branches/6.0/Release_Notes/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/Revision_History.xml 2012-12-09 23:45:41 UTC (rev 8983) +++ epp/docs/branches/6.0/Release_Notes/en-US/Revision_History.xml 2012-12-09 23:45:51 UTC (rev 8984) @@ -2,20 +2,20 @@ <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> <appendix id="appe-Release_Notes-Revision_History"> - <title>Revision history</title> + <title>Revision History</title> <simpara> <revhistory> <revision> - <revnumber>5.2.2-50</revnumber> - <date>Mon Sep 3 2012</date> + <revnumber>6.0.0-1</revnumber> + <date>Fri Dec 7 2012</date> <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> + <firstname>Russell</firstname> + <surname>Dickenson</surname> <email/> </author> <revdescription> <simplelist> - <member>Release Notes prepared for JBoss Enterprise Portal Platform 5.2.2.</member> + <member>Draft Release Notes prepared for JBoss Enterprise Portal Platform 6.0.0 Beta.</member> </simplelist> </revdescription> </revision> Modified: epp/docs/branches/6.0/Release_Notes/en-US/enhancement.xml =================================================================== (Binary files differ) Modified: epp/docs/branches/6.0/Release_Notes/en-US/known.xml =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/known.xml 2012-12-09 23:45:41 UTC (rev 8983) +++ epp/docs/branches/6.0/Release_Notes/en-US/known.xml 2012-12-09 23:45:51 UTC (rev 8984) @@ -1,5 +1,6 @@ <?xml version='1.0'?> -<!DOCTYPE chapter PUBLIC -//OASIS//DTD DocBook XML V4.5//EN http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd []> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> <chapter id="known"> <title>Known Issues</title> <para>There are no Known issues in this release.</para> Modified: epp/docs/branches/6.0/Release_Notes/en-US/resolved.xml =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/resolved.xml 2012-12-09 23:45:41 UTC (rev 8983) +++ epp/docs/branches/6.0/Release_Notes/en-US/resolved.xml 2012-12-09 23:45:51 UTC (rev 8984) @@ -1,5 +1,6 @@ <?xml version='1.0'?> -<!DOCTYPE chapter PUBLIC -//OASIS//DTD DocBook XML V4.5//EN http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd []> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> <chapter id="resolved"> <title>Resolved Issues</title> <para>There are no Resolved Issues in this release.</para>

12 years

1
0
0 / 0

gatein SVN: r8983 - epp/docs/branches/6.0/Release_Notes/en-US.

by do-not-reply＠jboss.org

Author: rdickens Date: 2012-12-09 18:45:41 -0500 (Sun, 09 Dec 2012) New Revision: 8983 Added: epp/docs/branches/6.0/Release_Notes/en-US/Release_Notes.ent epp/docs/branches/6.0/Release_Notes/en-US/Release_Notes.xml Log: Refresh of skeleton documents in preparation for 6.0.0 Beta Added: epp/docs/branches/6.0/Release_Notes/en-US/Release_Notes.ent =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/Release_Notes.ent (rev 0) +++ epp/docs/branches/6.0/Release_Notes/en-US/Release_Notes.ent 2012-12-09 23:45:41 UTC (rev 8983) @@ -0,0 +1,14 @@ + +<!ENTITY PRODUCT "JBoss Portal Platform"> + + +<!ENTITY BOOKID "JBoss Portal Platform Release Notes"> + + +<!ENTITY YEAR "2012"> +<!ENTITY HOLDER "Red Hat, Inc"> + + +<!ENTITY VX "6 Beta"> +<!ENTITY VY "6.0 Beta"> +<!ENTITY VZ "6.0.0 Beta"> Added: epp/docs/branches/6.0/Release_Notes/en-US/Release_Notes.xml =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/Release_Notes.xml (rev 0) +++ epp/docs/branches/6.0/Release_Notes/en-US/Release_Notes.xml 2012-12-09 23:45:41 UTC (rev 8983) @@ -0,0 +1,278 @@ +<?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 "Release_Notes.ent"> +%BOOK_ENTITIES; +]> +<book> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> + <part> + <title>General Info</title> + <chapter id="Portal_Platform_Introduction"> + <title>What is JBoss Portal Platform </title> + <para>JBoss Portal Platform offers an intuitive, easy to manage user interface and a proven core infrastructure to enable organizations to quickly build dynamic web sites in a highly reusable way. By bringing the principles of JBoss Open Choice to the presentation layer, JBoss Portal Platform 6 maximizes existing skills and technology investments. + </para> + <para>By integrating open source frameworks such as JBoss Seam, Hibernate, Tomcat, and JBoss Cache, JBoss Portal Platform takes advantage of innovations in the open source community. </para> + <para>JBoss Enterprise Portal Platform &VZ; is fully tested and supported by Red Hat, and is certified to work on many leading enterprise hardware and software products.</para> + </chapter> + <chapter id="Release_Notes-Installation"> + <title>Installation</title> + <para> + The JBoss Enterprise Portal Platform <citetitle>Installation Guide</citetitle> contains detailed installation instructions as well as environment requirements. + </para> + <para> + The Installation Guide is available in multiple formats from <ulink url="http://access.redhat.com/knowledge/docs/JBoss_Enterprise_Portal_Platform/" type="http"/>. + </para> + </chapter> + <chapter id="Release_Notes-Component_Features"> + <title>Component versions </title> + <remark>Updated table from https://docspace.corp.redhat.com/docs/DOC-68705 (version 34)</remark> + <table frame="all" pgwide="1"> + <title>Component Versions</title> + <tgroup cols="2" colsep="1"> + <colspec colnum="1"/> + <colspec colnum="2"/> + <thead> + <row> + <entry>Component</entry> + <entry>Version</entry> + </row> + </thead> + <tbody> + <row> + <entry>JBoss Enterprise Application Platform</entry> + <entry>5.1.2-GA</entry> + </row> + <row> + <entry>eXo junit</entry> + <entry>1.2.1-GA</entry> + </row> + <row> + <entry>eXo kernel</entry> + <entry>2.3.8-GA</entry> + </row> + <row> + <entry>eXo Core</entry> + <entry>2.4.8-GA</entry> + </row> + <row> + <entry>eXo WS</entry> + <entry>2.2.8-GA</entry> + </row> + <row> + <entry>eXo JCR</entry> + <entry>1.14.8-GA</entry> + </row> + <row> + <entry>Apache Shindig</entry> + <entry>2.0.2-CP01</entry> + </row> + <row> + <entry>Simple Captcha</entry> + <entry>1.1.1-GA-Patch01</entry> + </row> + <row> + <entry>GateIn Parent</entry> + <entry>1.1.0-GA</entry> + </row> + <row> + <entry>GateIn dep</entry> + <entry>1.1.0-GA</entry> + </row> + <row> + <entry>GateIn Common</entry> + <entry>2.0.4-GA</entry> + </row> + <row> + <entry>GateIn WCI</entry> + <entry>2.1.1-GA</entry> + </row> + <row> + <entry>GateIn PC</entry> + <entry>2.3.1-GA</entry> + </row> + <row> + <entry>GateIn WSRP</entry> + <entry>2.1.7-EPP522-GA</entry> + </row> + <row> + <entry>GateIn MOP</entry> + <entry>1.1.2-GA</entry> + </row> + <row> + <entry>GateIn SSO</entry> + <entry>1.1.1-GA</entry> + </row> + <row> + <entry>PicketLink IDM</entry> + <entry>1.3.2.CR01</entry> + </row> + <row> + <entry>Chromattic</entry> + <entry>1.1.3</entry> + </row> + <row> + <entry>Portlet Bridge</entry> + <entry>2.3.1.GA.EPP522</entry> + </row> + <row> + <entry>Seam</entry> + <entry>2.2.5.EAP5</entry> + </row> + <row> + <entry>Richfaces</entry> + <entry>3.3.1.SP3</entry> + </row> + <row> + <entry>Groovy</entry> + <entry>1.7.6</entry> + </row> + <row> + <entry>Commons DBCP</entry> + <entry>1.4</entry> + </row> + <row> + <entry>Commons IO</entry> + <entry>1.4</entry> + </row> + <row> + <entry>Commons Lang</entry> + <entry>2.6</entry> + </row> + <row> + <entry>HSQLDB</entry> + <entry>2.0.0</entry> + </row> + <row> + <entry>JBoss Cache</entry> + <entry>3.2.7</entry> + </row> + <row> + <entry>GateIn Management</entry> + <entry>1.0.1-GA</entry> + </row> + <row> + <entry>GateIn JBossON plug-in</entry> + <entry>1.0.1</entry> + </row> + </tbody> + </tgroup> + </table> + </chapter> + <chapter id="Release_Notes-Documentation"> + <title>Documentation</title> + <para> + An <citetitle>Installation Guide</citetitle> and a <citetitle>User Guide</citetitle> for JBoss Enterprise Portal Platform are available at <ulink url="http://access.redhat.com/knowledge/docs/JBoss_Enterprise_Portal_Platform/" type="http"/>. JBoss Enterprise Portal Platform specific documentation is also available from this location.</para> + <para>In this release, the <citetitle>Installation Guide</citetitle> has undergone heavy rework and is now presented in a task-based narrative style. Any feedback you have regarding this new format would be greatly appreciated. You can provide feedback by following the instructions in the Feedback section located in the preface of the <citetitle>Installation Guide</citetitle>.</para> + </chapter> + <chapter id="Release_Notes-_Product_Support_and_License_Website_Links_"> + <title> Product support links </title> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes"> + <title>Product Update and Support Processes</title> + <para> + <ulink url="https://access.redhat.com/support/policy/updates/jboss_notes/">https://access.redhat.com/support/policy/updates/jboss_notes/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Scope_of_Coverage_"> + <title> Developer Support Scope of Coverage, and Service Level Agreement</title> + <para><ulink url="https://access.redhat.com/support/offerings/developer/">https://access.redhat.com/support/offerings/developer/</ulink> + + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_JBoss_End_User_License_Agreement_"> + <title>Certified and Compatible Configurations</title> + <para> + <ulink url="http://www.jboss.com/products/platforms/portals/testedconfigurations/">http://www.jboss.com/products/platforms/portals/testedconfigurations/</ulink> + </para> + </formalpara> + </chapter> + </part> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="known.xml" encoding="XML"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="enhancement.xml" encoding="XML"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> +</book>

12 years

1
0
0 / 0

gatein SVN: r8982 - epp/docs/branches/6.0/Release_Notes/en-US.

by do-not-reply＠jboss.org

Author: rdickens Date: 2012-12-09 18:45:33 -0500 (Sun, 09 Dec 2012) New Revision: 8982 Removed: epp/docs/branches/6.0/Release_Notes/en-US/sp_known.xml epp/docs/branches/6.0/Release_Notes/en-US/sp_needinfo.xml epp/docs/branches/6.0/Release_Notes/en-US/sp_resolved.xml Log: Deleted unwanted placeholders files for Site Publisher Deleted: epp/docs/branches/6.0/Release_Notes/en-US/sp_known.xml =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/sp_known.xml 2012-12-07 17:35:52 UTC (rev 8981) +++ epp/docs/branches/6.0/Release_Notes/en-US/sp_known.xml 2012-12-09 23:45:33 UTC (rev 8982) @@ -1,24 +0,0 @@ -<?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" [ -]> -<chapter id="sp_known_issues"> - <title>Known issues</title> - <para>The following issues are known to exist in this release of the JBoss Enterprise Portal Platform Site Publisher Add-on, and will be fixed in a subsequent release.</para> - <variablelist> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=846276"> - <citetitle>BZ#846276</citetitle> - </ulink> - Include upgrade binaries in SP package</term> - <listitem> - <remark>Status: ASSIGNED</remark> - <para> -When migrating from EPP-SP 5.1.x to EPP-SP 5.2.x, the templates stored in the JCR database need to be updated to the latest version. -</para> - <para> -Red Hat is providing binaries which automatically convert the templates, as documented in this Red Hat Knowledgebase (KBase) article: https://access.redhat.com/knowledge/solutions/200333 -</para> - <para>Customers who are using Site Publisher in their implementation, must follow the instructions in the KBase to ensure correct operation of Site Publisher. </para> - </listitem> - </varlistentry> - </variablelist> -</chapter> Deleted: epp/docs/branches/6.0/Release_Notes/en-US/sp_needinfo.xml =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/sp_needinfo.xml 2012-12-07 17:35:52 UTC (rev 8981) +++ epp/docs/branches/6.0/Release_Notes/en-US/sp_needinfo.xml 2012-12-09 23:45:33 UTC (rev 8982) @@ -1,16 +0,0 @@ -<?xml version='1.0'?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -]> - -<chapter id = "sp_needinfo_issues"> - <title>NEEDINFO</title> - <para>The following issues require more information from developers, or need to be processed by the lead writer before they can be approved for Release Note inclusion.</para> - <remark> - These tickets will not be included in Release Notes as they currently stand. - This could be because the tickets have not been docs Ack'd (still at release_note?) - or the tickets have not been set to the correct resolution status (VERIFIED, CLOSED). - </remark> - <variablelist> - - </variablelist> -</chapter> Deleted: epp/docs/branches/6.0/Release_Notes/en-US/sp_resolved.xml =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/sp_resolved.xml 2012-12-07 17:35:52 UTC (rev 8981) +++ epp/docs/branches/6.0/Release_Notes/en-US/sp_resolved.xml 2012-12-09 23:45:33 UTC (rev 8982) @@ -1,30 +0,0 @@ -<?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" [ -]> -<chapter id="sp_resolved"> - <title>Resolved issues</title> - <para>Site Publisher issues affecting this release were fixed upstream in eXo Platform.</para> -</chapter>

12 years

1
0
0 / 0

gatein SVN: r8981 - epp/docs/branches/6.0/Reference_Guide/en-US.

by do-not-reply＠jboss.org

Author: ppenicka Date: 2012-12-07 12:35:52 -0500 (Fri, 07 Dec 2012) New Revision: 8981 Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml Log: One more revosion history correction, this time modification dates were not in chronological order. Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2012-12-07 17:31:46 UTC (rev 8980) +++ epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2012-12-07 17:35:52 UTC (rev 8981) @@ -21,8 +21,22 @@ </simplelist> </revdescription> </revision> + <revision> + <revnumber>6.0.0-24</revnumber> + <date>Tue Dec 04 2012</date> + <author> + <firstname>Jared</firstname> + <surname>Morgan</surname> + <email/> + </author> + <revdescription> + <simplelist> + <member>BZ#856430 - Incorporated final changes by Marek for CAS. These changes are considered final, and ready for release.</member> + </simplelist> + </revdescription> + </revision> <revision> - <revnumber>6.0.0-24</revnumber> + <revnumber>6.0.0-23</revnumber> <date>Fri Nov 30 2012</date> <author> <firstname>Scott</firstname> @@ -36,20 +50,6 @@ </revdescription> </revision> <revision> - <revnumber>6.0.0-23</revnumber> - <date>Tue Dec 04 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856430 - Incorporated final changes by Marek for CAS. These changes are considered final, and ready for release.</member> - </simplelist> - </revdescription> - </revision> - <revision> <revnumber>6.0.0-22</revnumber> <date>Fri Nov 30 2012</date> <author>

12 years

1
0
0 / 0

gatein SVN: r8980 - epp/docs/branches/6.0/Reference_Guide/en-US.

by do-not-reply＠jboss.org

Author: ppenicka Date: 2012-12-07 12:31:46 -0500 (Fri, 07 Dec 2012) New Revision: 8980 Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml Log: Just fixed pubs numbers in revision history. Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2012-12-07 17:27:30 UTC (rev 8979) +++ epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2012-12-07 17:31:46 UTC (rev 8980) @@ -8,7 +8,7 @@ <simpara> <revhistory> <revision> - <revnumber>6.0.0-24</revnumber> + <revnumber>6.0.0-25</revnumber> <date>Fri Dec 7 2012</date> <author> <firstname>Petr</firstname> @@ -22,7 +22,7 @@ </revdescription> </revision> <revision> - <revnumber>6.0.0-22</revnumber> + <revnumber>6.0.0-24</revnumber> <date>Fri Nov 30 2012</date> <author> <firstname>Scott</firstname>

12 years

1
0
0 / 0

gatein SVN: r8979 - in epp/docs/branches/6.0/Reference_Guide/en-US: modules/AuthenticationAndIdentity and 1 other directory.

by do-not-reply＠jboss.org

Author: ppenicka Date: 2012-12-07 12:27:30 -0500 (Fri, 07 Dec 2012) New Revision: 8979 Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml Log: BZ#856450: modified information about SSO in a cluster based on an updated Confluence document. Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2012-12-05 04:55:31 UTC (rev 8978) +++ epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2012-12-07 17:27:30 UTC (rev 8979) @@ -8,6 +8,20 @@ <simpara> <revhistory> <revision> + <revnumber>6.0.0-24</revnumber> + <date>Fri Dec 7 2012</date> + <author> + <firstname>Petr</firstname> + <surname>Penicka</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>BZ#856450: modified information about SSO in a cluster based on an updated Confluence document.</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>6.0.0-22</revnumber> <date>Fri Nov 30 2012</date> <author> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2012-12-05 04:55:31 UTC (rev 8978) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2012-12-07 17:27:30 UTC (rev 8979) @@ -4,11 +4,11 @@ %BOOK_ENTITIES; ]> <chapter id="sect-Reference_Guide-SSO_Single_Sign_On"> - <title>SSO - Single Sign On</title> + <title>Single Sign-On</title> <section id="sect-SSO_Single_Sign_On_-Overview"> <title>Overview and Configuration Assumptions</title> <para> -JBoss Portal Platform provides an implementation of Single Sign On (<literal>SSO</literal>) as an integration and aggregation platform. +JBoss Portal Platform provides an implementation of single sign-on (<literal>SSO</literal>) as an integration and aggregation platform. </para> <para> When logging into the portal, users can access many systems through portlets using a single identity. In many cases, however, the portal infrastructure must be integrated with other SSO enabled systems. @@ -62,279 +62,9 @@ Remove <filename>JBOSS_HOME/server/PROFILE/deploy/gatein-sample-extension.ear</filename> and <filename>JBOSS_HOME/server/PROFILE/deploy/gatein-sample-portal.ear</filename> which are packaged by default with JBoss Enterprise Portal Platform. </para> --> </warning> </section> - <section id="sect-SSO_Single_Sign_On_-Enabling_SSO_using_JBoss_SSO_Valve"> - <title><remark>NEEDINFO</remark>Enabling SSO using JBoss SSO Valve</title> - <remark>Is the SSO valve still valid for JPP 6?</remark> - <para> - The JBoss SSO valve is useful to authenticate a user on one JBoss Portal Platform node in a cluster and have that authentication automatically carry across to other nodes in the cluster. - </para> - <para> - This authentication can also be used in any other web applications which may require authentication, <emphasis role="bold">provided that these applications use same roles as the main portal instance</emphasis>. Attempting to use an SSO authentication in an application that uses different roles may create authorization errors (<emphasis role="bold">403</emphasis> errors, for example). - </para> - <note> - <title>Reauthentication</title> - <para> - This behavior is coming from the fact that same JAAS principal is added by SSO valve to all HTTP requests, even to other web applications. - </para> - <para> - So the same roles are required because of it. There is an alternative that allows you to configure the SSO valve with the <parameter>requireReauthentication=true</parameter> parameter, which will force the SSO valve to perform reauthentication with saved credentials in each HTTP request against security domain of particular web application where the request is coming. - </para> - <para> - This will ensure that a new principal for that web application will be created with updated roles for that web application. - </para> - <para> - In other words; when <parameter>requireReauthentication</parameter> is <emphasis role="bold">false</emphasis> (the default state), you need to have the same roles among web applications. When <parameter>requireReauthentication</parameter> is <emphasis role="bold">true</emphasis> you need to have same username and passwords. - </para> - </note> - <para> - More info about the JBoss SSO valve can be found at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Web_Platform/5/html/Ad..." type="http"/>. - </para> - <para> - To successfully implement SSO integration, do the following: - </para> - <procedure id="proc-Reference_Guide-Enabling_SSO_using_JBoss_SSO_Valve-SSO_Integration"> - <title>SSO Integration</title> - <remark>The file paths in this procedure need to be verified if this procedure is to remain for JPP 6</remark> - <step> - <para> - Open the <filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/jbossweb.sar/server.xml</filename> file and uncomment one of the two <parameter>Valve</parameter> entries: - </para> - <itemizedlist> - <listitem> - <para> - For a <emphasis>non-clustered</emphasis> implementation, uncomment: - </para> - <programlisting language="XML" role="XML"><Valve className="org.apache.catalina.authenticator.SingleSignOn" /> -</programlisting> - </listitem> - <listitem> - <para> - For a <emphasis>clustered</emphasis> implementation, uncomment: - </para> - <programlisting language="XML" role="XML"><Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" /></programlisting> - </listitem> - </itemizedlist> - </step> - <step> - <para> - For implementation of the SSO valve among the different nodes of cluster, all the nodes must share the same domain (<emphasis>node1.yourdomain.com</emphasis> and <emphasis>node2.yourdomain.com</emphasis>, for example). - </para> - <para> - This domain needs to be configured in the SSO valve parameter <parameter>cookieDomain</parameter>. This is required because the SSO valve adds the cookie <emphasis role="bold">JSESSIONIDSSO</emphasis>, which is, by default bound only to the host where the request is originating. - </para> - <para> - When the <parameter>cookieDomain</parameter> parameter is used, the cookie is bound to the domain (like <emphasis>yourdomain.com</emphasis>), which will ensure that it is shared among both hosts <emphasis>node1.yourdomain.com</emphasis> and <emphasis>node2.yourdomain.com</emphasis>. - </para> - <para> - So in this case, the valve configuration would be: - </para> - <programlisting language="XML" role="XML"><Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" -cookieDomain="yourdomain.com" /> -</programlisting> - </step> - <step> - <para> - Another important thing is that both cluster nodes needs to be on same cluster (using same parameter <emphasis role="bold">-g</emphasis> and same parameter <emphasis role="bold">-u</emphasis> and also using parameter <emphasis role="bold">-Dexo.profiles=cluster</emphasis>). - </para> - <para> - They must also share the same NFS directory and the same database and apply all the configuration needed for JBoss Portal Platform cluster. - </para> - </step> - </procedure> - <formalpara id="form-Reference_Guide-Enabling_SSO_using_JBoss_SSO_Valve-Testing_SSO_in_a_physical_cluster"> - <title>Testing SSO in a physical cluster</title> - <para> - In this example, we will try to simulate testing on more physical machines by simply using virtual hosts on single machine. - </para> - </formalpara> - <procedure id="proc-Reference_Guide-Enabling_SSO_using_JBoss_SSO_Valve-Testing_the_SSO_Valve"> - <title>Testing the SSO Valve</title> - <remark>The file paths in this procedure need to be verified if this procedure is to remain for JPP 6</remark> - <step> - <para> - If you are using a Linux system, you can configure file <emphasis role="bold">/etc/hosts</emphasis> to contain these lines: - </para> - <programlisting> -127.0.1.1 machine1.yourdomain.com -127.0.1.2 machine2.yourdomain.com -</programlisting> - </step> - <step> - <para> - Open the <filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/all/<replaceable>PROFILE</replaceable>/jbossweb.sar/server.xml</filename> file. - </para> - </step> - <step> - <para> - Uncomment the line: - </para> - <programlisting language="XML" role="XML"> -</programlisting> - </step> - <step> - <para> - And edit it to match the following: - </para> - <programlisting language="XML" role="XML"><Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" -cookieDomain="yourdomain.com" /> -</programlisting> - <para> - This will ensure the <literal>JSESSIONIDSSO</literal> cookie is used in the correct domain, allowing the SSO authentication to occur. - </para> - </step> - <step> - <para> - Copy server configuration <emphasis role="bold">all</emphasis> and create another two configurations <emphasis role="bold">node1</emphasis> and <emphasis role="bold">node2</emphasis> from it. - </para> - </step> - <step> - <para> - Start both cluster nodes with commands: - </para> - <programlisting> -./run.sh -c node1 -b machine1.yourdomain.com -Dexo.profiles=cluster -Djboss.messaging.ServerPeerID=0 & -./run.sh -c node2 -b machine2.yourdomain.com -Dexo.profiles=cluster -Djboss.messaging.ServerPeerID=1 & -</programlisting> - </step> - <step> - <para> - Go to <uri>http://machine1.yourdomain.com:8080/portal</uri> and login as a user. - </para> - </step> - <step> - <para> - Access a private URL on the second host, such as <uri>http://machine2.yourdomain.com:8080/portal/dologin</uri>, for example. - </para> - <para> - Now you should be logged directly into <literal>machine2</literal> thanks to SSO valve. - </para> - </step> - <step> - <para> - Logout from SSO initiating machine1.yourdomain.com should also logged you out from other cluster nodes. So you should be logout directly from machine2 as well. - </para> - </step> - </procedure> - <remark>The file paths in this procedure need to be verified if this procedure is to remain for JPP 6</remark> - <formalpara id="form-Reference_Guide-Enabling_SSO_using_JBoss_SSO_Valve-Enabling_SSO_with_Other_Web_Applications"> - <title>Enabling SSO with Other Web Applications</title> - <para> - As mentioned earlier, in order to use SSO authentication between JBoss Portal Platform instances and other web applications, the roles defined in the web application must match those used in the portal instance (unless you have the <parameter>requireReauthentication</parameter> parameter set to <literal>true</literal>). - </para> - </formalpara> - <para> - As an example, to use the SSO Valve to authenticate a user in both a portal instance and the JMX Console, the following actions would be required: - </para> - <procedure> - <title/> - <step> - <para> - Open the <filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/node1/deploy/jmx-console.war/WEB-INF/web.xml</filename> file and edit it as follows: - </para> - <substeps> - <step> - <para> - Change the <parameter><role-name></parameter> entry in the <parameter><auth-constraint></parameter> element (line <literal>110</literal>) from <literal>JBossAdmin</literal> to <literal>users</literal>: - </para> - <programlisting language="XML" role="XML"><auth-constraint> -  - <role-name>users</role-name> -</auth-constraint></programlisting> - </step> - <step> - <para> - Change the <parameter><role-name></parameter> entry in the <parameter><security-role></parameter> element (line <literal>120</literal>) from <literal>JBossAdmin</literal> to <literal>users</literal> - </para> - <programlisting language="XML" role="XML"><security-role> -  - <role-name>users</role-name> -</security-role></programlisting> - </step> - </substeps> - </step> - </procedure> - <formalpara id="form-Reference_Guide-Enabling_SSO_using_JBoss_SSO_Valve-Testing_SSO_With_Other_Web_Applications"> - <title>Testing SSO With Other Web Applications</title> - <para> - To test that SSO authentication is enabled from portal instances to other web applications (in this case, the JMX Console), do the following: - </para> - </formalpara> - <procedure id="proc-Reference_Guide-Enabling_SSO_using_JBoss_SSO_Valve-Test_SSO_Between_Portal_and_JMX_Console"> - <title>Test SSO Between Portal and JMX Console</title> - <remark>The file paths in this procedure need to be verified if this procedure is to remain for JPP 6</remark> - <step> - <para> - Start a portal instance on one node: - </para> - <programlisting>./run.sh -c node1 -b machine1.yourdomain.com -Dexo.profiles=cluster -Djboss.messaging.ServerPeerID=0 & -</programlisting> - </step> - <step> - <para> - Navigate to <uri>http://machine1.yourdomain.com:8080/portal/private/classic</uri> and authenticate with the pre-configured user account "<systemitem>root</systemitem>" (password "<systemitem>gtn </systemitem>"). - </para> - </step> - <step> - <para> - Navigate to <uri>http://machine1.yourdomain.com:8080/jmx-console</uri>. You should be automatically authenticated into the JMX Console. - </para> - </step> - </procedure> - <formalpara id="form-Reference_Guide-Enabling_SSO_using_JBoss_SSO_Valve-Using_SSO_to_Authenticate_From_the_Public_Page"> - <title>Using SSO to Authenticate From the Public Page</title> - <para> - The previous configuration changes in this section are useful if a user is using a secured URL (<ulink url="http://localhost:8080/portal/private/classic" type="http"/>, for example) to log in to the portal instance. - </para> - </formalpara> - <para> - Further changes are needed however, if SSO authentication is required to work with the <guilabel>Sign In</guilabel> button on the front page of the portal (<ulink url="http://localhost:8080/portal/classic" type="http"/>). - </para> - <para> - To enable this functionality, the <guilabel>Sign In</guilabel> link must redirect to some secured URL, which will ensure that JAAS authentication will be enforced directly without showing login dialog. - </para> - <procedure id="proc-Reference_Guide-Enabling_SSO_using_JBoss_SSO_Valve-Redirect_to_Use_SSO_Valve_Authentication"> - <title>Redirect to Use SSO Valve Authentication</title> - <remark>The file paths in this procedure need to be verified if this procedure is to remain for JPP 6</remark> - <step> - <para> - Open the <filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/web.war/groovy/groovy/webui/component/UIBannerPortlet.gtml</filename> file and edit the line: - </para> - <programlisting language="Java" role="java"><a class="Login" onclick="$signInAction"><%=_ctx.appRes("UILoginForm.label.Signin")%></a> -</programlisting> - <para> - To read: - </para> - <programlisting language="Java" role="java"><a class="Login" href="/portal/private/classic"><%=_ctx.appRes("UILoginForm.label.Signin")%></a> -</programlisting> - </step> - <step> - <para> - Open the <filename><replaceable>JPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/web.war/groovy/portal/webui/component/UILogoPortlet.gtmpl</filename> file and change the line: - </para> - <programlisting language="Java" role="java"><a onclick="$signInAction"><%=_ctx.appRes("UILogoPortlet.action.signin")%></a> -</programlisting> - <para> - To read: - </para> - <programlisting language="Java" role="java"><a href="/portal/private/classic"><%=_ctx.appRes("UILogoPortlet.action.signin")%></a> -</programlisting> - </step> - </procedure> - </section> <section id="sect-SSO_Single_Sign_On_-Central_Authentication_Service"> <title><remark>BZ#856430</remark>Central Authentication Service (CAS)</title> - <para>The CAS Single Sign On (SSO) plug-in enables seamless integration between the platform and the CAS SSO framework. General information about CAS can be found on the + <para>The CAS single sign-on (SSO) plug-in enables seamless integration between the platform and the CAS SSO framework. General information about CAS can be found on the <ulink url="http://www.jasig.org/cas">Jasig website</ulink> . </para> @@ -774,9 +504,9 @@ </section> <section id="sect-Reference_Guide-SSO_Single_Sign_On_-Java_Open_Single_Sign_On_Project"> <title>Java Open Single Sign-On Project</title> - <para>Configuring JOSSO for JBoss Enterprise Application Platform requires an Apache server instance to host JOSSO. JBoss Enterprise Application Platform communicates with the JOSSO Apache instance through the Single Sign On plug-in.</para> + <para>Configuring JOSSO for JBoss Enterprise Application Platform requires an Apache server instance to host JOSSO. JBoss Enterprise Application Platform communicates with the JOSSO Apache instance through the single sign-on plug-in.</para> <para> - This Single Sign On plug-in enables seamless integration between JBoss Portal Platform and the Java Open Single Sign-On Project (JOSSO) Single Sign On Framework. Details about JOSSO can be found at <ulink url="http://www.josso.org"/> . + This single sign-on plug-in enables seamless integration between JBoss Portal Platform and the Java Open Single Sign-On (JOSSO) framework. Details about JOSSO can be found at <ulink url="http://www.josso.org"/> . </para> <para> The procedures in this section detail setting up the JOSSO server to authenticate against the JBoss Portal Platform login module. </para> @@ -1241,7 +971,7 @@ </step> <step> <para> - The user experiences a seamless single sign on (SSO) into the web application. + The user experiences a seamless single sign-on (SSO) into the web application. </para> </step> </procedure> @@ -1619,8 +1349,117 @@ Clicking the 'Sign In' link on the JBoss Portal Platform should automatically sign the 'demo' user into the portal. </para> <para> - If you destroy your kerberos ticket with command <command>kdestroy</command>, then try to login again, you will directed to the login screen of JBoss Enterprise Portal Product because you do not have active Kerberos ticket. You can login with predefined account and password "demo"/"gtn" . + If you destroy your kerberos ticket with command <command>kdestroy</command>, then try to login again, you will directed to the login screen of JBoss Portal Platform because you do not have active Kerberos ticket. You can login with predefined account and password "demo"/"gtn" . </para> + </section> + </section> + <section id="sect-SSO_Single_Sign_On_-Enabling_SSO_using_JBoss_SSO_Valve"> + <title>Single Sign-On in a Cluster</title> + + <para> + In a cluster, the JBoss SSO valve can be used to authenticate a user on one JBoss Portal Platform node and have that authentication automatically carried across to other nodes in the cluster. + </para> + <section id="sect-SSO_Single_Sign_On_-Enabling_SSO_using_JBoss_SSO_Valve-Default_Config"> + <title>Default Configuration</title> + <para> + The JBoss SSO valve is enabled by default. The enablement is ensured by the following JBoss Web subsystem configuration entry in the <filename>JPP_DIST/standalone/configuration/standalon-ha.xml</filename> file: + </para> +<programlisting language="XML"><![CDATA[ +<sso cache-container="web" cache-name="sso" reauthenticate="false" /> +]]></programlisting> + <para> + When a loadbalancer is used in a cluster, no further configuration is needed to set up single sign-on. All JBoss Portal Platform servers in the cluster are accessed through the same URL, which is the URL of the loadbalancer. Automatic single sign-on is performed when the loadbalancer redirects client requests to individual nodes in the cluster. + </para> </section> + <section> + <title>Clustered Single-Sign On in a Shared DNS Domain</title> + <para> + If multiple JBoss Portal Platform servers are accessed through different URLs in the same DNS domain, single sign-on can be configured by adding the <parameter>domain</parameter> parameter to the <parameter>sso</parameter> configuration entry. + </para> +<programlisting language="XML"><![CDATA[ +<sso cache-container="web" cache-name="sso" reauthenticate="false" domain="yourdomain.com"/> +]]></programlisting> + <para> + The parameter must be added to the entry on all servers in the cluster and the name of the shared DNS domain must be specified as its value. This configuration ensures that the <parameter>JSESSIONIDSSO</parameter> cookie will be scoped to the specified domain, which is otherwise scoped only to the host where the initial authentication was performed. + </para> + <para> + The following procedure demonstrates how to configure and test single sign-on for two JBoss Portal Platform servers running in a shared domain on the same physical Linux machine. + </para> + <procedure id="proc-Reference_Guide-Enabling_SSO_using_JBoss_SSO_Valve-Testing_the_SSO_Valve"> + <title>Configuring and Testing Single-Sign On in a Shared DNS Domain</title> + <step> + <para> + Add the following lines to the <emphasis role="bold">/etc/hosts</emphasis> file. Modify the IP addresses in accordance with the IP addresses of the two JBoss Portal Platform servers. + </para> +<programlisting> +127.0.1.1 machine1.yourdomain.com +127.0.1.2 machine2.yourdomain.com +</programlisting> + </step> + <step> + <para> + On both servers, open the <filename><replaceable>JPP_DIST</replaceable>/standalone/configuration/standalone-ha.xml</filename> file. Add the <parameter>domain</parameter> parameter to the <parameter>sso</parameter> entry and specify the name of the shared DNS domain in its value. + </para> +<programlisting language="XML"><![CDATA[ +<sso cache-container="web" cache-name="sso" reauthenticate="false" domain="yourdomain.com"/> +]]></programlisting> + </step> + <step> + <para> + Start the first server using the following command: + </para> +<programlisting> +./standalone.sh -b machine1.yourdomain.com -c standalone-ha.xml -Djboss.node.name=node1 +</programlisting> + </step> + <step> + <para> + Start the second server using the following command: + </para> +<programlisting> +./standalone.sh -b machine2.yourdomain.com -c standalone-ha.xml -Djboss.node.name=node2 +</programlisting> + </step> + <step> + <para> + Access the first server at <ulink url="http://machine1.yourdomain.com:8080/portal">http://machine1.yourdomain.com:8080/portal</ulink> and log in as a user. + </para> + </step> + <step> + <para> + Access the second server at <ulink url="http://machine2.yourdomain.com:8080/portal">http://machine2.yourdomain.com:8080/portal</ulink>. When the page loads, you will be automatically logged in with the same user account that you used on the first server. + </para> + </step> + <step> + <para> + Log out on any of the two servers. Then switch to the other server and verify that you have been logged out of this server as well. + </para> + </step> + </procedure> + </section> + <section id="sect-SSO_Single_Sign_On_-Enabling_SSO_using_JBoss_SSO_Valve-Other_Web_Apps"> + <title>Reauthentication</title> + <para> + The JBoss SSO valve can also be used to authenticate with any other web application. If that application uses the same roles as the main JBoss Portal Platform instance, no further configuration is required. Because the JBoss SSO valve includes the same JAAS principal in all HTTP requests, even in requests to other web applications, matching roles ensure successful authentication with those applications. + </para> + <para> + To enable single sing-on authentication with an application that uses different roles, you need to set the <parameter>reauthenticate</parameter> parameter of the <parameter>sso</parameter> JBoss Web subsystem configuration entry to <literal>true</literal>. + </para> +<programlisting language="XML"><![CDATA[ +<sso cache-container="web" cache-name="sso" reauthenticate="true" /> +]]></programlisting> + <para> + The <literal>true</literal> value ensures that reauthentication with user credentials will be performed against the web application's security domain in each HTTP request. This will enforce creation of a new principal with updated roles for the web application. As user credentials are used for authentication in this case, it is required that the same user credentials exist in both the web application and the JBoss Portal Platform instance. + </para> + </section> </section> </chapter>

12 years

1
0
0 / 0

gatein SVN: r8978 - in epp/docs/branches/6.0/Reference_Guide/en-US: modules/PortalDevelopment and 1 other directory.

by do-not-reply＠jboss.org

Author: smumford Date: 2012-12-04 23:55:31 -0500 (Tue, 04 Dec 2012) New Revision: 8978 Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/PortalLifecycle.xml Log: Resolved svn conflict Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2012-12-04 07:06:38 UTC (rev 8977) +++ epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2012-12-05 04:55:31 UTC (rev 8978) @@ -7,6 +7,20 @@ <title>Revision History</title> <simpara> <revhistory> + <revision> + <revnumber>6.0.0-22</revnumber> + <date>Fri Nov 30 2012</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>BZ#807499: Added SME approved content regarding advanced WCI registration features.</member> + </simplelist> + </revdescription> + </revision> <revision> <revnumber>6.0.0-23</revnumber> <date>Tue Dec 04 2012</date> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/PortalLifecycle.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/PortalLifecycle.xml 2012-12-04 07:06:38 UTC (rev 8977) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/PortalLifecycle.xml 2012-12-05 04:55:31 UTC (rev 8978) @@ -87,10 +87,10 @@ <url-pattern>/gateinservlet</url-pattern> </servlet-mapping> ]]></programlisting> - </listitem> - </varlistentry> - </variablelist> - </section> + </listitem> + </varlistentry> + </variablelist> + </section> </section> <section id="sect-Reference_Guide-Portal_Life_cycle-The_Command_Servlet"> <title>The Command Servlet</title>

12 years

1
0
0 / 0

gatein SVN: r8977 - in epp/docs/branches/6.0/Reference_Guide/en-US: modules/AuthenticationAndIdentity and 1 other directories.

by do-not-reply＠jboss.org

Author: jaredmorgs Date: 2012-12-04 02:06:38 -0500 (Tue, 04 Dec 2012) New Revision: 8977 Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/PortalLifecycle.xml Log: BZ#856430 - Final incorporations for CAS work now committed, and staged Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2012-11-30 04:15:42 UTC (rev 8976) +++ epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2012-12-04 07:06:38 UTC (rev 8977) @@ -8,6 +8,20 @@ <simpara> <revhistory> <revision> + <revnumber>6.0.0-23</revnumber> + <date>Tue Dec 04 2012</date> + <author> + <firstname>Jared</firstname> + <surname>Morgan</surname> + <email/> + </author> + <revdescription> + <simplelist> + <member>BZ#856430 - Incorporated final changes by Marek for CAS. These changes are considered final, and ready for release.</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>6.0.0-22</revnumber> <date>Fri Nov 30 2012</date> <author> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml 2012-11-30 04:15:42 UTC (rev 8976) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml 2012-12-04 07:06:38 UTC (rev 8977) @@ -122,7 +122,7 @@ </para> </formalpara> </section> - <section id="sect-Reference_Guide-Authentication_Authorization_Intro-LoginModules"> + <section id="sect-Authentication_Authorization_Intro-Login_Modules"> <title>Login modules</title> <para> JBoss Portal Platform uses its own security domain (<emphasis role="bold">gatein-domain</emphasis>) with a set of predefined login modules. Login module configuration for <emphasis>gatein-domain</emphasis> is contained in the <filename>deploy/gatein.ear/META-INF/gatein-jboss-beans.xml</filename> file. Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2012-11-30 04:15:42 UTC (rev 8976) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2012-12-04 07:06:38 UTC (rev 8977) @@ -334,23 +334,13 @@ </section> <section id="sect-SSO_Single_Sign_On_-Central_Authentication_Service"> <title><remark>BZ#856430</remark>Central Authentication Service (CAS)</title> - <para>The CAS Single Sign On (SSO) plug-in enables seamless integration between the platform and the CAS SSO framework. Further information about CAS can be found on the + <para>The CAS Single Sign On (SSO) plug-in enables seamless integration between the platform and the CAS SSO framework. General information about CAS can be found on the <ulink url="http://www.jasig.org/cas">Jasig website</ulink> . </para> - <para>The integration consists of two parts:</para> - <itemizedlist> - <listitem> - <para>Installing and configuring a CAS server.</para> - </listitem> - <listitem> - <para>Setting up the portal to use the CAS server.</para> - </listitem> - </itemizedlist> <section id="sect-CAS-Authentication_Process"> <title>Authentication Process</title> <para>The authentication process with CAS integration occurs in the following order:</para> - <remark>Docs Note - jmorgan - have taken the original process in https://docs.jboss.org/author/display/GTNPORTAL35/Central+Authentication+... and have tried to break up some of the steps for clarity. If you could please verify these changes are accurate, that would be awesome, Marek.</remark> <orderedlist> <listitem> <para>A user visits the main portal page, and wishes to authenticate. The user clicks @@ -412,10 +402,7 @@ and saves the <emphasis role="italics">Identity</emphasis> object to the - <emphasis role="italics">IdentityRegistry</emphasis> - (See - <ulink url="https://docs.jboss.org/author/pages/viewpage.action?pageId=54264608_Authe...">Authentication and Authorization intro#Login modules</ulink> - for more details). + <emphasis role="italics">IdentityRegistry</emphasis>. For more information about login modules, refer to <xref linkend="sect-Authentication_Authorization_Intro-Login_Modules"/>. </para> </listitem> <listitem> @@ -427,7 +414,6 @@ <section id="sect-CAS-Logout_Workflow"> <title>Logout Process</title> <para>The logout process with CAS integration occurs in the following order:</para> - <remark>Docs Note - jmorgan - The same with this one Marek. Taken from the confluence page and reworked to introduce some separation into the steps. Just check my wording of each step to ensure I haven't changed the overall technical meaning with my changes. Cheers, Marek!</remark> <orderedlist> <listitem> <para>The authenticated user clicks the @@ -465,39 +451,24 @@ <para>For scope purposes, the setup instructions assume the following configuration outcomes: </para> <itemizedlist> <listitem> - <para>CAS 3.5 will be deployed on Tomcat 7 server, which will listen on - <emphasis role="italics">localhost:8888</emphasis></para> + <para>The CAS 3.5 is downloaded, and required changes are made to authentication plug-in, logout redirection, and CASTGC cookie configuration. </para> </listitem> <listitem> - <para>The portal will listen on - <emphasis role="italics">localhost:8080</emphasis></para> + <para>Once configured, Apache Maven is used to create the custom CAS web archive, suitable for deployment.</para> </listitem> + <listitem> + <para>The WAR is deployed to the Apache Tomcat server, which acts as the host for the CAS.</para> + </listitem> + <listitem> + <para>Apache Tomcat is configured to listen on <emphasis role="italics">localhost:8888</emphasis>.</para> + </listitem> + <listitem> + <para>JBoss Portal Platform is configured to listen on + <emphasis role="italics">localhost:8080</emphasis>.</para> + </listitem> </itemizedlist> - <section id="sect-CAS-Install_Tomcat_Server"> - <title>Install Apache Tomcat Server</title> - <para>Install and configure Apache Tomcat 7 before proceeding with other configuration relating to CAS. -</para> - <para>File name abbreviations in this section are described in <xref linkend="sect-File_Name_Conventions"/></para> - <procedure> - <title>Configuring Apache Tomcat for CAS</title> - <remark>Docs Note - redid the procedure with a view to Apache Tomcat, not Apache httpd. If installed from the Zip binary, does Apache Tomcat start a service like httpd (Step 4)?</remark> - <step> - <para>Visit <ulink url="http://tomcat.apache.org/download-70.cgi"/> and download the Tomcat 7 binary distribution.</para> - </step> - <step> - <para>Extract and install the binary on the server that is required to host CAS. This directory is now referred to as <replaceable>TOMCAT_DIST</replaceable>.</para> - </step> - <step> - <para>Edit <filename>TOMCAT_DIST/conf/server.xml</filename> and change port 8080 to 8888 to avoid a conflict with the default JBoss Portal Platform listen port.</para> - </step> - <step> - <para>Ensure port 8888 is open in the server firewall, and the service is enabled and running so the platform can communicate with Apache Tomcat on the same server. -</para> - </step> - </procedure> - </section> <section id="sect-CAS-Download_CAS"> - <title>Download CAS</title> + <title><remark>BZ#856430 </remark>Download CAS</title> <para> CAS can be downloaded from <ulink url="http://www.jasig.org/cas/download"/> @@ -505,16 +476,17 @@ <emphasis role="italics">CAS 3.5</emphasis> . More recent CAS versions may also work, however have not been officially tested as part of this specific configuration exercise. </para> + <remark>Docs Note - jmorgan - Marek, I originally incorrectly specified that an admin should extract the CAS source binary into the Tomcat server. It's my fault, because I didn't realise that you need to configure CAS first, *then* build the WAR, and finally deploy to Tomcat. The following sentence makes this much clearer now.</remark> <para> - Extract the downloaded file into a suitable location on the Tomcat server. This location will be referred to as + Extract the downloaded file into a suitable working directory. This location will be referred to as <code>CAS_DIR</code> - in subsequent instructions. + in subsequent configuration instructions. </para> </section> </section> <section id="sect-CAS-Modifying_CAS_Server"> <title>Modifying the CAS server</title> - <para>To configure the web archive as desired, the most effective way is to make the necessary changes directly in the CAS code base.</para> + <para>To configure the CAS server correctly, the most effective way is to make the necessary changes directly in the CAS code base. Follow the instructions in the sections below to make the required changes to the CAS code base, before using Maven to build the CAS web archive.</para> <section id="sect-CAS_Authentication_Plug-in"> <title>Authentication Plug-in </title> <para>While it is possible (and perfectly acceptable) for an administrator to configure CAS to retrieve user credentials from an external database, or from a LDAP server, it is also possible to use JBoss technology. </para> @@ -617,8 +589,34 @@ </variablelist> </section> </section> + <section id="sect-CAS-Install_Tomcat_Server"> + <title>Install Apache Tomcat Server</title> + <para>Install and configure Apache Tomcat 7, which provides the host server for the CAS server. </para> + <para>File name abbreviations in this section are described in <xref linkend="sect-File_Name_Conventions"/></para> + <procedure> + <title>Configuring Apache Tomcat for CAS</title> + <step> + <para>Visit <ulink url="http://tomcat.apache.org/download-70.cgi"/> and download the Tomcat 7 binary distribution.</para> + </step> + <step> + <para>Extract and install the binary on the server that is required to host CAS. This directory is now referred to as <replaceable>TOMCAT_DIST</replaceable>.</para> + </step> + <step> + <para>Edit <filename>TOMCAT_DIST/conf/server.xml</filename> and change port 8080 to 8888 to avoid a conflict with the default JBoss Portal Platform listen port.</para> + <remark>BZ#856430 - jmorgan - Added the new ports from the Confluence SSO Server Setup section</remark> + <important> + <para>If the Apache Tomcat server is installed on the same machine as JBoss Portal Platform, ensure other listen ports common to both servers are changed to prevent configuration issues. For example, change the Tomcat admin port from 8005 to 8805, and the Tomcat AJP port from 8009 to 8809.</para> + </important> + </step> + <step> + <para>Ensure all Apache Tomcat ports are open in the server firewall, and the service is enabled and running so the platform can communicate with Apache Tomcat on the same server. +</para> + </step> + </procedure> + </section> <section id="sect-CAS-Modifying_the_Portal"> <title>Modifying the Portal</title> + <para>Before building and deploying the Jasig CAS sever, configuration needs to be implemented on the JBoss Portal Platform server to prepare the portal for CAS integration.</para> <section id="sect-CAS_Portal_SSO_Primary_Configuration_File"> <title>Portal SSO Primary Configuration File</title> <para> @@ -748,6 +746,31 @@ </variablelist> </section> </section> + <section> + <title><remark>BZ#856430 </remark>Build and Deploy the CAS </title> + <remark>BZ#856430 - jmorgan - This is a new sections which captures the final step an admin needs to do to bring all the cofiguration together.</remark> + <para>Jasig CAS uses Apache Maven to build the <filename>cas.war</filename> file. Follow the instructions to produce this file, and deploy it to the Apache Tomcat server.</para> + <procedure> + <title>Building CAS, and Deploying to Tomcat</title> + <step> + <para>Install Maven by following the recommendations and links in the <ulink url="https://wiki.jasig.org/display/CASUM/Building+and+Deploying">Building and Deploying section</ulink> of the Jasig CAS user documentation.</para> + </step> + <step> + <para>In a terminal, navigate to <filename>CAS_DIR/cas-server-webapp/</filename>, and run <command>mvn install</command>.</para> + </step> + <step> + <para>Copy <filename>CAS_DIR/cas-server-webapp/target/cas.war</filename> to <filename>TOMCAT_DIST/webapps</filename>.</para> + </step> + <step> + <para>Tomcat should be running by default, if the process has been followed up to this step. Start JBoss Portal Platform, and verify the server is running by opening <ulink url="http://localhost:8080/"/>.</para> + </step> + <step> + <para>Open <ulink url="http://localhost:8888/cas"/> to verify the CAS server has correctly deployed to Tomcat. If the link does not open the CAS login page, restart Apache Tomcat and try again.</para> + </step> + </procedure> + <remark>BZ#856430 - jmorgan - Added this "wrap up" statement that should describe what customers are able to do after following the procedure.</remark> + <para>The CAS server is now deployed to Tomcat, and the portal will now redirect users to the CAS login page when they click on the Sign In link.</para> + </section> </section> <section id="sect-Reference_Guide-SSO_Single_Sign_On_-Java_Open_Single_Sign_On_Project"> <title>Java Open Single Sign-On Project</title> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/PortalLifecycle.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/PortalLifecycle.xml 2012-11-30 04:15:42 UTC (rev 8976) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/PortalLifecycle.xml 2012-12-04 07:06:38 UTC (rev 8977) @@ -22,142 +22,77 @@ <para> During deployment, JBoss Portal Platform will automatically and transparently inject a servlet into the portlet application to be able to interact with it. This feature is dependent on the underlying servlet container but will work out of the box on the proposed bundles. </para> - <section> - <title>Advanced WCI Registration</title> - - <para> + <section> + <title>Advanced WCI Registration</title> + <para> JBoss Portal Platform integrates with the web container to perform tasks such as automatic detection and registration of web applications. This is used by the portal container to detect when portlets are deployed and is accomplished through the WCI (Web Container Integration) component. </para> - - <para> + <para> Some applications, especially Spring based portlets, may have requirements that specific servlets be started before any portlets are initialized. Although portlets and servlet initialization order are meant to be independent of each other, JBoss Portal Platform does have a way to get around these limitations imposed by these specific third party applications. </para> - - <para> + <para> As a workaround to this issue, two new, advanced features have been integrated into the WCI component; </para> - - <variablelist> - <title></title> - - <varlistentry> - <term>Disabling Automatic registration</term> - - <listitem> - <para> + <variablelist> + <title>Advanced Features</title> + <varlistentry> + <term>Disabling Automatic registration</term> + <listitem> + <para> By default WCI will register all web applications and the portlet container will then analyse the registered applications and initialize any portlets contained. If you do not wish for your web application to be automatically registered by the WCI component you can disable this feature. By disabling this feature you can prevent the automatic initialization of the portlet and specify later when you want it to be initialized. </para> - - <para> + <para> This is done by setting the <parameter>gatein.wci.native.DisableRegistration</parameter> context-param to <literal>true</literal> in the <filename>web.xml</filename> file of the application, as shown below: </para> -<programlisting language="XML" role="XML"><![CDATA[ + <programlisting language="XML" role="XML"><![CDATA[ <context-param> <param-name>gatein.wci.native.DisableRegistration</param-name> <param-value>true</param-value> </context-param> ]]></programlisting> - </listitem> - </varlistentry> - - <varlistentry> - <term>Manual application deployment.</term> - - <listitem> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term>Manual application deployment.</term> + <listitem> + <para> If you have disabled the automatic registration of your application in the first step, the portal container will not know about any of the portlets contained and will not be able to initialize them. WCI does have a servlet which can be used to manually register the web application. Since servlets can specify when they are deployed with regards to other servlets, we can use this to specify that the web application gets registered by WCI after another servlet has already been started. This means that the a servlet, for example the Spring servlet, can be initialized before any of the portlets. </para> - - <para> + <para> Below is an example <filename>web.xml</filename> file configured to ensure the <systemitem>MyCustomServlet</systemitem> will be initialized before the webapp is registered by WCI: </para> -<programlisting language="XML" role="XML"><![CDATA[ + <programlisting language="XML" role="XML"><![CDATA[ <context-param> <param-name>gatein.wci.native.DisableRegistration</param-name> <param-value>true</param-value> </context-param> ]]></programlisting> -<programlisting language="XML" role="XML"><![CDATA[ + <programlisting language="XML" role="XML"><![CDATA[ <servlet> <servlet-name>GateInServlet</servlet-name> <servlet-class>org.gatein.wci.api.GateInServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> ]]></programlisting> -<programlisting language="XML" role="XML"><![CDATA[ + <programlisting language="XML" role="XML"><![CDATA[ <servlet> <servlet-name>MyCustomServlet</servlet-name> <servlet-class>my.custom.Servlet</servlet-class> <load-on-startup>0</load-on-startup> </servlet> ]]></programlisting> -<programlisting language="XML" role="XML"><![CDATA[ + <programlisting language="XML" role="XML"><![CDATA[ <servlet-mapping> <servlet-name>GateInServlet</servlet-name> <url-pattern>/gateinservlet</url-pattern> </servlet-mapping> ]]></programlisting> - </listitem> - </varlistentry> - </variablelist> - </section> - </section> + </listitem> + </varlistentry> + </variablelist> + </section> </section> - <section id="sect-Reference_Guide-Portal_Life_cycle-The_Command_Servlet"> + <section id="sect-Reference_Guide-Portal_Life_cycle-The_Command_Servlet"> <title>The Command Servlet</title> <para> The CommandServlet is called by the portlet container for requests to particular portlets, it also includes some <literal>init</literal> code when the portal is launched. This servlet (<literal>org.gatein.wci.api.GateInServlet</literal>) is automatically added during the deployment of each portlet application and mapped to <literal>/gateinservlet</literal>.

12 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-commits December 2012