-
1. Re: pages in dashboard
theute May 21, 2007 8:29 AM (in response to eagleit)There is a "special" portal called template. It is used as a template for all users to create their dashboard
-
2. Re: pages in dashboard
eagleit May 21, 2007 8:45 AM (in response to eagleit)Oh thanks. But I can't add pages directly in my "default-object.xml" !! What I must to do to add pages ??
-
3. Re: pages in dashboard
eagleit May 21, 2007 8:54 AM (in response to eagleit)I'm sorry I was mistaken. I can add page. But in my template, I want the dashboard properties !! I put the properties which written in the "default-object.xml" but when I move portlet, the position is not kept !
-
4. Re: pages in dashboard
theute May 21, 2007 8:57 AM (in response to eagleit)Explain...
Did you specify how you wanted the windows ordered by specifying height on the window descriptor ? -
5. Re: pages in dashboard
eagleit May 21, 2007 9:36 AM (in response to eagleit)I want a portal for each user based in the same template (example : 1 portal with 4 tabs/pages).
This portal must be personalisable by user (drag and drop, keep the position of the drag and drop, add content/new portlet).
Have you a database model for the dashboard ? In which table is persisted the information about each portlet position for each user ?
Have you any documentation about dashboard/template/user preferences.
Best regards. Sorry for my English. -
6. Re: pages in dashboard
eagleit May 21, 2007 9:39 AM (in response to eagleit)I give you my "default-object.xml" :
<?xml version="1.0" encoding="UTF-8"?> <!--~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~ JBoss, a division of Red Hat ~ ~ Copyright 2006, Red Hat Middleware, LLC, and individual ~ ~ contributors as indicated by the @authors tag. See the ~ ~ copyright.txt in the distribution for a full listing of ~ ~ individual contributors. ~ ~ ~ ~ This is free software; you can redistribute it and/or modify it ~ ~ under the terms of the GNU Lesser General Public License as ~ ~ published by the Free Software Foundation; either version 2.1 of ~ ~ the License, or (at your option) any later version. ~ ~ ~ ~ This software is distributed in the hope that it will be useful, ~ ~ but WITHOUT ANY WARRANTY; without even the implied warranty of ~ ~ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU ~ ~ Lesser General Public License for more details. ~ ~ ~ ~ You should have received a copy of the GNU Lesser General Public ~ ~ License along with this software; if not, write to the Free ~ ~ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA ~ ~ 02110-1301 USA, or see the FSF site: http://www.fsf.org. ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~--> <!DOCTYPE deployments PUBLIC "-//JBoss Portal//DTD Portal Object 2.6//EN" "http://www.jboss.org/portal/dtd/portal-object_2_6.dtd"> <!--~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ PORTAIL CPAGE ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~--> <deployments> <deployment> <parent-ref/> <if-exists>overwrite</if-exists> <portal> <portal-name>default</portal-name> <supported-modes> <mode>view</mode> <mode>edit</mode> <mode>help</mode> </supported-modes> <supported-window-states> <window-state>normal</window-state> <window-state>minimized</window-state> <window-state>maximized</window-state> </supported-window-states> <properties> <!-- | Set the layout for the default portal, see also portal-layouts.xml. --> <property> <name>layout.id</name> <value>CPage1Col</value> </property> <!-- | Set the theme for the default portal, see also portal-themes.xml. --> <property> <name>theme.id</name> <value>renaissance</value> </property> <!-- | Set the default render set name (used by the render tag in layouts), see also portal-renderSet.xml --> <property> <name>theme.renderSetId</name> <value>divRenderer</value> </property> <!-- | Set the default strategy name (used by the strategy interceptor), see also portal-strategies.xml --> <property> <name>layout.strategyId</name> <value>maximizedRegion</value> </property> <!-- | The default page name, if the property is not explicited then the default page name is "default" --> <property> <name>portal.defaultObjectName</name> <value>default</value> </property> </properties> <!--PAGE DEFAULT--> <page> <page-name>default</page-name> <window> <window-name>CatalogPortlet</window-name> <instance-ref>CatalogPortletInstance</instance-ref> <region>center</region> <height>0</height> </window> </page> </portal> </deployment> <!--~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ PORTAIL DASHBOARD ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~--> <deployment> <parent-ref/> <if-exists>keep</if-exists> <context> <context-name>dashboard</context-name> <properties> <!-- | Set the layout for the default portal, see also portal-layouts.xml. --> <property> <name>layout.id</name> <value>generic</value> </property> <!-- | Set the theme for the default portal, see also portal-themes.xml. --> <property> <name>theme.id</name> <value>renaissance</value> </property> <!-- | Set the default render set name (used by the render tag in layouts), see also portal-renderSet.xml --> <property> <name>theme.renderSetId</name> <value>divRenderer</value> </property> <!-- | Set the dashboard property --> <property> <name>dashboard</name> <value>true</value> </property> <!-- | Set the dnd property --> <property> <name>theme.dyna.dnd_enabled</name> <value>true</value> </property> <!-- | Set the partial refresh property --> <property> <name>theme.dyna.partial_refresh_enabled</name> <value>true</value> </property> </properties> </context> </deployment> <!--~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ PORTAIL TEMPLATE ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~--> <deployment> <parent-ref/> <if-exists>keep</if-exists> <portal> <portal-name>template</portal-name> <supported-modes> <mode>view</mode> <mode>edit</mode> <mode>help</mode> </supported-modes> <supported-window-states> <window-state>normal</window-state> <window-state>minimized</window-state> <window-state>maximized</window-state> </supported-window-states> <properties> <!-- | Set the layout for the default portal, see also portal-layouts.xml. --> <property> <name>layout.id</name> <value>generic</value> </property> <!-- | Set the theme for the default portal, see also portal-themes.xml. --> <property> <name>theme.id</name> <value>renaissance</value> </property> <!-- | Set the default render set name (used by the render tag in layouts), see also portal-renderSet.xml --> <property> <name>theme.renderSetId</name> <value>divRenderer</value> </property> <!-- | The default page name, if the property is not explicited then the default page name is "default" --> <property> <name>portal.defaultObjectName</name> <value>Bureau</value> </property> <!-- | Set the dashboard property --> <property> <name>dashboard</name> <value>true</value> </property> <!-- | Set the dnd property --> <property> <name>theme.dyna.dnd_enabled</name> <value>true</value> </property> <!-- | Set the partial refresh property --> <property> <name>theme.dyna.partial_refresh_enabled</name> <value>true</value> </property> </properties> <security-constraint> <policy-permission> <role-name>User</role-name> <action-name>viewrecursive</action-name> </policy-permission> <policy-permission> <role-name>Admin</role-name> <action-name>viewrecursive</action-name> </policy-permission> </security-constraint> <!-- PAGE BUREAU--> <page> <page-name>Bureau</page-name> <properties> <property> <name>order</name> <value>1</value> </property> <!-- | Set the layout for the default portal, see also portal-layouts.xml. --> <property> <name>layout.id</name> <value>CPage4Col</value> </property> <!-- | Set the theme for the default portal, see also portal-themes.xml. --> </properties> </page> <!-- PAGE OUTILS--> <page> <page-name>Outils</page-name> <properties> <property> <name>order</name> <value>2</value> </property> <!-- | Set the layout for the default portal, see also portal-layouts.xml. --> <property> <name>layout.id</name> <value>CPage4Col</value> </property> <!-- | Set the theme for the default portal, see also portal-themes.xml. --> </properties> </page> <!-- PAGE COLLABORATION--> <page> <page-name>Collaboration</page-name> <properties> <property> <name>order</name> <value>3</value> </property> <!-- | Set the layout for the default portal, see also portal-layouts.xml. --> <property> <name>layout.id</name> <value>CPage2ColQuart</value> </property> <!-- | Set the theme for the default portal, see also portal-themes.xml. --> </properties> </page> <!-- PAGE AGENDA--> <page> <page-name>Agenda</page-name> <properties> <property> <name>order</name> <value>4</value> </property> <!-- | Set the layout for the default portal, see also portal-layouts.xml. --> <property> <name>layout.id</name> <value>CPage2ColAgenda</value> </property> <!-- | Set the theme for the default portal, see also portal-themes.xml. --> </properties> </page> <!-- PAGE INFORMATIONS--> <page> <page-name>Informations</page-name> <properties> <property> <name>order</name> <value>5</value> </property> <!-- | Set the layout for the default portal, see also portal-layouts.xml. --> <property> <name>layout.id</name> <value>CPage2ColEgales</value> </property> <!-- | Set the theme for the default portal, see also portal-themes.xml. --> </properties> <window> <window-name>CMS</window-name> <instance-ref>CMSAdminPortletInstance</instance-ref> <region>right</region> <height>2</height> </window> <window> <window-name>DashboardConfigPortlet</window-name> <instance-ref>DashboardConfigPortletInstance</instance-ref> <region>right</region> <height>3</height> </window> </page> </portal> </deployment> <!--~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ PORTAIL ADMIN ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~--> <deployment> <parent-ref/> <if-exists>keep</if-exists> <portal> <portal-name>admin</portal-name> <supported-modes> <mode>view</mode> <mode>edit</mode> <mode>help</mode> </supported-modes> <supported-window-states> <window-state>normal</window-state> <window-state>minimized</window-state> <window-state>maximized</window-state> </supported-window-states> <properties> <!-- | Set the layout for the default portal, see also portal-layouts.xml. --> <property> <name>layout.id</name> <value>CPage2ColEgales</value> </property> <!-- | Set the theme for the default portal, see also portal-themes.xml. --> <property> <name>theme.id</name> <value>renaissance</value> </property> <!-- | Set the default render set name (used by the render tag in layouts), see also portal-renderSet.xml --> <property> <name>theme.renderSetId</name> <value>divRenderer</value> </property> <!-- | Set the default strategy name (used by the strategy interceptor), see also portal-strategies.xml --> <property> <name>layout.strategyId</name> <value>maximizedRegion</value> </property> <!-- | The default page name, if the property is not explicited then the default page name is "default" --> <property> <name>portal.defaultObjectName</name> <value>default</value> </property> </properties> <security-constraint> <policy-permission> <action-name>viewrecursive</action-name> <role-name>Admin</role-name> </policy-permission> </security-constraint> <page> <page-name>default</page-name> <window> <window-name>AdminPortletWindow</window-name> <instance-ref>AdminPortletInstance</instance-ref> <region>right</region> <height>0</height> </window> <window> <window-name>CatalogPortletWindow</window-name> <instance-ref>CatalogPortletInstance</instance-ref> <region>left</region> <height>0</height> </window> </page> <page> <page-name>Members</page-name> <window> <window-name>UserPortletWindow</window-name> <instance-ref>UserPortletInstance</instance-ref> <region>right</region> <height>0</height> </window> <window> <window-name>RolePortletWindow</window-name> <instance-ref>RolePortletInstance</instance-ref> <region>left</region> <height>0</height> </window> </page> </portal> </deployment> </deployments>
Are there any mistake ??? -
7. Re: pages in dashboard
eagleit May 22, 2007 3:44 AM (in response to eagleit)Nobody can help me ??
-
8. Re: pages in dashboard
theute May 22, 2007 8:28 PM (in response to eagleit)I want a portal for each user based in the same template (example : 1 portal with 4 tabs/pages).
This portal must be personalisable by user (drag and drop, keep the position of the drag and drop, add content/new portlet).
This is the default use case.
Modify the portal called template to create the 4 pages.
Every user logging in his dashboard will see the 4 pages, he will be able to modify those pages. keep the position, add content and this will only be visible by him. -
9. Re: pages in dashboard
eagleit May 23, 2007 3:42 AM (in response to eagleit)Thank you. But in my dashboard, I can't drag and drop the portlet I have created. Internet explorer throw this error :
Line : 1090 Char : 3 Error : 'Prototype.BrowserFeatures.XPath' is null or is not an object. Code : 0 URL : http://localhost:8080/portal/auth/dashboard
I think it is the cause of the dysfunctionof the dashboard. Do you know how to repair this error ?
Regards. -
10. Re: pages in dashboard
theute May 23, 2007 3:59 AM (in response to eagleit)Which version of IE are you using ? And Are you using JBoss Portal 2.6 CR 2 ?
-
11. Re: pages in dashboard
eagleit May 23, 2007 4:10 AM (in response to eagleit)I use the 6.0 version of internet explorer and the 2.6 CR2 version of jboss portal ...
-
12. Re: pages in dashboard
javatwo May 26, 2007 8:49 PM (in response to eagleit)"thomas.heute@jboss.com" wrote:
This is the default use case.
Modify the portal called template to create the 4 pages.
Every user logging in his dashboard will see the 4 pages, he will be able to modify those pages. keep the position, add content and this will only be visible by him.
A user created his own pages and adding content(applying layout/theme), is the page accessible to public? In my case, each user should be able to customize a page, for example, page A, and they need to be accessible publicly. In other words, user Scott's page A and user Tiger's page A is different, but they are visible to public. Can this be done in Portal?
Thanks for guidance.
Dave