gatein SVN: r7248 - in portal/trunk/component/portal/src: test/java/org/exoplatform/portal/mop/navigation and 1 other directory.
by do-not-reply＠jboss.org
Author: julien_viet
Date: 2011-08-29 11:24:55 -0400 (Mon, 29 Aug 2011)
New Revision: 7248
Modified:
portal/trunk/component/portal/src/main/java/org/exoplatform/portal/mop/navigation/NavigationServiceImpl.java
portal/trunk/component/portal/src/test/java/org/exoplatform/portal/mop/navigation/Node.java
portal/trunk/component/portal/src/test/java/org/exoplatform/portal/mop/navigation/TestNavigationServiceSave.java
Log:
GTNPORTAL-2057 : NPE during transitive remove of transient node
Modified: portal/trunk/component/portal/src/main/java/org/exoplatform/portal/mop/navigation/NavigationServiceImpl.java
===================================================================
--- portal/trunk/component/portal/src/main/java/org/exoplatform/portal/mop/navigation/NavigationServiceImpl.java 2011-08-29 15:11:02 UTC (rev 7247)
+++ portal/trunk/component/portal/src/main/java/org/exoplatform/portal/mop/navigation/NavigationServiceImpl.java 2011-08-29 15:24:55 UTC (rev 7248)
@@ -611,26 +611,37 @@
Navigation sourceNav = session.findObjectById(ObjectType.NAVIGATION, target.data.id);
//
- String objectId = sourceNav.getObjectId();
-
- //
- toEvict.add(objectId);
toEvict.add(parentNav.getObjectId());
sourceNav.destroy();
//
parent.data = new NodeData(parentNav);
+ toUpdate.add(parent.handle);
//
- toUpdate.add(parent.handle);
+ destroy(target);
+ }
+ private void destroy(NodeContext<N> ctx)
+ {
+ toPersist.values().remove(ctx.handle);
+
//
- if (toPersist.values().contains(objectId))
+ toUpdate.remove(ctx.handle);
+
+ //
+ toEvict.add(ctx.handle);
+
+ // Recurse
+ if (ctx.isExpanded())
{
- toPersist.values().remove(objectId);
+ for (NodeContext<N> child = ctx.getFirst();child != null;child = child.getNext())
+ {
+ destroy(child);
+ }
}
- toUpdate.remove(objectId);
}
+
@Override
public void onUpdate(NodeContext<N> source, NodeState state) throws NavigationServiceException
{
Modified: portal/trunk/component/portal/src/test/java/org/exoplatform/portal/mop/navigation/Node.java
===================================================================
--- portal/trunk/component/portal/src/test/java/org/exoplatform/portal/mop/navigation/Node.java 2011-08-29 15:11:02 UTC (rev 7247)
+++ portal/trunk/component/portal/src/test/java/org/exoplatform/portal/mop/navigation/Node.java 2011-08-29 15:24:55 UTC (rev 7248)
@@ -63,6 +63,11 @@
return context.getId();
}
+ public String getHandle()
+ {
+ return context.handle;
+ }
+
public String getName()
{
return context.getName();
Modified: portal/trunk/component/portal/src/test/java/org/exoplatform/portal/mop/navigation/TestNavigationServiceSave.java
===================================================================
--- portal/trunk/component/portal/src/test/java/org/exoplatform/portal/mop/navigation/TestNavigationServiceSave.java 2011-08-29 15:11:02 UTC (rev 7247)
+++ portal/trunk/component/portal/src/test/java/org/exoplatform/portal/mop/navigation/TestNavigationServiceSave.java 2011-08-29 15:24:55 UTC (rev 7248)
@@ -1056,7 +1056,7 @@
//
NavigationContext navigation = service.loadNavigation(SiteKey.portal("remove_added"));
Node root = service.loadNode(Node.MODEL, navigation, Scope.GRANDCHILDREN, null).getNode();
- root.addChild("foo");
+ root.addChild("foo").getHandle();
root.removeChild("foo");
service.saveNode(root.context, null);
@@ -1071,6 +1071,33 @@
assertEquals(0, root.getChildren().size());
}
+ public void testTransitiveRemoveTransient() throws Exception
+ {
+ MOPService mop = mgr.getPOMService();
+ Site portal = mop.getModel().getWorkspace().addSite(ObjectType.PORTAL_SITE, "transitive_remove_transient");
+ portal.getRootNavigation().addChild("default");
+
+ //
+ sync(true);
+
+ //
+ NavigationContext navigation = service.loadNavigation(SiteKey.portal("transitive_remove_transient"));
+ Node root = service.loadNode(Node.MODEL, navigation, Scope.GRANDCHILDREN, null).getNode();
+ root.addChild("foo").addChild("bar");
+ root.removeChild("foo");
+ service.saveNode(root.context, null);
+
+ //
+ root.assertConsistent();
+
+ //
+ sync(true);
+
+ //
+ root = service.loadNode(Node.MODEL, navigation, Scope.GRANDCHILDREN, null).getNode();
+ assertEquals(0, root.getChildren().size());
+ }
+
public void testRenameCreatedNode() throws Exception
{
MOPService mop = mgr.getPOMService();
13 years, 4 months
- 1
- 0
gatein SVN: r7247 - in epp/portal/branches/EPP_5_2_Branch: component and 1 other directories.
by do-not-reply＠jboss.org
Author: theute
Date: 2011-08-29 11:11:02 -0400 (Mon, 29 Aug 2011)
New Revision: 7247
Modified:
epp/portal/branches/EPP_5_2_Branch/
epp/portal/branches/EPP_5_2_Branch/component/
epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ar.xml
epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_de.properties
epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_en.properties
epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_es.properties
epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_fr.properties
epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_it.properties
epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ja.properties
epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ko.xml
epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ne.properties
epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_nl.properties
epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_pt_BR.properties
epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ru.properties
epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_uk.properties
epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_vi.properties
epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_zh.xml
epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_zh_TW.xml
Log:
JBEPP-1134: URI label missing from page node setting
Property changes on: epp/portal/branches/EPP_5_2_Branch
___________________________________________________________________
Modified: svn:mergeinfo
- /epp/portal/branches/EPP_5_1_0_GA_JBEPP-795:5868
/portal/branches/branch-GTNPORTAL-1592:4894
/portal/branches/branch-GTNPORTAL-1643:5002,5063,5167
/portal/branches/branch-GTNPORTAL-1700:5348,5363,5402,5445
/portal/branches/branch-GTNPORTAL-1731:5622,5668
/portal/branches/branch-GTNPORTAL-1745:5765
/portal/branches/branch-GTNPORTAL-1790:5871
/portal/branches/branch-GTNPORTAL-1822:5943,5952
/portal/branches/branch-GTNPORTAL-1832:6030,6063
/portal/branches/branch-GTNPORTAL-1872:6400,6551
/portal/branches/branch-GTNPORTAL-1921:6603
/portal/branches/branch-GTNPORTAL-1963:6904,6915-6916
/portal/branches/decoupled-webos:6214-6243
/portal/branches/gatein-management:6920-6958
/portal/branches/global-portlet-metadata:6298-6384
/portal/branches/site-describability:6171-6235
/portal/trunk:4891,5744,5822,5943,6168,6196,6201-6203,6205-6206,6437,6440,6449,6452,6573,6783-6784,6912-6913,6960,7042,7061,7117,7125,7132-7134
+ /epp/portal/branches/EPP_5_1_0_GA_JBEPP-795:5868
/portal/branches/branch-GTNPORTAL-1592:4894
/portal/branches/branch-GTNPORTAL-1643:5002,5063,5167
/portal/branches/branch-GTNPORTAL-1700:5348,5363,5402,5445
/portal/branches/branch-GTNPORTAL-1731:5622,5668
/portal/branches/branch-GTNPORTAL-1745:5765
/portal/branches/branch-GTNPORTAL-1790:5871
/portal/branches/branch-GTNPORTAL-1822:5943,5952
/portal/branches/branch-GTNPORTAL-1832:6030,6063
/portal/branches/branch-GTNPORTAL-1872:6400,6551
/portal/branches/branch-GTNPORTAL-1921:6603
/portal/branches/branch-GTNPORTAL-1963:6904,6915-6916
/portal/branches/decoupled-webos:6214-6243
/portal/branches/gatein-management:6920-6958
/portal/branches/global-portlet-metadata:6298-6384
/portal/branches/site-describability:6171-6235
/portal/trunk:4891,5744,5822,5943,6168,6196,6201-6203,6205-6206,6437,6440,6449,6452,6573,6783-6784,6912-6913,6960,7042,7061,7095,7117,7125,7132-7134,7210
Property changes on: epp/portal/branches/EPP_5_2_Branch/component
___________________________________________________________________
Modified: svn:mergeinfo
- /epp/portal/branches/EPP_5_1_0_GA_JBEPP-795/component:5868
/portal/branches/branch-GTNPORTAL-1592/component:4894
/portal/branches/branch-GTNPORTAL-1643/component:5002,5063,5167
/portal/branches/branch-GTNPORTAL-1700/component:5348,5363,5402,5445
/portal/branches/branch-GTNPORTAL-1731/component:5622,5668
/portal/branches/branch-GTNPORTAL-1745/component:5765
/portal/branches/branch-GTNPORTAL-1790/component:5871
/portal/branches/branch-GTNPORTAL-1822/component:5943,5952
/portal/branches/branch-GTNPORTAL-1832/component:6030,6063
/portal/branches/branch-GTNPORTAL-1872/component:6400,6551
/portal/branches/branch-GTNPORTAL-1921/component:6603
/portal/branches/branch-GTNPORTAL-1963/component:6904,6915-6916
/portal/trunk/component:4891,5744,5822,5943,6031,6033,6168,6196,6201-6203,6205-6206,6292,6437,6440,6449,6452,6573,6783-6784,6912-6913,6960,7042,7061,7117,7125,7132-7134
+ /epp/portal/branches/EPP_5_1_0_GA_JBEPP-795/component:5868
/portal/branches/branch-GTNPORTAL-1592/component:4894
/portal/branches/branch-GTNPORTAL-1643/component:5002,5063,5167
/portal/branches/branch-GTNPORTAL-1700/component:5348,5363,5402,5445
/portal/branches/branch-GTNPORTAL-1731/component:5622,5668
/portal/branches/branch-GTNPORTAL-1745/component:5765
/portal/branches/branch-GTNPORTAL-1790/component:5871
/portal/branches/branch-GTNPORTAL-1822/component:5943,5952
/portal/branches/branch-GTNPORTAL-1832/component:6030,6063
/portal/branches/branch-GTNPORTAL-1872/component:6400,6551
/portal/branches/branch-GTNPORTAL-1921/component:6603
/portal/branches/branch-GTNPORTAL-1963/component:6904,6915-6916
/portal/trunk/component:4891,5744,5822,5943,6031,6033,6168,6196,6201-6203,6205-6206,6292,6437,6440,6449,6452,6573,6783-6784,6912-6913,6960,7042,7061,7095,7117,7125,7132-7134,7210
Modified: epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ar.xml
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ar.xml 2011-08-29 08:11:39 UTC (rev 7246)
+++ epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ar.xml 2011-08-29 15:11:02 UTC (rev 7247)
@@ -1029,7 +1029,7 @@
</action>
<label>
<name> إسم العقدة </name>
- <uri> #{word.uri}:</uri>
+ <URI> #{word.uri}:</URI>
<pageReference> مرجع صفحة</pageReference>
<description> #{word.description}</description>
<type>نوع الصفحة </type>
Modified: epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_de.properties
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_de.properties 2011-08-29 08:11:39 UTC (rev 7246)
+++ epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_de.properties 2011-08-29 15:11:02 UTC (rev 7247)
@@ -500,7 +500,7 @@
UIPageNodeForm.action.Back=#{word.back}
UIPageNodeForm.action.Close=#{word.cancel}
UIPageNodeForm.label.name=Knotenname:
-UIPageNodeForm.label.uri=#{word.uri}:
+UIPageNodeForm.label.URI=#{word.uri}:
UIPageNodeForm.label.pageReference=Seiten-Referenz
UIPageNodeForm.label.description=#{word.description}
UIPageNodeForm.label.type=Seitentyp
Modified: epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_en.properties
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_en.properties 2011-08-29 08:11:39 UTC (rev 7246)
+++ epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_en.properties 2011-08-29 15:11:02 UTC (rev 7247)
@@ -531,7 +531,7 @@
UIPageNodeForm.action.Back=#{word.back}
UIPageNodeForm.action.Close=#{word.cancel}
UIPageNodeForm.label.name=Node Name:
-UIPageNodeForm.label.uri=#{word.uri}:
+UIPageNodeForm.label.URI=#{word.uri}:
UIPageNodeForm.label.pageReference=Page Reference
UIPageNodeForm.label.description=#{word.description}
UIPageNodeForm.label.type=Page Type
Modified: epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_es.properties
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_es.properties 2011-08-29 08:11:39 UTC (rev 7246)
+++ epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_es.properties 2011-08-29 15:11:02 UTC (rev 7247)
@@ -498,7 +498,7 @@
UIPageNodeForm.action.Back=#{word.back}
UIPageNodeForm.action.Close=#{word.cancel}
UIPageNodeForm.label.name=Nombre de Nodo:
-UIPageNodeForm.label.uri=#{word.uri}:
+UIPageNodeForm.label.URI=#{word.uri}:
UIPageNodeForm.label.pageReference=Referencia a P\u00e1gina
UIPageNodeForm.label.description=#{word.description}
UIPageNodeForm.label.type=Tipo de P\u00e1gina
Modified: epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_fr.properties
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_fr.properties 2011-08-29 08:11:39 UTC (rev 7246)
+++ epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_fr.properties 2011-08-29 15:11:02 UTC (rev 7247)
@@ -488,7 +488,7 @@
UIPageNodeForm.action.Back=#{word.back}
UIPageNodeForm.action.Close=Fermer
UIPageNodeForm.label.name=Nom du noeud :
-UIPageNodeForm.label.uri=#{word.uri} :
+UIPageNodeForm.label.URI=#{word.uri} :
UIPageNodeForm.label.pageReference=Référence de la page
UIPageNodeForm.label.description=#{word.description}
UIPageNodeForm.label.type=Type de page
Modified: epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_it.properties
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_it.properties 2011-08-29 08:11:39 UTC (rev 7246)
+++ epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_it.properties 2011-08-29 15:11:02 UTC (rev 7247)
@@ -527,7 +527,7 @@
UIPageNodeForm.action.Back=#{word.back}
UIPageNodeForm.action.Close=#{word.cancel}
UIPageNodeForm.label.name=Nome del Nodo:
-UIPageNodeForm.label.uri=#{word.uri}:
+UIPageNodeForm.label.URI=#{word.uri}:
UIPageNodeForm.label.pageReference=Collegamento alla Pagina
UIPageNodeForm.label.description=#{word.description}
UIPageNodeForm.label.type=Tipo della Pagina
Modified: epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ja.properties
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ja.properties 2011-08-29 08:11:39 UTC (rev 7246)
+++ epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ja.properties 2011-08-29 15:11:02 UTC (rev 7247)
@@ -501,7 +501,7 @@
UIPageNodeForm.action.Back=#{word.back}
UIPageNodeForm.action.Close=#{word.cancel}
UIPageNodeForm.label.name=\u30ce\u30fc\u30c9\u540d:
-UIPageNodeForm.label.uri=#{word.uri}:
+UIPageNodeForm.label.URI=#{word.uri}:
UIPageNodeForm.label.pageReference=\u30da\u30fc\u30b8\u53c2\u7167
UIPageNodeForm.label.description=#{word.description}
UIPageNodeForm.label.type=\u30da\u30fc\u30b8\u30bf\u30a4\u30d7
Modified: epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ko.xml
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ko.xml 2011-08-29 08:11:39 UTC (rev 7246)
+++ epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ko.xml 2011-08-29 15:11:02 UTC (rev 7247)
@@ -791,7 +791,7 @@
</action>
<label>
<name>노드 이름:</name>
- <uri>#{word.uri}:</uri>
+ <URI>#{word.uri}:</URI>
<pageReference>페이지 레퍼런스</pageReference>
<description>#{word.description}</description>
<type>페이지 유형</type>
Modified: epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ne.properties
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ne.properties 2011-08-29 08:11:39 UTC (rev 7246)
+++ epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ne.properties 2011-08-29 15:11:02 UTC (rev 7247)
@@ -500,7 +500,7 @@
UIPageNodeForm.action.Back=#{word.back}
UIPageNodeForm.action.Close=#{word.cancel}
UIPageNodeForm.label.name=\u0928\u094b\u0921\u0915\u094b \u0928\u093e\u092e:
-UIPageNodeForm.label.uri=#{word.uri}:
+UIPageNodeForm.label.URI=#{word.uri}:
UIPageNodeForm.label.pageReference=\u092a\u0947\u091c \u0930\u093f\u092b\u0947\u0930\u0947\u0928\u094d\u0938
UIPageNodeForm.label.description=#{word.description}
UIPageNodeForm.label.type=\u092a\u0947\u091c\u0915\u094b \u0915\u093f\u0938\u093f\u092e
Modified: epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_nl.properties
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_nl.properties 2011-08-29 08:11:39 UTC (rev 7246)
+++ epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_nl.properties 2011-08-29 15:11:02 UTC (rev 7247)
@@ -500,7 +500,7 @@
UIPageNodeForm.action.Back=#{word.back}
UIPageNodeForm.action.Close=#{word.cancel}
UIPageNodeForm.label.name=Node naam:
-UIPageNodeForm.label.uri=#{word.uri}:
+UIPageNodeForm.label.URI=#{word.uri}:
UIPageNodeForm.label.pageReference=Pagina referentie
UIPageNodeForm.label.description=#{word.description}
UIPageNodeForm.label.type=Pagina type
Modified: epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_pt_BR.properties
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_pt_BR.properties 2011-08-29 08:11:39 UTC (rev 7246)
+++ epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_pt_BR.properties 2011-08-29 15:11:02 UTC (rev 7247)
@@ -496,7 +496,7 @@
UIPageNodeForm.action.Back=#{word.back}
UIPageNodeForm.action.Close=#{word.cancel}
UIPageNodeForm.label.name=Nome:
-UIPageNodeForm.label.uri=#{word.uri}:
+UIPageNodeForm.label.URI=#{word.uri}:
UIPageNodeForm.label.pageReference=Página
UIPageNodeForm.label.description=#{word.description}
UIPageNodeForm.label.type=Tipo de Página
Modified: epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ru.properties
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ru.properties 2011-08-29 08:11:39 UTC (rev 7246)
+++ epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_ru.properties 2011-08-29 15:11:02 UTC (rev 7247)
@@ -484,7 +484,7 @@
UIPageNodeForm.action.Back=#{word.back}
UIPageNodeForm.action.Close=#{word.cancel}
UIPageNodeForm.label.name=Название узла:
-UIPageNodeForm.label.uri=#{word.uri}:
+UIPageNodeForm.label.URI=#{word.uri}:
UIPageNodeForm.label.pageReference=Cноска страницы
UIPageNodeForm.label.description=#{word.description}
UIPageNodeForm.label.type=Тип страницы
Modified: epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_uk.properties
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_uk.properties 2011-08-29 08:11:39 UTC (rev 7246)
+++ epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_uk.properties 2011-08-29 15:11:02 UTC (rev 7247)
@@ -475,7 +475,7 @@
UIPageNodeForm.action.Back=#{word.back}
UIPageNodeForm.action.Close=#{word.cancel}
UIPageNodeForm.label.name=Назва вузла:
-UIPageNodeForm.label.uri=#{word.uri}:
+UIPageNodeForm.label.URI=#{word.uri}:
UIPageNodeForm.label.pageReference=Початкова сторінка
UIPageNodeForm.label.description=#{word.description}
UIPageNodeForm.label.type=Тип сторінки
Modified: epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_vi.properties
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_vi.properties 2011-08-29 08:11:39 UTC (rev 7246)
+++ epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_vi.properties 2011-08-29 15:11:02 UTC (rev 7247)
@@ -490,7 +490,7 @@
UIPageNodeForm.action.Back=#{word.back}
UIPageNodeForm.action.Close=#{word.cancel}
UIPageNodeForm.label.name=Tên node :
-UIPageNodeForm.label.uri=#{word.uri}:
+UIPageNodeForm.label.URI=#{word.uri}:
UIPageNodeForm.label.pageReference=Trang liên quan
UIPageNodeForm.label.description=#{word.description}
UIPageNodeForm.label.type=Kiểu trang
Modified: epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_zh.xml
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_zh.xml 2011-08-29 08:11:39 UTC (rev 7246)
+++ epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_zh.xml 2011-08-29 15:11:02 UTC (rev 7247)
@@ -747,7 +747,7 @@
</action>
<label>
<name>节点名：</name>
- <uri>#{word.uri}:</uri>
+ <URI>#{word.uri}:</URI>
<pageReference>页面选项</pageReference>
<description>#{word.description}</description>
<type>页面类型</type>
Modified: epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_zh_TW.xml
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_zh_TW.xml 2011-08-29 08:11:39 UTC (rev 7246)
+++ epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/WEB-INF/classes/locale/portal/webui_zh_TW.xml 2011-08-29 15:11:02 UTC (rev 7247)
@@ -892,7 +892,7 @@
</action>
<label>
<name>節點名：</name>
- <uri>#{word.uri}:</uri>
+ <URI>#{word.uri}:</URI>
<pageReference>頁面選項</pageReference>
<description>#{word.description}</description>
<type>頁面類型</type>
13 years, 4 months
- 1
- 0
gatein SVN: r7246 - epp/docs/branches/5.2/Release_Notes/en-US.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-08-29 04:11:39 -0400 (Mon, 29 Aug 2011)
New Revision: 7246
Modified:
epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml
epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml
epp/docs/branches/5.2/Release_Notes/en-US/need_info.xml
epp/docs/branches/5.2/Release_Notes/en-US/not_documented.xml
epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml
Log:
Created draft version to capture new 5.2.0 JIRA filters
Modified: epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml 2011-08-29 07:26:59 UTC (rev 7245)
+++ epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml 2011-08-29 08:11:39 UTC (rev 7246)
@@ -4,7 +4,7 @@
%BOOK_ENTITIES;
]>
<articleinfo id="arti-5.1.1_Release_Notes-5.1.1_Release_Notes">
- <title>5.1.1 Release Notes</title>
+ <title>5.2.0 Release Notes</title>
<subtitle>For use with JBoss Enterprise Portal Platform &VZ;</subtitle>
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.2</productnumber>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml 2011-08-29 07:26:59 UTC (rev 7245)
+++ epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml 2011-08-29 08:11:39 UTC (rev 7246)
@@ -5,24 +5,18 @@
<variablelist>
- <!-- https://issues.jboss.org/browse/JBEPP-1079 -->
+ <!-- https://issues.jboss.org/browse/JBEPP-715 -->
<varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-1079" /></term>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-715" /></term>
<listitem>
+ <remark>JIRA is OPEN</remark>
+
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- Pre-release testing has found that attempting to edit a category that does not have a description will produce the following error:
-<screen>IllegalArgumentException: Must pass a non null String
-</screen>
- </para>
- <para>
- A patch that corrects this behavior is available from <CSP>, as are the required installation instructions.
- </para>
- </warning>
+ <para>
+ </para>
+
</listitem>
</varlistentry>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/need_info.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/need_info.xml 2011-08-29 07:26:59 UTC (rev 7245)
+++ epp/docs/branches/5.2/Release_Notes/en-US/need_info.xml 2011-08-29 08:11:39 UTC (rev 7246)
@@ -1,125 +1,4 @@
-<?xml version='1.0'?>
-<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<variablelist>
-
- <!-- https://issues.jboss.org/browse/JBEPP-764 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-764" /></term>
- <listitem>
-
-
- <para>
- To isolate multiple clusters running on the same network, the JBoss Cache and JGroups configuration files used in JBoss Enterprise Portal Platform have been updated to include partition name (-g) and multicast address (-u) properties used in JBoss Enterprise Application Platform.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-874 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-874" /></term>
- <listitem>
-
-
- <para>
- It was found that, in previous versions of JBoss Enterprise Portal Platform, using JCR addNode within a transaction caused a javax.transaction.HeuristicMixedException (internally, org.exoplatform.services.transaction.TransactionException caused by org.jboss.cache.lock.TimeoutException) when the new node was first accessed. This has been corrected by ensuring that loading data into cache occurs outside the current transaction.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-884 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-884" /></term>
- <listitem>
-
-
- <para>
- Changed level of error message for JS compressor
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-961 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-961" /></term>
- <listitem>
-
-
- <para>
- Release Notes need more information about the issue and how it was fixed.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-1010 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-1010" /></term>
- <listitem>
-
-
- <para>
- This issue requires more information to be included in the 5.1.1 Release Notes.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-1013 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-1013" /></term>
- <listitem>
-
-
- <para>
- This issue needs more information to be provided for the 5.1.1 Release Notes.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-1018 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-1018" /></term>
- <listitem>
-
-
- <para>
- If this issue requires a Release Note, more information (about how the problem presented to users and how it was fixed) is required.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-1023 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-1023" /></term>
- <listitem>
-
-
- <para>
- This issue requires more information about how it was resolved if it requires a 5.1.1 Release Note.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-1036 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-1036" /></term>
- <listitem>
-
-
- <para>
- This issue requires more information about the underlying cause and the fix implemented if it requires a 5.1.1 Release Note.
- </para>
-
- </listitem>
- </varlistentry>
-
-</variablelist>
+<para>
+There are no issues that require more information at this time.
+</para>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/not_documented.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/not_documented.xml 2011-08-29 07:26:59 UTC (rev 7245)
+++ epp/docs/branches/5.2/Release_Notes/en-US/not_documented.xml 2011-08-29 08:11:39 UTC (rev 7246)
@@ -1,3 +1,38 @@
-<para>
-All Issues are documented.
-</para>
+<?xml version='1.0'?>
+<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+
+<variablelist>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-599 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-599" /></term>
+ <listitem>
+
+
+ <para>
+ If a portal is deleted from its own Site management page (that is; if a user deletes the portal they are currently logged into), the resultant redirect returns the user to the public mode of the default portal (/portal/public/classic) .
+
+The user should be redirected to the private mode of the default portal (/portal/private/classic).
+
+
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-779 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-779" /></term>
+ <listitem>
+
+
+ <para>
+ Configuration moved from jar file to portal.war.
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+</variablelist>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml 2011-08-29 07:26:59 UTC (rev 7245)
+++ epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml 2011-08-29 08:11:39 UTC (rev 7246)
@@ -5,372 +5,6 @@
<variablelist>
- <!-- https://issues.jboss.org/browse/JBEPP-400 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-400" /></term>
- <listitem>
-
-
- <para>
- Warning messages were found in the server log when starting JBoss Enterprise Portal Platform 5 without an active internet connection. This was because the Java EE Webservices Metadata Handler 2.0 schema was requested via the network at start up. The schema is now bundled with the WSRP which allows JBoss Enterprise Portal Platform to start without producing error messages if there is no internet connection.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-459 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-459" /></term>
- <listitem>
-
-
- <para>
- A thread safety issue in the breadcrumb portlet could lead to <literal>NullPointerException</literal> under load. The issue has been fixed in this release.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-566 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-566" /></term>
- <listitem>
-
-
- <para>
- A bug which prompted users to <guilabel>Save and Close</guilabel> an <emphasis>Edit Portlet</emphasis> dialog if a tab in the window was clicked but the mouse cursor was removed from the tab before the mouse button was released has been corrected in this release.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-568 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-568" /></term>
- <listitem>
-
-
- <para>
- In previous releases of JBoss Enterprise Portal Platform, users found that, when creating sub-nodes of system nodes (<literal>portal navigation</literal>, <literal>group navigation</literal>, <literal>register</literal> etc.), these new nodes were not visible once created. This issue, and a related issue encountered when attempting to '<emphasis>Cut</emphasis>' sub-nodes of system nodes, have been resolved in this latest release.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-597 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-597" /></term>
- <listitem>
-
-
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- The name of a dashboard page entered by user was not properly encoded before being returned on the web browser. This allowed javascript snippets to be executed when creating a new page through the Portal Dashboard. The name of the page is now properly HTML encoded before being returned and javascript is no longer invoked when entered into page fields.
- </para>
- </warning>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-723 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-723" /></term>
- <listitem>
-
-
- <para>
- A bug in the <code>UIUserInGroup.setValues()</code> code caused previous versions of JBoss Enterprise Portal Platform to throw an error when users attempted to navigate to a new page within the Group management view of the Organization portlet by any method other than the page indicator buttons. This release includes a patch which resolves this issue and allows users to navigate between pages using various UI elements.
- </para>
- <para>
- Further details can be found in <ulink type="http" url="https://issues.jboss.org/browse/GTNPORTAL-1356"></ulink>
-
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-733 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-733" /></term>
- <listitem>
-
-
- <para>
- A bug caused the JBoss Enterprise Portal Platform upload service to not work properly with Internet Explorer 7. As a result, any application using the upload service (such as Site Publisher) would not behave correctly with this web browser unless a name was provided. The bug has been fixed and the upload service now works as expected in all browsers (including IE7).
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-768 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-768" /></term>
- <listitem>
-
-
- <para>
- An issue with the <emphasis role="bold">FileUpload</emphasis> demo not populating file information fields has been corrected with an upgrade to the Portlet Bridge component.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-771 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-771" /></term>
- <listitem>
-
-
- <para>
- Prior to this release, CAS ticket validation failed when the JBoss Enterprise Portal Platform instance was set up with SSL. This has been fixed with an upgrade to the SSO component. CAS ticket validation now works as expected with <literal>http</literal> and <literal>https</literal> addresses.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-772 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-772" /></term>
- <listitem>
-
-
- <para>
- In this release of JBoss Enterprise Portal Platform, <systemitem>JndiMultiplexedJBossCacheRegionFactory</systemitem> is used for IDM second level caching. This makes it easier to switch to TCP.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-773 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-773" /></term>
- <listitem>
-
-
- <para>
- A bug prevented the '<emphasis>Preferences</emphasis>' tab from appearing in some portlets. The tab would only appear in portlets that were customized during the first deployment through the <literal>portal.xml</literal> descriptor.
- </para>
- <para>
- Non-customized portlets would not show a '<emphasis>Preferences</emphasis>' tab. The <filename>UIFormInputSet.java</filename> and <filename>UIPortletForm.java</filename> files have been patched to fix the issue and now the tab now appears in all portlets that have configurable preferences.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-780 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-780" /></term>
- <listitem>
-
-
- <para>
- The two JBoss Cache instances created by PicketLink were calling on the same configuration file in <filename>idm-configuration.xml</filename> and, as a result, were using the same cluster names. This could lead to conflicts as the same JBoss Cache instance could join the same channel twice.
- </para>
- <para>
- Separate configuration files were added to the distribution package and the Portal configuration was customized to call on the different files. JBoss Cache instances can now run simultaneously without conflict.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-782 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-782" /></term>
- <listitem>
-
-
- <para>
- It was found that separate instances of JBoss Enterprise Portal Platform 5.1 deployed on the same network and started with the '<literal>Default</literal>' server profile would communicate as if in a cluster.
- </para>
- <para>
- This behavior has been resolved with new cluster configuration.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-786 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-786" /></term>
- <listitem>
-
-
- <para>
- An error in the XML definition in the <filename>gatein_objects_1_0</filename> file was found to cause errors in Eclipse environments when using the default <filename>pages.xml</filename> or <filename>navigation.xml</filename> files.
- </para>
- <para>
- This was because the file did not include '<literal>VISIBLE</literal>' in the allowed values of the '<parameter>visibility</parameter>' element. This error has been corrected.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-788 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-788" /></term>
- <listitem>
-
-
- <para>
- Custom WSRP <systemitem>RegistrationPolicy</systemitem> implementations were not properly handled in previous versions of JBoss Enterprise Portal Platform.
- </para>
- <para>
- This caused an exception when the product was started. This issue has been resolved.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-794 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-794" /></term>
- <listitem>
-
-
- <para>
- When adding resources (js, css, etc) to the Head of the HTML response with the <literal>doHeaders</literal> method a bug was encountered which caused those resources to be added twice. A patch has been applied to fix the bug and new resources are now only linked once.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-811 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-811" /></term>
- <listitem>
-
-
- <para>
- A race condition, encountered when more than one portal user attempts to create a page at the same time has been adressed in this release. The issue presented if two pages were created simultaneously, with one process finishing slightly after the first, but before the first process had redirected to the new page. This scenario would result in the second page overwriting the first.
- </para>
- <para>
- Patches which resolve the page creation issue have been applied to this release. However, further development will be required in later iterations to resolve concurrency issues completely.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-813 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-813" /></term>
- <listitem>
-
-
- <para>
- An issue with navigational elements not being correctly translated into languages with a country variant has been resolved in this release. Navigation elements are now translated correctly.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-848 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-848" /></term>
- <listitem>
-
-
- <para>
- A bug in data caching prevented some changes to Portal navigation from reloading in real time. When changing a group navigation priority, the reordering of the groups was only happening after a log-out. The <filename>UIPageNavigationForm.java</filename> file has been patched to correct this and navigation changes now update immediately, without the user needing to log-out.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-854 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-854" /></term>
- <listitem>
-
-
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- In previous versions of JBoss Enterprise Portal Platform, an error would be encountered when slashes were used in the context path of a portlet. This issue has been corrected in this release.
- </para>
- </warning>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-856 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-856" /></term>
- <listitem>
-
-
- <para>
- Problems encountered when trying to run various gadgets (including the RSS Reader) in a portal instance using secure https mode has been resolved in this release. All gadgets should now render and behave as expect in both <literal>http</literal> and <literal>https</literal> modes.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-857 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-857" /></term>
- <listitem>
-
-
- <para>
- WSRP Strict mode was previously set only via listeners, which were not triggered when the service started since they did not yet exist at that time. This meant that WSRP Strict Mode was not properly restored when JBoss Enterprise Portal Platform was started. An upgrade to WSRP 2.0.1 GA corrects this issue and WSRP Strict Mode is now properly restored from persistent state at start up.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-873 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-873" /></term>
- <listitem>
-
-
- <para>
- Previous versions of JBoss Enterprise Portal Platform encountered problems when attempting to access files though the WebDAV interface if the file name included special characters. An upstream patch ensures characters are escaped correctly and resolves the issue.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-883 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-883" /></term>
- <listitem>
-
-
- <para>
- Some mistranslations in <systemitem>webui_ja.properties</systemitem> have been corrected in this release of JBoss Enterprise Portal Platform.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-887 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-887" /></term>
- <listitem>
-
-
- <para>
- A conflict between the <systemitem>javax.portlet.faces.extension.resetModeViewId</systemitem> the portlet.xml configuration file and the error page specified by the error-page tag in web.xml has been resolved in an upgrade of the JBoss Portlet Bridge component.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-890 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-890" /></term>
- <listitem>
-
-
- <para>
- Exceptions thrown by the <systemitem>handleFaceletNotFound</systemitem> method (when a facelet file was not found) were being obscured by <systemitem>FaceletViewHandler</systemitem> as the response object was not a subtype of <systemitem>HttpServletResponse</systemitem> (it is an instance of <systemitem>PortletResponse</systemitem>). <filename>FaceletPortletViewHandler.java</filename> has been updated to handle instances of both HttpServletResponse and PortletResponse response objects.
- </para>
-
- </listitem>
- </varlistentry>
-
<!-- https://issues.jboss.org/browse/JBEPP-893 -->
<varlistentry>
<term><ulink url="https://issues.jboss.org/browse/JBEPP-893" /></term>
@@ -384,158 +18,30 @@
</listitem>
</varlistentry>
- <!-- https://issues.jboss.org/browse/JBEPP-896 -->
+ <!-- https://issues.jboss.org/browse/JBEPP-1013 -->
<varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-896" /></term>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1013" /></term>
<listitem>
<para>
- The Single Sign On (SSO) <systemitem>AbstractLogoutFilter</systemitem> in JBoss Enterprise Portal Platform would read request parameters before setting the character encoding. When a form was submitted with non-UTF-8 characters (while SSO was enabled) the values could be garbled on output. An upgrade of the SSO component to version 1.0.2-epp-GA (which includes a patch to the <systemitem>AbstractLogoutFilter</systemitem> code) resolves this issue and Non-UTF-8 characters are now specified correctly.
+ The demo iFrame portlet was setup to use the GateIn blog as an example page. With the new GateIn blog, the portal is redirected so that the blog takes the full page. The location has changed to point to gatein.org homepage which doesn't do any redirection.
</para>
</listitem>
</varlistentry>
- <!-- https://issues.jboss.org/browse/JBEPP-899 -->
+ <!-- https://issues.jboss.org/browse/JBEPP-1018 -->
<varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-899" /></term>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1018" /></term>
<listitem>
<para>
- <systemitem>MOPPortalStructuralAccess</systemitem> was improperly closing the <systemitem>POMSession</systemitem> that was under control of another Portal component, leaving that component unable to properly access JCR state.
+ Previous versions of JBoss Enterprise Portal Platform did not honor the location of the WSRP consumer configuration file specified in wsrp-configuration.xml. This made it impossible to use any configuration file other than the default. This version of JBoss Enterprise Portal Platform honors the configuration file location by adding the ability to configure consumers from an InputStream similar to the method used by the producer configuration. Administrators can now use custom consumer configuration files instead of needing to modify the default file.
</para>
- <para>
- An NPE was thrown when other components tried to access the closed <systemitem>POMSession</systemitem>. <systemitem>MOPPortalStructureAccess</systemitem> now saves the session instead of saving <emphasis role="bold">and</emphasis> closing it.
- </para>
- <para>
- Since <systemitem>MOPPortalStructuralAccess</systemitem> no longer closes the POMSession, it can still be used by components upstream without issue.
- </para>
</listitem>
</varlistentry>
- <!-- https://issues.jboss.org/browse/JBEPP-902 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-902" /></term>
- <listitem>
-
-
- <para>
- In previous Portal versions, page definitions were held in system memory before being written when starting the Portal. This could cause an Out Of Memory error if a large number of pages were defined in the XML descriptors. The transaction has now been split so that not all page definitions are held in memory prior to being written and the Out Of Memory error is no longer encountered.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-904 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-904" /></term>
- <listitem>
-
-
- <para>
- JBoss Enterprise Portal Platform doesn't set content-type on css-files added via gatein-resources.xml. This causes Internet Explorer 9 to ignore these css-files due to new security policy (a console message states: SEC7113: CSS was ignored due to mime type mismatch). The ResourceRequestFilter.java file has been modified to set the content type so that content-types will be set and Internet Explorer 9 will render the Portal as expected.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-945 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-945" /></term>
- <listitem>
-
-
- <para>
- An error that caused IntegrationCache to not be invalidated when calling invalidateAll() on PicketlinkIDMCacheService MBean has been corrected in this release.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-954 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-954" /></term>
- <listitem>
-
-
- <para>
- Attempting to remove an inexistent ConsumerGroup would cause a NullPointerException. JCRRegistrationPersistenceManager now properly handles the situation.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-955 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-955" /></term>
- <listitem>
-
-
- <para>
- Local state was improperly initialized causing a NullPointerException when attempting to insert a new ConsumerGroup. Properly retrieving the state from the JCR persistence fixed the issue.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-958 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-958" /></term>
- <listitem>
-
-
- <para>
- In previous JBoss Enterprise Portal Platform versions, calling org.exoplatform.webui.form.UIFormCheckBoxInput.setValue() with a String value of 'true', would result in the value being interpreted as 'false' as only Boolean values (not String values) were parsed. This behavior has been corrected by recognizing string values when entered and converting them to boolean values.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-966 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-966" /></term>
- <listitem>
-
-
- <para>
- In previous versions of JBoss Enterprise Portal Platform, the ErrorLoginServlet did not return the HTTP header content-type. This could be problematic when running the portal instance behind Apache loadbalancer. An upstream patch has been incorporated in this release to address the issue.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-987 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-987" /></term>
- <listitem>
-
-
- <para>
- The JCR cache configuration files in JBoss Enterprise Portal Platform 5.1.1 have been moved from the /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/lib/exo.portal.component.common-<version>.jar to /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/02portal.war/WEB-INF/conf/.
-
-This change created problems when attempting to start upgraded versions of JBoss Enterprise Portal Platform that had the original file path stored in the JCR_CONFIG table in the database. To resolve the issue, duplicates of the configuration files have been retained in the original location. This also ensures backward compatibility, without the need to change the database.
-
-Note:
-After this change, if configuration changes to the JCR cache are required, it is important that the JCR_CONFIG table be updated to use the "war:" prefix instead of "classpath:" (for example; file:war:/conf/jcr/jbosscache/local/config.xml).
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-1019 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-1019" /></term>
- <listitem>
-
-
- <para>
- A bug which caused the day of the month in the calendar pop-up to not be translated has been corrected in this release.
- </para>
-
- </listitem>
- </varlistentry>
-
</variablelist>
13 years, 4 months
- 1
- 0
gatein SVN: r7245 - in epp/docs/branches/5.2: Reference_Guide/en-US and 5 other directories.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-08-29 03:26:59 -0400 (Mon, 29 Aug 2011)
New Revision: 7245
Modified:
epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml
epp/docs/branches/5.2/Installation_Guide/en-US/Installation_Guide.ent
epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml
epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml
epp/docs/branches/5.2/Reference_Guide/en-US/Reference_Guide.ent
epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml
epp/docs/branches/5.2/Release_Notes/en-US/5.1.1_Release_Notes.ent
epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml
epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.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/Revision_History.xml
epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Site_Publisher_Installation_Guide.ent
epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Article_Info.xml
epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Revision_History.xml
epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.1.1_Release_Notes.ent
epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/Book_Info.xml
epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/Revision_History.xml
epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/Site_Publisher_User_Guide.ent
epp/docs/branches/5.2/User_Guide/en-US/Book_Info.xml
epp/docs/branches/5.2/User_Guide/en-US/Revision_History.xml
epp/docs/branches/5.2/User_Guide/en-US/User_Guide.ent
Log:
Updated versions and reset rev/pub/ed numbers
Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml 2011-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml 2011-08-29 07:26:59 UTC (rev 7245)
@@ -7,9 +7,9 @@
<title>Installation Guide</title>
<subtitle>An Installation Guide for JBoss Enterprise Portal Platform &VZ;</subtitle>
<productname>JBoss Enterprise Portal Platform</productname>
- <productnumber>5.1</productnumber>
- <edition>2</edition>
- <pubsnumber>5.1.4</pubsnumber>
+ <productnumber>5.2</productnumber>
+ <edition>5.2.0</edition>
+ <pubsnumber>1</pubsnumber>
<abstract>
<para>
This book provides information about obtaining, installing and running JBoss Enterprise Portal Platform. It forms part of the complete document suite along with the <emphasis role="bold">User Guide</emphasis> and <emphasis role="bold">Reference Guide</emphasis> available at <ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." />.
Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Installation_Guide.ent
===================================================================
--- epp/docs/branches/5.2/Installation_Guide/en-US/Installation_Guide.ent 2011-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/Installation_Guide/en-US/Installation_Guide.ent 2011-08-29 07:26:59 UTC (rev 7245)
@@ -15,5 +15,5 @@
<!-- Version Specifcs: -->
<!ENTITY VX "5">
-<!ENTITY VY "5.1">
-<!ENTITY VZ "5.1.1">
\ No newline at end of file
+<!ENTITY VY "5.2">
+<!ENTITY VZ "5.2.0">
\ No newline at end of file
Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml 2011-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml 2011-08-29 07:26:59 UTC (rev 7245)
@@ -4,13 +4,13 @@
%BOOK_ENTITIES;
]>
-<appendix id="appe-Install_Guide-Revision_History">
+<appendix id="appe-Release_Notes-Revision_History">
<title>Revision History</title>
- <simpara>
- <revhistory>
- <revision>
- <revnumber>2-5.1.4</revnumber>
- <date>Fri Jul 15 2011</date>
+ <simpara>
+ <revhistory>
+ <revision>
+ <revnumber>5.2.0-1</revnumber>
+ <date>Mon Aug 29 2011</date>
<author>
<firstname>Scott</firstname>
<surname>Mumford</surname>
@@ -18,224 +18,10 @@
</author>
<revdescription>
<simplelist>
- <member>Updated for 5.1.1 Release.</member>
+ <member>Updating version and resetting pubs/ed numbers.</member>
</simplelist>
</revdescription>
- </revision>
- <revision>
- <revnumber>1-5.2</revnumber>
- <date>Wed June 22 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Incorporated new Bugzilla feedback link.</member>
- <member>Corrected minor typographical errors.</member>
- </simplelist>
- </revdescription>
- </revision>
- <!-- <revision>
- <revnumber>1-5.1</revnumber>
- <date>Tue Dec 21 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>December 2010 release.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-4.2</revnumber>
- <date>Mon Dec 13 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Incorporated QE feedback.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-4.1</revnumber>
- <date>Fri Dec 10 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added new procedure to encrypt Messaging password.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-4.0</revnumber>
- <date>Thu Dec 09 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Numerous bug fixes.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-2.3</revnumber>
- <date>Mon Nov 29 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added "Gadget Proxy Configuration" section.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-2.1</revnumber>
- <date>Mon Nov 22 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added Installing Add-ons chapter. Updated .ent file</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-2.0</revnumber>
- <date>Wed Nov 17 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added supported database details for 5.1.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.9</revnumber>
- <date>Fri Nov 12 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added and edited HTTPS Configuration section.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.8</revnumber>
- <date>Tue Oct 26 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added Recommended Practices section.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.7</revnumber>
- <date>Tue Oct 26 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Rebuilt for new Publican version features.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.6</revnumber>
- <date>Thu Sep 30 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Edit Product version number for publishing restructure.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.3</revnumber>
- <date>Tue Apr 28 2010</date>
- <author>
- <firstname>Luc</firstname>
- <surname>Texier</surname>
- <email>ltexier(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>https://jira.jboss.org/jira/browse/JBEPP-274.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.2</revnumber>
- <date>Tue Apr 13 2010</date>
- <author>
- <firstname>Ben</firstname>
- <surname>Clare</surname>
- <email>bclare(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Updates as described in JBEPP-288 for the version 5.0 release.</member>
- </simplelist>
- </revdescription>
- </revision>-->
-
- <revision>
- <revnumber>1-1.1</revnumber>
- <date>Tue Nov 24 2009</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Initial creation of book in Publican</member>
- </simplelist>
- </revdescription>
- </revision>
-
+ </revision>
</revhistory>
</simpara>
-</appendix>
-
+</appendix>
\ No newline at end of file
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-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml 2011-08-29 07:26:59 UTC (rev 7245)
@@ -7,9 +7,9 @@
<title>Reference Guide</title>
<subtitle>An in-depth guide to Enterprise Portal Platform &VZ;</subtitle>
<productname>JBoss Enterprise Portal Platform</productname>
- <productnumber>5.1</productnumber>
- <edition>2</edition>
- <pubsnumber>5.1.8</pubsnumber>
+ <productnumber>5.2</productnumber>
+ <edition>5.2.0</edition>
+ <pubsnumber>1</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/Reference_Guide.ent
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/Reference_Guide.ent 2011-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/Reference_Guide.ent 2011-08-29 07:26:59 UTC (rev 7245)
@@ -15,5 +15,5 @@
<!-- Version Specifcs: -->
<!ENTITY VX "5">
-<!ENTITY VY "5.1">
-<!ENTITY VZ "5.1.1">
\ No newline at end of file
+<!ENTITY VY "5.2">
+<!ENTITY VZ "5.2.0">
\ No newline at end of file
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-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml 2011-08-29 07:26:59 UTC (rev 7245)
@@ -3,13 +3,13 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent">
%BOOK_ENTITIES;
]>
-<appendix id="appe-Reference_Guide-Revision_History">
+<appendix id="appe-Release_Notes-Revision_History">
<title>Revision History</title>
- <simpara>
- <revhistory>
- <revision>
- <revnumber>2-5.1.8</revnumber>
- <date>Thu Aug 11 2011</date>
+ <simpara>
+ <revhistory>
+ <revision>
+ <revnumber>5.2.0-1</revnumber>
+ <date>Mon Aug 29 2011</date>
<author>
<firstname>Scott</firstname>
<surname>Mumford</surname>
@@ -17,518 +17,10 @@
</author>
<revdescription>
<simplelist>
- <member>Prep for 5.1.1 release.</member>
+ <member>Updating version and resetting pubs/ed numbers.</member>
</simplelist>
</revdescription>
- </revision>
- <!-- <revision>
- <revnumber>2-5.1.6</revnumber>
- <date>Wed Aug 10 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>Incorporated QA feedback.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>2-5.1.5</revnumber>
- <date>Fri Aug 5 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>Incorporated changes from GateIn revision 6987.</member>
- </simplelist>
- </revdescription>
- </revision> -->
- <revision>
- <revnumber>2-5.1.4</revnumber>
- <date>Tue Aug 2 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>JBEPP-894: Updated 'Enable SSO' section.</member>
- </simplelist>
- </revdescription>
- </revision>
- <!--<revision>
- <revnumber>2-5.1.3</revnumber>
- <date>Mon Aug 1 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>JBEPP-894: Added Section 14.7.2. Enabling SSO.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>2-5.1.2</revnumber>
- <date>Fri Jul 15 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>Updated for 5.1.1 Release.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>2-5.1.1</revnumber>
- <date>Monday June 27 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Updated for 5.1.1 Release.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-5.8</revnumber>
- <date>Wed June 22 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Incorporated new Bugzilla feedback link.</member>
- <member>Corrected minor typographical errors.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-5.7</revnumber>
- <date>Mon May 30 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Updated WSRP Configuration details based (JBEPP-962)</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-5.6</revnumber>
- <date>Fri May 13 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Updated 'Password Encryption' section.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-5.5</revnumber>
- <date>Thu May 12 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added 'Password Encryption' Draft.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-5.4</revnumber>
- <date>Wed Apr 27 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Completed first draft of new LDAP section.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-5.2</revnumber>
- <date>Wed Mar 23 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Adding WSRP removal procedure as per JBEPP-739.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-5.1</revnumber>
- <date>Tue Dec 21 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>December 2010 release.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-4.6</revnumber>
- <date>Sat Dec 18 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Converted images to 32 bit to resolve pdf color bug.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-4.4</revnumber>
- <date>Wed Dec 15 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added "Simple RichFaces vs RichFaces over WSRP" table and updated WSRP removal.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-4.2</revnumber>
- <date>Mon Dec 13 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Incorprated QE feedback.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-4.1</revnumber>
- <date>Fri Dec 10 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Incorporating updates from Thomas Heute.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-4.0</revnumber>
- <date>Thu Dec 09 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Numerous bug fixes.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.22</revnumber>
- <date>Mon Dec 06 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Republished for 5.1 branch.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.21</revnumber>
- <date>Wed Dec 01 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Incorporated further QA feedback. Corrected errors in WSRP update.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.20</revnumber>
- <date>Mon Nov 29 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added Localization Configuration chapter. Incorporated QA feedback.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.18</revnumber>
- <date>Wed Nov 17 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Removed version-specific content and documentation notes for limited Beta release.</member>
- </simplelist>
- </revdescription>
- </revision>
-
- <revision>
- <revnumber>1-1.17</revnumber>
- <date>Mon Nov 15 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Refined handling of version-specific information.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.15</revnumber>
- <date>Thu Nov 11 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Incorporated further feedback from GLS.</member>
- <member>Added first cut of WSRP 2.0 content.</member>
- <member>Highlighted JCR sections for possible removal.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.14</revnumber>
- <date>Tue Nov 02 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Updated to remove numerous minor spelling and typographic errors.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.13</revnumber>
- <date>Tue Oct 26 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Rebuilt to utilize new Publican branding (includes some minor typographical and grammatical error corrections).</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.11</revnumber>
- <date>Thu Sep 30 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Edit Product version number for publishing restructure.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.10</revnumber>
- <date>Thu Sep 23 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Split <filename>repository-configuration.xml</filename> code sample into two smaller samples (workaround callout pointer bug). Removed further references to components in standalone mode.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.9</revnumber>
- <date>Wed Sep 15 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Started content for "Debugging Resource Bundle Usage" section. Started homoginizing filepath variables.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.8</revnumber>
- <date>Fri Aug 27 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added new concept definitions to JCR chapter.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.7</revnumber>
- <date>Mon Aug 9 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Further clean-up of programlisting rendering.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.6</revnumber>
- <date>Thu Aug 5 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Extracted code snippets.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.5</revnumber>
- <date>Thu Jul 29 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Updated for 5.0.1 Release. Extracted programlistings/structure changes.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.1</revnumber>
- <date>Sat Mar 20 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Update for Staging</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.1</revnumber>
- <date>Mon Feb 15 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>First complete edit</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.0</revnumber>
- <date>Wed Nov 11 2009</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Initial creation of book by publican</member>
- </simplelist>
- </revdescription>
- </revision> -->
+ </revision>
</revhistory>
</simpara>
-</appendix>
+</appendix>
\ No newline at end of file
Modified: epp/docs/branches/5.2/Release_Notes/en-US/5.1.1_Release_Notes.ent
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/5.1.1_Release_Notes.ent 2011-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/Release_Notes/en-US/5.1.1_Release_Notes.ent 2011-08-29 07:26:59 UTC (rev 7245)
@@ -10,5 +10,5 @@
<!-- Version Specifcs: -->
<!ENTITY VX "5">
-<!ENTITY VY "5.1">
-<!ENTITY VZ "5.1.1">
\ No newline at end of file
+<!ENTITY VY "5.2">
+<!ENTITY VZ "5.2.0">
\ No newline at end of file
Modified: epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml 2011-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml 2011-08-29 07:26:59 UTC (rev 7245)
@@ -7,9 +7,9 @@
<title>5.1.1 Release Notes</title>
<subtitle>For use with JBoss Enterprise Portal Platform &VZ;</subtitle>
<productname>JBoss Enterprise Portal Platform</productname>
- <productnumber>5.1</productnumber>
- <edition>2.1</edition>
- <pubsnumber>5.1.8</pubsnumber>
+ <productnumber>5.2</productnumber>
+ <edition>5.2.0</edition>
+ <pubsnumber>1</pubsnumber>
<abstract>
<para>
These release notes contain important information related to JBoss Enterprise Portal Platform &VX; that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing the product.
Modified: epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml 2011-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml 2011-08-29 07:26:59 UTC (rev 7245)
@@ -3,139 +3,24 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "5.1.1_Release_Notes.ent">
%BOOK_ENTITIES;
]>
-<appendix id="appe-5.1.1_Release_Notes-Revision_History">
+<appendix id="appe-Release_Notes-Revision_History">
<title>Revision History</title>
<simpara>
<revhistory>
- <revision>
- <revnumber>2.1-5.1.8</revnumber>
- <date>Fri Aug 12 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>Prepared for 5.1.1 release.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>2.1-5.1.7</revnumber>
- <date>Wed Aug 10 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added CVE-2011-1484 to Security section.</member>
- <member>Corrected minor typographical errors.</member>
- </simplelist>
- </revdescription>
- </revision>
- <!--<revision>
- <revnumber>2.1-5.1.4</revnumber>
- <date>Tue Aug 9 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>Rebuilt using broader JIRA filters.</member>
- <member>Added Security Issues section.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>2.1-5.1.3</revnumber>
- <date>Fri Aug 5 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>Updated to incorporate further bug fixes.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>2.1-5.1.2</revnumber>
- <date>Mon Jul 11 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added more resolved issues and 'Not Yet Documented' section.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>2.1-5.1.1</revnumber>
- <date>Monday June 27 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Updated for 5.1.1 Release.</member>
- </simplelist>
- </revdescription>
- </revision> -->
- <revision>
- <revnumber>1-1.3</revnumber>
- <date>Thu Jun 02 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added "Recommended Practices" section.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.1</revnumber>
- <date>Wed May 4 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Compiled full Resolved Issues list and added component version details.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.0</revnumber>
- <date>Thu Apr 28 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Initial draft of Release Notes created.</member>
- </simplelist>
- </revdescription>
- </revision>
+ <revision>
+ <revnumber>5.2.0-1</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>
-
+</appendix>
\ No newline at end of file
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-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Book_Info.xml 2011-08-29 07:26:59 UTC (rev 7245)
@@ -7,9 +7,9 @@
<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.1</productnumber>
- <edition>2</edition>
- <pubsnumber>5.1.3</pubsnumber>
+ <productnumber>5.2</productnumber>
+ <edition>5.2.0</edition>
+ <pubsnumber>1</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" />
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-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Revision_History.xml 2011-08-29 07:26:59 UTC (rev 7245)
@@ -3,13 +3,13 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
%BOOK_ENTITIES;
]>
-<appendix id="appe-Installation_Guide-Revision_History">
+<appendix id="appe-Release_Notes-Revision_History">
<title>Revision History</title>
<simpara>
<revhistory>
- <revision>
- <revnumber>2-5.1.3</revnumber>
- <date>Fri Jul 15 2011</date>
+ <revision>
+ <revnumber>5.2.0-1</revnumber>
+ <date>Mon Aug 29 2011</date>
<author>
<firstname>Scott</firstname>
<surname>Mumford</surname>
@@ -17,168 +17,10 @@
</author>
<revdescription>
<simplelist>
- <member>Updated for 5.1.1 Release.</member>
+ <member>Updating version and resetting pubs/ed numbers.</member>
</simplelist>
</revdescription>
- </revision>
- <!--<revision>
- <revnumber>2-5.1.1</revnumber>
- <date>Monday June 27 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Updated for 5.1.1 Release.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-5.3</revnumber>
- <date>Wed June 22 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Incorporated new Bugzilla feedback link.</member>
- <member>Corrected minor typographical errors.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-5.2</revnumber>
- <date>Thu Jun 02 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Corrected errors after PRODUCT entity find/replace sweep.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-5.1</revnumber>
- <date>Tue Dec 21 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>December 2010 release.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-4.3</revnumber>
- <date>Thu Dec 16</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Preparation for 5.1.0 release.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-4.2</revnumber>
- <date>Mon Dec 13 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Incorporated QE feedback.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-4.1</revnumber>
- <date>Fri Dec 10 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Updated entities. Removed deprecated URLs.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-4.0</revnumber>
- <date>Thu Dec 09 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Updated base installation admonitions.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.2</revnumber>
- <date>Mon Dec 06 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Published to 5.1 branch.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.1</revnumber>
- <date>Wed Nov 17 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added first draft content.</member>
- </simplelist>
- </revdescription>
- </revision> -->
-
- <revision>
- <revnumber>1-1.0</revnumber>
- <date>Wed Nov 17 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Initial creation of book by publican</member>
- </simplelist>
- </revdescription>
- </revision>
-
+ </revision>
</revhistory>
</simpara>
-</appendix>
-
+</appendix>
\ No newline at end of file
Modified: epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Site_Publisher_Installation_Guide.ent
===================================================================
--- epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Site_Publisher_Installation_Guide.ent 2011-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Site_Publisher_Installation_Guide.ent 2011-08-29 07:26:59 UTC (rev 7245)
@@ -15,5 +15,5 @@
<!-- Version Specifcs: -->
<!ENTITY VX "5">
-<!ENTITY VY "5.1">
-<!ENTITY VZ "5.1.1">
\ No newline at end of file
+<!ENTITY VY "5.2">
+<!ENTITY VZ "5.2.0">
\ No newline at end of file
Modified: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Article_Info.xml
===================================================================
--- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Article_Info.xml 2011-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Article_Info.xml 2011-08-29 07:26:59 UTC (rev 7245)
@@ -7,9 +7,9 @@
<title>Site Publisher 5.1.1 Release Notes</title>
<subtitle>For the JBoss Enterprise Portal Platform Site Publisher &VZ; extension.</subtitle>
<productname>JBoss Enterprise Portal Platform</productname>
- <productnumber>5.1</productnumber>
- <edition>2</edition>
- <pubsnumber>5.1.5</pubsnumber>
+ <productnumber>5.2</productnumber>
+ <edition>5.2.0</edition>
+ <pubsnumber>1</pubsnumber>
<abstract>
<para>
These release notes contain important information related to JBoss Site Publisher &VZ; that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing the product.
Modified: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Revision_History.xml 2011-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Revision_History.xml 2011-08-29 07:26:59 UTC (rev 7245)
@@ -7,122 +7,21 @@
<title>Revision History</title>
<simpara>
<revhistory>
- <revision>
- <revnumber>2-5.1.5</revnumber>
- <date>Thu Aug 11 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added new issues.</member>
- <member>Prep for 5.1.1 release.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>2-5.1.4</revnumber>
- <date>Fri Aug 5 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>Updated with new upstream JIRAs.</member>
- <member>Added flag for open JIRAs.</member>
- </simplelist>
- </revdescription>
- </revision>
- <!--<revision>
- <revnumber>2-5.1.3</revnumber>
- <date>Fri Jul 15 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>Updated for 5.1.1 Release.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>2-5.1.1</revnumber>
- <date>Monday June 27 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Updated for 5.1.1 Release.</member>
- </simplelist>
- </revdescription>
- </revision>-->
- <revision>
- <revnumber>1-1.3</revnumber>
- <date>Wed Jun 15 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added 'Issues Fixed Upstream' section and populated with eXo ECMS fixes.</member>
- </simplelist>
- </revdescription>
- </revision>
- <!--<revision>
- <revnumber>1-1.2</revnumber>
- <date>Thu Jun 02 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Corrected errors after PRODUCT entity find/replace sweep.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.1</revnumber>
- <date>Wed Jun 01 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Rebuilt document to capture updated Release Notes JIRA.</member>
- </simplelist>
- </revdescription>
- </revision>-->
- <revision>
- <revnumber>1-1.0</revnumber>
- <date>Mon May 30 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Initial creation of book for Staging.</member>
- </simplelist>
- </revdescription>
- </revision>
+ <revision>
+ <revnumber>5.2.0-1</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/Release_Notes/en-US/Site_Publisher_5.1.1_Release_Notes.ent
===================================================================
--- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.1.1_Release_Notes.ent 2011-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.1.1_Release_Notes.ent 2011-08-29 07:26:59 UTC (rev 7245)
@@ -10,5 +10,5 @@
<!-- Version Specifcs: -->
<!ENTITY VX "5">
-<!ENTITY VY "5.1">
-<!ENTITY VZ "5.1.1">
\ No newline at end of file
+<!ENTITY VY "5.2">
+<!ENTITY VZ "5.2.0">
\ No newline at end of file
Modified: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/Book_Info.xml 2011-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/Book_Info.xml 2011-08-29 07:26:59 UTC (rev 7245)
@@ -7,9 +7,9 @@
<title>Site Publisher User Guide</title>
<subtitle>A guide to using JBoss Enterprise Portal Platform Site Publisher &VZ;</subtitle>
<productname>JBoss Enterprise Portal Platform</productname>
- <productnumber>5.1</productnumber>
- <edition>2</edition>
- <pubsnumber>5.7</pubsnumber>
+ <productnumber>5.2</productnumber>
+ <edition>5.2.0</edition>
+ <pubsnumber>1</pubsnumber>
<abstract>
<para>
This document provides an easy to follow guide to the functions and options available in the Enterprise Portal Platform Site Publisher extension (powered by eXo). It is intended to be accessible and useful to both experienced and novice portal users.
Modified: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/Revision_History.xml 2011-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/Revision_History.xml 2011-08-29 07:26:59 UTC (rev 7245)
@@ -3,310 +3,24 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "User_Guide.ent">
%BOOK_ENTITIES;
]>
-<appendix id="appe-User_Guide-Revision_History">
+<appendix id="appe-Release_Notes-Revision_History">
<title>Revision History</title>
<simpara>
<revhistory>
- <revision>
- <revnumber>2-5.7</revnumber>
- <date>Fri Aug 12 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>Prepared for 5.1.1 release.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>2-5.6</revnumber>
- <date>Fri Jul 15 2011</date>
+ <revision>
+ <revnumber>5.2.0-1</revnumber>
+ <date>Mon Aug 29 2011</date>
<author>
<firstname>Scott</firstname>
<surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
+ <email></email>
</author>
<revdescription>
<simplelist>
- <member>Added content for <ulink type="http" url="https://issues.jboss.org/browse/JBEPP-886">JBEPP-886</ulink>.</member>
+ <member>Updating version and resetting pubs/ed numbers.</member>
</simplelist>
</revdescription>
- </revision>
- <revision>
- <revnumber>1-5.5</revnumber>
- <date>Wed June 01 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>JBEPP-849: Major edit sweep of copy and XML tagging.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-5.4</revnumber>
- <date>Fri May 27 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>JBEPP-919: Minor edits from translation review.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-5.3</revnumber>
- <date>Tue Mar 22 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Removed inline icon graphics for accessibility and aesthetic reasons.</member>
- <member>Replaced icon graphics with text.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-5.2</revnumber>
- <date>Tue Feb 15 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Resized images and added explicit width attributes for better rendering.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-5.1</revnumber>
- <date>Tue Dec 21 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>December 2010 release.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-2.5</revnumber>
- <date>Sun Dec 19 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Incorporated Red Hat branded screenshots and removed references to eXo start logo.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-2.3</revnumber>
- <date>Wed Dec 15 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Exported company-specific content to separate files.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-2.1.1</revnumber>
- <date>Fri Nov 19 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
-
- </author>
- <revdescription>
- <simplelist>
- <member>Updated docbook source to WCM 2.1.1</member>
-
- </simplelist>
-
- </revdescription>
-
- </revision>
- <revision>
- <revnumber>1-2.0</revnumber>
- <date>Mon Oct 25 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
-
- </author>
- <author>
- <firstname>Laura</firstname>
- <surname>Bailey</surname>
-
- </author>
- <author>
- <firstname>Tom</firstname>
- <surname>Wells</surname>
-
- </author>
- <author>
- <firstname>Eslpeth</firstname>
- <surname>Thorne</surname>
-
- </author>
- <author>
- <firstname>Rebecca</firstname>
- <surname>Newton</surname>
-
- </author>
- <author>
- <firstname>Jared</firstname>
- <surname>Morgan</surname>
-
- </author>
- <revdescription>
- <simplelist>
- <member>Completed docbook conversion.</member>
-
- </simplelist>
-
- </revdescription>
-
- </revision>
- <!--
- <revision>
- <revnumber>1-1.5</revnumber>
- <date>Wed Oct 20 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
-
- </author>
- <revdescription>
- <simplelist>
- <member>Further docbook conversion.</member>
-
- </simplelist>
-
- </revdescription>
-
- </revision>
- <revision>
- <revnumber>1-1.4</revnumber>
- <date>Tue Oct 19 2010</date>
- <author>
- <firstname>Joshua</firstname>
- <surname>Wulf</surname>
- <email>jwulf(a)redhat.com</email>
-
- </author>
- <revdescription>
- <simplelist>
- <member>Removed problematic characters in book abstract as workaround to Publican bug</member>
-
- </simplelist>
-
- </revdescription>
-
- </revision>
- <revision>
- <revnumber>1-1.3</revnumber>
- <date>Mon Oct 11 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
-
- </author>
- <revdescription>
- <simplelist>
- <member>Removed "draft' status for publication.</member>
-
- </simplelist>
-
- </revdescription>
-
- </revision>
- <revision>
- <revnumber>1-1.2</revnumber>
- <date>Mon Oct 11 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
-
- </author>
- <revdescription>
- <simplelist>
- <member>Edit Product version number for publishing restructure.</member>
-
- </simplelist>
-
- </revdescription>
-
- </revision>
- <revision>
- <revnumber>1-1.1</revnumber>
- <date>Thu Oct 07 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
-
- </author>
- <revdescription>
- <simplelist>
- <member>Second staging push of conversion in-progess</member>
-
- </simplelist>
-
- </revdescription>
-
- </revision>
- --> <revision>
- <revnumber>1-0</revnumber>
- <date>Tue Sep 28 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
-
- </author>
- <revdescription>
- <simplelist>
- <member>Initial creation of book by publican</member>
-
- </simplelist>
-
- </revdescription>
-
- </revision>
-
+ </revision>
</revhistory>
-
</simpara>
-</appendix>
-
+</appendix>
\ No newline at end of file
Modified: epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/Site_Publisher_User_Guide.ent
===================================================================
--- epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/Site_Publisher_User_Guide.ent 2011-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/Site_Publisher/User_Guide/en-US/Site_Publisher_User_Guide.ent 2011-08-29 07:26:59 UTC (rev 7245)
@@ -15,5 +15,5 @@
<!-- Version Specifcs: -->
<!ENTITY VX "5">
-<!ENTITY VY "5.1">
-<!ENTITY VZ "5.1.1">
\ No newline at end of file
+<!ENTITY VY "5.2">
+<!ENTITY VZ "5.2.0">
\ No newline at end of file
Modified: epp/docs/branches/5.2/User_Guide/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.2/User_Guide/en-US/Book_Info.xml 2011-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/User_Guide/en-US/Book_Info.xml 2011-08-29 07:26:59 UTC (rev 7245)
@@ -5,9 +5,9 @@
<title>User Guide</title>
<subtitle>A User Guide for Enterprise Portal Platform &VZ;</subtitle>
<productname>JBoss Enterprise Portal Platform</productname>
- <productnumber>5.1</productnumber>
- <edition>2</edition>
- <pubsnumber>5.1.8</pubsnumber>
+ <productnumber>5.2</productnumber>
+ <edition>5.2.0</edition>
+ <pubsnumber>1</pubsnumber>
<abstract>
<para>
This document provides an easy to follow guide to the functions and
Modified: epp/docs/branches/5.2/User_Guide/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.2/User_Guide/en-US/Revision_History.xml 2011-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/User_Guide/en-US/Revision_History.xml 2011-08-29 07:26:59 UTC (rev 7245)
@@ -3,69 +3,13 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "User_Guide.ent">
%BOOK_ENTITIES;
]>
-<appendix id="appe-User_Guide-Revision_History">
+<appendix id="appe-Release_Notes-Revision_History">
<title>Revision History</title>
- <simpara>
+ <simpara>
<revhistory>
- <revision>
- <revnumber>2-5.1.8</revnumber>
- <date>Fri Aug 26 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added "Non-visible pages and security" admonition.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>2-5.1.7</revnumber>
- <date>Thu Aug 25 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>Removed assertion that non-'visible' pages are inaccessible in all circumstances.</member>
- </simplelist>
- </revdescription>
- </revision>
- <!--<revision>
- <revnumber>2-5.1.6</revnumber>
- <date>Thu Aug 11 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>Prep for 5.1.1 release.</member>
- </simplelist>
- </revdescription>
- </revision> -->
- <revision>
- <revnumber>2-5.1.5</revnumber>
- <date>Wed Aug 10 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>Incorporated QA feedback.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>2-5.1.4</revnumber>
- <date>Thu Aug 4 2011</date>
+ <revision>
+ <revnumber>5.2.0-1</revnumber>
+ <date>Mon Aug 29 2011</date>
<author>
<firstname>Scott</firstname>
<surname>Mumford</surname>
@@ -73,307 +17,10 @@
</author>
<revdescription>
<simplelist>
- <member>BZ#692170: Added Portlet Container Concept section.</member>
+ <member>Updating version and resetting pubs/ed numbers.</member>
</simplelist>
</revdescription>
- </revision>
- <revision>
- <revnumber>2-5.1.3</revnumber>
- <date>Mon Aug 1 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added "Supported Browsers" chapter.</member>
- </simplelist>
- </revdescription>
- </revision>
- <!--<revision>
- <revnumber>2-5.1.2</revnumber>
- <date>Fri Jul 15 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email></email>
- </author>
- <revdescription>
- <simplelist>
- <member>Updated for 5.1.1 release.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>2-5.1.1</revnumber>
- <date>Monday June 27 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Updated for 5.1.1 Release.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-5.4</revnumber>
- <date>Wed June 22 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Incorporated new Bugzilla feedback link.</member>
- <member>Corrected minor typographical errors.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-5.3</revnumber>
- <date>Wed Jun 01 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added highlighting to 5.2.3 section header for review.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-5.2</revnumber>
- <date>Thu Apr 7 2011</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added reference to JBDS Portlet Tools Guide to section 5.2.3.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-5.1</revnumber>
- <date>Tue Dec 21 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>December 2010 release.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-4.4</revnumber>
- <date>Sat Dec 18 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Incorporated further QE feedback.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-4.3</revnumber>
- <date>Fri Dec 17 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Converted images to 32 bit to resolve pdf color bug.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-4.2</revnumber>
- <date>Mon Dec 13 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Incorprated QE feedback.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-4.0</revnumber>
- <date>Thu Dec 09 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Numerous bug fixes.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-2.10</revnumber>
- <date>Mon Dec 06 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Re-published for 5.1 branch.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-2.9</revnumber>
- <date>Tue Oct 26 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Rebuilt for new Publican version features.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-2.7</revnumber>
- <date>Thu Sep 30 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Edit Product version number for publishing restructure.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-2.6</revnumber>
- <date>Fri Sep 10 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Added icons/ folder to workaround Publican bug. Corrected typo in Introduction.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-2.5</revnumber>
- <date>Mon May 10 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Quality Engineering changes.</member>
- </simplelist>
- </revdescription>
- </revision>
-
- <revision>
- <revnumber>1-2.0</revnumber>
- <date>Sat Mar 20 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Finalised all edits and image updating.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.5</revnumber>
- <date>Tue Jan 19 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Finalised first pass of copy edit.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.1</revnumber>
- <date>Mon Dec 07 2009</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>First structural edit.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.0</revnumber>
- <date>Thu Nov 19 2009</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>First edit to add/remove content.</member>
- </simplelist>
- </revdescription>
- </revision> -->
- <revision>
- <revnumber>1-0</revnumber>
- <date>Tue Nov 17 2009</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Initial creation of book by publican</member>
- </simplelist>
- </revdescription>
- </revision>
+ </revision>
</revhistory>
</simpara>
-</appendix>
-
+</appendix>
\ No newline at end of file
Modified: epp/docs/branches/5.2/User_Guide/en-US/User_Guide.ent
===================================================================
--- epp/docs/branches/5.2/User_Guide/en-US/User_Guide.ent 2011-08-29 07:26:00 UTC (rev 7244)
+++ epp/docs/branches/5.2/User_Guide/en-US/User_Guide.ent 2011-08-29 07:26:59 UTC (rev 7245)
@@ -15,5 +15,5 @@
<!-- Version Specifcs: -->
<!ENTITY VX "5">
-<!ENTITY VY "5.1">
-<!ENTITY VZ "5.1.1">
\ No newline at end of file
+<!ENTITY VY "5.2">
+<!ENTITY VZ "5.2.0">
\ No newline at end of file
13 years, 4 months
- 1
- 0
gatein SVN: r7244 - in epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US: modules and 9 other directories.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-08-29 03:26:00 -0400 (Mon, 29 Aug 2011)
New Revision: 7244
Added:
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Attributes/
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Attributes/API.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Attributes/SPI.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Concepts_API_SPI/
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Concepts_API_SPI/Associations.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Concepts_API_SPI/Introduction.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Concepts_API_SPI/Role.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Concepts_API_SPI/User_and_Group.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/API_Cache.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/IdentitySessionFactory.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/IdentityStore.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/IdentityStoreRepository.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/Realm.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/Realm_Templates.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/XML_Configuration.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Credentials/
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Credentials/Credential_API.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Credentials/Credential_SPI.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Deployment/
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Deployment/Deployment.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Deployment/Usage_Scenario.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/API_Model.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/Architecture.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/Group_And_Roles.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/Main_Concepts.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/Realms.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/SPI_Model.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStoreRepository_Implementations/
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStoreRepository_Implementations/FallbackIdentityStoreRepository.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStoreRepository_Implementations/WrapperIdentityStoreRepository.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStore_Implementations/
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStore_Implementations/Hibernate_IdentityStore.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStore_Implementations/LDAP_IdentityStore.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStore_Implementations/Minimal_Configuration.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Quick_Start/
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Quick_Start/Core_Files.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Quick_Start/Examples.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Quick_Start/Test_Cases.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Attributes.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Concepts_API_SPI.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Configuration.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Credentials.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Deployment.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Design_and_Architecture.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_IdentityStoreRepository_Implementations.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_IdentityStore_Implementations.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Quick_Start.xml
Removed:
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/API.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/API_Cache.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/API_Model.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Architecture.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Associations.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Core_Files.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Credential_API.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Credential_SPI.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Deployment.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Examples.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/FallbackIdentityStoreRepository.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Group_And_Roles.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Hibernate_IdentityStore.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/IdentitySessionFactory.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/IdentityStore.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/IdentityStoreRepository.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Introduction.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/LDAP_IdentityStore.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Main_Concepts.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Minimal_Configuration.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Realm.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Realm_Templates.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Realms.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Role.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/SPI.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/SPI_Model.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Test_Cases.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Usage_Scenario.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/User_and_Group.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/WrapperIdentityStoreRepository.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/XML_Configuration.xml
Modified:
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Book_Info.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/PicketLink_IDM_Reference_Guide.ent
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/PicketLink_IDM_Reference_Guide.xml
epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Revision_History.xml
Log:
Restructured book and updated vers/rev/pub/ed numbers
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/API.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/API.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/API.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,71 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-API">
- <title>API</title>
- <para>
- On the API level each IdentityType object (Identity and Group) can have associated Attribute objects. All operations are exposed by AttributesManager interface. Each attribute is described with AttributeDescription that contains its properties such as:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">name</emphasis> - attribute name
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">readonly</emphasis> - if attribute values can be changed
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">multivalued</emphasis> - if attribute can have many values
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">required</emphasis> - if attribute can be removed
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">type</emphasis> - type of attribute values.
- </para>
-
- </listitem>
-
- </itemizedlist>
- <para>
- Default implementation provides two attribute types:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">text</emphasis> - java.lang.String object
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">binary</emphasis> - byte[] object
- </para>
-
- </listitem>
-
- </itemizedlist>
- <section id="sect-PicketLink_IDM_Reference_Guide-API-Sample_operations">
- <title>Sample operations</title>
-
-<programlisting role="Java"><xi:include href="extras/sample-operations.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
-
- </section>
-
-
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/API_Cache.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/API_Cache.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/API_Cache.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,51 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-API_Cache">
- <title>API Cache</title>
- <para>
- At the realm level IDM API cache layer can be enabled
- </para>
-
-<programlisting><realm>
- <id>idm_realm</id>
- <repository-id-ref>DefaultRepository</repository-id-ref>
- <identity-type-mappings>
- <user-mapping>USER</user-mapping>
- </identity-type-mappings>
- <options>
- <option>
- <name>cache.providerClass</name>
- <value>JBossCacheAPICacheProviderImpl</value>
- </option>
- </options>
-</realm></programlisting>
- <para>
- Cache related options :
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">cache.providerClass</emphasis> - class implementing APICacheProvider interface
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">cache.providerRegistryName</emphasis> - id of instantiated APICacheProvider implementation stored in configuration registry
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">cache.scope</emphasis> - namespace used to store entities in cache. Can be "realm" (default) or "session".
- </para>
-
- </listitem>
-
- </itemizedlist>
-
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/API_Model.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/API_Model.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/API_Model.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,87 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-API_Model">
- <title>API Model</title>
- <para>
- The API operates on the identity model that is defined by the following set of interfaces:
- </para>
- <variablelist>
- <title>API Interfaces</title>
- <varlistentry>
- <term>org.picketlink.idm.api.IdentityType</term>
- <listitem>
- <para>
- This is a parent interface for Group and Identity.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>org.picketlink.idm.api.Identity</term>
- <listitem>
- <para>
- This represents an Identity, which can be a user (within organization) or a machine (in authentication or security use case)
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>org.picketlink.idm.api.Group</term>
- <listitem>
- <para>
- This represents a Group.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>org.picketlink.idm.api.GroupType</term>
- <listitem>
- <para>
- This represents type of a Group. It can be an organization, organization unit, administration group, global role, community or any other entity.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>org.picketlink.idm.api.Role</term>
- <listitem>
- <para>
- This represents one to one relationship between Identity and Group. Role has a type. The idea behind the concept is described below.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>org.picketlink.idm.api.RoleType</term>
- <listitem>
- <para>
- This represents type of a Role.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>org.picketlink.idm.api.Attribute</term>
- <listitem>
- <para>
- This represents an attribute connected with <parameter>IdentityType</parameter> (Group or Identity). It can have many complex type values (text or binary). <parameter>AttributeDescription</parameter> describes such properties of Attribute like: name, type of values, readonly, multivalued, required.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>org.picketlink.idm.api.Credential</term>
- <listitem>
- <para>
- This represents credentials connected with an Identity.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>org.picketlink.idm.api.CredentialType</term>
- <listitem>
- <para>
- This represents type of a Credential. For example it can be text password or binary certificate.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Architecture.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Architecture.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Architecture.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,123 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-Architecture">
- <title>Architecture</title>
- <para>
- The most important part of architecture is a split between the API and the SPI.
- </para>
- <mediaobject>
- <imageobject>
- <imagedata contentdepth="6in" contentwidth="6in" fileref="images/IDM-api-spi.png" width="444" />
- </imageobject>
- <caption align="right"> <para>
- <emphasis role="bold">PicketLink IDM architecture</emphasis>
- </para>
- </caption>
- </mediaobject>
- <para>
- API part contains of following interfaces:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">Realm</emphasis> - described later in this document. Groups configuration of several identity stores and exposes all of them with one consistent identity model.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">IdentitySessionFactory</emphasis> - Main entry point in the API. Enables to create/get IdentitySession for a given Realm
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">IdentitySession</emphasis> - Session that groups all identity management operation. Contains transaction support and exposes four managers that handle all identity management operations.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">PersistenceManager</emphasis> - Operates witin IdentitySession. Performs all operations on Identity and Group objects. Create/Remove/Find
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">RelationshipManager</emphasis> - Operates witin IdentitySession. Associate and deassociate Identity and Group objects. Find Idenity and Group objects depending on their relationships
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">RoleManager</emphasis> - Operates witin IdentitySession. Operations on Role objects. Optional feature.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">AttributeManager</emphasis> - Operates witin IdentitySession. Manages Identity and Group (IdentityType objects) attributes. Each configured attribute is described with AttributeDescription interface
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">SearchCriteria</emphasis> - Enables to apply additional conditions to search operations. May be leveraged to receive results sorted, paginated or filtered with attributes.
- </para>
-
- </listitem>
-
- </itemizedlist>
- <para>
- SPI part contains of following interfaces
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">IdentityStoreSession</emphasis> - Session that groups all identity management operations within identity persistence stores.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">IdentityStoreSessionFactory</emphasis> - Entry point in the SPI to initialize IdentityStoreSession inside IdentityStore or AttributeStore.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">IdentityStoreInvocationContext</emphasis> - IdentityStoreSession aware context object that is passed during any invocation of AttributeStore or IdentityStore methods. Thanks to this actual store implementation doesn't need to be aware of current session state. Therefore one instance of AttributeStore or IdentityStore can be invoked by different realms at the same time.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">AttributeStore</emphasis> - Exposes operations on identity store with attributes. This is a separate interface as in multi store configuration scenario, profile may need to be stored outside of actual data store for a given identity (LDAP + DB)
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">IdentityStore</emphasis> - Extends AttributeStore. Implementation of this interface performs operations on the real data store.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">IdentityStoreRepository</emphasis> - Extends IdentityStore. Groups several IdentityStore objects and exposes operations on them within single interface for the API. The implementation is responsible for aggregate identity objects from many configured underlaying IdentityStore objects and map different IdentityObjectTypes between them. The place where the whole magic happens
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">IdentityObjectSearchControl</emphasis> - Enables to apply additional conditions to search operations. May be leveraged to receive results sorted, paginated or filtered withattributes.
- </para>
-
- </listitem>
-
- </itemizedlist>
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Associations.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Associations.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Associations.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,33 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-Associations">
- <title>Associations</title>
- <para>
- Group and Users can be associated. This represents simple relationship that can be described like "user John belongs to Group IT". Association can be created between Group and User or between two Groups.
- </para>
- <para>
- Those operations are managed by RelationshipManager:
- </para>
-
-<programlisting role="Java">
-RelationshipManager rm = identitySession.getRelationshipManager();
-
-rm.associateUser(parisOffice, annUser);
-rm.associateUser(atlantaOffice, stefanUser);
-rm.associateUser(itDep, stefanUser);
-
-assertTrue(rm.isAssociated(parisOffice, annUser));</programlisting>
- <para>
- At the SPI level this is mapped to IdentityObjectRelationship entity. This relationship has a type. Simple assotiations can be marked with a type named "JBOSS_IDENTITY_MEMBERSHIP" (this is implementation detail) which describes simple membership. Note that IdentityObjectRelationship creates a connection between any two IdentityObject entities.
- </para>
- <mediaobject>
- <imageobject>
- <imagedata contentdepth="6in" contentwidth="6in" fileref="images/SPI2.png" width="444" />
- </imageobject>
-
- </mediaobject>
-</chapter>
-
Modified: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Book_Info.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Book_Info.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -4,32 +4,32 @@
%BOOK_ENTITIES;
]>
<bookinfo id="book-PicketLink_IDM_Reference_Guide-PicketLink_IDM_Reference_Guide">
- <title>PicketLink IDM Reference Guide</title>
- <subtitle>A guide to the PicketLink IDM component in JBoss Enterprise Portal Platform &VZ;</subtitle>
- <productname>JBoss Enterprise Portal Platform</productname>
- <productnumber>5.1</productnumber>
- <edition>1</edition>
- <pubsnumber>1.0</pubsnumber>
- <abstract>
- <!-- Source Metadata
+ <title>PicketLink IDM Reference Guide</title>
+ <subtitle>A guide to the PicketLink IDM component in JBoss Enterprise Portal Platform &VZ;</subtitle>
+ <productname>JBoss Enterprise Portal Platform</productname>
+ <productnumber>5.2</productnumber>
+ <edition>5.2.0</edition>
+ <pubsnumber>1</pubsnumber>
+ <abstract>
+ <!-- Source Metadata
URL: http://www.jboss.org/picketlink/IDM.html
Author [w/email]: Boleslaw Davidowicz?
License:
--> <para>
- PicketLink IDM aims to provide a common identity model for Identity Management operations. This includes easy management of identities like Users/Groups/Roles and their attributes. Framework also provides usage of different identity stores like LDAP or RDBMS.
- </para>
+ PicketLink IDM aims to provide a common identity model for Identity Management operations. This includes easy management of identities like Users/Groups/Roles and their attributes. Framework also provides usage of different identity stores like LDAP or RDBMS.
+ </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>
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Core_Files.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Core_Files.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Core_Files.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,22 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-Core_Files">
- <title>Core Files</title>
- <para>
- Although the best way to start playing with the framework is to look at Maven2 sample project mentioned above lets list minimal set of configuration files. To setup the basic framework core depending on hibernate IdentityStore two files will be needed
- </para>
- <para>
- <emphasis role="bold">idm-config.xml</emphasis> - that will set proper configuration for all framework components described in section above. Sample one below.
- </para>
-
-<programlisting language="XML" role="XML"><xi:include href="extras/idm-config.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <para>
- <emphasis role="bold">hibernate.cfg.xml</emphasis> - hibernate SessionFactory setup
- </para>
-
-<programlisting language="XML" role="XML"><xi:include href="extras/hibernate.cfg.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Credential_API.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Credential_API.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Credential_API.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,67 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-Credential_API">
- <title>Credential API</title>
- <para>
- API contains Credential and CredentialType interfaces. CredentialType defines type of credential object. Default implementation supports two types:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">PASSWORD</emphasis> - text password represented by java.lang.String object
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">BINARY</emphasis> - binary credential represented by byte[]. For example some kind of certificate.
- </para>
-
- </listitem>
-
- </itemizedlist>
- <para>
- Two basic implementations are provided:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">org.picketlink.idm.impl.api.BinaryCredential</emphasis> - Credential with BINARY CredentialType
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">org.picketlink.idm.impl.api.PasswordCredential</emphasis> - Credential with PASSWORD CredentialType
- </para>
-
- </listitem>
-
- </itemizedlist>
- <para>
- Because credentials values are stored as hash or in other encoded form both SPI and API only enables to update and validate credential value and not to read it from persistence store. API enables to only protect Identity objects with credentials. All related management operations are exposed in AttributesManager interface.
- </para>
-
-<programlisting role="Java">
-User anotherOne = session.getPersistenceManager().createUser("blah1");
-
-session.getAttributesManager().updatePassword(anotherOne, "Password2000");
-assertTrue(session.getAttributesManager().validatePassword(anotherOne, "Password2000"));
-
-Credential password = new PasswordCredential("SuperPassword2345");
-session.getAttributesManager().updateCredential(anotherOne, password);
-assertTrue(session.getAttributesManager().validateCredentials(anotherOne, new Credential[]{password}));
-
-// binary credential
-byte[] cert = new byte[512000];
-random.nextBytes(cert);
-Credential binaryCredential = new BinaryCredential(cert);
-session.getAttributesManager().updateCredential(anotherOne, binaryCredential);
-assertTrue(session.getAttributesManager().validateCredentials(anotherOne, new Credential[]{binaryCredential}));
-
-</programlisting>
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Credential_SPI.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Credential_SPI.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Credential_SPI.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-Credential_SPI">
- <title>Credential SPI</title>
- <para>
- SPI contains IdentityObjectCredential and IdentityObjectCredentialType interfaces that correspons to Credential and CredentialType interfaces in the API. Implementation supports the same two (PASSWORD and BINARY) types. Management operations are exposed in IdentityStore interface. Each IdentityObjectType can be configured to support different IdentityObjectCredentialType. This information is exposed by FeaturesMetaData interface.
- </para>
- <para>
- IdentityObjectCredential interface exposes two methods to retrieve credential value:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">getValue</emphasis> - returns either String for text based credentials or byte[] for binary. True credential value may be needed by different IdentityStore implementations for validation. For example with LDAP authentication for IdentityObject entry will be performed
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">getEncodedValue</emphasis> - Enables to provide IdentityStore with custom credential encoding method. IdentityStore is not obligated to use encoded value. This should return either String for text based credentials or byte[] for binary. May return null if credential implementation doesn't provide encoding mechanism. IdentityStore
- </para>
-
- </listitem>
-
- </itemizedlist>
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Deployment.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Deployment.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Deployment.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,122 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-JBoss_AS_5_Deployment">
- <title>JBoss AS 5 Deployment</title>
- <para>
- Now, lets look at the second case, by deploying the idm into the JBoss AS 5. By doing this different services can share the identity component, instead of having its own seperate identity component.
- </para>
- <para>
- The jobs that need to be done for the deployment in the container is quite simple:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Populate the idm schema if neccessary.
- </para>
-
- </listitem>
- <listitem>
- <para>
- Start the IdentitySessionFactory, and then register it into the JNDI.
- </para>
-
- </listitem>
-
- </itemizedlist>
- <para>
- Before we look at it further, lets see the configuration files that jboss idm needed typically. (Say using db back-end, hibernate impl combination)
- </para>
- <itemizedlist>
- <listitem>
- <para>
- jboss idm configuration file. say jboss.idm.cfg.xml
- </para>
-
- </listitem>
- <listitem>
- <para>
- datasource file, say idm-ds.xml
- </para>
-
- </listitem>
- <listitem>
- <para>
- hibernate cfg file, say jboss.idm.hibernate.cfg.xml.
- </para>
-
- </listitem>
-
- </itemizedlist>
- <para>
- With regard to the detail of jboss idm configuration file, you can refer to the configuration documentation.
- </para>
- <para>
- So, if we want to deploy the idm into container with a specified JNDI name, we need to have a deployment file to define the JNDI and other neccessary properties.
- </para>
- <para>
- For the integration with JBoss AS5, the AS5 has a great deployment feature, we've built our own deployer to extend it, so that the AS can listen on the -jboss-idm.xml suffix file to start the IdentitySessionFactory.
- </para>
- <para>
- Basically, we had two deployer, one is: IDMConfigParsingDeployer class, which is taking responsible for parsing files that ends with the -jboss-idm.xml suffix into Java object. The other is: IDMDeployer class, this one is to do the real job, which means it might populate the schema, initial dataset into target db, and then start the IdentitySessionFactory, register it into the JNDI with the specified name at last.
- </para>
- <para>
- We will see a very typical deployment file looks like. (default-jboss-idm.xml)
- </para>
-
-<programlisting><?xml version="1.0" encoding="UTF-8"?>
-<jboss-idm-deployer xmlns="urn:jboss:identity:idm:deployer:v1_0_alpha"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="urn:jboss:identity:idm:deployer:v1_0_alpha identity-deployer.xsd">
- <JNDIName>java:/IdentitySessionFactory</JNDIName>
- <idmConfigFile>jboss.idm.cfg.xml</idmConfigFile>
- <hibernateDeployer>
- <hibernateConfiguration>jboss.idm.hibernate.cfg.xml</hibernateConfiguration>
-<hibernateSessionFactoryJNDIName>java:/IDMHibernateSessionFactory</hibernateSessionFactoryJNDIName>
- </hibernateDeployer>
- <initializers>
- <datasource>java:/jbossidmDS</datasource>
- <sqlInitializer>
- <sqlFile>idm-sql/jboss.idm.@database@.create.sql</sqlFile>
- <exitSQL>select * from jbid_io</exitSQL>
- </sqlInitializer>
- </initializers>
-</jboss-idm-deployer></programlisting>
- <itemizedlist>
- <listitem>
- <para>
- The deployment file must be named -jboss-idm.xml as suffix, otherwise, it won't be recoginzed in the JBoss AS5 container.
- </para>
-
- </listitem>
- <listitem>
- <para>
- The "JNDIName" and "idmConfigFile" attributes are required. The JNDIName is the name for keeping the started IdentitySessionFactory.
- </para>
-
- </listitem>
- <listitem>
- <para>
- The hibernateDeployer is optional, the reason that why we had the hibernateDeployer is that we can reuse the hibernateSessionFactory in the jboss idm configuration file.
- </para>
-
- </listitem>
- <listitem>
- <para>
- The Initializer is optional, it is responsible for populating the db schema and initialized dataset if any.
- </para>
-
- </listitem>
-
- </itemizedlist>
- <para>
- detailed information about the deployment file is specified in the identity-deployer.xsd file.
- </para>
- <para>
- Once you've deployed the idm into JBoss AS5, by using the distribution. It will copy the idm-deployer into the JBoss AS5/server/$config/deployers folder, and the idm folder into the JBoss AS5/server/$config/deploy folder, which contains the default configuration files, like the jboss.idm.cfg.xml, idm-ds.xml etc.
- </para>
-
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Examples.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Examples.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Examples.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,36 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-Examples">
- <title>Examples</title>
- <para>
- As PicketLink IDM is a Maven2 based project it is very easy to leverage it from this build system. There is a ready to use Maven2 example project in the svn. It contains three sample test cases for with following configurations:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- database setup
- </para>
-
- </listitem>
- <listitem>
- <para>
- LDAP setup
- </para>
-
- </listitem>
- <listitem>
- <para>
- mixed LDAP + database setup
- </para>
-
- </listitem>
-
- </itemizedlist>
- <para>
- Sample project uses embedded OpenDS and HSQLDB so there is no need for any additional setup to be able to play with the API.
- </para>
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/FallbackIdentityStoreRepository.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/FallbackIdentityStoreRepository.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/FallbackIdentityStoreRepository.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,50 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-FallbackIdentityStoreRepository">
- <title>FallbackIdentityStoreRepository</title>
- <section id="sect-PicketLink_IDM_Reference_Guide-FallbackIdentityStoreRepository-ClassName">
- <title>ClassName</title>
- <para>
- org.picketlink.idm.impl.repository.FallbackIdentityStoreRepository
- </para>
-
- </section>
-
- <section id="sect-PicketLink_IDM_Reference_Guide-FallbackIdentityStoreRepository-Behaviour">
- <title>Behaviour</title>
- <para>
- Resolves proper IdentityStore from IdentityObjectType mapping and delegates method invocation. For relationship related methods, if both IdentityObjectTypes are not mapped in one store, repository will try to sync them and associate in defaultIdentityStore. For attributes that are not mapped inside mapped IdentityStore repository will try to assign those attributes in defaultAttributeStore.
- </para>
-
- </section>
-
- <section id="sect-PicketLink_IDM_Reference_Guide-FallbackIdentityStoreRepository-Configuration_Options">
- <title>Configuration Options</title>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">allowNotDefinedAttributes</emphasis> - if mapped IdentityStore doesn't support any attribute that was passed in method invocation FallbackIdentityStoreRepository will try to store it in defaultAttributeStore. If this option is set to true such attribute will be passed to defaultAttributeStore even if it is not mapped there.
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </section>
-
- <section id="sect-PicketLink_IDM_Reference_Guide-FallbackIdentityStoreRepository-Sample_Configuration">
- <title>Sample Configuration</title>
-
-<programlisting language="XML" role="XML"><xi:include href="extras/sample_config3.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <para>
- The <emphasis role="bold">readOnly</emphasis> options specifies that the only write operation performed on the store will be password update.
- </para>
-
- </section>
-
-
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Group_And_Roles.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Group_And_Roles.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Group_And_Roles.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,27 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-Groups_and_Roles">
- <title>Groups and Roles</title>
- <para>
- Groups are entities that can contain other groups or identity objects which can be associated in tree-like organizational structures. These structures do not need to be hierarchical only, as a single group can be a member of many other groups (that is; a group can have many parents).
- </para>
- <para>
- Possible relationships between groups are controlled with group types. Administrators can configure which different group types can be associated or even which group types can or can not contain identity objects. Groups have unique names per group type. This allows the existance of two groups with the same name, provided they have different group types.
- </para>
- <para>
- Roles form connections between <emphasis>Identity</emphasis> and <emphasis>Group</emphasis> objects. A practical example of this is if we posit that user <emphasis role="bold">John</emphasis> is the <emphasis role="bold">Manager</emphasis> of <emphasis role="bold">XX Team"</emphasis>. In this example you can see how the role form the link between an Identity and a group; <emphasis role="bold">John</emphasis> (an <emphasis>Identity</emphasis>) is the <emphasis role="bold">Manager</emphasis> (a <emphasis>Role</emphasis>) of <emphasis role="bold">XX Team</emphasis> (a <emphasis>Group</emphasis>).
- </para>
- <para>
- This type of information is difficult to map with typical Group objects as <emphasis>John</emphasis> can be a manager of several different groups. Futhermore, other identities (<emphasis>Mary</emphasis>, <emphasis>Jack</emphasis> or <emphasis>Stan</emphasis>) could have the same <emphasis>RoleType</emphasis> in different groups (<emphasis>XY Team</emphasis> or <emphasis>YY Team</emphasis>).
- </para>
- <para>
- Within each Realm (the concept of Realms is described later) we can define several RoleType objects with unique names. Each Role defines a unique combination of Identity, Group and RoleType within a Realm.
- </para>
- <para>
- The Role concept is very powerful but it does not fit easily into all identity store types. While quite easy to map in a relational database it does not fit into every LDAP tree present in organizations. Because of this Role support is optional in the API level
- </para>
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Hibernate_IdentityStore.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Hibernate_IdentityStore.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Hibernate_IdentityStore.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,119 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-Hibernate_IdentityStore">
- <title>Hibernate IdentityStore</title>
- <section id="sect-PicketLink_IDM_Reference_Guide-Hibernate_IdentityStore-Class_Name">
- <title>Class Name</title>
- <para>
- org.picketlink.idm.impl.store.hibernate.HibernateIdentityStoreImpl
- </para>
-
- </section>
-
- <section id="sect-PicketLink_IDM_Reference_Guide-Hibernate_IdentityStore-Overview">
- <title>Overview</title>
- <para>
- HibernateIdentityStoreImpl maps PicketLink IDM SPI model into Hibernate entities. This enables to use any RDBMS supported by Hibernate as identity persistence store (IdentityStore). Because of flexibility that ORM gives this IdentityStore implementation support all of the optional design concepts like role management. It can be used as the default IdentityStore together with other more limited implementations. For example in combination with LDAP IdentityStore it can handle IdentityObject attributes that are not supported in LDAP schema. In such configuration part of IdentityObject profile will be stored in LDAP and part in relational database. To learn more about such setup please read FallbackIdentityStoreRepository documentation. In current version implementation doesn't have any caching mechanism besides of what can be set in hibernate configuration
- </para>
-
- </section>
-
- <section id="sect-PicketLink_IDM_Reference_Guide-Hibernate_IdentityStore-Configuration_Options">
- <title>Configuration Options</title>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">hibernateConfiguration</emphasis> - the hibernate configuration file that will be used to create SessionFactory
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">hibernateSessionFactoryJNDIName</emphasis> - JNDI name of hibernate SessionFactory that will be used to obtain it
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">hibernateSessionFactoryRegistryName</emphasis> - name of hibernate SessionFactory placed in the IdentityConfigurationRegistry that will be used to obtain it
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">addHibernateMappings</emphasis> - of set to true all annotated hibernate model classes will be added to the hibernate configuration before SessionFactory is created
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">populateRelationshipTypes</emphasis> - true/false - Populate configured <supported-relationship-types> (IdentityObjectRelationshipType in SPI model) during IdentityStore initialization. Default value is 'false'
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">populateIdentityObjectTypes</emphasis> - true/false - Populate configured <supported-identity-object-types> (IdentityObjectType in SPI model) during IdentityStore initialization. Default value is 'false'
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">allowNotDefinedAttributes</emphasis> - true/false - Allow to set IdentityObject attributes that are not specified in <identity-object-type> configuration. Such attributes are assumed to have "text" type and many values. Default value is 'false'.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">isRealmAware</emphasis> - true/false - If set to true HibernateIdentityStoreImpl will create separate namespaces for different Realms from which method invocations come. This means that each IdentityObject, IdentityObjectRelationship and IdentityObjectRelationshipName will be connected and only accessible with a realm name in which it was created. Entities representing IdentityObjectType, IdentityObjectCredentialType and IdentityObjectRelationshipType are always same for all realms and not affected with this option. Default value is 'false'.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">manageTransactionDuringBootstrap</emphasis> - true/false - indicate that transactions should be managed manually during store bootstrap when initial entities are created.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">allowNotDefinedIdentityObjectTypes</emphasis> - true/false - indicate that store won't check for a given IdentityObjectType configuration and if one is not specified it will be just lazily created. This option enables to have minimal xml config without definition of all constraints in relationship between types.
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
-
- </section>
-
- <section id="sect-PicketLink_IDM_Reference_Guide-Hibernate_IdentityStore-Sample_Configuration">
- <title>Sample Configuration</title>
-
-<programlisting language="XML" role="XML"><xi:include href="extras/sample_config.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <para>
- In case 'addHibernateMappings' option is not set to true hibernate configuration need to list all annotated model classes:
- </para>
-
-<programlisting><mapping resource="mappings/HibernateRealm.hbm.xml"/>
-<mapping resource="mappings/HibernateIdentityObjectCredentialBinaryValue.hbm.xml"/>
-<mapping resource="mappings/HibernateIdentityObjectAttributeBinaryValue.hbm.xml"/>
-<mapping resource="mappings/HibernateIdentityObject.hbm.xml"/>
-<mapping resource="mappings/HibernateIdentityObjectCredential.hbm.xml"/>
-<mapping resource="mappings/HibernateIdentityObjectCredentialType.hbm.xml"/>
-<mapping resource="mappings/HibernateIdentityObjectAttribute.hbm.xml"/>
-<mapping resource="mappings/HibernateIdentityObjectType.hbm.xml"/>
-<mapping resource="mappings/HibernateIdentityObjectRelationship.hbm.xml"/>
-<mapping resource="mappings/HibernateIdentityObjectRelationshipType.hbm.xml"/>
-<mapping resource="mappings/HibernateIdentityObjectRelationshipName.hbm.xml"/></programlisting>
-
- </section>
-
-
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/IdentitySessionFactory.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/IdentitySessionFactory.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/IdentitySessionFactory.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,33 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-IdentitySessionFactory">
- <title>IdentitySessionFactory</title>
- <para>
- IdentitySessionFactory interface is a main entry point into the API. Default implementation IdentitySessionFactoryImpl has two constructors:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- public IdentitySessionFactoryImpl(IdentityConfigurationMetaData configMD) throws Exception
- </para>
-
- </listitem>
- <listitem>
- <para>
- public IdentitySessionFactoryImpl(File configFile) throws Exception
- </para>
-
- </listitem>
-
- </itemizedlist>
- <para>
- Framework configuration can be defined in two ways. It can be passed as implementation of a set of metadata interfaces grouped in org.picketlink.idm.spi.configuration.metadata package. Main one is IdentityConfigurationMetaData.
- </para>
- <para>
- Other possibility is to use xml configuration file that will be unmarshaled into JAXB model (org.picketlink.idm.impl.configuration.jaxb2.generated package) and used to create IdentityConfigurationMetaData object. XML configuration is described by identity-config.xsd file. It is good to take a look at the example organization-test-config.xml that is used in the testsuite.
- </para>
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/IdentityStore.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/IdentityStore.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/IdentityStore.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,148 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-IdentityStore">
- <title>IdentityStore</title>
- <para>
- This part is represented by <emphasis role="bold"><stores><identity-store>...</emphasis> element
- </para>
-
-<programlisting><stores>
- <attribute-stores/>
- <identity-stores>
- <identity-store> ... </identity-store>
- <identity-store> ... </identity-store>
- </identity-stores>
- </stores></programlisting>
- <note>
- <para>
- <emphasis role="bold"><stores/></emphasis> element contains <emphasis role="bold"><identity-store></emphasis> and <emphasis role="bold"><attribute-store></emphasis> elements. Currently <emphasis role="bold"><attribute-store></emphasis> configuration is ignored so only <emphasis role="bold"><identity-store></emphasis> elements can be configured.
- </para>
-
- </note>
-
-<programlisting language="XML" role="XML"><xi:include href="extras/identity-store.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <para>
- <emphasis role="bold"><identity-store></emphasis> element:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">id</emphasis> - IdentityStore id
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">class</emphasis> - IdentityStore class name
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">external-config</emphasis> - external configuration file used by IdentityStore
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">supported-relationship-types</emphasis> - IdentityObjectRelationshipType names that are supported by this IdentityStore. JBOSS_IDENTITY_MEMBERSHIP is standard value used by default framework implementation for membership type relationships (between two Group objects) and JBOSS_IDENTITY_ROLE is standard value for Role type memberships (named relationships)
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">supported-identity-object-types</emphasis> - configuration of IdentityObjectType objects mapped by IdentityStore
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">options</emphasis> - other IdentityStore configuration options
- </para>
-
- </listitem>
-
- </itemizedlist>
-
-<programlisting language="XML" role="XML"><xi:include href="extras/identity-object-type.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <para>
- <identity-object-type> element:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">name</emphasis>- IdentityObjectType name
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">relationships</emphasis> - relationships in which IdentityObjectType can be parent side. <emphasis role="bold"><relationship-type-ref></emphasis> must point to one of values from <emphasis role="bold"><supported-relationship-types></emphasis> . <emphasis role="bold"><identity-object-type-ref></emphasis> must be one of <emphasis role="bold"><identity-object-type><name></emphasis> values configured in this IdentityStore.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">credentials</emphasis> - IdentityObjectCredentialType names allowed for this IdentityObjectType
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">attributes</emphasis> - allowed attribute mappings. Each contains:
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">name</emphasis> - attribute name
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">mapping</emphasis> - real name to be used inside IdentityStore. For example LDAP attribute name
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">type</emphasis> - either "binary" or "text" value
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">isRequired</emphasis> - if attribute cannot have no values
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">isMultivalued</emphasis> - if attribute can have many values
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">isReadonly</emphasis> - if attribute values can be modified
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">options</emphasis> - other options for IdentityObjectType configuration
- </para>
-
- </listitem>
-
- </itemizedlist>
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/IdentityStoreRepository.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/IdentityStoreRepository.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/IdentityStoreRepository.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,56 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-IdentityStoreRepository">
- <title>IdentityStoreRepository</title>
- <para>
- This section is represented by <emphasis role="bold"> <repositories><repository></emphasis> element
- </para>
-
-<programlisting language="XML" role="XML"><xi:include href="extras/repositories.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <para>
- <emphasis role="bold"><repository></emphasis> element contains:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">id</emphasis> - IdentityStoreRepository id.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">class</emphasis> - class name of IdentityStoreRepository implementation.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">external-config</emphasis> - external configuration file used by IdentityStoreRepository.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">default-identity-store-id</emphasis> - id of configured IdentityStore to be used by default.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">default-attribute-store-id</emphasis> - id of configured AttributeStore (or IdentityStore) to be used by default
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">identity-store-mappings</emphasis> - optional element. Mappings between IdentityObjectType names and IdentityStore ids.
- </para>
-
- </listitem>
-
- </itemizedlist>
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Introduction.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Introduction.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Introduction.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,12 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-Introduction">
- <title>Introduction</title>
- <para>
- The most confusing part of the framework is probably connection between API and SPI. This part will try to explain how operations on API model are translated into the SPI. It will also enable to dive in the API and framework capabilities by looking on realcode examples
- </para>
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/LDAP_IdentityStore.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/LDAP_IdentityStore.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/LDAP_IdentityStore.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,239 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-LDAP_IdentityStore">
- <title>LDAP IdentityStore</title>
- <section id="sect-PicketLink_IDM_Reference_Guide-LDAP_IdentityStore-Class_Name">
- <title>Class Name</title>
- <para>
- org.picketlink.idm.impl.store.ldap.LDAPIdentityStoreImpl
- </para>
-
- </section>
-
- <section id="sect-PicketLink_IDM_Reference_Guide-LDAP_IdentityStore-Overview">
- <title>Overview</title>
- <para>
- LDAPIdentityStoreImpl provides support for LDAP as identity persistence store (IdentityStore). At this stage the implementation is a bit limitted:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Role management (IdentityObjectRelationshipName) is not supported
- </para>
-
- </listitem>
- <listitem>
- <para>
- Only "text" attribute type can be mapped
- </para>
-
- </listitem>
- <listitem>
- <para>
- Only "PASSWORD" <credential-type> can be mapped
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </section>
-
- <section id="sect-PicketLink_IDM_Reference_Guide-LDAP_IdentityStore-Configuration">
- <title>Configuration</title>
- <para>
- <identity-object-type><options>
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">idAttributeName</emphasis> - attribute name under which IdentityObject name is specified. Required.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">passwordAttributeName</emphasis> - attribute name under which IdentityObject password is specified. Optional.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">ctxDNs</emphasis> - DN that will be used as context for IdentityObject searches. More than one value can be specified.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">allowCreateEntry</emphasis> - true/false - Specify if new IdentityObject can be created.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">createEntryAttributeValues</emphasis> - defines a set of ldap attributes that will be set on IdentityObject entry creation. Values are in "name=value" format. This enables to fulfill LDAP schema requirements.Default is false
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">parentMembershipAttributeName</emphasis> - LDAP attribute that defines children of IdentityObject. This will be used to retrieved relationships from IdentityObject entry. Option is required if IdentityObjectType can be part of relationship.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">isParentMembershipAttributeDN</emphasis> - defines if values of attribute defined in parentMembershipAttributeName are fully qualified LDAP DNs.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">allowEmptyMemberships</emphasis> - defines if IdentityObject entry can have no members. Sometimes it is not allowed by LDAP schema.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">parentMembershipAttributePlaceholder</emphasis> - if LDAP schema doesn't allow empty memberships this value will be used as a placeholder. IdentityObject specified here won't be recognized as a member and ignored
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">childMembershipAttributeName</emphasis> - LDAP attribute that defines parents of IdentityObject. This will be used to retrieved relationships from IdentityObject entry. Good example of such attribute in LDAP schema is 'memberOf'
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">childMembershipAttributeDN</emphasis> - defines if values of attribute defined in childMembershipAttributeName are fully qualified LDAP DNs.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">childMembershipAttributeVirtual</emphasis> - specifies if attribute defined in 'childMembershipAttributeName' is a real attribute that can be updated or virtual one which value is managed by a directory and should not be updated
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">entrySearchFilter</emphasis> - ldap filter to search IdentityObject with. {0} will be substitute with IdentityObject name. Example filter can look like this: "(uid={0})". This substitution behavior comes from the standard DirContext.search(Name, String, Object, SearchControls cons) method
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">entrySearchScope</emphasis> - defines a search scope. Values can be "subtree" and "object"
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">enclosePasswordWith</emphasis> - if specified password will be surunted with a given chars before update
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">passwordEncoding</emphasis> - if specified password will be encoded before update. For example Microsoft Active Directory requires password to be enclosed with '"' and encoded using 'UTF-16LE' for update.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">passwordUpdateAttributeValues</emphasis> - list of attributes that should be changed during password update
- </para>
-
- </listitem>
-
- </itemizedlist>
- <para>
- <emphasis role="bold"><identity-store><options></emphasis>
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">providerURL</emphasis> - LDAP connection URL. For example "ldap://localhost:389"
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">adminDN</emphasis> - LDAP entry used to connect to the server.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">adminPassword</emphasis> - password related to adminDN
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">searchTimeLimit</emphasis> -searchTimeLimit for LDAP search operations in miliseconds. Default value is 10000.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">customJNDIConnectionParameters</emphasis> - list of additional 'key=value' parameters that will be used to create JNDI context. Can be usefull to use additional JNDI options.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">customSystemProperties</emphasis> - list of 'key=value' properties that will be added using System.setProperty() method. This can be used to configure LDAP JNDI connection pooling which is set per JVM
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">externalJNDIContext</emphasis> - name that will be used to perform JDNI lookup to grab JNDI connection context
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">sortExtensionSupported</emphasis> - if set to "false" will disable the use of sort extension that triggers sort on LDAP server side
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">pagedResultsExtensionSupported</emphasis> - if set to "true" will enable paged search. Searches that exceed size defined by "pagedResultsExtensionSize" option will be splitted into few smaller ones.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">pagedResultsExtensionSize</emphasis> - defines page size for "pagedResultsExtensionSupported" option.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">createMissingContexts</emphasis> - if set to "true" LDAP store will try to create missing LDAP contexts defined in the configuration.
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </section>
-
- <section id="sect-PicketLink_IDM_Reference_Guide-LDAP_IdentityStore-Sample_Configuration">
- <title>Sample Configuration</title>
-
-<programlisting language="XML" role="XML"><xi:include href="extras/sample_config2.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
-
- </section>
-
-
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Main_Concepts.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Main_Concepts.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Main_Concepts.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,93 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-Main_Concepts">
- <title>Main Concepts</title>
-
- <variablelist>
- <title>Terms</title>
- <varlistentry>
- <term>PicketLink</term>
- <listitem>
- <para>
- PicketLink is an umbrella project that aims to address different Identity Management needs.
- </para>
- <!--http://www.jboss.org/picketlink-->
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>IDM</term>
- <listitem>
- <para>
- IDM stand for <emphasis role="bold">ID</emphasis>entity <emphasis role="bold">M</emphasis>anagement.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Identity Management</term>
- <listitem>
- <para>
- Identity management deals with the management of digital identities. Typically these identities are used to authenticate an organizations users so as to control access to organizational resources. However, other entities, including devices, processes and applications, in a networked environment may be represtented in the identity model.
- </para>
- <!--http://download.oracle.com/docs/cd/B14099_19/core.1012/b13995/glossary.htm#sthref2905-->
- <!--http://download.oracle.com/docs/cd/B14099_19/idmanage.1012/b14080/glossary.htm#sthref2905-->
-
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>API</term>
- <listitem>
- <para>
- An <emphasis role="bold">A</emphasis>pplication <emphasis role="bold">P</emphasis>rogramming <emphasis role="bold">I</emphasis>nterface (<emphasis role="bold">API</emphasis>) is a set of specifications that allow applications that use the same API to communicate and share data.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>SPI</term>
- <listitem>
- <para>
- An <emphasis role="bold">S</emphasis>ervice <emphasis role="bold">P</emphasis>rovider <emphasis role="bold">I</emphasis>nterface (<emphasis role="bold">SPI</emphasis>) is the set of specifications that a service defines.
- </para>
- <!--http://www.developer.com/java/article.php/3848881/Service-Provider-Interface-Creating-Extensible-Java-Applications.htm-->
- </listitem>
- </varlistentry>
- </variablelist>
- <para>
- PicketLink IDM aims to provide a common identity model for various JBoss projects. As every project has specific needs, designing a common API and identity model that will fit all of them can be difficult. Therefore the PicketLink IDM architecture consists of two main parts:
- </para>
- <variablelist>
- <title></title>
- <varlistentry>
- <term>Core SPI</term>
- <listitem>
- <para>
- The PicketLink <emphasis role="bold">SPI</emphasis> uses an abstract identity model that provides the flexibility for defining different identity object types and possible relationships between them.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Common API</term>
- <listitem>
- <para>
- The PcketLink <emphasis role="bold">API</emphasis> uses a simpler identity model that fits most common use cases. Identity model has more strictly defined object types and possible relationships.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
- <mediaobject>
- <imageobject role="html">
- <imagedata fileref="images/IDM-global-arch.png" format="PNG" align="center"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata fileref="images/IDM-global-arch.png" format="PNG" align="center" width="120mm"/>
- </imageobject>
- </mediaobject>
- <para>
- Too much abstraction in the API layer would confuse people using the framework. One of the goals is to make the design easily extendible. Framework adopters should be able to remove the API layer and reuse core SPI implementation if needed.
- </para>
-
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Minimal_Configuration.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Minimal_Configuration.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Minimal_Configuration.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,15 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-Minimal_Configuration">
- <title>Minimal Configuration</title>
- <para>
- The main role of configuration is to define relationship between separate framework components. It also enables to specify a lot of meta data information describing possible connections between IdentityObject types. It is however possible to not define all those meta data information and let the framework to be maximum permissive about allowed operations and lazily create not defined types:
- </para>
-
-<programlisting language="XML" role="XML"><xi:include href="extras/lazy-config.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
-
-</chapter>
-
Modified: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/PicketLink_IDM_Reference_Guide.ent
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/PicketLink_IDM_Reference_Guide.ent 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/PicketLink_IDM_Reference_Guide.ent 2011-08-29 07:26:00 UTC (rev 7244)
@@ -15,5 +15,5 @@
<!-- Version Specifcs: -->
<!ENTITY VX "5">
-<!ENTITY VY "5.1">
-<!ENTITY VZ "5.1.1">
\ No newline at end of file
+<!ENTITY VY "5.2">
+<!ENTITY VZ "5.2.0">
\ No newline at end of file
Modified: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/PicketLink_IDM_Reference_Guide.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/PicketLink_IDM_Reference_Guide.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/PicketLink_IDM_Reference_Guide.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -6,74 +6,15 @@
<book>
<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <part id="part-PicketLink_IDM_Reference_Guide-Design_and_Architecture">
- <title>Design and Architecture</title>
- <xi:include href="Main_Concepts.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="API_Model.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Group_And_Roles.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <!--Edited to here.-->
- <xi:include href="SPI_Model.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Architecture.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Realms.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- </part>
- <part id="part-PicketLink_IDM_Reference_Guide-Concepts_behind_API_to_SPI_mappings">
- <title>Concepts behind API to SPI mappings</title>
- <xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="User_and_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Associations.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Role.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- </part>
- <part id="part-PicketLink_IDM_Reference_Guide-Quick_Start">
- <title>Quick Start</title>
- <xi:include href="Test_Cases.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Examples.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Core_Files.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- </part>
- <part id="part-PicketLink_IDM_Reference_Guide-Configuration">
- <title>Configuration</title>
- <xi:include href="IdentitySessionFactory.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="XML_Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="IdentityStore.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="IdentityStoreRepository.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Realm.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Realm_Templates.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="API_Cache.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- </part>
- <part id="part-PicketLink_IDM_Reference_Guide-IdentityStore_Implementations">
- <title>IdentityStore Implementations</title>
- <xi:include href="Hibernate_IdentityStore.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="LDAP_IdentityStore.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Minimal_Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- </part>
- <part id="part-PicketLink_IDM_Reference_Guide-IdentityStoreRepository_Implementations">
- <title>IdentityStoreRepository Implementations</title>
- <xi:include href="WrapperIdentityStoreRepository.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="FallbackIdentityStoreRepository.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- </part>
- <part id="part-PicketLink_IDM_Reference_Guide-Attributes">
- <title>Attributes</title>
- <xi:include href="API.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="SPI.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- </part>
- <part id="part-PicketLink_IDM_Reference_Guide-Credentials">
- <title>Credentials</title>
- <xi:include href="Credential_API.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Credential_SPI.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- </part>
- <part id="part-PicketLink_IDM_Reference_Guide-Deployment">
- <title>Deployment</title>
- <xi:include href="Usage_Scenario.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Deployment.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
- </part>
+ <xi:include href="modules/chap_Design_and_Architecture.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/chap_Concepts_API_SPI.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/chap_Quick_Start.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/chap_Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/chap_IdentityStore_Implementations.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/chap_IdentityStoreRepository_Implementations.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/chap_Attributes.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/chap_Credentials.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="modules/chap_Deployment.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>
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Realm.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Realm.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Realm.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,54 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-Realm">
- <title>Realm</title>
- <para>
- This section is represented by <emphasis role="bold"><realms><realm></emphasis> element
- </para>
-
-<programlisting><realm>
- <id>realm://RedHat/DB</id>
- <repository-id-ref>RedHat Repository DB</repository-id-ref>
- <identity-type-mappings>
- <identity-mapping>IDENTITY</identity-mapping>
- </identity-type-mappings>
-</realm></programlisting>
- <para>
- <emphasis role="bold"><realm></emphasis> element contains:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">id</emphasis> - realm id
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">repository-id-ref</emphasis> - id of configured IdentityStoreRepository
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">identity-type-mappings</emphasis> <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">identity-mapping</emphasis> - name of IdentityObjectType that should be maped as Identity object on the API side
- </para>
-
- </listitem>
-
- </itemizedlist>
-
- </para>
-
- </listitem>
-
- </itemizedlist>
-
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Realm_Templates.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Realm_Templates.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Realm_Templates.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,51 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-Realm_Templates">
- <title>Realm Templates</title>
- <para>
- Realm can be marked as a template. This means that if a different realm name is requested using the API and such name contains template realm as a prefix then this realm configuration will be used
- </para>
-
-<programlisting><realm>
- <id>idm_realm</id>
- <repository-id-ref>DefaultRepository</repository-id-ref>
- <identity-type-mappings>
- <user-mapping>USER</user-mapping>
- </identity-type-mappings>
- <options>
- <option>
- <name>template</name>
- <value>true</value>
- </option>
- </options>
- </realm></programlisting>
- <para>
- In this example for "idm_realm_foo" framework will return "idm_realm" configuration. Request for "foo" realm won't return valid configuration.
- </para>
-
-<programlisting><realms>
- <realm>
- <id>idm_realm</id>
- <repository-id-ref>DefaultRepository</repository-id-ref>
- <identity-type-mappings>
- <user-mapping>USER</user-mapping>
- </identity-type-mappings>
-
- </realm>
- </realms>
- <repositories>...</repositories>
- <stores>...</stores>
- <options>
- <option>
- <name>defaultTemplate</name>
- <value>idm_realm</value>
- </option>
- </options></programlisting>
- <para>
- The "defaultTemplate" option defines idm_realm as the one that should be used when requested realm name is not found in configuration
- </para>
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Realms.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Realms.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Realms.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,22 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-Realms">
- <title>Realms</title>
- <para>
- The purpose of a Realm is to group configuration of several identity stores. IdentitySession exposes operations within single Realm
- </para>
- <mediaobject>
- <imageobject>
- <imagedata contentdepth="6in" contentwidth="6in" fileref="images/IDM-global-realm.png" width="444" />
- </imageobject>
- <caption align="right"> <para>
- <emphasis role="bold">PicketLink IDM architecture</emphasis>
- </para>
- </caption>
- </mediaobject>
-
-</chapter>
-
Modified: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Revision_History.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Revision_History.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -3,31 +3,24 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
%BOOK_ENTITIES;
]>
-<appendix id="appe-PicketLink_IDM_Reference_Guide-Revision_History">
- <title>Revision History</title>
- <simpara>
- <revhistory>
- <revision>
- <revnumber>0-0</revnumber>
- <date>Mon Aug 1 2011</date>
- <author>
- <firstname>Dude</firstname>
- <surname>McPants</surname>
- <email>Dude.McPants(a)example.com</email>
-
- </author>
- <revdescription>
- <simplelist>
- <member>Initial creation of book by publican</member>
-
- </simplelist>
-
- </revdescription>
-
- </revision>
-
- </revhistory>
-
- </simpara>
-</appendix>
-
+<appendix id="appe-Release_Notes-Revision_History">
+ <title>Revision History</title>
+ <simpara>
+ <revhistory>
+ <revision>
+ <revnumber>5.2.0-1</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
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Role.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Role.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Role.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,60 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-Role">
- <title>Role</title>
- <para>
- Roles are direct typed connections between Identity and Group objects. If you think about a sentence: "John is the Manager of XX Team" what matters is the context. So "John (Identity) is the Manager (RoleType) of XX Team (Group)". The whole sentence describes the Role that John has. This type of information is hard to map with typical Group object as John can be a manager of several different groups and other identities (Marry, Jack, Stan...) can have the same RoleType in context of different groups (XY Team, YY Team). Within each Realm (concept of Realms is described later) we can define several RoleType objects with unique names. Each Role defines a unique combination of Identity, Group and RoleType within Realm.
- </para>
- <para>
- Roles are managed with RoleManager interface:
- </para>
-
-<programlisting role="Java">
-RoleManager roleManager = identitySession.getRoleManager();
-
-roleManager.createRoleType("manager");
-RoleType adminRT = roleManager.createRoleType("administrator");
-
-Role role1 = roleManager.createRole("manager", annUser.getId(), parisOffice.getId());
-roleManager.createRole(adminRT, stefanUser, itDep);
-
-assertTrue(roleManager.hasRole(stefanUser, itDep, adminRT));
-</programlisting>
- <para>
- At the SPI level the main difference between plain association is that IdentityObjectRelationship has a IdentityObjectRelationshipName which is simple mapping of a RoleType used in the API
- </para>
- <mediaobject>
- <imageobject>
- <imagedata contentdepth="6in" contentwidth="6in" fileref="images/SPI3.png" width="444" />
- </imageobject>
- <!-- <caption align="right"> --> <!-- <para> --> <!-- <emphasis role="bold"></emphasis> --> <!-- </para> --> <!-- </caption> -->
- </mediaobject>
- <para>
- What is important to note about the Role concept is that it is not natural in all kinds of identity stores. Entities represented on attached figures are easy to map in the database. However in store like LDAP typical relationships are represanted in a more plain manner. For example:
- </para>
-
-<programlisting>dn: uid=admin,ou=People,o=test,dc=portal,dc=example,dc=com
-objectclass: top
-objectclass: inetOrgPerson
-objectclass: person
-uid: admin
-cn: Java Duke
-sn: Duke
-userPassword: admin
-mail: email(a)email.com
-
-dn: cn=Administrators,ou=Groups,o=test,dc=portal,dc=example,dc=com
-objectClass: top
-objectClass: groupOfNames
-cn: Administrators
-description: Portal admin role
-member: uid=admin,ou=People,o=test,dc=portal,dc=example,dc=com</programlisting>
- <para>
- The whole relationship between User "admin" and Group "Administrators" is described by one attribute value ("member"). In such typical LDAP tree shape there is no place to store additional information that are needed to describe Role shown above. Obviously it is possible to shape LDAP tree in a way that will allow such a mapping but in most cases it is not possible to redesign already used LDAP server tree.
- </para>
-
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/SPI.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/SPI.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/SPI.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,66 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-SPI">
- <title>SPI</title>
- <para>
- On the SPI level IdentityObject can be associated with several IdentityObjectAttribute objects. IdentityObjectAttribute is described by IdentityObjectAttributeMetaData object that contains its properties such as:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">name</emphasis> - attribute name
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">readonly</emphasis> - if attribute values can be changed
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">multivalued</emphasis> - if attribute can have many values
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">required</emphasis> - if attribute can be removed
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">type</emphasis> - type of attribute values.
- </para>
-
- </listitem>
-
- </itemizedlist>
- <para>
- IdentityObjectAttribute types supported by default implementations are the same as in the API level:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">text</emphasis> - java.lang.String object
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">binary</emphasis> - byte[] object
- </para>
-
- </listitem>
-
- </itemizedlist>
- <para>
- All operations related to IdentityObjectAttribute are exposed by the AttributeStore interface
- </para>
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/SPI_Model.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/SPI_Model.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/SPI_Model.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,61 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-SPI_Abstract_Model">
- <title>SPI (Abstract) Model</title>
- <para>
- SPI Model contains following interfaces:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">org.picketlink.idm.spi.model.IdentityObject</emphasis> - represents identity object. Contains information about object name and type (IdentityObjectType). Name and IdentityObjectType pair should be unique within realm.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">org.picketlink.idm.spi.model.IdentityObjectType</emphasis> - represents identity object type. Name of IdentityType is unique.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">org.picketlink.idm.spi.model.IdentityObjectAttribute</emphasis> - attribute assigned to IdentityObject
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">org.picketlink.idm.spi.model.IdentityObjectCredential</emphasis> - credential assigned to IdentityObject
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">org.picketlink.idm.spi.model.IdentityObjectCredentialType</emphasis> - represents type of IdentityObjectCredential.
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">org.picketlink.idm.spi.model.IdentityObjectRelationship</emphasis> - Directional relationship between two IdentityObject objects. Relationship is directional as it keeps information about from and to IdentityObject. Each IdentityObjectRelationship has a type (IdentityObjectRelationshipType) and can have a name (not required).
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold">org.picketlink.idm.spi.model.IdentityObjectRelationshipType</emphasis> - named type of relationship
- </para>
-
- </listitem>
-
- </itemizedlist>
- <para>
- Model described above is very flexible as IdentityObjectType is able to map any kind of entities. Identity object and Group/GroupType objects are only one of many possible options (API is a subset of SPI possibilities). IdentityObjectRelationship defines a connection between any two IdentityObject objects. Each IdentityObjectRelationship has a type. To map previously described API two IdentityObjectRelationshipType objects are needed. One to map normal MEMBERSHIP like between an Identity and a Group or Group and Group objects. Second one to map Role concept. For API Role - RoleType refers to the name of the IdentityObjectRelationship. In default Hibernate implementation possible names of IdentityObjectRelationship are kept in a separate table. All of those can be easily redefined to support different kind of API.
- </para>
-
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Test_Cases.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Test_Cases.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Test_Cases.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,12 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-Test_Cases">
- <title>Test Cases</title>
- <para>
- One of the best ways to get familiar with the PicketLink IDM component is to look at the source code. You will find link to the subversion repository in the project webpage. There are couple of quite meaningful testcases there. One of the best to start with is OrganizationTest under 'idm-testsuite' module . It contains two example identity structures. One mapping hierarchical organization of Red Hat and JBoss projects and the other describes theoretical portal tree for ACME company.
- </para>
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Usage_Scenario.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Usage_Scenario.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/Usage_Scenario.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,38 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-IDM_Usage_Scenario">
- <title>IDM Usage Scenario</title>
- <para>
- There are two ways to use the jboss idm:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Use it as the embedded way
- </para>
-
- </listitem>
- <listitem>
- <para>
- Deploy it into the container (JBoss AS5), and then all other projects can use it by getting IdentitySessionFactory from JNDI.
- </para>
-
- </listitem>
-
- </itemizedlist>
- <para>
- For the 1st case, users need to use the API to start the IdentitySessionFactory, and then use it. The code is as following, which you can find on the example module.
- </para>
-
-<programlisting>IdentitySessionFactory identitySessionFactory = new IdentityConfigurationImpl().
-configure(new File("src/test/resources/example-db-config.xml")).buildIdentitySessionFactory();
-IdentitySession identitySession = identitySessionFactory.createIdentitySession("realm://JBossIdentityExample/SampleRealm");
-</programlisting>
- <para>
- And then use the IdentitySession to do the operations etc. So it is very easy to use. We will look closer at the second scenario in the next chapter
- </para>
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/User_and_Group.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/User_and_Group.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/User_and_Group.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,37 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-User_and_Group">
- <title>User and Group</title>
- <para>
- Objects represented by User and Group interfaces are managed by PersistenceManager. In the example below 3 users and 4 groups are created.
- </para>
-
-<programlisting role="Java">PersistenceManager pm = identitySession.getPersistenceManager();
-User johnUser = pm.createUser("John");
-User annUser = pm.createUser("Ann");
-User stefanUser = pm.createUser("Stefan");
-
-String OFFICE = "OFFICE";
-String DEPARTMENT = "DEPARTMENT";
-
-Group parisOffice = pm.createGroup("Paris", OFFICE);
-Group atlantaOffice = pm.createGroup("Atlanta", OFFICE);
-
-assertEquals(OFFICE, parisOffice.getGroupType());
-
-Group itDep = pm.createGroup("IT", DEPARTMENT);
-Group hrDep = pm.createGroup("HR", DEPARTMENT);</programlisting>
- <para>
- At the SPI level both Group and User are mapped as IdentityObject. What differentiate them is the IdentityObjectType. IdentityObjectType "USER" is mapped to represent User objects while other are mapped to represent different Group types names.
- </para>
- <mediaobject>
- <imageobject>
- <imagedata contentdepth="6in" contentwidth="6in" fileref="images/SPI1.png" width="444" />
- </imageobject>
-
- </mediaobject>
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/WrapperIdentityStoreRepository.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/WrapperIdentityStoreRepository.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/WrapperIdentityStoreRepository.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,39 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-WrapperIdentityStoreRepository">
- <title>WrapperIdentityStoreRepository</title>
- <section id="sect-PicketLink_IDM_Reference_Guide-WrapperIdentityStoreRepository-ClassName">
- <title>ClassName</title>
- <para>
- org.picketlink.idm.impl.repository.WrapperIdentityStoreRepository
- </para>
-
- </section>
-
- <section id="sect-PicketLink_IDM_Reference_Guide-WrapperIdentityStoreRepository-Behaviour">
- <title>Behaviour</title>
- <para>
- Simply wraps single AttributeStore and IdentityStore and pass all method invocations
- </para>
-
- </section>
-
- <section id="sect-PicketLink_IDM_Reference_Guide-WrapperIdentityStoreRepository-Sample_Configuration">
- <title>Sample Configuration</title>
-
-<programlisting><repository>
- <id>Sample Repository</id
- <class>org.picketlink.idm.impl.repository.WrapperIdentityStoreRepository</class>
- <external-config/>
- <default-identity-store-id>LDAP Store</default-identity-store-id>
- <default-attribute-store-id>LDAP Store</default-attribute-store-id>
-</repository></programlisting>
-
- </section>
-
-
-</chapter>
-
Deleted: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/XML_Configuration.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/XML_Configuration.xml 2011-08-29 03:56:57 UTC (rev 7243)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/XML_Configuration.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -1,41 +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" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "PicketLink_IDM_Reference_Guide.ent">
-%BOOK_ENTITIES;
-]>
-<chapter id="chap-PicketLink_IDM_Reference_Guide-XML_Configuration">
- <title>XML Configuration</title>
-
-<programlisting><jboss-identity xmlns="urn:jboss:identity:idm:config:v1_0_alpha"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="urn:jboss:identity:idm:config:v1_0_alpha identity-config.xsd">
- <realms/>
- <repositories/>
- <stores/>
-</jboss-identity></programlisting>
- <para>
- Identity XML configuration can be divided into three parts:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold"><stores/></emphasis> - defines IdentityStore and AttributeStore instances
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold"><repositories/></emphasis> - defines IdentityStoreRepository instances
- </para>
-
- </listitem>
- <listitem>
- <para>
- <emphasis role="bold"><realms/></emphasis> - defines identity realms
- </para>
-
- </listitem>
-
- </itemizedlist>
-</chapter>
-
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Attributes/API.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Attributes/API.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Attributes/API.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,71 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-API">
+ <title>API</title>
+ <para>
+ On the API level each IdentityType object (Identity and Group) can have associated Attribute objects. All operations are exposed by AttributesManager interface. Each attribute is described with AttributeDescription that contains its properties such as:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">name</emphasis> - attribute name
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">readonly</emphasis> - if attribute values can be changed
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">multivalued</emphasis> - if attribute can have many values
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">required</emphasis> - if attribute can be removed
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">type</emphasis> - type of attribute values.
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+ <para>
+ Default implementation provides two attribute types:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">text</emphasis> - java.lang.String object
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">binary</emphasis> - byte[] object
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+ <section id="sect-PicketLink_IDM_Reference_Guide-API-Sample_operations">
+ <title>Sample operations</title>
+
+<programlisting role="Java"><xi:include href="../../extras/sample-operations.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+
+ </section>
+
+
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Attributes/SPI.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Attributes/SPI.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Attributes/SPI.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,66 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-SPI">
+ <title>SPI</title>
+ <para>
+ On the SPI level IdentityObject can be associated with several IdentityObjectAttribute objects. IdentityObjectAttribute is described by IdentityObjectAttributeMetaData object that contains its properties such as:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">name</emphasis> - attribute name
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">readonly</emphasis> - if attribute values can be changed
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">multivalued</emphasis> - if attribute can have many values
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">required</emphasis> - if attribute can be removed
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">type</emphasis> - type of attribute values.
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+ <para>
+ IdentityObjectAttribute types supported by default implementations are the same as in the API level:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">text</emphasis> - java.lang.String object
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">binary</emphasis> - byte[] object
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+ <para>
+ All operations related to IdentityObjectAttribute are exposed by the AttributeStore interface
+ </para>
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Concepts_API_SPI/Associations.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Concepts_API_SPI/Associations.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Concepts_API_SPI/Associations.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,33 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-Associations">
+ <title>Associations</title>
+ <para>
+ Group and Users can be associated. This represents simple relationship that can be described like "user John belongs to Group IT". Association can be created between Group and User or between two Groups.
+ </para>
+ <para>
+ Those operations are managed by RelationshipManager:
+ </para>
+
+<programlisting role="Java">
+RelationshipManager rm = identitySession.getRelationshipManager();
+
+rm.associateUser(parisOffice, annUser);
+rm.associateUser(atlantaOffice, stefanUser);
+rm.associateUser(itDep, stefanUser);
+
+assertTrue(rm.isAssociated(parisOffice, annUser));</programlisting>
+ <para>
+ At the SPI level this is mapped to IdentityObjectRelationship entity. This relationship has a type. Simple assotiations can be marked with a type named "JBOSS_IDENTITY_MEMBERSHIP" (this is implementation detail) which describes simple membership. Note that IdentityObjectRelationship creates a connection between any two IdentityObject entities.
+ </para>
+ <mediaobject>
+ <imageobject>
+ <imagedata contentdepth="6in" contentwidth="6in" fileref="images/SPI2.png" width="444" />
+ </imageobject>
+
+ </mediaobject>
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Concepts_API_SPI/Introduction.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Concepts_API_SPI/Introduction.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Concepts_API_SPI/Introduction.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-Introduction">
+ <title>Introduction</title>
+ <para>
+ The most confusing part of the framework is probably connection between API and SPI. This part will try to explain how operations on API model are translated into the SPI. It will also enable to dive in the API and framework capabilities by looking on realcode examples
+ </para>
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Concepts_API_SPI/Role.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Concepts_API_SPI/Role.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Concepts_API_SPI/Role.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,60 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-Role">
+ <title>Role</title>
+ <para>
+ Roles are direct typed connections between Identity and Group objects. If you think about a sentence: "John is the Manager of XX Team" what matters is the context. So "John (Identity) is the Manager (RoleType) of XX Team (Group)". The whole sentence describes the Role that John has. This type of information is hard to map with typical Group object as John can be a manager of several different groups and other identities (Marry, Jack, Stan...) can have the same RoleType in context of different groups (XY Team, YY Team). Within each Realm (concept of Realms is described later) we can define several RoleType objects with unique names. Each Role defines a unique combination of Identity, Group and RoleType within Realm.
+ </para>
+ <para>
+ Roles are managed with RoleManager interface:
+ </para>
+
+<programlisting role="Java">
+RoleManager roleManager = identitySession.getRoleManager();
+
+roleManager.createRoleType("manager");
+RoleType adminRT = roleManager.createRoleType("administrator");
+
+Role role1 = roleManager.createRole("manager", annUser.getId(), parisOffice.getId());
+roleManager.createRole(adminRT, stefanUser, itDep);
+
+assertTrue(roleManager.hasRole(stefanUser, itDep, adminRT));
+</programlisting>
+ <para>
+ At the SPI level the main difference between plain association is that IdentityObjectRelationship has a IdentityObjectRelationshipName which is simple mapping of a RoleType used in the API
+ </para>
+ <mediaobject>
+ <imageobject>
+ <imagedata contentdepth="6in" contentwidth="6in" fileref="images/SPI3.png" width="444" />
+ </imageobject>
+ <!-- <caption align="right"> --> <!-- <para> --> <!-- <emphasis role="bold"></emphasis> --> <!-- </para> --> <!-- </caption> -->
+ </mediaobject>
+ <para>
+ What is important to note about the Role concept is that it is not natural in all kinds of identity stores. Entities represented on attached figures are easy to map in the database. However in store like LDAP typical relationships are represanted in a more plain manner. For example:
+ </para>
+
+<programlisting>dn: uid=admin,ou=People,o=test,dc=portal,dc=example,dc=com
+objectclass: top
+objectclass: inetOrgPerson
+objectclass: person
+uid: admin
+cn: Java Duke
+sn: Duke
+userPassword: admin
+mail: email(a)email.com
+
+dn: cn=Administrators,ou=Groups,o=test,dc=portal,dc=example,dc=com
+objectClass: top
+objectClass: groupOfNames
+cn: Administrators
+description: Portal admin role
+member: uid=admin,ou=People,o=test,dc=portal,dc=example,dc=com</programlisting>
+ <para>
+ The whole relationship between User "admin" and Group "Administrators" is described by one attribute value ("member"). In such typical LDAP tree shape there is no place to store additional information that are needed to describe Role shown above. Obviously it is possible to shape LDAP tree in a way that will allow such a mapping but in most cases it is not possible to redesign already used LDAP server tree.
+ </para>
+
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Concepts_API_SPI/User_and_Group.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Concepts_API_SPI/User_and_Group.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Concepts_API_SPI/User_and_Group.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,37 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-User_and_Group">
+ <title>User and Group</title>
+ <para>
+ Objects represented by User and Group interfaces are managed by PersistenceManager. In the example below 3 users and 4 groups are created.
+ </para>
+
+<programlisting role="Java">PersistenceManager pm = identitySession.getPersistenceManager();
+User johnUser = pm.createUser("John");
+User annUser = pm.createUser("Ann");
+User stefanUser = pm.createUser("Stefan");
+
+String OFFICE = "OFFICE";
+String DEPARTMENT = "DEPARTMENT";
+
+Group parisOffice = pm.createGroup("Paris", OFFICE);
+Group atlantaOffice = pm.createGroup("Atlanta", OFFICE);
+
+assertEquals(OFFICE, parisOffice.getGroupType());
+
+Group itDep = pm.createGroup("IT", DEPARTMENT);
+Group hrDep = pm.createGroup("HR", DEPARTMENT);</programlisting>
+ <para>
+ At the SPI level both Group and User are mapped as IdentityObject. What differentiate them is the IdentityObjectType. IdentityObjectType "USER" is mapped to represent User objects while other are mapped to represent different Group types names.
+ </para>
+ <mediaobject>
+ <imageobject>
+ <imagedata contentdepth="6in" contentwidth="6in" fileref="images/SPI1.png" width="444" />
+ </imageobject>
+
+ </mediaobject>
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/API_Cache.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/API_Cache.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/API_Cache.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,51 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-API_Cache">
+ <title>API Cache</title>
+ <para>
+ At the realm level IDM API cache layer can be enabled
+ </para>
+
+<programlisting><realm>
+ <id>idm_realm</id>
+ <repository-id-ref>DefaultRepository</repository-id-ref>
+ <identity-type-mappings>
+ <user-mapping>USER</user-mapping>
+ </identity-type-mappings>
+ <options>
+ <option>
+ <name>cache.providerClass</name>
+ <value>JBossCacheAPICacheProviderImpl</value>
+ </option>
+ </options>
+</realm></programlisting>
+ <para>
+ Cache related options :
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">cache.providerClass</emphasis> - class implementing APICacheProvider interface
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">cache.providerRegistryName</emphasis> - id of instantiated APICacheProvider implementation stored in configuration registry
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">cache.scope</emphasis> - namespace used to store entities in cache. Can be "realm" (default) or "session".
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/IdentitySessionFactory.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/IdentitySessionFactory.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/IdentitySessionFactory.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,33 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-IdentitySessionFactory">
+ <title>IdentitySessionFactory</title>
+ <para>
+ IdentitySessionFactory interface is a main entry point into the API. Default implementation IdentitySessionFactoryImpl has two constructors:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ public IdentitySessionFactoryImpl(IdentityConfigurationMetaData configMD) throws Exception
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ public IdentitySessionFactoryImpl(File configFile) throws Exception
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+ <para>
+ Framework configuration can be defined in two ways. It can be passed as implementation of a set of metadata interfaces grouped in org.picketlink.idm.spi.configuration.metadata package. Main one is IdentityConfigurationMetaData.
+ </para>
+ <para>
+ Other possibility is to use xml configuration file that will be unmarshaled into JAXB model (org.picketlink.idm.impl.configuration.jaxb2.generated package) and used to create IdentityConfigurationMetaData object. XML configuration is described by identity-config.xsd file. It is good to take a look at the example organization-test-config.xml that is used in the testsuite.
+ </para>
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/IdentityStore.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/IdentityStore.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/IdentityStore.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,148 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-IdentityStore">
+ <title>IdentityStore</title>
+ <para>
+ This part is represented by <emphasis role="bold"><stores><identity-store>...</emphasis> element
+ </para>
+
+<programlisting><stores>
+ <attribute-stores/>
+ <identity-stores>
+ <identity-store> ... </identity-store>
+ <identity-store> ... </identity-store>
+ </identity-stores>
+ </stores></programlisting>
+ <note>
+ <para>
+ <emphasis role="bold"><stores/></emphasis> element contains <emphasis role="bold"><identity-store></emphasis> and <emphasis role="bold"><attribute-store></emphasis> elements. Currently <emphasis role="bold"><attribute-store></emphasis> configuration is ignored so only <emphasis role="bold"><identity-store></emphasis> elements can be configured.
+ </para>
+
+ </note>
+
+<programlisting language="XML" role="XML"><xi:include href="../../extras/identity-store.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ <para>
+ <emphasis role="bold"><identity-store></emphasis> element:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">id</emphasis> - IdentityStore id
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">class</emphasis> - IdentityStore class name
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">external-config</emphasis> - external configuration file used by IdentityStore
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">supported-relationship-types</emphasis> - IdentityObjectRelationshipType names that are supported by this IdentityStore. JBOSS_IDENTITY_MEMBERSHIP is standard value used by default framework implementation for membership type relationships (between two Group objects) and JBOSS_IDENTITY_ROLE is standard value for Role type memberships (named relationships)
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">supported-identity-object-types</emphasis> - configuration of IdentityObjectType objects mapped by IdentityStore
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">options</emphasis> - other IdentityStore configuration options
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+<programlisting language="XML" role="XML"><xi:include href="../../extras/identity-object-type.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ <para>
+ <identity-object-type> element:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">name</emphasis>- IdentityObjectType name
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">relationships</emphasis> - relationships in which IdentityObjectType can be parent side. <emphasis role="bold"><relationship-type-ref></emphasis> must point to one of values from <emphasis role="bold"><supported-relationship-types></emphasis> . <emphasis role="bold"><identity-object-type-ref></emphasis> must be one of <emphasis role="bold"><identity-object-type><name></emphasis> values configured in this IdentityStore.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">credentials</emphasis> - IdentityObjectCredentialType names allowed for this IdentityObjectType
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">attributes</emphasis> - allowed attribute mappings. Each contains:
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">name</emphasis> - attribute name
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">mapping</emphasis> - real name to be used inside IdentityStore. For example LDAP attribute name
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">type</emphasis> - either "binary" or "text" value
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">isRequired</emphasis> - if attribute cannot have no values
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">isMultivalued</emphasis> - if attribute can have many values
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">isReadonly</emphasis> - if attribute values can be modified
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">options</emphasis> - other options for IdentityObjectType configuration
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/IdentityStoreRepository.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/IdentityStoreRepository.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/IdentityStoreRepository.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,56 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-IdentityStoreRepository">
+ <title>IdentityStoreRepository</title>
+ <para>
+ This section is represented by <emphasis role="bold"> <repositories><repository></emphasis> element
+ </para>
+
+<programlisting language="XML" role="XML"><xi:include href="../../extras/repositories.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ <para>
+ <emphasis role="bold"><repository></emphasis> element contains:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">id</emphasis> - IdentityStoreRepository id.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">class</emphasis> - class name of IdentityStoreRepository implementation.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">external-config</emphasis> - external configuration file used by IdentityStoreRepository.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">default-identity-store-id</emphasis> - id of configured IdentityStore to be used by default.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">default-attribute-store-id</emphasis> - id of configured AttributeStore (or IdentityStore) to be used by default
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">identity-store-mappings</emphasis> - optional element. Mappings between IdentityObjectType names and IdentityStore ids.
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/Realm.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/Realm.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/Realm.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,54 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-Realm">
+ <title>Realm</title>
+ <para>
+ This section is represented by <emphasis role="bold"><realms><realm></emphasis> element
+ </para>
+
+<programlisting><realm>
+ <id>realm://RedHat/DB</id>
+ <repository-id-ref>RedHat Repository DB</repository-id-ref>
+ <identity-type-mappings>
+ <identity-mapping>IDENTITY</identity-mapping>
+ </identity-type-mappings>
+</realm></programlisting>
+ <para>
+ <emphasis role="bold"><realm></emphasis> element contains:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">id</emphasis> - realm id
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">repository-id-ref</emphasis> - id of configured IdentityStoreRepository
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">identity-type-mappings</emphasis> <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">identity-mapping</emphasis> - name of IdentityObjectType that should be maped as Identity object on the API side
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/Realm_Templates.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/Realm_Templates.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/Realm_Templates.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,51 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-Realm_Templates">
+ <title>Realm Templates</title>
+ <para>
+ Realm can be marked as a template. This means that if a different realm name is requested using the API and such name contains template realm as a prefix then this realm configuration will be used
+ </para>
+
+<programlisting><realm>
+ <id>idm_realm</id>
+ <repository-id-ref>DefaultRepository</repository-id-ref>
+ <identity-type-mappings>
+ <user-mapping>USER</user-mapping>
+ </identity-type-mappings>
+ <options>
+ <option>
+ <name>template</name>
+ <value>true</value>
+ </option>
+ </options>
+ </realm></programlisting>
+ <para>
+ In this example for "idm_realm_foo" framework will return "idm_realm" configuration. Request for "foo" realm won't return valid configuration.
+ </para>
+
+<programlisting><realms>
+ <realm>
+ <id>idm_realm</id>
+ <repository-id-ref>DefaultRepository</repository-id-ref>
+ <identity-type-mappings>
+ <user-mapping>USER</user-mapping>
+ </identity-type-mappings>
+
+ </realm>
+ </realms>
+ <repositories>...</repositories>
+ <stores>...</stores>
+ <options>
+ <option>
+ <name>defaultTemplate</name>
+ <value>idm_realm</value>
+ </option>
+ </options></programlisting>
+ <para>
+ The "defaultTemplate" option defines idm_realm as the one that should be used when requested realm name is not found in configuration
+ </para>
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/XML_Configuration.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/XML_Configuration.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Configuration/XML_Configuration.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,41 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-XML_Configuration">
+ <title>XML Configuration</title>
+
+<programlisting><jboss-identity xmlns="urn:jboss:identity:idm:config:v1_0_alpha"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="urn:jboss:identity:idm:config:v1_0_alpha identity-config.xsd">
+ <realms/>
+ <repositories/>
+ <stores/>
+</jboss-identity></programlisting>
+ <para>
+ Identity XML configuration can be divided into three parts:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold"><stores/></emphasis> - defines IdentityStore and AttributeStore instances
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold"><repositories/></emphasis> - defines IdentityStoreRepository instances
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold"><realms/></emphasis> - defines identity realms
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Credentials/Credential_API.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Credentials/Credential_API.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Credentials/Credential_API.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,66 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-Credential_API">
+ <title>Credential API</title>
+ <para>
+ API contains Credential and CredentialType interfaces. CredentialType defines type of credential object. Default implementation supports two types:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">PASSWORD</emphasis> - text password represented by java.lang.String object
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">BINARY</emphasis> - binary credential represented by byte[]. For example some kind of certificate.
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+ <para>
+ Two basic implementations are provided:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">org.picketlink.idm.impl.api.BinaryCredential</emphasis> - Credential with BINARY CredentialType
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">org.picketlink.idm.impl.api.PasswordCredential</emphasis> - Credential with PASSWORD CredentialType
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+ <para>
+ Because credentials values are stored as hash or in other encoded form both SPI and API only enables to update and validate credential value and not to read it from persistence store. API enables to only protect Identity objects with credentials. All related management operations are exposed in AttributesManager interface.
+ </para>
+
+<programlisting role="Java">
+User anotherOne = session.getPersistenceManager().createUser("blah1");
+
+session.getAttributesManager().updatePassword(anotherOne, "Password2000");
+assertTrue(session.getAttributesManager().validatePassword(anotherOne, "Password2000"));
+
+Credential password = new PasswordCredential("SuperPassword2345");
+session.getAttributesManager().updateCredential(anotherOne, password);
+assertTrue(session.getAttributesManager().validateCredentials(anotherOne, new Credential[]{password}));
+
+// binary credential
+byte[] cert = new byte[512000];
+random.nextBytes(cert);
+Credential binaryCredential = new BinaryCredential(cert);
+session.getAttributesManager().updateCredential(anotherOne, binaryCredential);
+assertTrue(session.getAttributesManager().validateCredentials(anotherOne, new Credential[]{binaryCredential}));
+
+</programlisting>
+</section>
\ No newline at end of file
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Credentials/Credential_SPI.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Credentials/Credential_SPI.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Credentials/Credential_SPI.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,29 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-Credential_SPI">
+ <title>Credential SPI</title>
+ <para>
+ SPI contains IdentityObjectCredential and IdentityObjectCredentialType interfaces that correspons to Credential and CredentialType interfaces in the API. Implementation supports the same two (PASSWORD and BINARY) types. Management operations are exposed in IdentityStore interface. Each IdentityObjectType can be configured to support different IdentityObjectCredentialType. This information is exposed by FeaturesMetaData interface.
+ </para>
+ <para>
+ IdentityObjectCredential interface exposes two methods to retrieve credential value:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">getValue</emphasis> - returns either String for text based credentials or byte[] for binary. True credential value may be needed by different IdentityStore implementations for validation. For example with LDAP authentication for IdentityObject entry will be performed
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">getEncodedValue</emphasis> - Enables to provide IdentityStore with custom credential encoding method. IdentityStore is not obligated to use encoded value. This should return either String for text based credentials or byte[] for binary. May return null if credential implementation doesn't provide encoding mechanism. IdentityStore
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+</section>
\ No newline at end of file
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Deployment/Deployment.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Deployment/Deployment.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Deployment/Deployment.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,121 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-JBoss_AS_5_Deployment">
+ <title>JBoss AS 5 Deployment</title>
+ <para>
+ Now, lets look at the second case, by deploying the idm into the JBoss AS 5. By doing this different services can share the identity component, instead of having its own seperate identity component.
+ </para>
+ <para>
+ The jobs that need to be done for the deployment in the container is quite simple:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Populate the idm schema if neccessary.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Start the IdentitySessionFactory, and then register it into the JNDI.
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+ <para>
+ Before we look at it further, lets see the configuration files that jboss idm needed typically. (Say using db back-end, hibernate impl combination)
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ jboss idm configuration file. say jboss.idm.cfg.xml
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ datasource file, say idm-ds.xml
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ hibernate cfg file, say jboss.idm.hibernate.cfg.xml.
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+ <para>
+ With regard to the detail of jboss idm configuration file, you can refer to the configuration documentation.
+ </para>
+ <para>
+ So, if we want to deploy the idm into container with a specified JNDI name, we need to have a deployment file to define the JNDI and other neccessary properties.
+ </para>
+ <para>
+ For the integration with JBoss AS5, the AS5 has a great deployment feature, we've built our own deployer to extend it, so that the AS can listen on the -jboss-idm.xml suffix file to start the IdentitySessionFactory.
+ </para>
+ <para>
+ Basically, we had two deployer, one is: IDMConfigParsingDeployer class, which is taking responsible for parsing files that ends with the -jboss-idm.xml suffix into Java object. The other is: IDMDeployer class, this one is to do the real job, which means it might populate the schema, initial dataset into target db, and then start the IdentitySessionFactory, register it into the JNDI with the specified name at last.
+ </para>
+ <para>
+ We will see a very typical deployment file looks like. (default-jboss-idm.xml)
+ </para>
+
+<programlisting><?xml version="1.0" encoding="UTF-8"?>
+<jboss-idm-deployer xmlns="urn:jboss:identity:idm:deployer:v1_0_alpha"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="urn:jboss:identity:idm:deployer:v1_0_alpha identity-deployer.xsd">
+ <JNDIName>java:/IdentitySessionFactory</JNDIName>
+ <idmConfigFile>jboss.idm.cfg.xml</idmConfigFile>
+ <hibernateDeployer>
+ <hibernateConfiguration>jboss.idm.hibernate.cfg.xml</hibernateConfiguration>
+<hibernateSessionFactoryJNDIName>java:/IDMHibernateSessionFactory</hibernateSessionFactoryJNDIName>
+ </hibernateDeployer>
+ <initializers>
+ <datasource>java:/jbossidmDS</datasource>
+ <sqlInitializer>
+ <sqlFile>idm-sql/jboss.idm.@database@.create.sql</sqlFile>
+ <exitSQL>select * from jbid_io</exitSQL>
+ </sqlInitializer>
+ </initializers>
+</jboss-idm-deployer></programlisting>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The deployment file must be named -jboss-idm.xml as suffix, otherwise, it won't be recoginzed in the JBoss AS5 container.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ The "JNDIName" and "idmConfigFile" attributes are required. The JNDIName is the name for keeping the started IdentitySessionFactory.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ The hibernateDeployer is optional, the reason that why we had the hibernateDeployer is that we can reuse the hibernateSessionFactory in the jboss idm configuration file.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ The Initializer is optional, it is responsible for populating the db schema and initialized dataset if any.
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+ <para>
+ detailed information about the deployment file is specified in the identity-deployer.xsd file.
+ </para>
+ <para>
+ Once you've deployed the idm into JBoss AS5, by using the distribution. It will copy the idm-deployer into the JBoss AS5/server/$config/deployers folder, and the idm folder into the JBoss AS5/server/$config/deploy folder, which contains the default configuration files, like the jboss.idm.cfg.xml, idm-ds.xml etc.
+ </para>
+
+</section>
\ No newline at end of file
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Deployment/Usage_Scenario.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Deployment/Usage_Scenario.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Deployment/Usage_Scenario.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,37 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-IDM_Usage_Scenario">
+ <title>IDM Usage Scenario</title>
+ <para>
+ There are two ways to use the jboss idm:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Use it as the embedded way
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Deploy it into the container (JBoss AS5), and then all other projects can use it by getting IdentitySessionFactory from JNDI.
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+ <para>
+ For the 1st case, users need to use the API to start the IdentitySessionFactory, and then use it. The code is as following, which you can find on the example module.
+ </para>
+
+<programlisting>IdentitySessionFactory identitySessionFactory = new IdentityConfigurationImpl().
+configure(new File("src/test/resources/example-db-config.xml")).buildIdentitySessionFactory();
+IdentitySession identitySession = identitySessionFactory.createIdentitySession("realm://JBossIdentityExample/SampleRealm");
+</programlisting>
+ <para>
+ And then use the IdentitySession to do the operations etc. So it is very easy to use. We will look closer at the second scenario in the next chapter
+ </para>
+</section>
\ No newline at end of file
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/API_Model.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/API_Model.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/API_Model.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,87 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-API_Model">
+ <title>API Model</title>
+ <para>
+ The API operates on the identity model that is defined by the following set of interfaces:
+ </para>
+ <variablelist>
+ <title>API Interfaces</title>
+ <varlistentry>
+ <term>org.picketlink.idm.api.IdentityType</term>
+ <listitem>
+ <para>
+ This is a parent interface for Group and Identity.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>org.picketlink.idm.api.Identity</term>
+ <listitem>
+ <para>
+ This represents an Identity, which can be a user (within organization) or a machine (in authentication or security use case)
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>org.picketlink.idm.api.Group</term>
+ <listitem>
+ <para>
+ This represents a Group.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>org.picketlink.idm.api.GroupType</term>
+ <listitem>
+ <para>
+ This represents type of a Group. It can be an organization, organization unit, administration group, global role, community or any other entity.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>org.picketlink.idm.api.Role</term>
+ <listitem>
+ <para>
+ This represents one to one relationship between Identity and Group. Role has a type. The idea behind the concept is described below.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>org.picketlink.idm.api.RoleType</term>
+ <listitem>
+ <para>
+ This represents type of a Role.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>org.picketlink.idm.api.Attribute</term>
+ <listitem>
+ <para>
+ This represents an attribute connected with <parameter>IdentityType</parameter> (Group or Identity). It can have many complex type values (text or binary). <parameter>AttributeDescription</parameter> describes such properties of Attribute like: name, type of values, readonly, multivalued, required.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>org.picketlink.idm.api.Credential</term>
+ <listitem>
+ <para>
+ This represents credentials connected with an Identity.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>org.picketlink.idm.api.CredentialType</term>
+ <listitem>
+ <para>
+ This represents type of a Credential. For example it can be text password or binary certificate.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/Architecture.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/Architecture.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/Architecture.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,123 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-Architecture">
+ <title>Architecture</title>
+ <para>
+ The most important part of architecture is a split between the API and the SPI.
+ </para>
+ <mediaobject>
+ <imageobject>
+ <imagedata contentdepth="6in" contentwidth="6in" fileref="images/IDM-api-spi.png" width="444" />
+ </imageobject>
+ <caption align="right"> <para>
+ <emphasis role="bold">PicketLink IDM architecture</emphasis>
+ </para>
+ </caption>
+ </mediaobject>
+ <para>
+ API part contains of following interfaces:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">Realm</emphasis> - described later in this document. Groups configuration of several identity stores and exposes all of them with one consistent identity model.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">IdentitySessionFactory</emphasis> - Main entry point in the API. Enables to create/get IdentitySession for a given Realm
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">IdentitySession</emphasis> - Session that groups all identity management operation. Contains transaction support and exposes four managers that handle all identity management operations.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">PersistenceManager</emphasis> - Operates witin IdentitySession. Performs all operations on Identity and Group objects. Create/Remove/Find
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">RelationshipManager</emphasis> - Operates witin IdentitySession. Associate and deassociate Identity and Group objects. Find Idenity and Group objects depending on their relationships
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">RoleManager</emphasis> - Operates witin IdentitySession. Operations on Role objects. Optional feature.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">AttributeManager</emphasis> - Operates witin IdentitySession. Manages Identity and Group (IdentityType objects) attributes. Each configured attribute is described with AttributeDescription interface
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">SearchCriteria</emphasis> - Enables to apply additional conditions to search operations. May be leveraged to receive results sorted, paginated or filtered with attributes.
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+ <para>
+ SPI part contains of following interfaces
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">IdentityStoreSession</emphasis> - Session that groups all identity management operations within identity persistence stores.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">IdentityStoreSessionFactory</emphasis> - Entry point in the SPI to initialize IdentityStoreSession inside IdentityStore or AttributeStore.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">IdentityStoreInvocationContext</emphasis> - IdentityStoreSession aware context object that is passed during any invocation of AttributeStore or IdentityStore methods. Thanks to this actual store implementation doesn't need to be aware of current session state. Therefore one instance of AttributeStore or IdentityStore can be invoked by different realms at the same time.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">AttributeStore</emphasis> - Exposes operations on identity store with attributes. This is a separate interface as in multi store configuration scenario, profile may need to be stored outside of actual data store for a given identity (LDAP + DB)
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">IdentityStore</emphasis> - Extends AttributeStore. Implementation of this interface performs operations on the real data store.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">IdentityStoreRepository</emphasis> - Extends IdentityStore. Groups several IdentityStore objects and exposes operations on them within single interface for the API. The implementation is responsible for aggregate identity objects from many configured underlaying IdentityStore objects and map different IdentityObjectTypes between them. The place where the whole magic happens
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">IdentityObjectSearchControl</emphasis> - Enables to apply additional conditions to search operations. May be leveraged to receive results sorted, paginated or filtered withattributes.
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/Group_And_Roles.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/Group_And_Roles.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/Group_And_Roles.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,27 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-Groups_and_Roles">
+ <title>Groups and Roles</title>
+ <para>
+ Groups are entities that can contain other groups or identity objects which can be associated in tree-like organizational structures. These structures do not need to be hierarchical only, as a single group can be a member of many other groups (that is; a group can have many parents).
+ </para>
+ <para>
+ Possible relationships between groups are controlled with group types. Administrators can configure which different group types can be associated or even which group types can or can not contain identity objects. Groups have unique names per group type. This allows the existance of two groups with the same name, provided they have different group types.
+ </para>
+ <para>
+ Roles form connections between <emphasis>Identity</emphasis> and <emphasis>Group</emphasis> objects. A practical example of this is if we posit that user <emphasis role="bold">John</emphasis> is the <emphasis role="bold">Manager</emphasis> of <emphasis role="bold">XX Team"</emphasis>. In this example you can see how the role form the link between an Identity and a group; <emphasis role="bold">John</emphasis> (an <emphasis>Identity</emphasis>) is the <emphasis role="bold">Manager</emphasis> (a <emphasis>Role</emphasis>) of <emphasis role="bold">XX Team</emphasis> (a <emphasis>Group</emphasis>).
+ </para>
+ <para>
+ This type of information is difficult to map with typical Group objects as <emphasis>John</emphasis> can be a manager of several different groups. Futhermore, other identities (<emphasis>Mary</emphasis>, <emphasis>Jack</emphasis> or <emphasis>Stan</emphasis>) could have the same <emphasis>RoleType</emphasis> in different groups (<emphasis>XY Team</emphasis> or <emphasis>YY Team</emphasis>).
+ </para>
+ <para>
+ Within each Realm (the concept of Realms is described later) we can define several RoleType objects with unique names. Each Role defines a unique combination of Identity, Group and RoleType within a Realm.
+ </para>
+ <para>
+ The Role concept is very powerful but it does not fit easily into all identity store types. While quite easy to map in a relational database it does not fit into every LDAP tree present in organizations. Because of this Role support is optional in the API level
+ </para>
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/Main_Concepts.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/Main_Concepts.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/Main_Concepts.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,93 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-Main_Concepts">
+ <title>Main Concepts</title>
+
+ <variablelist>
+ <title>Terms</title>
+ <varlistentry>
+ <term>PicketLink</term>
+ <listitem>
+ <para>
+ PicketLink is an umbrella project that aims to address different Identity Management needs.
+ </para>
+ <!--http://www.jboss.org/picketlink-->
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>IDM</term>
+ <listitem>
+ <para>
+ IDM stands for <emphasis role="bold">ID</emphasis>entity <emphasis role="bold">M</emphasis>anagement.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Identity Management</term>
+ <listitem>
+ <para>
+ Identity management deals with the management of digital identities. Typically these identities are used to authenticate an organization's users so as to control access to organizational resources. However, other entities, including devices, processes and applications in a networked environment may be represtented in the identity model.
+ </para>
+ <!--http://download.oracle.com/docs/cd/B14099_19/core.1012/b13995/glossary.htm#sthref2905-->
+ <!--http://download.oracle.com/docs/cd/B14099_19/idmanage.1012/b14080/glossary.htm#sthref2905-->
+
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>API</term>
+ <listitem>
+ <para>
+ An <emphasis role="bold">A</emphasis>pplication <emphasis role="bold">P</emphasis>rogramming <emphasis role="bold">I</emphasis>nterface (<emphasis role="bold">API</emphasis>) is a set of specifications that allow applications that use the same API to communicate and share data.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>SPI</term>
+ <listitem>
+ <para>
+ An <emphasis role="bold">S</emphasis>ervice <emphasis role="bold">P</emphasis>rovider <emphasis role="bold">I</emphasis>nterface (<emphasis role="bold">SPI</emphasis>) is the set of specifications that a service defines.
+ </para>
+ <!--http://www.developer.com/java/article.php/3848881/Service-Provider-Interface-Creating-Extensible-Java-Applications.htm-->
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ PicketLink IDM aims to provide a common identity model for various JBoss projects. As every project has specific needs, designing a common API and identity model that will fit all of them can be difficult. Therefore the PicketLink IDM architecture consists of two main parts:
+ </para>
+ <variablelist>
+ <title></title>
+ <varlistentry>
+ <term>Core SPI</term>
+ <listitem>
+ <para>
+ The PicketLink <emphasis role="bold">SPI</emphasis> uses an abstract identity model that provides the flexibility for defining different identity object types and possible relationships between them.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Common API</term>
+ <listitem>
+ <para>
+ The PcketLink <emphasis role="bold">API</emphasis> uses a simpler identity model that fits most common use cases. Identity model has more strictly defined object types and possible relationships.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="images/IDM-global-arch.png" format="PNG" align="center"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="images/IDM-global-arch.png" format="PNG" align="center" width="120mm"/>
+ </imageobject>
+ </mediaobject>
+ <para>
+ Too much abstraction in the API layer would confuse people using the framework. One of the goals is to make the design easily extendible. Framework adopters should be able to remove the API layer and reuse core SPI implementation if needed.
+ </para>
+
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/Realms.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/Realms.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/Realms.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,22 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-Realms">
+ <title>Realms</title>
+ <para>
+ The purpose of a Realm is to group configuration of several identity stores. IdentitySession exposes operations within single Realm
+ </para>
+ <mediaobject>
+ <imageobject>
+ <imagedata contentdepth="6in" contentwidth="6in" fileref="images/IDM-global-realm.png" width="444" />
+ </imageobject>
+ <caption align="right"> <para>
+ <emphasis role="bold">PicketLink IDM architecture</emphasis>
+ </para>
+ </caption>
+ </mediaobject>
+
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/SPI_Model.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/SPI_Model.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Design_and_Architecture/SPI_Model.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,61 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-SPI_Abstract_Model">
+ <title>SPI (Abstract) Model</title>
+ <para>
+ SPI Model contains following interfaces:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">org.picketlink.idm.spi.model.IdentityObject</emphasis> - represents identity object. Contains information about object name and type (IdentityObjectType). Name and IdentityObjectType pair should be unique within realm.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">org.picketlink.idm.spi.model.IdentityObjectType</emphasis> - represents identity object type. Name of IdentityType is unique.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">org.picketlink.idm.spi.model.IdentityObjectAttribute</emphasis> - attribute assigned to IdentityObject
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">org.picketlink.idm.spi.model.IdentityObjectCredential</emphasis> - credential assigned to IdentityObject
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">org.picketlink.idm.spi.model.IdentityObjectCredentialType</emphasis> - represents type of IdentityObjectCredential.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">org.picketlink.idm.spi.model.IdentityObjectRelationship</emphasis> - Directional relationship between two IdentityObject objects. Relationship is directional as it keeps information about from and to IdentityObject. Each IdentityObjectRelationship has a type (IdentityObjectRelationshipType) and can have a name (not required).
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">org.picketlink.idm.spi.model.IdentityObjectRelationshipType</emphasis> - named type of relationship
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+ <para>
+ Model described above is very flexible as IdentityObjectType is able to map any kind of entities. Identity object and Group/GroupType objects are only one of many possible options (API is a subset of SPI possibilities). IdentityObjectRelationship defines a connection between any two IdentityObject objects. Each IdentityObjectRelationship has a type. To map previously described API two IdentityObjectRelationshipType objects are needed. One to map normal MEMBERSHIP like between an Identity and a Group or Group and Group objects. Second one to map Role concept. For API Role - RoleType refers to the name of the IdentityObjectRelationship. In default Hibernate implementation possible names of IdentityObjectRelationship are kept in a separate table. All of those can be easily redefined to support different kind of API.
+ </para>
+
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStoreRepository_Implementations/FallbackIdentityStoreRepository.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStoreRepository_Implementations/FallbackIdentityStoreRepository.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStoreRepository_Implementations/FallbackIdentityStoreRepository.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,50 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-FallbackIdentityStoreRepository">
+ <title>FallbackIdentityStoreRepository</title>
+ <section id="sect-PicketLink_IDM_Reference_Guide-FallbackIdentityStoreRepository-ClassName">
+ <title>ClassName</title>
+ <para>
+ org.picketlink.idm.impl.repository.FallbackIdentityStoreRepository
+ </para>
+
+ </section>
+
+ <section id="sect-PicketLink_IDM_Reference_Guide-FallbackIdentityStoreRepository-Behaviour">
+ <title>Behaviour</title>
+ <para>
+ Resolves proper IdentityStore from IdentityObjectType mapping and delegates method invocation. For relationship related methods, if both IdentityObjectTypes are not mapped in one store, repository will try to sync them and associate in defaultIdentityStore. For attributes that are not mapped inside mapped IdentityStore repository will try to assign those attributes in defaultAttributeStore.
+ </para>
+
+ </section>
+
+ <section id="sect-PicketLink_IDM_Reference_Guide-FallbackIdentityStoreRepository-Configuration_Options">
+ <title>Configuration Options</title>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">allowNotDefinedAttributes</emphasis> - if mapped IdentityStore doesn't support any attribute that was passed in method invocation FallbackIdentityStoreRepository will try to store it in defaultAttributeStore. If this option is set to true such attribute will be passed to defaultAttributeStore even if it is not mapped there.
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+ <section id="sect-PicketLink_IDM_Reference_Guide-FallbackIdentityStoreRepository-Sample_Configuration">
+ <title>Sample Configuration</title>
+
+<programlisting language="XML" role="XML"><xi:include href="../../extras/sample_config3.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ <para>
+ The <emphasis role="bold">readOnly</emphasis> options specifies that the only write operation performed on the store will be password update.
+ </para>
+
+ </section>
+
+
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStoreRepository_Implementations/WrapperIdentityStoreRepository.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStoreRepository_Implementations/WrapperIdentityStoreRepository.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStoreRepository_Implementations/WrapperIdentityStoreRepository.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,39 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-WrapperIdentityStoreRepository">
+ <title>WrapperIdentityStoreRepository</title>
+ <section id="sect-PicketLink_IDM_Reference_Guide-WrapperIdentityStoreRepository-ClassName">
+ <title>ClassName</title>
+ <para>
+ org.picketlink.idm.impl.repository.WrapperIdentityStoreRepository
+ </para>
+
+ </section>
+
+ <section id="sect-PicketLink_IDM_Reference_Guide-WrapperIdentityStoreRepository-Behaviour">
+ <title>Behaviour</title>
+ <para>
+ Simply wraps single AttributeStore and IdentityStore and pass all method invocations
+ </para>
+
+ </section>
+
+ <section id="sect-PicketLink_IDM_Reference_Guide-WrapperIdentityStoreRepository-Sample_Configuration">
+ <title>Sample Configuration</title>
+
+<programlisting><repository>
+ <id>Sample Repository</id
+ <class>org.picketlink.idm.impl.repository.WrapperIdentityStoreRepository</class>
+ <external-config/>
+ <default-identity-store-id>LDAP Store</default-identity-store-id>
+ <default-attribute-store-id>LDAP Store</default-attribute-store-id>
+</repository></programlisting>
+
+ </section>
+
+
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStore_Implementations/Hibernate_IdentityStore.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStore_Implementations/Hibernate_IdentityStore.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStore_Implementations/Hibernate_IdentityStore.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,119 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-Hibernate_IdentityStore">
+ <title>Hibernate IdentityStore</title>
+ <section id="sect-PicketLink_IDM_Reference_Guide-Hibernate_IdentityStore-Class_Name">
+ <title>Class Name</title>
+ <para>
+ org.picketlink.idm.impl.store.hibernate.HibernateIdentityStoreImpl
+ </para>
+
+ </section>
+
+ <section id="sect-PicketLink_IDM_Reference_Guide-Hibernate_IdentityStore-Overview">
+ <title>Overview</title>
+ <para>
+ HibernateIdentityStoreImpl maps PicketLink IDM SPI model into Hibernate entities. This enables to use any RDBMS supported by Hibernate as identity persistence store (IdentityStore). Because of flexibility that ORM gives this IdentityStore implementation support all of the optional design concepts like role management. It can be used as the default IdentityStore together with other more limited implementations. For example in combination with LDAP IdentityStore it can handle IdentityObject attributes that are not supported in LDAP schema. In such configuration part of IdentityObject profile will be stored in LDAP and part in relational database. To learn more about such setup please read FallbackIdentityStoreRepository documentation. In current version implementation doesn't have any caching mechanism besides of what can be set in hibernate configuration
+ </para>
+
+ </section>
+
+ <section id="sect-PicketLink_IDM_Reference_Guide-Hibernate_IdentityStore-Configuration_Options">
+ <title>Configuration Options</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">hibernateConfiguration</emphasis> - the hibernate configuration file that will be used to create SessionFactory
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">hibernateSessionFactoryJNDIName</emphasis> - JNDI name of hibernate SessionFactory that will be used to obtain it
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">hibernateSessionFactoryRegistryName</emphasis> - name of hibernate SessionFactory placed in the IdentityConfigurationRegistry that will be used to obtain it
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">addHibernateMappings</emphasis> - of set to true all annotated hibernate model classes will be added to the hibernate configuration before SessionFactory is created
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">populateRelationshipTypes</emphasis> - true/false - Populate configured <supported-relationship-types> (IdentityObjectRelationshipType in SPI model) during IdentityStore initialization. Default value is 'false'
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">populateIdentityObjectTypes</emphasis> - true/false - Populate configured <supported-identity-object-types> (IdentityObjectType in SPI model) during IdentityStore initialization. Default value is 'false'
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">allowNotDefinedAttributes</emphasis> - true/false - Allow to set IdentityObject attributes that are not specified in <identity-object-type> configuration. Such attributes are assumed to have "text" type and many values. Default value is 'false'.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">isRealmAware</emphasis> - true/false - If set to true HibernateIdentityStoreImpl will create separate namespaces for different Realms from which method invocations come. This means that each IdentityObject, IdentityObjectRelationship and IdentityObjectRelationshipName will be connected and only accessible with a realm name in which it was created. Entities representing IdentityObjectType, IdentityObjectCredentialType and IdentityObjectRelationshipType are always same for all realms and not affected with this option. Default value is 'false'.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">manageTransactionDuringBootstrap</emphasis> - true/false - indicate that transactions should be managed manually during store bootstrap when initial entities are created.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">allowNotDefinedIdentityObjectTypes</emphasis> - true/false - indicate that store won't check for a given IdentityObjectType configuration and if one is not specified it will be just lazily created. This option enables to have minimal xml config without definition of all constraints in relationship between types.
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ </section>
+
+ <section id="sect-PicketLink_IDM_Reference_Guide-Hibernate_IdentityStore-Sample_Configuration">
+ <title>Sample Configuration</title>
+
+<programlisting language="XML" role="XML"><xi:include href="../../extras/sample_config.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ <para>
+ In case 'addHibernateMappings' option is not set to true hibernate configuration need to list all annotated model classes:
+ </para>
+
+<programlisting><mapping resource="mappings/HibernateRealm.hbm.xml"/>
+<mapping resource="mappings/HibernateIdentityObjectCredentialBinaryValue.hbm.xml"/>
+<mapping resource="mappings/HibernateIdentityObjectAttributeBinaryValue.hbm.xml"/>
+<mapping resource="mappings/HibernateIdentityObject.hbm.xml"/>
+<mapping resource="mappings/HibernateIdentityObjectCredential.hbm.xml"/>
+<mapping resource="mappings/HibernateIdentityObjectCredentialType.hbm.xml"/>
+<mapping resource="mappings/HibernateIdentityObjectAttribute.hbm.xml"/>
+<mapping resource="mappings/HibernateIdentityObjectType.hbm.xml"/>
+<mapping resource="mappings/HibernateIdentityObjectRelationship.hbm.xml"/>
+<mapping resource="mappings/HibernateIdentityObjectRelationshipType.hbm.xml"/>
+<mapping resource="mappings/HibernateIdentityObjectRelationshipName.hbm.xml"/></programlisting>
+
+ </section>
+
+
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStore_Implementations/LDAP_IdentityStore.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStore_Implementations/LDAP_IdentityStore.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStore_Implementations/LDAP_IdentityStore.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,239 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-LDAP_IdentityStore">
+ <title>LDAP IdentityStore</title>
+ <section id="sect-PicketLink_IDM_Reference_Guide-LDAP_IdentityStore-Class_Name">
+ <title>Class Name</title>
+ <para>
+ org.picketlink.idm.impl.store.ldap.LDAPIdentityStoreImpl
+ </para>
+
+ </section>
+
+ <section id="sect-PicketLink_IDM_Reference_Guide-LDAP_IdentityStore-Overview">
+ <title>Overview</title>
+ <para>
+ LDAPIdentityStoreImpl provides support for LDAP as identity persistence store (IdentityStore). At this stage the implementation is a bit limitted:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Role management (IdentityObjectRelationshipName) is not supported
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Only "text" attribute type can be mapped
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ Only "PASSWORD" <credential-type> can be mapped
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+ <section id="sect-PicketLink_IDM_Reference_Guide-LDAP_IdentityStore-Configuration">
+ <title>Configuration</title>
+ <para>
+ <identity-object-type><options>
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">idAttributeName</emphasis> - attribute name under which IdentityObject name is specified. Required.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">passwordAttributeName</emphasis> - attribute name under which IdentityObject password is specified. Optional.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">ctxDNs</emphasis> - DN that will be used as context for IdentityObject searches. More than one value can be specified.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">allowCreateEntry</emphasis> - true/false - Specify if new IdentityObject can be created.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">createEntryAttributeValues</emphasis> - defines a set of ldap attributes that will be set on IdentityObject entry creation. Values are in "name=value" format. This enables to fulfill LDAP schema requirements.Default is false
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">parentMembershipAttributeName</emphasis> - LDAP attribute that defines children of IdentityObject. This will be used to retrieved relationships from IdentityObject entry. Option is required if IdentityObjectType can be part of relationship.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">isParentMembershipAttributeDN</emphasis> - defines if values of attribute defined in parentMembershipAttributeName are fully qualified LDAP DNs.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">allowEmptyMemberships</emphasis> - defines if IdentityObject entry can have no members. Sometimes it is not allowed by LDAP schema.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">parentMembershipAttributePlaceholder</emphasis> - if LDAP schema doesn't allow empty memberships this value will be used as a placeholder. IdentityObject specified here won't be recognized as a member and ignored
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">childMembershipAttributeName</emphasis> - LDAP attribute that defines parents of IdentityObject. This will be used to retrieved relationships from IdentityObject entry. Good example of such attribute in LDAP schema is 'memberOf'
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">childMembershipAttributeDN</emphasis> - defines if values of attribute defined in childMembershipAttributeName are fully qualified LDAP DNs.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">childMembershipAttributeVirtual</emphasis> - specifies if attribute defined in 'childMembershipAttributeName' is a real attribute that can be updated or virtual one which value is managed by a directory and should not be updated
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">entrySearchFilter</emphasis> - ldap filter to search IdentityObject with. {0} will be substitute with IdentityObject name. Example filter can look like this: "(uid={0})". This substitution behavior comes from the standard DirContext.search(Name, String, Object, SearchControls cons) method
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">entrySearchScope</emphasis> - defines a search scope. Values can be "subtree" and "object"
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">enclosePasswordWith</emphasis> - if specified password will be surunted with a given chars before update
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">passwordEncoding</emphasis> - if specified password will be encoded before update. For example Microsoft Active Directory requires password to be enclosed with '"' and encoded using 'UTF-16LE' for update.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">passwordUpdateAttributeValues</emphasis> - list of attributes that should be changed during password update
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+ <para>
+ <emphasis role="bold"><identity-store><options></emphasis>
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">providerURL</emphasis> - LDAP connection URL. For example "ldap://localhost:389"
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">adminDN</emphasis> - LDAP entry used to connect to the server.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">adminPassword</emphasis> - password related to adminDN
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">searchTimeLimit</emphasis> -searchTimeLimit for LDAP search operations in miliseconds. Default value is 10000.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">customJNDIConnectionParameters</emphasis> - list of additional 'key=value' parameters that will be used to create JNDI context. Can be usefull to use additional JNDI options.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">customSystemProperties</emphasis> - list of 'key=value' properties that will be added using System.setProperty() method. This can be used to configure LDAP JNDI connection pooling which is set per JVM
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">externalJNDIContext</emphasis> - name that will be used to perform JDNI lookup to grab JNDI connection context
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">sortExtensionSupported</emphasis> - if set to "false" will disable the use of sort extension that triggers sort on LDAP server side
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">pagedResultsExtensionSupported</emphasis> - if set to "true" will enable paged search. Searches that exceed size defined by "pagedResultsExtensionSize" option will be splitted into few smaller ones.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">pagedResultsExtensionSize</emphasis> - defines page size for "pagedResultsExtensionSupported" option.
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">createMissingContexts</emphasis> - if set to "true" LDAP store will try to create missing LDAP contexts defined in the configuration.
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+ <section id="sect-PicketLink_IDM_Reference_Guide-LDAP_IdentityStore-Sample_Configuration">
+ <title>Sample Configuration</title>
+
+<programlisting language="XML" role="XML"><xi:include href="../../extras/sample_config2.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+
+ </section>
+
+
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStore_Implementations/Minimal_Configuration.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStore_Implementations/Minimal_Configuration.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/IdentityStore_Implementations/Minimal_Configuration.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,15 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-Minimal_Configuration">
+ <title>Minimal Configuration</title>
+ <para>
+ The main role of configuration is to define relationship between separate framework components. It also enables to specify a lot of meta data information describing possible connections between IdentityObject types. It is however possible to not define all those meta data information and let the framework to be maximum permissive about allowed operations and lazily create not defined types:
+ </para>
+
+<programlisting language="XML" role="XML"><xi:include href="../../extras/lazy-config.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Quick_Start/Core_Files.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Quick_Start/Core_Files.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Quick_Start/Core_Files.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,22 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-Core_Files">
+ <title>Core Files</title>
+ <para>
+ Although the best way to start playing with the framework is to look at Maven2 sample project mentioned above lets list minimal set of configuration files. To setup the basic framework core depending on hibernate IdentityStore two files will be needed
+ </para>
+ <para>
+ <emphasis role="bold">idm-config.xml</emphasis> - that will set proper configuration for all framework components described in section above. Sample one below.
+ </para>
+
+<programlisting language="XML" role="XML"><xi:include href="../../extras/idm-config.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ <para>
+ <emphasis role="bold">hibernate.cfg.xml</emphasis> - hibernate SessionFactory setup
+ </para>
+
+<programlisting language="XML" role="XML"><xi:include href="../../extras/hibernate.cfg.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Quick_Start/Examples.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Quick_Start/Examples.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Quick_Start/Examples.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,36 @@
+<?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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-Examples">
+ <title>Examples</title>
+ <para>
+ As PicketLink IDM is a Maven2 based project it is very easy to leverage it from this build system. There is a ready to use Maven2 example project in the svn. It contains three sample test cases for with following configurations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ database setup
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ LDAP setup
+ </para>
+
+ </listitem>
+ <listitem>
+ <para>
+ mixed LDAP + database setup
+ </para>
+
+ </listitem>
+
+ </itemizedlist>
+ <para>
+ Sample project uses embedded OpenDS and HSQLDB so there is no need for any additional setup to be able to play with the API.
+ </para>
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Quick_Start/Test_Cases.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Quick_Start/Test_Cases.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/Quick_Start/Test_Cases.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +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 "../../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-PicketLink_IDM_Reference_Guide-Test_Cases">
+ <title>Test Cases</title>
+ <para>
+ One of the best ways to get familiar with the PicketLink IDM component is to look at the source code. You will find link to the subversion repository in the project webpage. There are couple of quite meaningful testcases there. One of the best to start with is OrganizationTest under 'idm-testsuite' module . It contains two example identity structures. One mapping hierarchical organization of Red Hat and JBoss projects and the other describes theoretical portal tree for ACME company.
+ </para>
+</section>
+
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Attributes.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Attributes.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Attributes.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,11 @@
+<?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 "../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+
+<chapter>
+ <title>Attributes</title>
+ <xi:include href="Attributes/API.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Attributes/SPI.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</chapter>
\ No newline at end of file
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Concepts_API_SPI.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Concepts_API_SPI.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Concepts_API_SPI.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,13 @@
+<?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 "../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+
+<chapter>
+ <title>Concepts behind API to SPI mappings</title>
+ <xi:include href="Concepts_API_SPI/Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Concepts_API_SPI/User_and_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Concepts_API_SPI/Associations.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Concepts_API_SPI/Role.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</chapter>
\ No newline at end of file
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Configuration.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Configuration.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Configuration.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,16 @@
+<?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 "../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+
+<chapter>
+ <title>Configuration</title>
+ <xi:include href="Configuration/IdentitySessionFactory.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Configuration/XML_Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Configuration/IdentityStore.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Configuration/IdentityStoreRepository.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Configuration/Realm.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Configuration/Realm_Templates.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Configuration/API_Cache.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</chapter>
\ No newline at end of file
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Credentials.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Credentials.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Credentials.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,11 @@
+<?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 "../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+
+<chapter>
+ <title>Credentials</title>
+ <xi:include href="Credentials/Credential_API.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Credentials/Credential_SPI.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</chapter>
\ No newline at end of file
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Deployment.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Deployment.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Deployment.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,11 @@
+<?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 "../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+
+<chapter>
+ <title>Deployment</title>
+ <xi:include href="Deployment/Usage_Scenario.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Deployment/Deployment.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</chapter>
\ No newline at end of file
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Design_and_Architecture.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Design_and_Architecture.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Design_and_Architecture.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,16 @@
+<?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 "../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+
+<chapter>
+ <title>Design and Architecture</title>
+ <xi:include href="Design_and_Architecture/Main_Concepts.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Design_and_Architecture/API_Model.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Design_and_Architecture/Group_And_Roles.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <!--Edited to here.-->
+ <xi:include href="Design_and_Architecture/SPI_Model.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Design_and_Architecture/Architecture.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Design_and_Architecture/Realms.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</chapter>
\ No newline at end of file
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_IdentityStoreRepository_Implementations.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_IdentityStoreRepository_Implementations.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_IdentityStoreRepository_Implementations.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,11 @@
+<?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 "../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+
+<chapter>
+ <title>IdentityStoreRepository Implementations</title>
+ <xi:include href="IdentityStoreRepository_Implementations/WrapperIdentityStoreRepository.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="IdentityStoreRepository_Implementations/FallbackIdentityStoreRepository.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</chapter>
\ No newline at end of file
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_IdentityStore_Implementations.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_IdentityStore_Implementations.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_IdentityStore_Implementations.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,12 @@
+<?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 "../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+
+<chapter>
+ <title>IdentityStore Implementations</title>
+ <xi:include href="IdentityStore_Implementations/Hibernate_IdentityStore.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="IdentityStore_Implementations/LDAP_IdentityStore.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="IdentityStore_Implementations/Minimal_Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</chapter>
\ No newline at end of file
Added: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Quick_Start.xml
===================================================================
--- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Quick_Start.xml (rev 0)
+++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/modules/chap_Quick_Start.xml 2011-08-29 07:26:00 UTC (rev 7244)
@@ -0,0 +1,12 @@
+<?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 "../PicketLink_IDM_Reference_Guide.ent">
+%BOOK_ENTITIES;
+]>
+
+<chapter>
+ <title>Quick Start</title>
+ <xi:include href="Quick_Start/Test_Cases.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Quick_Start/Examples.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Quick_Start/Core_Files.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</chapter>
\ No newline at end of file
13 years, 4 months
- 1
- 0
gatein SVN: r7243 - in epp/docs/branches/5.2: Reference_Guide/en-US/modules/PortalDevelopment and 1 other directories.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-08-28 23:56:57 -0400 (Sun, 28 Aug 2011)
New Revision: 7243
Modified:
epp/docs/branches/5.2/Installation_Guide/en-US/Accessing.xml
epp/docs/branches/5.2/Installation_Guide/en-US/Installation_Guide.xml
epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml
epp/docs/branches/5.2/User_Guide/en-US/Book_Info.xml
epp/docs/branches/5.2/User_Guide/en-US/Revision_History.xml
Log:
Porting updates from 5.1 branch
Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Accessing.xml
===================================================================
--- epp/docs/branches/5.2/Installation_Guide/en-US/Accessing.xml 2011-08-29 03:48:03 UTC (rev 7242)
+++ epp/docs/branches/5.2/Installation_Guide/en-US/Accessing.xml 2011-08-29 03:56:57 UTC (rev 7243)
@@ -7,16 +7,16 @@
]>
<chapter id="chap-Install_Guide-Accessing_PRODUCT">
- <title>Accessing JBoss Enterprise Portal Platform</title>
- <section id="sect-Install_Guide-Accessing_PRODUCT-Browser_URL">
- <title>Browser URL</title>
- <para>
- The URL to a locally installed instance of JBoss Enterprise Portal Platform is <ulink type="http" url="http://localhost:8080/portal/public/classic/home" />
- </para>
- <para>
- This URL will take users to the front page of JBoss Enterprise Portal Platform where they can log in and begin to undertake actions within the portal itself.
- </para>
- </section>
+ <title>Accessing JBoss Enterprise Portal Platform</title>
+ <section id="sect-Install_Guide-Accessing_PRODUCT-Browser_URL">
+ <title>Browser URL</title>
+ <para>
+ The URL to a locally installed instance of JBoss Enterprise Portal Platform is <ulink type="http" url="http://localhost:8080/portal/public/classic/home" />
+ </para>
+ <para>
+ This URL will take users to the front page of JBoss Enterprise Portal Platform where they can log in and begin to undertake actions within the portal itself.
+ </para>
+ </section>
</chapter>
Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Installation_Guide.xml
===================================================================
--- epp/docs/branches/5.2/Installation_Guide/en-US/Installation_Guide.xml 2011-08-29 03:48:03 UTC (rev 7242)
+++ epp/docs/branches/5.2/Installation_Guide/en-US/Installation_Guide.xml 2011-08-29 03:56:57 UTC (rev 7243)
@@ -1,23 +1,19 @@
<?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">
-%BOOK_ENTITIES;
-<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
-%BOOK_ENTITIES;
-
]>
<book>
- <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <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="Getting_Started.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="Post_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Add-ons.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Test_Your_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Uninstall_JBoss.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <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="Getting_Started.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="Post_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Add-ons.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Test_Your_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Uninstall_JBoss.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <index />
+ <index />
</book>
Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml 2011-08-29 03:48:03 UTC (rev 7242)
+++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml 2011-08-29 03:56:57 UTC (rev 7243)
@@ -250,15 +250,15 @@
User navigation is the set of nodes and pages that are owned by a user. They are part of the user's dashboard.
</para>
<!-- DOC NOTE: Get an answer on the below!-->
- <!--<remark>This Paragraph:</remark>-->
+ <!-- This Paragraph:-->
<para>
Two files configure the user navigation (<filename>navigation.xml</filename> and <filename>pages.xml</filename>). They are located in the directory "<filename>02portal.war/WEB-INF/conf/portal/users/{userName}</filename>".
</para>
- <!--<remark>Became this paragraph in GateIn r6987</remark>
+ <!--Became this paragraph in GateIn r6987
<para>
Three files configure the user navigation (<filename>navigation.xml</filename>, <filename>pages.xml</filename> and <filename>portlet-preferences.xml</filename>). They are located in the <filename>{templateLocation}/{ownerType}/{predefinedOwner}</filename> directory with <literal>ownerType</literal> is <literal>user</literal> and <literal>predefinedOwner</literal> is username that want to create the navigation. For example, if administrator want to create navigation for user <literal>root</literal>, he has to locate the configuration files in <filename>portal.war/WEB-INF/conf/portal/user/root </filename>
</para>
- <remark>Which is appropriate for EPP 5.1.1?</remark>-->
+ Which is appropriate for EPP 5.1.1?-->
<para>
The file <filename>eXoGadgets.war/WEB-INF/gadget.xml</filename> defines the gadgets that will be available on a user dashboard.
</para>
Modified: epp/docs/branches/5.2/User_Guide/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.2/User_Guide/en-US/Book_Info.xml 2011-08-29 03:48:03 UTC (rev 7242)
+++ epp/docs/branches/5.2/User_Guide/en-US/Book_Info.xml 2011-08-29 03:56:57 UTC (rev 7243)
@@ -7,7 +7,7 @@
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.1</productnumber>
<edition>2</edition>
- <pubsnumber>5.1.7</pubsnumber>
+ <pubsnumber>5.1.8</pubsnumber>
<abstract>
<para>
This document provides an easy to follow guide to the functions and
Modified: epp/docs/branches/5.2/User_Guide/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.2/User_Guide/en-US/Revision_History.xml 2011-08-29 03:48:03 UTC (rev 7242)
+++ epp/docs/branches/5.2/User_Guide/en-US/Revision_History.xml 2011-08-29 03:56:57 UTC (rev 7243)
@@ -8,6 +8,20 @@
<simpara>
<revhistory>
<revision>
+ <revnumber>2-5.1.8</revnumber>
+ <date>Fri Aug 26 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email></email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Added "Non-visible pages and security" admonition.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
<revnumber>2-5.1.7</revnumber>
<date>Thu Aug 25 2011</date>
<author>
13 years, 4 months
- 1
- 0
gatein SVN: r7242 - in epp/docs/branches/5.1: Reference_Guide/en-US/modules/PortalDevelopment and 3 other directories.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-08-28 23:48:03 -0400 (Sun, 28 Aug 2011)
New Revision: 7242
Modified:
epp/docs/branches/5.1/Installation_Guide/en-US/Accessing.xml
epp/docs/branches/5.1/Installation_Guide/en-US/Installation_Guide.xml
epp/docs/branches/5.1/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml
epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml
epp/docs/branches/5.1/Release_Notes/en-US/known_issues.xml
epp/docs/branches/5.1/Release_Notes/en-US/need_info.xml
epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml
epp/docs/branches/5.1/Release_Notes/publican.cfg
epp/docs/branches/5.1/User_Guide/en-US/Book_Info.xml
epp/docs/branches/5.1/User_Guide/en-US/Revision_History.xml
Log:
Prepping for 5.1.1 release
Modified: epp/docs/branches/5.1/Installation_Guide/en-US/Accessing.xml
===================================================================
--- epp/docs/branches/5.1/Installation_Guide/en-US/Accessing.xml 2011-08-29 03:43:15 UTC (rev 7241)
+++ epp/docs/branches/5.1/Installation_Guide/en-US/Accessing.xml 2011-08-29 03:48:03 UTC (rev 7242)
@@ -7,16 +7,16 @@
]>
<chapter id="chap-Install_Guide-Accessing_PRODUCT">
- <title>Accessing JBoss Enterprise Portal Platform</title>
- <section id="sect-Install_Guide-Accessing_PRODUCT-Browser_URL">
- <title>Browser URL</title>
- <para>
- The URL to a locally installed instance of JBoss Enterprise Portal Platform is <ulink type="http" url="http://localhost:8080/portal/public/classic/home" />
- </para>
- <para>
- This URL will take users to the front page of JBoss Enterprise Portal Platform where they can log in and begin to undertake actions within the portal itself.
- </para>
- </section>
+ <title>Accessing JBoss Enterprise Portal Platform</title>
+ <section id="sect-Install_Guide-Accessing_PRODUCT-Browser_URL">
+ <title>Browser URL</title>
+ <para>
+ The URL to a locally installed instance of JBoss Enterprise Portal Platform is <ulink type="http" url="http://localhost:8080/portal/public/classic/home" />
+ </para>
+ <para>
+ This URL will take users to the front page of JBoss Enterprise Portal Platform where they can log in and begin to undertake actions within the portal itself.
+ </para>
+ </section>
</chapter>
Modified: epp/docs/branches/5.1/Installation_Guide/en-US/Installation_Guide.xml
===================================================================
--- epp/docs/branches/5.1/Installation_Guide/en-US/Installation_Guide.xml 2011-08-29 03:43:15 UTC (rev 7241)
+++ epp/docs/branches/5.1/Installation_Guide/en-US/Installation_Guide.xml 2011-08-29 03:48:03 UTC (rev 7242)
@@ -1,23 +1,19 @@
<?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">
-%BOOK_ENTITIES;
-<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
-%BOOK_ENTITIES;
-
]>
<book>
- <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <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="Getting_Started.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="Post_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Add-ons.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Test_Your_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Uninstall_JBoss.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <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="Getting_Started.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="Post_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Add-ons.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Test_Your_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Uninstall_JBoss.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <index />
+ <index />
</book>
Modified: epp/docs/branches/5.1/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml
===================================================================
--- epp/docs/branches/5.1/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml 2011-08-29 03:43:15 UTC (rev 7241)
+++ epp/docs/branches/5.1/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml 2011-08-29 03:48:03 UTC (rev 7242)
@@ -250,15 +250,15 @@
User navigation is the set of nodes and pages that are owned by a user. They are part of the user's dashboard.
</para>
<!-- DOC NOTE: Get an answer on the below!-->
- <!--<remark>This Paragraph:</remark>-->
+ <!-- This Paragraph:-->
<para>
Two files configure the user navigation (<filename>navigation.xml</filename> and <filename>pages.xml</filename>). They are located in the directory "<filename>02portal.war/WEB-INF/conf/portal/users/{userName}</filename>".
</para>
- <!--<remark>Became this paragraph in GateIn r6987</remark>
+ <!--Became this paragraph in GateIn r6987
<para>
Three files configure the user navigation (<filename>navigation.xml</filename>, <filename>pages.xml</filename> and <filename>portlet-preferences.xml</filename>). They are located in the <filename>{templateLocation}/{ownerType}/{predefinedOwner}</filename> directory with <literal>ownerType</literal> is <literal>user</literal> and <literal>predefinedOwner</literal> is username that want to create the navigation. For example, if administrator want to create navigation for user <literal>root</literal>, he has to locate the configuration files in <filename>portal.war/WEB-INF/conf/portal/user/root </filename>
</para>
- <remark>Which is appropriate for EPP 5.1.1?</remark>-->
+ Which is appropriate for EPP 5.1.1?-->
<para>
The file <filename>eXoGadgets.war/WEB-INF/gadget.xml</filename> defines the gadgets that will be available on a user dashboard.
</para>
Modified: epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml 2011-08-29 03:43:15 UTC (rev 7241)
+++ epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml 2011-08-29 03:48:03 UTC (rev 7242)
@@ -11,7 +11,7 @@
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 Open Choice to the presentation layer, JBoss Enterprise Portal Platform 5 maximizes existing skills and technology investments.
</para>
<para>
- By integrating proven 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. As well, JBoss Enterprise Portal Platform version 5.1.1 is fully tested and supported by Red Hat, and is certified to work on many leading enterprise hardware and software products.
+ By integrating proven 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. As well, JBoss Enterprise Portal Platform version &VZ; is fully tested and supported by Red Hat, and is certified to work on many leading enterprise hardware and software products.
</para>
</section>
@@ -65,7 +65,7 @@
<term>eXo JCR</term>
<listitem>
<para>
- The eXo Java Content Repository has been upgraded to version 1.12.9. <!--JBEPP-996-->
+ The eXo Java Content Repository has been upgraded to version 1.12.9-GA. <!--JBEPP-996-->
</para>
</listitem>
</varlistentry>
@@ -89,7 +89,7 @@
<term>WSRP</term>
<listitem>
<para>
- The WSRP component has been upgraded to 2.0.1-GA. <!--JBEPP-789-->
+ The WSRP component has been upgraded to 2.0.1.GA.EPP51. <!--JBEPP-789-->
</para>
</listitem>
</varlistentry>
@@ -232,7 +232,7 @@
GateIn WSRP
</entry>
<entry>
- 2.0.1-EPP51-GA
+ 2.0.1.GA.EPP51
</entry>
</row>
<row>
@@ -371,15 +371,15 @@
<xi:include href="known_issues.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</section>
- <section>
+ <!--<section>
<title><remark>NEEDINFO Issues</remark></title>
<xi:include href="need_info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- </section>
+ </section>-->
- <section>
+ <!--<section>
<title><remark>Not Documented Issues</remark></title>
<xi:include href="not_documented.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- </section>
+ </section>-->
<section>
<title>Security Related Issues</title>
<variablelist>
@@ -419,12 +419,12 @@
</listitem>
</varlistentry>
<varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-881" /></term>
+ <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-1484" /></term>
<listitem>
<!-- Added on advice from Dave Jorm in the security team -->
<para>
- It was found that JBoss Seam 2 did not properly block access to JBoss Expression Language (EL) constructs in page exception handling, allowing arbitrary Java methods to be executed. A remote attacker could use this flaw to execute arbitrary code via a specially-crafted URL provided to certain applications based on the JBoss Seam 2 framework.
+ It was found that JBoss Web Services Native did not properly protect against recursive entity resolution when processing Document Type Definitions (DTD). A remote attacker could exploit this flaw by sending a specially-crafted HTTP POST request to a deployed web service, causing excessive CPU and memory consumption on the system hosting that service. If the attack is repeated to consume all available network sockets, the server will become unavailable. (CVE-2011-1483)
</para>
<para>
This issue has been fixed in JBoss Enterprise Application Platform version 5.1.1, which is incorporated in this release of JBoss Enterprise Portal Platform.
Modified: epp/docs/branches/5.1/Release_Notes/en-US/known_issues.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/known_issues.xml 2011-08-29 03:43:15 UTC (rev 7241)
+++ epp/docs/branches/5.1/Release_Notes/en-US/known_issues.xml 2011-08-29 03:48:03 UTC (rev 7242)
@@ -2,28 +2,6 @@
<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-
-<variablelist>
-
- <!-- https://issues.jboss.org/browse/JBEPP-1079 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-1079" /></term>
- <listitem>
-
-
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- Pre-release testing has found that attempting to edit a category that does not have a description will produce the following error:
-<screen>IllegalArgumentException: Must pass a non null String
-</screen>
- </para>
- <para>
- A patch that corrects this behavior is available from <CSP>, as are the required installation instructions.
- </para>
- </warning>
-
- </listitem>
- </varlistentry>
-
-</variablelist>
+<para>
+ There are no known issues in this release.
+</para>
Modified: epp/docs/branches/5.1/Release_Notes/en-US/need_info.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/need_info.xml 2011-08-29 03:43:15 UTC (rev 7241)
+++ epp/docs/branches/5.1/Release_Notes/en-US/need_info.xml 2011-08-29 03:48:03 UTC (rev 7242)
@@ -1,125 +1,11 @@
-<?xml version='1.0'?>
-<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<?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">
+%BOOK_ENTITIES;
]>
+<para>
+
+</para>
-<variablelist>
-
- <!-- https://issues.jboss.org/browse/JBEPP-764 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-764" /></term>
- <listitem>
-
-
- <para>
- To isolate multiple clusters running on the same network, the JBoss Cache and JGroups configuration files used in JBoss Enterprise Portal Platform have been updated to include partition name (-g) and multicast address (-u) properties used in JBoss Enterprise Application Platform.
- </para>
-
- </listitem>
- </varlistentry>
- <!-- https://issues.jboss.org/browse/JBEPP-874 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-874" /></term>
- <listitem>
-
-
- <para>
- It was found that, in previous versions of JBoss Enterprise Portal Platform, using JCR addNode within a transaction caused a javax.transaction.HeuristicMixedException (internally, org.exoplatform.services.transaction.TransactionException caused by org.jboss.cache.lock.TimeoutException) when the new node was first accessed. This has been corrected by ensuring that loading data into cache occurs outside the current transaction.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-884 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-884" /></term>
- <listitem>
-
-
- <para>
- Changed level of error message for JS compressor
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-961 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-961" /></term>
- <listitem>
-
-
- <para>
- Release Notes need more information about the issue and how it was fixed.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-1010 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-1010" /></term>
- <listitem>
-
-
- <para>
- This issue requires more information to be included in the 5.1.1 Release Notes.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-1013 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-1013" /></term>
- <listitem>
-
-
- <para>
- This issue needs more information to be provided for the 5.1.1 Release Notes.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-1018 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-1018" /></term>
- <listitem>
-
-
- <para>
- If this issue requires a Release Note, more information (about how the problem presented to users and how it was fixed) is required.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-1023 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-1023" /></term>
- <listitem>
-
-
- <para>
- This issue requires more information about how it was resolved if it requires a 5.1.1 Release Note.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!-- https://issues.jboss.org/browse/JBEPP-1036 -->
- <varlistentry>
- <term><ulink url="https://issues.jboss.org/browse/JBEPP-1036" /></term>
- <listitem>
-
-
- <para>
- This issue requires more information about the underlying cause and the fix implemented if it requires a 5.1.1 Release Note.
- </para>
-
- </listitem>
- </varlistentry>
-
-</variablelist>
Modified: epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml 2011-08-29 03:43:15 UTC (rev 7241)
+++ epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml 2011-08-29 03:48:03 UTC (rev 7242)
@@ -115,6 +115,19 @@
</listitem>
</varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-764 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-764" /></term>
+ <listitem>
+
+
+ <para>
+ To isolate multiple clusters running on the same network, the JBoss Cache and JGroups configuration files used in JBoss Enterprise Portal Platform have been updated to take advantage of the partition name (-g) and multicast address (-u) properties used in JBoss Enterprise Application Platform.
+ </para>
+
+ </listitem>
+ </varlistentry>
<!-- https://issues.jboss.org/browse/JBEPP-771 -->
<varlistentry>
@@ -331,6 +344,19 @@
</listitem>
</varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-874 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-874" /></term>
+ <listitem>
+
+
+ <para>
+ It was found that, in previous versions of JBoss Enterprise Portal Platform, using JCR addNode within a transaction caused a javax.transaction.HeuristicMixedException (internally, org.exoplatform.services.transaction.TransactionException caused by org.jboss.cache.lock.TimeoutException) when the new node was first accessed. This has been corrected by ensuring that loading data into cache occurs outside the current transaction.
+ </para>
+
+ </listitem>
+ </varlistentry>
<!-- https://issues.jboss.org/browse/JBEPP-883 -->
<varlistentry>
@@ -345,6 +371,19 @@
</listitem>
</varlistentry>
+ <!-- https://issues.jboss.org/browse/JBEPP-884 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-884" /></term>
+ <listitem>
+
+
+ <para>
+ In previous versions of JBoss Enterprise Portal Platform it was possible to disable the Javascript compressor, however this would produce an error that no compressor had been set up. This version (and future versions) of the product will report a warning instead, as disabling the compressor is a deliberate choice by the user.
+ </para>
+
+ </listitem>
+ </varlistentry>
+
<!-- https://issues.jboss.org/browse/JBEPP-887 -->
<varlistentry>
<term><ulink url="https://issues.jboss.org/browse/JBEPP-887" /></term>
@@ -423,7 +462,7 @@
<para>
- In previous Portal versions, page definitions were held in system memory before being written when starting the Portal. This could cause an Out Of Memory error if a large number of pages were defined in the XML descriptors. The transaction has now been split so that not all page definitions are held in memory prior to being written and the Out Of Memory error is no longer encountered.
+ In previous Portal versions, page definitions were held in system memory before being written when starting the Portal. This could cause an <systemitem>Out Of Memory</systemitem> error if a large number of pages were defined in the XML descriptors. The transaction has now been split so that not all page definitions are held in memory prior to being written and the <systemitem>Out Of Memory</systemitem> error is no longer encountered.
</para>
</listitem>
@@ -436,7 +475,7 @@
<para>
- JBoss Enterprise Portal Platform doesn't set content-type on css-files added via gatein-resources.xml. This causes Internet Explorer 9 to ignore these css-files due to new security policy (a console message states: SEC7113: CSS was ignored due to mime type mismatch). The ResourceRequestFilter.java file has been modified to set the content type so that content-types will be set and Internet Explorer 9 will render the Portal as expected.
+ JBoss Enterprise Portal Platform doesn't set content-type on css-files added via <filename>gatein-resources.xml</filename>. This causes Internet Explorer 9 to ignore these css-files due to new security policy (a console message states: <systemitem>SEC7113: CSS was ignored due to mime type mismatch</systemitem>). The <filename>ResourceRequestFilter.java</filename> file has been modified to set the content type so that content-types will be set and Internet Explorer 9 will render the Portal as expected.
</para>
</listitem>
@@ -449,7 +488,7 @@
<para>
- An error that caused IntegrationCache to not be invalidated when calling invalidateAll() on PicketlinkIDMCacheService MBean has been corrected in this release.
+ An error that caused IntegrationCache to not be invalidated when calling <systemitem>invalidateAll()</systemitem> on <systemitem>PicketlinkIDMCacheService</systemitem> MBean has been corrected in this release.
</para>
</listitem>
@@ -462,7 +501,7 @@
<para>
- Attempting to remove an inexistent ConsumerGroup would cause a NullPointerException. JCRRegistrationPersistenceManager now properly handles the situation.
+ Attempting to remove an inexistent <systemitem>ConsumerGroup</systemitem> would cause a <systemitem>NullPointerException</systemitem>. <systemitem>JCRRegistrationPersistenceManager</systemitem> now properly handles the situation.
</para>
</listitem>
@@ -475,7 +514,7 @@
<para>
- Local state was improperly initialized causing a NullPointerException when attempting to insert a new ConsumerGroup. Properly retrieving the state from the JCR persistence fixed the issue.
+ Local state was improperly initialized causing a <systemitem>NullPointerException</systemitem> when attempting to insert a new <systemitem>ConsumerGroup</systemitem>. Properly retrieving the state from the JCR persistence fixed the issue.
</para>
</listitem>
@@ -488,12 +527,26 @@
<para>
- In previous JBoss Enterprise Portal Platform versions, calling org.exoplatform.webui.form.UIFormCheckBoxInput.setValue() with a String value of 'true', would result in the value being interpreted as 'false' as only Boolean values (not String values) were parsed. This behavior has been corrected by recognizing string values when entered and converting them to boolean values.
+ In previous JBoss Enterprise Portal Platform versions, calling <systemitem>org.exoplatform.webui.form.UIFormCheckBoxInput.setValue()</systemitem> with a String value of '<literal>true</literal>', would result in the value being interpreted as '<literal>false</literal>' as only Boolean values (not String values) were parsed. This behavior has been corrected by recognizing string values when entered and converting them to boolean values.
</para>
</listitem>
</varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-961 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-961" /></term>
+ <listitem>
+
+
+ <para>
+ Due to improper checks in the JCR persistence of the WSRP producer configuration, a <systemitem>NullPointerException</systemitem> was thrown when the producer did not require consumers to register with it. The issue has been addressed in this release by properly checking that a <systemitem>RegistrationPolicy</systemitem> is provided before attempting to work with it.
+ </para>
+
+ </listitem>
+ </varlistentry>
+
<!-- https://issues.jboss.org/browse/JBEPP-966 -->
<varlistentry>
<term><ulink url="https://issues.jboss.org/browse/JBEPP-966" /></term>
@@ -501,7 +554,7 @@
<para>
- In previous versions of JBoss Enterprise Portal Platform, the ErrorLoginServlet did not return the HTTP header content-type. This could be problematic when running the portal instance behind Apache loadbalancer. An upstream patch has been incorporated in this release to address the issue.
+ In previous versions of JBoss Enterprise Portal Platform, the <systemitem>ErrorLoginServlet</systemitem> did not return the HTTP header content-type. This could be problematic when running the portal instance behind Apache loadbalancer. An upstream patch has been incorporated in this release to address the issue.
</para>
</listitem>
@@ -514,16 +567,63 @@
<para>
- The JCR cache configuration files in JBoss Enterprise Portal Platform 5.1.1 have been moved from the /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/lib/exo.portal.component.common-<version>.jar to /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/02portal.war/WEB-INF/conf/.
-
-This change created problems when attempting to start upgraded versions of JBoss Enterprise Portal Platform that had the original file path stored in the JCR_CONFIG table in the database. To resolve the issue, duplicates of the configuration files have been retained in the original location. This also ensures backward compatibility, without the need to change the database.
-
-Note:
-After this change, if configuration changes to the JCR cache are required, it is important that the JCR_CONFIG table be updated to use the "war:" prefix instead of "classpath:" (for example; file:war:/conf/jcr/jbosscache/local/config.xml).
+ The JCR cache configuration files in JBoss Enterprise Portal Platform 5.1.1 have been moved from <filename>/JBOSS_HOME/server/PROFILE/deploy/gatein.ear/lib/exo.portal.component.common-<version>.jar</filename> to <filename>/JBOSS_HOME/server/PROFILE/deploy/gatein.ear/02portal.war/WEB-INF/conf/</filename>.
+ </para>
+ <para>
+ This change created problems when attempting to start upgraded versions of JBoss Enterprise Portal Platform that had the original file path stored in the <systemitem>JCR_CONFIG</systemitem> table in the database. To resolve the issue, duplicates of the configuration files have been retained in the original location. This also ensures backward compatibility, without the need to change the database.
+ </para>
+ <para>
+ Note: After this change, if configuration changes to the JCR cache are required, it is important that the <systemitem>JCR_CONFIG</systemitem> table be updated to use the "war:" prefix instead of "classpath:" (for example; <filename>file:war:/conf/jcr/jbosscache/local/config.xml</filename>).
</para>
</listitem>
</varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1010 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1010" /></term>
+ <listitem>
+
+
+ <para>
+ This release of JBoss Enterprise Portal Platform makes it possible to optimize the portal when user dashboards are not used. This can be done by modifying the <systemitem>org.exoplatform.portal.config.DataStorage</systemitem> service for a simplified implementation: <systemitem>org.exoplatform.portal.config.ConstantUserNavigationsDataStorageImpl</systemitem>.
+ </para>
+ <para>
+ Portal administrators should note, however, that this action will render the dashboard functionality inoperative.
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1013 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1013" /></term>
+ <listitem>
+
+ <para>
+ In previous versions of JBoss Enterprise Portal Platform, the demonstration iFrame portlet was configured to use the GateIn blog as an example page. However, the new GateIn blog redirects itself out of iFrames and loads in the entire browser window, overriding the current portal page.
+ </para>
+ <para>
+ To prevent this, the address used in the example portlet has been changed to point to the <ulink type="http" url="gatein.org"></ulink> homepage, which does not do any redirection.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1018 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1018" /></term>
+ <listitem>
+
+
+ <para>
+ Previous versions of JBoss Enterprise Portal Platform did not honor the location of the WSRP consumer configuration file specified in <filename>wsrp-configuration.xml</filename>. This made it impossible to use any configuration file other than the default.
+ </para>
+ <para>
+ This version of JBoss Enterprise Portal Platform honors the configuration file location by adding the ability to configure consumers from an <systemitem>InputStream</systemitem> similar to the method used by the producer configuration. Administrators can now use custom consumer configuration files instead of needing to modify the default file.
+ </para>
+
+ </listitem>
+ </varlistentry>
<!-- https://issues.jboss.org/browse/JBEPP-1019 -->
<varlistentry>
@@ -538,4 +638,36 @@
</listitem>
</varlistentry>
+ <!-- https://issues.jboss.org/browse/JBEPP-1023 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1023" /></term>
+ <listitem>
+
+
+ <para>
+ A fix that was implemented to resolve an XSS vulnerabily, affected all textarea inputs and caused any gadget source code entered into the <systemitem>App Registry</systemitem> to be escaped with <> characters and rendered invalid to the portal. This prevented new gadgets being added to the portal as well as preventing any changes being made to existing gadgets.
+ </para>
+ <para>
+ The underlying issue was resolved in a fix for another bug and as a result this issue no longer presents.
+ </para>
+
+ </listitem>
+ </varlistentry>
+
+ <!-- https://issues.jboss.org/browse/JBEPP-1036 -->
+ <varlistentry>
+ <term><ulink url="https://issues.jboss.org/browse/JBEPP-1036" /></term>
+ <listitem>
+
+
+ <para>
+ It was found that editing a dashboard page that contained more than two gadgets would produce a <literal>NullPointerException</literal> in the <systemitem>MOPConsumerStructureProvider</systemitem> class and result in an <guilabel>Unknown error</guilabel> dialog in the User interface.
+ </para>
+ <para>
+ The <systemitem>MOPConsumerStructureProvider</systemitem> class has been updated to handle scenarios wherein the windowName is <literal>null</literal>, resolving this issue.
+ </para>
+
+ </listitem>
+ </varlistentry>
+
</variablelist>
Modified: epp/docs/branches/5.1/Release_Notes/publican.cfg
===================================================================
--- epp/docs/branches/5.1/Release_Notes/publican.cfg 2011-08-29 03:43:15 UTC (rev 7241)
+++ epp/docs/branches/5.1/Release_Notes/publican.cfg 2011-08-29 03:48:03 UTC (rev 7242)
@@ -4,7 +4,7 @@
debug: 1
xml_lang: en-US
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-5.1.1_Release_Notes-5.1-web-__LANG__
\ No newline at end of file
Modified: epp/docs/branches/5.1/User_Guide/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.1/User_Guide/en-US/Book_Info.xml 2011-08-29 03:43:15 UTC (rev 7241)
+++ epp/docs/branches/5.1/User_Guide/en-US/Book_Info.xml 2011-08-29 03:48:03 UTC (rev 7242)
@@ -7,7 +7,7 @@
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.1</productnumber>
<edition>2</edition>
- <pubsnumber>5.1.7</pubsnumber>
+ <pubsnumber>5.1.8</pubsnumber>
<abstract>
<para>
This document provides an easy to follow guide to the functions and
Modified: epp/docs/branches/5.1/User_Guide/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.1/User_Guide/en-US/Revision_History.xml 2011-08-29 03:43:15 UTC (rev 7241)
+++ epp/docs/branches/5.1/User_Guide/en-US/Revision_History.xml 2011-08-29 03:48:03 UTC (rev 7242)
@@ -8,6 +8,20 @@
<simpara>
<revhistory>
<revision>
+ <revnumber>2-5.1.8</revnumber>
+ <date>Fri Aug 26 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email></email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Added "Non-visible pages and security" admonition.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
<revnumber>2-5.1.7</revnumber>
<date>Thu Aug 25 2011</date>
<author>
13 years, 4 months
- 1
- 0
gatein SVN: r7241 - epp/docs/branches.
by do-not-reply＠jboss.org
Author: smumford
Date: 2011-08-28 23:43:15 -0400 (Sun, 28 Aug 2011)
New Revision: 7241
Added:
epp/docs/branches/5.2/
Log:
Creating 5.2 branch
13 years, 4 months
- 1
- 0
gatein SVN: r7240 - in epp/portal/branches/EPP_5_2_Branch: webui/portal/src/main/java/org/exoplatform/portal/webui/portal and 1 other directory.
by do-not-reply＠jboss.org
Author: mwringe
Date: 2011-08-26 14:59:50 -0400 (Fri, 26 Aug 2011)
New Revision: 7240
Modified:
epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/groovy/portal/webui/portal/UILanguageSelector.gtmpl
epp/portal/branches/EPP_5_2_Branch/webui/portal/src/main/java/org/exoplatform/portal/webui/portal/UILanguageSelector.java
Log:
JBEPP-699: merge in patch from GateIn to fix the issue (GTNPORTAL-1717, r5716)
Modified: epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/groovy/portal/webui/portal/UILanguageSelector.gtmpl
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/groovy/portal/webui/portal/UILanguageSelector.gtmpl 2011-08-26 15:11:27 UTC (rev 7239)
+++ epp/portal/branches/EPP_5_2_Branch/web/portal/src/main/webapp/groovy/portal/webui/portal/UILanguageSelector.gtmpl 2011-08-26 18:59:50 UTC (rev 7240)
@@ -48,7 +48,14 @@
<%
for(opt in options) {
String itemSelected = "NormalItem";
- if (opt.isSelected()) itemSelected = "SelectedItem";
+ if (opt.isSelected()) {
+ def setSelected = "eXo.webui.UIItemSelector.SelectedItem = new Object();";
+ setSelected += "eXo.webui.UIItemSelector.SelectedItem.component = '$selector.name';";
+ setSelected += "eXo.webui.UIItemSelector.SelectedItem.option = '$opt.value';";
+
+ rcontext.getJavascriptManager().addCustomizedOnLoadScript(setSelected);
+ itemSelected = "SelectedItem";
+ }
String onclickOption = "eXo.webui.UIItemSelector.onClickOption(this, '$uicomponent.name', '$selector.name', '$opt.value')";
%>
<div class="$itemSelected" onclick="$onclickOption">
Modified: epp/portal/branches/EPP_5_2_Branch/webui/portal/src/main/java/org/exoplatform/portal/webui/portal/UILanguageSelector.java
===================================================================
--- epp/portal/branches/EPP_5_2_Branch/webui/portal/src/main/java/org/exoplatform/portal/webui/portal/UILanguageSelector.java 2011-08-26 15:11:27 UTC (rev 7239)
+++ epp/portal/branches/EPP_5_2_Branch/webui/portal/src/main/java/org/exoplatform/portal/webui/portal/UILanguageSelector.java 2011-08-26 18:59:50 UTC (rev 7240)
@@ -21,12 +21,16 @@
import org.exoplatform.container.ExoContainer;
import org.exoplatform.container.ExoContainerContext;
+import org.exoplatform.portal.Constants;
import org.exoplatform.portal.application.PortalRequestContext;
import org.exoplatform.portal.webui.util.Util;
import org.exoplatform.portal.webui.workspace.UIMaskWorkspace;
import org.exoplatform.portal.webui.workspace.UIPortalApplication;
+import org.exoplatform.services.organization.OrganizationService;
+import org.exoplatform.services.organization.UserProfile;
import org.exoplatform.services.resources.LocaleConfig;
import org.exoplatform.services.resources.LocaleConfigService;
+import org.exoplatform.services.resources.LocaleContextInfo;
import org.exoplatform.services.resources.ResourceBundleService;
import org.exoplatform.web.url.ResourceType;
import org.exoplatform.web.url.navigation.NodeURL;
@@ -165,21 +169,30 @@
public void execute(Event<UILanguageSelector> event) throws Exception
{
String language = event.getRequestContext().getRequestParameter("language");
+ PortalRequestContext prqCtx = PortalRequestContext.getCurrentInstance();
UIPortalApplication uiApp = Util.getUIPortalApplication();
UIMaskWorkspace uiMaskWS = uiApp.getChildById(UIPortalApplication.UI_MASK_WS_ID);
uiMaskWS.setUIComponent(null);
// event.getRequestContext().addUIComponentToUpdateByAjax(uiMaskWS) ;
- Util.getPortalRequestContext().ignoreAJAXUpdateOnPortlets(false);
- if (language == null || language.trim().length() < 1)
+ prqCtx.ignoreAJAXUpdateOnPortlets(false);
+
+ if (language == null || language.trim().equals(prqCtx.getLocale().getLanguage()))
+ {
+ //LocalizationLifecycle will save userProfile if locale is changed
+ //We need to handle case : locale is not changed, but user's locale setting has not been initialized
+ if (prqCtx.getRemoteUser() != null)
+ {
+ saveLocaleToUserProfile(prqCtx);
+ }
return;
+ }
// if(!uiPortal.isModifiable()) return;
LocaleConfigService localeConfigService = event.getSource().getApplicationComponent(LocaleConfigService.class);
LocaleConfig localeConfig = localeConfigService.getLocaleConfig(language);
if (localeConfig == null)
localeConfig = localeConfigService.getDefaultLocaleConfig();
- PortalRequestContext prqCtx = PortalRequestContext.getCurrentInstance();
prqCtx.setLocale(localeConfig.getLocale());
if (prqCtx.getRequestLocale() != null)
@@ -189,6 +202,27 @@
prqCtx.sendRedirect(url.toString());
}
}
+
+ private void saveLocaleToUserProfile(PortalRequestContext context) throws Exception
+ {
+ ExoContainer container = context.getApplication().getApplicationServiceContainer();
+ OrganizationService svc = (OrganizationService)
+ container.getComponentInstanceOfType(OrganizationService.class);
+
+ // Don't rely on UserProfileLifecycle loaded UserProfile when doing
+ // an update to avoid a potential overwrite of other changes
+ UserProfile userProfile = svc.getUserProfileHandler().findUserProfileByName(context.getRemoteUser());
+ if (userProfile != null && userProfile.getUserInfoMap() != null)
+ {
+ //Only save if user's locale has not been set
+ String currLocale = userProfile.getUserInfoMap().get(Constants.USER_LANGUAGE);
+ if (currLocale == null || currLocale.trim().equals(""))
+ {
+ userProfile.getUserInfoMap().put(Constants.USER_LANGUAGE, LocaleContextInfo.getLocaleAsString(context.getLocale()));
+ svc.getUserProfileHandler().saveUserProfile(userProfile, false);
+ }
+ }
+ }
}
private String capitalizeFirstLetter(String word)
13 years, 4 months
- 1
- 0
gatein SVN: r7239 - portal/trunk/wsrp-integration/extension-war/src/main/webapp/WEB-INF/conf/wsrp.
by do-not-reply＠jboss.org
Author: nscavell
Date: 2011-08-26 11:11:27 -0400 (Fri, 26 Aug 2011)
New Revision: 7239
Modified:
portal/trunk/wsrp-integration/extension-war/src/main/webapp/WEB-INF/conf/wsrp/wsrp-configuration.xml
Log:
GTNPORTAL-2051: WSRP admin page doesn't appear anymore
Modified: portal/trunk/wsrp-integration/extension-war/src/main/webapp/WEB-INF/conf/wsrp/wsrp-configuration.xml
===================================================================
--- portal/trunk/wsrp-integration/extension-war/src/main/webapp/WEB-INF/conf/wsrp/wsrp-configuration.xml 2011-08-26 10:33:42 UTC (rev 7238)
+++ portal/trunk/wsrp-integration/extension-war/src/main/webapp/WEB-INF/conf/wsrp/wsrp-configuration.xml 2011-08-26 15:11:27 UTC (rev 7239)
@@ -164,6 +164,9 @@
<name>group.configuration</name>
<description>description</description>
<object type="org.exoplatform.portal.config.NewPortalConfig">
+ <field name="importMode">
+ <string>merge</string>
+ </field>
<field name="predefinedOwner">
<collection type="java.util.HashSet">
<value>
13 years, 4 months
- 1
- 0