Re: Bread Crumb Navigation Portlet

[TTelcik]

Hello Jaq,

allow me clarify a litte more ...

Users will not have the ability to customise
portlets on our web site. All users will be considered "anonymous"
without any customisation priviledges.

We would define a bread crumb navigation
portlet that is displayed on each page, hence the navigation portlet would
always be displayed.

We would have a main (aka. home) page
with category and sub-category pages.

The bread crumb portlet would be used
in conjunction with the main menu and side menu (when required).

We are hoping to avoid an explicit site/structure
file, instead deriving the page location from implicit or explicit meta
data associated with PSML documents.

We are still learning our way around
Jetspeed 1, so any pointers are welcome.

I am also curious as the correct keywords
to use when describing this problem to others within this mail group and
other portlet developers.
Does bread crumb navigation have another
more common or generalised name ?


Tim.


Jaq Marit wrote:

>A bread crumb in the entire portal is not much of use since the portlets,
>panes,
>and other components are already organized (and can be customized)
in such a
>way that navigation is already made very convenient. Besides, you can't
expect
>that all users will have the same profiles/preferences with regards
to the
>content of their pages.  I guess, this is one of the major distinctions
between
>a web site (same content for all users) and a portal (customized content
for
>every user).  
>
>Ifever you need a bread crumb, that should already be associated directly
to a
>particular portlet.
>
>Just a thought...
>
>Quoting [EMAIL PROTECTED]:
>
>  
>
>>Hello Peoples,
>>
>>we are looking to implement a "bread crumb" (path) style
navigation 
>>portlet within Jetspeed 1.5 (and then Jetspeed 1.6 with the JSR
168 
>>adapter when available).
>>
>>...
>>
>>This feature is quite common for many web sites with a single view.
>>
>>Does this style of navigation have a general name ?
>>
>>Has anybody seen or worked on a general approach (or pattern) for
this 
>>type of problem ?
>>
>>It would seem this type of portlet could be used for many web sites

>>requiring a particular kind of navigation.
>>
>>Comments and thoughts welcome.
>>    
>>
>
>
>
>This message was sent using IMP, the Internet Messaging Program.
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>




+++
Tim Telcik
Technical Application Architect
Business Systems Delivery
Group Services, HBF, Inc.
[EMAIL PROTECTED]
Tel: 9214 6744    Fax: 9214 6779


HBF Health Funds Inc. a registered organisation under the National Health ActHBF Insurance Pty Ltd ACN  009 268 27This email is a confidential communication intended only for the named Addressee(s). If you are not that person any disclosure, copying, distribution or use of this email or the information in it is prohibited. Please notify us immediately by telephone, (+61) 08 9265 6111 or return email and delete this email.-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-jetspeed-2/applications/pam/src/java/org/apache/jetspeed/portlets/pam/beans PortletApplicationBean.java TabBean.java

[jford]

jford   2004/09/02 21:10:23

  Modified:applications/pam/src/java/org/apache/jetspeed/portlets/pam
PortletApplicationDetail.java
  Added:   applications/pam/src/java/org/apache/jetspeed/portlets/pam/beans
PortletApplicationBean.java TabBean.java
  Log:
  Added tab navigation
  
  Revision  ChangesPath
  1.4   +3 -4  
jakarta-jetspeed-2/applications/pam/src/java/org/apache/jetspeed/portlets/pam/PortletApplicationDetail.java
  
  Index: PortletApplicationDetail.java
  ===
  RCS file: 
/home/cvs/jakarta-jetspeed-2/applications/pam/src/java/org/apache/jetspeed/portlets/pam/PortletApplicationDetail.java,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- PortletApplicationDetail.java 2 Sep 2004 22:03:53 -   1.3
  +++ PortletApplicationDetail.java 3 Sep 2004 04:10:23 -   1.4
  @@ -1,10 +1,9 @@
   /*
 * Copyright 2000-2004 The Apache Software Foundation.
 * 
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 * 
 *  http://www.apache.org/licenses/LICENSE-2.0
 * 
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
package org.apache.jetspeed.portlets.pam;
   
  -import java.io.IOException;
import javax.portlet.ActionRequest;
import javax.portlet.ActionResponse;
import javax.portlet.PortletConfig;
import javax.portlet.PortletContext;
import javax.portlet.PortletException;
import javax.portlet.PortletSession;
import javax.portlet.RenderRequest;
import javax.portlet.RenderResponse;
import org.apache.jetspeed.portlet.ServletPortlet;
import org.apache.jetspeed.components.portletregistry.PortletRegistryComponent;
import org.apache.jetspeed.om.common.portlet.MutablePortletApplication;
import org.apache.pluto.om.portlet.PortletDefinition;

  -/**
 * This portlet is a browser over all the portlet applications in the system.
 *
 * @author mailto:[EMAIL PROTECTED]">Jeremy Ford
 * @author mailto:[EMAIL PROTECTED]">David Sean Taylor
 * @version $Id$
 */
public class PortletApplicationDetail extends ServletPortlet
{
private final String VIEW_PA = "portletApplication"; 
private final String VIEW_PD = "portletDefinition";

private PortletContext context;
private PortletRegistryComponent registry;

public void init(PortletConfig config)
throws PortletException 
{
super.init(config);
context = getPortletContext();
registry = 
(PortletRegistryComponent)context.getAttribute(PortletApplicationResources.CPS_REGISTRY_COMPONENT);
if (null == registry)
{
throw new PortletException("Failed to find the Portlet Registry on portlet 
initialization");
}
}

public void doView(RenderRequest request, RenderResponse response)
  +import java.io.IOException;
import java.util.ArrayList;
import java.util.HashMap;

import javax.portlet.ActionRequest;
import javax.portlet.ActionResponse;
import javax.portlet.PortletConfig;
import javax.portlet.PortletContext;
import javax.portlet.PortletException;
import javax.portlet.PortletSession;
import javax.portlet.RenderRequest;
import javax.portlet.RenderResponse;
import org.apache.jetspeed.portlet.ServletPortlet;
import org.apache.jetspeed.portlets.pam.beans.PortletApplicationBean;
import org.apache.jetspeed.portlets.pam.beans.TabBean;
import org.apache.jetspeed.components.portletregistry.PortletRegistryComponent;
import org.apache.jetspeed.om.common.portlet.MutablePortletApplication;
import org.apache.pluto.om.portlet.PortletDefinition;
/**
 * This portlet is a browser over all the portlet applications in the system.
 *
 * @author mailto:[EMAIL PROTECTED]">Jeremy Ford
 * @author mailto:[EMAIL PROTECTED]">David Sean Taylor
 * @version $Id$
 */
public class PortletApplicationDetail extends ServletPortlet
{
private final String VIEW_PA = "portletApplication"; 
private final String VIEW_PD = "portletDefinition";

private PortletContext context;
private PortletRegistryComponent registry;
private HashMap tabMap = new HashMap();

public void init(PortletConfig config)
throws PortletException 
{
super.init(config);
context = getPortletContext();
registry = 
(PortletRegistryComponent)context.getAttribute(PortletApplicationResources.CPS_REGISTRY_COMPONENT);
if (null == registry)
{
throw new PortletException("Failed to find the Portlet Registry on portlet 
initialization");
}

TabBean tb1 = new TabBean("Details", "Deta

cvs commit: jakarta-jetspeed-2/applications/pam/src/java/org/apache/jetspeed/portlets/pam/beans - New directory

[jford]

jford   2004/09/02 21:10:21

  jakarta-jetspeed-2/applications/pam/src/java/org/apache/jetspeed/portlets/pam/beans 
- New directory

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-jetspeed-2/applications/pam/src/webapp/WEB-INF/view pam-detail.jsp

[jford]

jford   2004/09/02 21:10:03

  Modified:applications/pam/src/webapp/WEB-INF/view pam-detail.jsp
  Log:
  Added tab navigation
  
  Revision  ChangesPath
  1.4   +1 -1  
jakarta-jetspeed-2/applications/pam/src/webapp/WEB-INF/view/pam-detail.jsp
  
  Index: pam-detail.jsp
  ===
  RCS file: 
/home/cvs/jakarta-jetspeed-2/applications/pam/src/webapp/WEB-INF/view/pam-detail.jsp,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- pam-detail.jsp2 Sep 2004 22:04:05 -   1.3
  +++ pam-detail.jsp3 Sep 2004 04:10:03 -   1.4
  @@ -1 +1 @@
  -<%--
Copyright 2004 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
--%>
<%@ page language="java" import="javax.portlet.*, java.util.*, 
org.apache.jetspeed.portlets.pam.PortletApplicationBean, 
org.apache.jetspeed.om.common.portlet.PortletDefinitionComposite" session="true" %>
<%@ taglib uri='/WEB-INF/portlet.tld' prefix='portlet'%>
<%@ taglib uri="http://java.sun.com/jstl/core"; prefix="c" %>



Portlet Application Detail





app.name = 
app.version = 

TODO: Details






<%--We must do this since portlet taglib doesn't support 
expressions--%>
<% String pdefName = (String) pageContext.getAttribute("pdefName"); %>





">









Selected Portlet




  \ No newline at end of file
  +<%--
Copyright 2004 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
--%>
<%@ page language="java" import="javax.portlet.*, java.util.*, 
org.apache.jetspeed.portlets.pam.PortletApplicationBean, 
org.apache.jetspeed.portlets.pam.beans.TabBean, 
org.apache.jetspeed.om.common.portlet.PortletDefinitionComposite" session="true" %>
<%@ taglib uri='/WEB-INF/portlet.tld' prefix='portlet'%>
<%@ taglib uri="http://java.sun.com/jstl/core"; prefix="c" %>



Portlet Application Detail








app.name = 
app.version = 

TODO: Details






 class="LTabLeft" 

 class="LTabLeftLow" 

 style="font-size:1pt;" nowrap="true">
  

 class="LTab" 
 class="LTabLow" 
 align="center" valign="middle" nowrap="true">
 
 <% String tabid = 
((TabBean)pageContext.getAttribute("tab")).getId(); %>
 
 
 
 
">



 class="LTabRight" 
 class="LTabRightLow"  
style="font-size:1pt;" nowrap="true">
 









<%--We must do this since portlet taglib doesn't support expressions--%>
<% String pdefName = (String) pageContext.getAttribute("pdefName"); %>





">









Selected Portlet




  \ No newline at end of file
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-jetspeed-2/applications/pam/src/webapp/WEB-INF/view pam-detail.jsp

[jford]

jford   2004/09/02 15:04:06

  Modified:applications/pam/src/webapp/WEB-INF/view pam-detail.jsp
  Log:
  Added the ability to select a portlet from the application
  
  Revision  ChangesPath
  1.3   +1 -1  
jakarta-jetspeed-2/applications/pam/src/webapp/WEB-INF/view/pam-detail.jsp
  
  Index: pam-detail.jsp
  ===
  RCS file: 
/home/cvs/jakarta-jetspeed-2/applications/pam/src/webapp/WEB-INF/view/pam-detail.jsp,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- pam-detail.jsp6 Jul 2004 16:11:45 -   1.2
  +++ pam-detail.jsp2 Sep 2004 22:04:05 -   1.3
  @@ -1 +1 @@
  -<%--
Copyright 2004 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
--%>
<%@ page language="java" import="javax.portlet.*, 
org.apache.jetspeed.portlets.pam.PortletApplicationBean" session="true" %>
<%@ taglib uri='/WEB-INF/portlet.tld' prefix='portlet'%>
<%@ taglib uri="http://java.sun.com/jstl/core"; prefix="c" %>

Portlet Application Detail

<%
String name = "N/A";
String version = "0.0";
PortletApplicationBean pa = 
(PortletApplicationBean)renderRequest.getAttribute("portletApplication");
if (null != pa)
{
name = pa.getName();
version = pa.getVersion();
}

%>


app.name = <%= name %>
app.version = <%= version %>

TODO: Details

  \ No newline at end of file
  +<%--
Copyright 2004 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
--%>
<%@ page language="java" import="javax.portlet.*, java.util.*, 
org.apache.jetspeed.portlets.pam.PortletApplicationBean, 
org.apache.jetspeed.om.common.portlet.PortletDefinitionComposite" session="true" %>
<%@ taglib uri='/WEB-INF/portlet.tld' prefix='portlet'%>
<%@ taglib uri="http://java.sun.com/jstl/core"; prefix="c" %>



Portlet Application Detail





app.name = 
app.version = 

TODO: Details






<%--We must do this since portlet taglib doesn't support 
expressions--%>
<% String pdefName = (String) pageContext.getAttribute("pdefName"); %>





">









Selected Portlet




  \ No newline at end of file
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-jetspeed-2/applications/pam/src/java/org/apache/jetspeed/portlets/pam PortletApplicationDetail.java

[jford]

jford   2004/09/02 15:03:53

  Modified:applications/pam/src/java/org/apache/jetspeed/portlets/pam
PortletApplicationDetail.java
  Log:
  Added the ability to select a portlet from the application
  
  Revision  ChangesPath
  1.3   +6 -6  
jakarta-jetspeed-2/applications/pam/src/java/org/apache/jetspeed/portlets/pam/PortletApplicationDetail.java
  
  Index: PortletApplicationDetail.java
  ===
  RCS file: 
/home/cvs/jakarta-jetspeed-2/applications/pam/src/java/org/apache/jetspeed/portlets/pam/PortletApplicationDetail.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- PortletApplicationDetail.java 6 Jul 2004 16:11:25 -   1.2
  +++ PortletApplicationDetail.java 2 Sep 2004 22:03:53 -   1.3
  @@ -1,10 +1,10 @@
  -/*
 * Copyright 2000-2004 The Apache Software Foundation.
 * 
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 * 
 *  http://www.apache.org/licenses/LICENSE-2.0
 * 
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
package org.apache.jetspeed.portlets.pam;

  +/*
 * Copyright 2000-2004 The Apache Software Foundation.
 * 
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 * 
 *  http://www.apache.org/licenses/LICENSE-2.0
 * 
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
package org.apache.jetspeed.portlets.pam;
   
  -import java.io.IOException;
import javax.portlet.ActionRequest;
import javax.portlet.ActionResponse;
import javax.portlet.PortletConfig;
import javax.portlet.PortletContext;
import javax.portlet.PortletException;
import javax.portlet.PortletSession;
import javax.portlet.RenderRequest;
import javax.portlet.RenderResponse;
import org.apache.jetspeed.portlet.ServletPortlet;
import org.apache.jetspeed.components.portletregistry.PortletRegistryComponent;
import org.apache.jetspeed.om.common.portlet.MutablePortletApplication;


  -/**
 * This portlet is a browser over all the portlet applications in the system.
 *
 * @author mailto:[EMAIL PROTECTED]">Jeremy Ford
 * @author mailto:[EMAIL PROTECTED]">David Sean Taylor
 * @version $Id$
 */
public class PortletApplicationDetail extends ServletPortlet
{
private final String VIEW_PA = "portletApplication"; 

private PortletContext context;
private PortletRegistryComponent registry;

public void init(PortletConfig config)
throws PortletException 
{
super.init(config);
context = getPortletContext();
registry = 
(PortletRegistryComponent)context.getAttribute(PortletApplicationResources.CPS_REGISTRY_COMPONENT);
if (null == registry)
{
throw new PortletException("Failed to find the Portlet Registry on portlet 
initialization");
}
}

public void doView(RenderRequest request, RenderResponse response)
  +import java.io.IOException;
import javax.portlet.ActionRequest;
import javax.portlet.ActionResponse;
import javax.portlet.PortletConfig;
import javax.portlet.PortletContext;
import javax.portlet.PortletException;
import javax.portlet.PortletSession;
import javax.portlet.RenderRequest;
import javax.portlet.RenderResponse;
import org.apache.jetspeed.portlet.ServletPortlet;
import org.apache.jetspeed.components.portletregistry.PortletRegistryComponent;
import org.apache.jetspeed.om.common.portlet.MutablePortletApplication;
import org.apache.pluto.om.portlet.PortletDefinition;

  +/**
 * This portlet is a browser over all the portlet applications in the system.
 *
 * @author mailto:[EMAIL PROTECTED]">Jeremy Ford
 * @author mailto:[EMAIL PROTECTED]">David Sean Taylor
 * @version $Id$
 */
public class PortletApplicationDetail extends ServletPortlet
{
private final String VIEW_PA = "portletApplication"; 
private final String VIEW_PD = "portletDefinition";

private PortletContext context;
private PortletRegistryComponent registry;

public void init(PortletConfig config)
throws PortletException 
{
super.init(config);
context = getPortletContext();
registry = 
(PortletRegistryComponent)context.getAttribute(PortletApplicationResources.CPS_R

Re: [PATCH] [J2] Page Navigation Tabs Decorators

[Randy Watler]

Sorry about that.  Fix is on the way.
Jeremy Ford
[EMAIL PROTECTED]

Thanks Jeremy! WFM.
Randy Watler
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Jetspeed2 Page Profiler/Locator Status

[David Sean Taylor]

Randy Watler wrote:

David Sean Taylor wrote:

Finally, I am wondering if this work would conflict with current 
jetspeed 2 development by commiters... judging by the fact that you 
are splitting the profiler and page-manager components out now, 
perhaps you are already at work here. If not, could this kind of 
effort help at all if contributed?


I don't see how splitting the components will conflict with your work 
although it might be best for you to base your patches off the split 
components if you are going to take a few days to write it
It would be great to work with you on completing the profiler 
functionality
I look forward to it!

Will do. I will go ahead and start this work and keep you appraised. 
Eventual JCMS integration seems like a good goal... everyone on the 
list seems to wants one!

OK, I'll hold off on splitting the profiler out to its own module for now.
I am working on getting JCMS into Apache.
Its a donation from myself and Christophe Lombard
Im not very good at Apache bureaucracy, so getting the code into CVS  is 
taking far longer than for some one who is well-connected.
We are now looking into integrating the J2 security policy into JCMS

Thanks for the support,
Randy Watler

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Jetspeed2 Page Profiler/Locator Status

[Randy Watler]

David Sean Taylor wrote:

Finally, I am wondering if this work would conflict with current 
jetspeed 2 development by commiters... judging by the fact that you 
are splitting the profiler and page-manager components out now, 
perhaps you are already at work here. If not, could this kind of 
effort help at all if contributed?

I don't see how splitting the components will conflict with your work 
although it might be best for you to base your patches off the split 
components if you are going to take a few days to write it
It would be great to work with you on completing the profiler 
functionality
I look forward to it!

Will do. I will go ahead and start this work and keep you appraised. 
Eventual JCMS integration seems like a good goal... everyone on the list 
seems to wants one!

Thanks for the support,
Randy Watler

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PATCH] [J2] Page Navigation Tabs Decorators

[Randy Watler]

Randy Watler wrote:
This appears to be because the portlet css stylesheet is now not 
linked into the document in maximized mode.

Perhaps this has to do with the recent changes in 
PageAggregatorImpl/PortletAggregatorImpl that moved the "cssUrls" 
setting from a context session to a plain context attribute? I am 
still trying to track down how the setting makes its way ino the 
renderRequest object used by the decorator via the 
JetspeedPowerTool... I am guessing someone more familiar with the core 
can find the problem more quickly?

It seems odd to me that the maximized render case in 
PageAggregatorImpl.build() does not call addStyle() for the portlet 
decorator?

Randy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-jetspeed-2/portal/src/java/org/apache/jetspeed/aggregator/impl PageAggregatorImpl.java

[jford]

jford   2004/09/02 14:23:48

  Modified:portal/src/java/org/apache/jetspeed/aggregator/impl
PageAggregatorImpl.java
  Log:
  Make sure to add decorator to portlet when in Max mode
  
  Revision  ChangesPath
  1.13  +11 -1 
jakarta-jetspeed-2/portal/src/java/org/apache/jetspeed/aggregator/impl/PageAggregatorImpl.java
  
  Index: PageAggregatorImpl.java
  ===
  RCS file: 
/home/cvs/jakarta-jetspeed-2/portal/src/java/org/apache/jetspeed/aggregator/impl/PageAggregatorImpl.java,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- PageAggregatorImpl.java   2 Sep 2004 17:09:15 -   1.12
  +++ PageAggregatorImpl.java   2 Sep 2004 21:23:48 -   1.13
  @@ -162,6 +162,16 @@
   
context.getRequest().setAttribute("org.apache.jetspeed.maximized.Fragment", fragment);
   
context.getRequest().setAttribute("org.apache.jetspeed.maximized.Layout", 
page.getRootFragment());
   
  +if(fragment.getDecorator() != null)
  +{
  +log.debug("decorator=" + currentFragment.getDecorator());
  + addStyle(context, fragment.getDecorator(), Fragment.PORTLET);
  +} 
  +else 
  +{
  +log.debug("no decorator for defined for portlet fragement," 
+ currentFragment.getId()+".  So using page default, "+defaultPortletDecorator);
  +addStyle(context, defaultPortletDecorator, 
Fragment.PORTLET);
  +}
   renderer.renderNow(page.getRootFragment(), context);
   
   
context.getRequest().removeAttribute("org.apache.jetspeed.maximized.Fragment");
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PATCH] [J2] Page Navigation Tabs Decorators

[Jeremy Ford]

Sorry about that.  Fix is on the way.
Jeremy Ford
[EMAIL PROTECTED]

From: "Scott T. Weaver" <[EMAIL PROTECTED]>
Reply-To: "Jetspeed Developers List" <[EMAIL PROTECTED]>
To: Jetspeed Developers List <[EMAIL PROTECTED]>
Subject: Re: [PATCH] [J2] Page Navigation Tabs Decorators
Date: Thu, 02 Sep 2004 16:58:00 -0400
Im seeing (or not seeing) the same thing David is on Firefox 0.9.3
David Sean Taylor wrote:
Randy Watler wrote:
David,
Just discovered during testing that the decorators are not correctly 
displaying the background in the title bar in maximize mode.
Are you seeing that too?

I am not seeing any odd behavior in the portlet title bars in maximized 
mode. Which browser are you using?

Mozilla (Firefox)
Internet Explorer 6
same behavior on both
The title bar background is white, thus you dont really see the title bar
Perhaps you forgot to send a patched file, or I missed one?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--
"Great minds discuss ideas. Average minds discuss events. Small minds 
discuss people."  - Admiral Hyman Rickover

***
*   Scott T. Weaver   *
* <[EMAIL PROTECTED]> *
* *
* --  *
*   Apache Jetspeed Enterprise Portal *
* Apache Pluto Portlet Container  *
* *
* OpenEditPro, Website Content Management *
* *
***
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_
Get ready for school! Find articles, homework help and more in the Back to 
School Guide! http://special.msn.com/network/04backtoschool.armx

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PATCH] [J2] Page Navigation Tabs Decorators

[Scott T. Weaver]

Im seeing (or not seeing) the same thing David is on Firefox 0.9.3
David Sean Taylor wrote:
Randy Watler wrote:
David,
Just discovered during testing that the decorators are not correctly 
displaying the background in the title bar in maximize mode.
Are you seeing that too?

I am not seeing any odd behavior in the portlet title bars in 
maximized mode. Which browser are you using?

Mozilla (Firefox)
Internet Explorer 6
same behavior on both
The title bar background is white, thus you dont really see the title bar
Perhaps you forgot to send a patched file, or I missed one?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--
"Great minds discuss ideas. Average minds discuss events. Small minds discuss people." 
 - Admiral Hyman Rickover
***
*   Scott T. Weaver   *
* <[EMAIL PROTECTED]> *
* *
* --  *
*   Apache Jetspeed Enterprise Portal *
* Apache Pluto Portlet Container  *
* *
* OpenEditPro, Website Content Management *
* *
***
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PATCH] [J2] Page Navigation Tabs Decorators

[Randy Watler]

David/Scott:
David Sean Taylor wrote:
Randy Watler wrote:
David,
Just discovered during testing that the decorators are not correctly 
displaying the background in the title bar in maximize mode.
Are you seeing that too?

I am not seeing any odd behavior in the portlet title bars in 
maximized mode. Which browser are you using?

Mozilla (Firefox)
Internet Explorer 6
same behavior on both
The title bar background is white, thus you dont really see the title bar
Perhaps you forgot to send a patched file, or I missed one? 
No, neither. This appears to be because the portlet css stylesheet is 
now not linked into the document in maximized mode.

Perhaps this has to do with the recent changes in 
PageAggregatorImpl/PortletAggregatorImpl that moved the "cssUrls" 
setting from a context session to a plain context attribute? I am still 
trying to track down how the setting makes its way ino the renderRequest 
object used by the decorator via the JetspeedPowerTool... I am guessing 
someone more familiar with the core can find the problem more quickly?

Still looking anyway,
Randy Watler

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Jetspeed2 Page Profiler/Locator Status

[David Sean Taylor]

Randy Watler wrote:
David,

David/Scott/All,
Looking at the Jetspeed2 CVS HEAD, it appears that the 
profiler/locator system is not active and instead PSML pages are 
pulled directly from the page-manager. There were also one or two 
"under construction" comments that have also supported this conclusion.

Assuming I have not missed anything obvious, I am wondering where 
this support stands? Since we will need group/role profiling at a 
minimum before we can roll out a production Jetspeed2 
implementation, I would certainly be willing to help out in the 
coding, debugging, or any other capacity if my efforts would be 
welcome.

Right now the simple algorithm is to use the page name to locate the 
page.
Nothing more.
I hope to start writing an admin portlet this week to setup profile 
rules

Understood. Our immediate need is to have the system execute on the 
existing "j1", "role-fallback", and "path" role sets.

The good ole J1 Role Fallback solution.
To that end, I have tinkered with some of the "under construction" 
code in o/a/j/profiler/impl/ProfilerValveImpl and 
o/a/j/profiler/impl/JetspeedProfiler. I am considering hacking 
o/a/j/page/impl/CastorXmlPageManager to support page ids formatted by 
the existing profiler, (i.e. 
'page:/default-page.psml:user:anon:mediatype:html:language:en:country:US'). 
I envision using a J1 like PSML directory structure under the existing 
pages directory for this. However, I am not sure this is what is 
intended!
In J2, the Profiiler and PageManager are designed to work in the same 
way as J1: using a locator object to specify the generalized page location.
The big difference is the profiler is no longer hard-coded solution. Its 
engine is all driven by configurable rules.

Here are some J2 design questions I have related to these thoughts:
- Apparently, the file system arrangement of the PSML resources under 
the pages directory is currently used to determine navigation and 
default pages. Ultimately, this information would need to be 
customized/generated by the profiler in its rule context instead of 
being read from the file system/database, no?
Yes, the locator does this.
Im looking into JCMS as a PageManager component impl, still working out 
details, like getting JCMS into incubation for starters

- Given the default values in the "path.session" and "request.session" 
rules, I assume the profiler rules should be determining the default 
page instead of the default name available in 
o/a/j/om/folder/FolderImpl. Is this correct?

Well the profiler will give hints to the page service via the locator
Its up to the page service to figure out what gets ultimately served up
- After adding debug code to loop over the profiler fallback iterator, 
I am wondering how the "group.role.user" rule is intended to be 
iterated over. It seems to be only binding to the "user" at the moment:

page:/test-page.psml:user:manager:mediatype:html:language:en:country:US
page:/test-page.psml:user:manger:mediatype:html:language:en
page:/test-page.psml:user:manger:mediatype:html
page:/test-page.psml:user:manager
I too need to review it, its been a while, my guess is that its not complete
I should be working on this all day tomorrow
Would I expect to see something like 
"page:/test-page.psml:role:user:..." and 
"page:/test-page.psml:role:manager:..." out of this locator or are 
multiple locators required? Given that the "path.session" rule is part 
of the "j1" definition,  I would also expect the following to be 
available on the fallback iterator:

page:/test-page.psml
page:/default-page.psml
Would that be a reasonable expectation?
Yes, that is a valid rule.
If you don't find the given page, fall back to a default page
- It seems that by enabling the JetspeedProfiler page access, 
extending the CastorXMLPageManager to map the profiler/locator page 
urls to the directory structure, and improving the generation of the 
Folder exported via a request attribute I can bootstrap a rudimentary 
profiling system for pages. Am I missing something?

Nope, not that Im aware
I hope to get a UI in place by next week for defining profile rules
See how that goes...
Finally, I am wondering if this work would conflict with current 
jetspeed 2 development by commiters... judging by the fact that you 
are splitting the profiler and page-manager components out now, 
perhaps you are already at work here. If not, could this kind of 
effort help at all if contributed?

I don't see how splitting the components will conflict with your work 
although it might be best for you to base your patches off the split 
components if you are going to take a few days to write it
It would be great to work with you on completing the profiler functionality
I look forward to it!

Randy Watler

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsub

cvs commit: jakarta-jetspeed-2/portal/src/webapp/WEB-INF/decorations/portlet/html/minty-blue/images view.gif

[taylor]

taylor  2004/09/02 12:05:58

  Modified:portal/src/webapp/WEB-INF/decorations/portlet/html/jetspeed/images
view.gif
   portal/src/webapp/WEB-INF/decorations/portlet/html/metal/images
view.gif
   portal/src/webapp/WEB-INF/decorations/portlet/html/minty-blue/images
view.gif
  Log:
  view mode icon changed to restore-like icon instead of confusing X (close)
  
  CVS: --
  CVS: PR:
  CVS:   If this change addresses a PR in the problem report tracking
  CVS:   database, then enter the PR number(s) here.
  CVS: Obtained from:
  CVS:   If this change has been taken from another system, such as NCSA,
  CVS:   then name the system in this line, otherwise delete it.
  CVS: Submitted by:
  CVS:   If this code has been contributed to Apache by someone else; i.e.,
  CVS:   they sent us a patch or a new module, then include their name/email
  CVS:   address here. If this is your work then delete this line.
  CVS: Reviewed by:
  CVS:   If we are doing pre-commit code reviews and someone else has
  CVS:   reviewed your changes, include their name(s) here.
  CVS:   If you have not had it reviewed then delete this line.
  
  Revision  ChangesPath
  1.2   +2 -1  
jakarta-jetspeed-2/portal/src/webapp/WEB-INF/decorations/portlet/html/jetspeed/images/view.gif
  
<>
  
  
  1.2   +2 -1  
jakarta-jetspeed-2/portal/src/webapp/WEB-INF/decorations/portlet/html/metal/images/view.gif
  
<>
  
  
  1.2   +2 -1  
jakarta-jetspeed-2/portal/src/webapp/WEB-INF/decorations/portlet/html/minty-blue/images/view.gif
  
<>
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PATCH] [J2] Page Navigation Tabs Decorators

[David Sean Taylor]

Randy Watler wrote:
David,
Just discovered during testing that the decorators are not correctly 
displaying the background in the title bar in maximize mode.
Are you seeing that too?

I am not seeing any odd behavior in the portlet title bars in 
maximized mode. Which browser are you using?

Mozilla (Firefox)
Internet Explorer 6
same behavior on both
The title bar background is white, thus you dont really see the title bar
Perhaps you forgot to send a patched file, or I missed one?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PATCH] [J2] Page Navigation Tabs Decorators

[Randy Watler]

David,
Just discovered during testing that the decorators are not correctly 
displaying the background in the title bar in maximize mode.
Are you seeing that too?

I am not seeing any odd behavior in the portlet title bars in maximized 
mode. Which browser are you using?

The only bug I have seen relates to the content search paths that 
displays "jetspeed" action icons in the "metal" and "minty-blue" portlets.

If it persists, I will update from CVS and check it out.
Randy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Bread Crumb Navigation Portlet

[David Sean Taylor]

[EMAIL PROTECTED] wrote:
Hello Peoples,
we are looking to implement a "bread crumb" (path) style navigation 
portlet within Jetspeed 1.5 (and then Jetspeed 1.6 with the JSR 168 
adapter when available).

J1 does not have this feature
I would like to add a breadcrumb trail to J2, but I personally do not 
plan on doing the same for J1

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Jetspeed2 Page Profiler/Locator Status

[Randy Watler]

David,

David/Scott/All,
Looking at the Jetspeed2 CVS HEAD, it appears that the 
profiler/locator system is not active and instead PSML pages are 
pulled directly from the page-manager. There were also one or two 
"under construction" comments that have also supported this conclusion.

Assuming I have not missed anything obvious, I am wondering where this 
support stands? Since we will need group/role profiling at a minimum 
before we can roll out a production Jetspeed2 implementation, I would 
certainly be willing to help out in the coding, debugging, or any 
other capacity if my efforts would be welcome.

Right now the simple algorithm is to use the page name to locate the page.
Nothing more.
I hope to start writing an admin portlet this week to setup profile rules
Understood. Our immediate need is to have the system execute on the 
existing "j1", "role-fallback", and "path" role sets.

To that end, I have tinkered with some of the "under construction" code 
in o/a/j/profiler/impl/ProfilerValveImpl and 
o/a/j/profiler/impl/JetspeedProfiler. I am considering hacking 
o/a/j/page/impl/CastorXmlPageManager to support page ids formatted by 
the existing profiler, (i.e. 
'page:/default-page.psml:user:anon:mediatype:html:language:en:country:US'). 
I envision using a J1 like PSML directory structure under the existing 
pages directory for this. However, I am not sure this is what is intended!

Here are some J2 design questions I have related to these thoughts:
- Apparently, the file system arrangement of the PSML resources under 
the pages directory is currently used to determine navigation and 
default pages. Ultimately, this information would need to be 
customized/generated by the profiler in its rule context instead of 
being read from the file system/database, no?

- Given the default values in the "path.session" and "request.session" 
rules, I assume the profiler rules should be determining the default 
page instead of the default name available in 
o/a/j/om/folder/FolderImpl. Is this correct?

- After adding debug code to loop over the profiler fallback iterator, I 
am wondering how the "group.role.user" rule is intended to be iterated 
over. It seems to be only binding to the "user" at the moment:

page:/test-page.psml:user:manager:mediatype:html:language:en:country:US
page:/test-page.psml:user:manger:mediatype:html:language:en
page:/test-page.psml:user:manger:mediatype:html
page:/test-page.psml:user:manager
Would I expect to see something like 
"page:/test-page.psml:role:user:..." and 
"page:/test-page.psml:role:manager:..." out of this locator or are 
multiple locators required? Given that the "path.session" rule is part 
of the "j1" definition,  I would also expect the following to be 
available on the fallback iterator:

page:/test-page.psml
page:/default-page.psml
Would that be a reasonable expectation?
- It seems that by enabling the JetspeedProfiler page access, extending 
the CastorXMLPageManager to map the profiler/locator page urls to the 
directory structure, and improving the generation of the Folder exported 
via a request attribute I can bootstrap a rudimentary profiling system 
for pages. Am I missing something?

Finally, I am wondering if this work would conflict with current 
jetspeed 2 development by commiters... judging by the fact that you are 
splitting the profiler and page-manager components out now, perhaps you 
are already at work here. If not, could this kind of effort help at all 
if contributed?

Randy Watler

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PATCH] [J2] Page Navigation Tabs Decorators

[David Sean Taylor]

Randy Watler wrote:
Reattached patch... webmail strikes again!
Randy Watler
I applied the patch.
Just discovered during testing that the decorators are not correctly 
displaying the background in the title bar in maximize mode.
Are you seeing that too?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Resolved: (JS2-89) Implement PLT.C CSS Style Definitions

[jetspeed-dev]

Message:

   The following issue has been resolved as FIXED.

   Resolver: Jeremy Ford
   Date: Thu, 2 Sep 2004 10:11 AM

All remaining issues have been resolved.
-
View the issue:
  http://issues.apache.org/jira/browse/JS2-89

Here is an overview of the issue:
-
Key: JS2-89
Summary: Implement PLT.C CSS Style Definitions
   Type: New Feature

 Status: Resolved
   Priority: Major
 Resolution: FIXED

Project: Jetspeed 2
 Components: 
 Layout
   Fix Fors:
 2.0-dev/cvs
   Versions:
 2.0-dev/cvs

   Assignee: David Sean Taylor
   Reporter: David Sean Taylor

Created: Tue, 6 Jul 2004 9:40 AM
Updated: Thu, 2 Sep 2004 10:11 AM

Description:
Implement PLT.C CSS Style Definitions from the Portlet API Spec
This will allow portlets to use common CSS Styles



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-jetspeed-2/portal/src/java/org/apache/jetspeed/aggregator/impl PortletAggregatorImpl.java PageAggregatorImpl.java

[jford]

jford   2004/09/02 10:09:15

  Modified:portal/src/java/org/apache/jetspeed/aggregator/impl
PortletAggregatorImpl.java PageAggregatorImpl.java
  Log:
  CSS styles not stored in the request object
  
  PR: JIRA #JS2-89
  
  Revision  ChangesPath
  1.7   +3 -3  
jakarta-jetspeed-2/portal/src/java/org/apache/jetspeed/aggregator/impl/PortletAggregatorImpl.java
  
  Index: PortletAggregatorImpl.java
  ===
  RCS file: 
/home/cvs/jakarta-jetspeed-2/portal/src/java/org/apache/jetspeed/aggregator/impl/PortletAggregatorImpl.java,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- PortletAggregatorImpl.java2 Aug 2004 17:58:05 -   1.6
  +++ PortletAggregatorImpl.java2 Sep 2004 17:09:15 -   1.7
  @@ -84,12 +84,12 @@
   private void addStyle(RequestContext context, String decoratorName, String 
decoratorType) 
   {
   log.debug("addStyle: decoratorName=" + decoratorName + ", decoratorType=" + 
decoratorType );
  -Set cssUrls = (Set) context.getSessionAttribute("cssUrls");
  +Set cssUrls = (Set) context.getAttribute("cssUrls");
   
   if (cssUrls == null)
   {
   cssUrls = new HashSet();
  -context.setSessionAttribute("cssUrls", cssUrls);
  +context.setAttribute("cssUrls", cssUrls);
   }
   
   //cssUrls.add("/WEB-INF/decorations/" + decoratorType + "/html/" + 
decoratorName + "/css/styles.css");
  
  
  
  1.12  +3 -3  
jakarta-jetspeed-2/portal/src/java/org/apache/jetspeed/aggregator/impl/PageAggregatorImpl.java
  
  Index: PageAggregatorImpl.java
  ===
  RCS file: 
/home/cvs/jakarta-jetspeed-2/portal/src/java/org/apache/jetspeed/aggregator/impl/PageAggregatorImpl.java,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- PageAggregatorImpl.java   6 Aug 2004 19:05:21 -   1.11
  +++ PageAggregatorImpl.java   2 Sep 2004 17:09:15 -   1.12
  @@ -273,12 +273,12 @@
   
   private void addStyle(RequestContext context, String decoratorName, String 
decoratorType) 
   {
  -Set cssUrls = (Set) context.getSessionAttribute("cssUrls");
  +Set cssUrls = (Set) context.getAttribute("cssUrls");
   
   if (cssUrls == null)
   {
   cssUrls = new HashSet();
  -context.setSessionAttribute("cssUrls", cssUrls);
  +context.setAttribute("cssUrls", cssUrls);
   }
   
   if(decoratorType.equals(Fragment.LAYOUT))
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-jetspeed-2/portal/src/webapp/WEB-INF/decorations/layout/html/minty-blue decorator-top.vm

[jford]

jford   2004/09/02 10:08:42

  Modified:portal/src/webapp/WEB-INF/decorations/layout/html/metal
decorator-top.vm
   portal/src/webapp/WEB-INF/decorations/layout/html/jetspeed
decorator-top.vm
   portal/src/webapp/WEB-INF/decorations/layout/html/minty-blue
decorator-top.vm
  Log:
  CSS styles not stored in the request object
  
  PR: JIRA #JS2-89
  
  Revision  ChangesPath
  1.5   +1 -1  
jakarta-jetspeed-2/portal/src/webapp/WEB-INF/decorations/layout/html/metal/decorator-top.vm
  
  Index: decorator-top.vm
  ===
  RCS file: 
/home/cvs/jakarta-jetspeed-2/portal/src/webapp/WEB-INF/decorations/layout/html/metal/decorator-top.vm,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- decorator-top.vm  28 Jul 2004 13:46:02 -  1.4
  +++ decorator-top.vm  2 Sep 2004 17:08:41 -   1.5
  @@ -19,7 +19,7 @@
   
   
   $jetspeed.page.title 
  -#set($cssUrls = $renderRequest.getPortletSession().getAttribute("cssUrls"))
  +#set($cssUrls = $renderRequest.getAttribute("cssUrls"))
   #foreach($cssUrl in $cssUrls)
   
   #end
  
  
  
  1.12  +1 -1  
jakarta-jetspeed-2/portal/src/webapp/WEB-INF/decorations/layout/html/jetspeed/decorator-top.vm
  
  Index: decorator-top.vm
  ===
  RCS file: 
/home/cvs/jakarta-jetspeed-2/portal/src/webapp/WEB-INF/decorations/layout/html/jetspeed/decorator-top.vm,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- decorator-top.vm  2 Sep 2004 00:42:49 -   1.11
  +++ decorator-top.vm  2 Sep 2004 17:08:41 -   1.12
  @@ -19,7 +19,7 @@
   
   
   $jetspeed.page.title
  -#set($cssUrls = $renderRequest.getPortletSession().getAttribute("cssUrls"))
  +#set($cssUrls = $renderRequest.getAttribute("cssUrls"))
   #foreach($cssUrl in $cssUrls)
   
   #end
  
  
  
  1.5   +1 -1  
jakarta-jetspeed-2/portal/src/webapp/WEB-INF/decorations/layout/html/minty-blue/decorator-top.vm
  
  Index: decorator-top.vm
  ===
  RCS file: 
/home/cvs/jakarta-jetspeed-2/portal/src/webapp/WEB-INF/decorations/layout/html/minty-blue/decorator-top.vm,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- decorator-top.vm  28 Jul 2004 13:46:03 -  1.4
  +++ decorator-top.vm  2 Sep 2004 17:08:42 -   1.5
  @@ -19,7 +19,7 @@
   
   
   $jetspeed.page.title
  -#set($cssUrls = $renderRequest.getPortletSession().getAttribute("cssUrls"))
  +#set($cssUrls = $renderRequest.getAttribute("cssUrls"))
   #foreach($cssUrl in $cssUrls)
   
   #end
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (JS2-69) Finallizing Portal Navigation using the Profiler

[jetspeed-dev]

The following comment has been added to this issue:

 Author: Scott T Weaver
Created: Thu, 2 Sep 2004 9:37 AM
   Body:
Current status based on http://www.mail-archive.com/[EMAIL PROTECTED]/msg14579.html

Here is what I have done so far:

- Created a CMSish node/document handling api to easily allow us to support documents 
other than .psml.  This will also make transitioning to a CMS backed repository, like 
JCMS much easier.

- Refactored CastorXMLPageManager to just delegated to the new CMSish api.  We can 
probably rename it since the new CMSish api can easily support RDBMS or whatever.

- Added support for folder metadata which current supports the current functionallity: 
node ordering, localization and acl assignment.

- Pages (.psml) now fully support localized metadata

- Added document handler support for .link docuemnts that just link out to an external 
URL.
-
View this comment:
  http://issues.apache.org/jira/browse/JS2-69?page=comments#action_39524

-
View the issue:
  http://issues.apache.org/jira/browse/JS2-69

Here is an overview of the issue:
-
Key: JS2-69
Summary: Finallizing Portal Navigation using the Profiler
   Type: New Feature

 Status: Unassigned
   Priority: Critical

Project: Jetspeed 2
 Components: 
 Profiling/Portal Navigation
   Versions:
 2.0-dev/cvs
 2.0-a1

   Assignee: 
   Reporter: Scott T Weaver

Created: Fri, 4 Jun 2004 8:56 AM
Updated: Thu, 2 Sep 2004 9:37 AM

Description:
We still haven't settled on how we are going to generate navigations in J2.  I have 
some modifications to the Profiler and to the theme logic which may give us some 
direction.  I am bringing this up as I have been privellage to quite a few vendor 
portal demos lately allowing me to see both the good and the bad of multiple 
implementations.

- I would say we replace the getDesktop() with getFolders().  There is really no need 
for a "root" item or Folder per se since we will be leaving this job to the current 
set of profilling rules that have been assigned to the Profiler.  

- Folders will contain any number of pages and/or folders.

- Folder items would be ordered the following way: first by assigned index then by 
alphabetical order.

- Remove defaultPage logic from Folder, the focused Folder item would be set in this 
fashion: set the focus to the last selected child in that Folder then by Folder Item 
ordering algothrim defined above.

- It should be the Profiler's responsibility to preserve a user's active item on a per 
Folder basis.

- A Folder would still posses the defaultTheme capabillity but with the added abillity 
to enforce the defaultTheme on its childern and its childrens' children by overriding 
the theme settings for those items with its own.

- Rendering the contents of the Profiler.getFolders() would be left entirely up to the 
theme (currently called the layout decorator).  Example: a theme could render the 
first 2 levels as tabs and the rest as a hierarchical menu to the left of the layout 
area.

- DO NOT introduce the idea of controls and controllers.  It has been stated before 
that these easily confuse people and I agree 100%.  We need to keep things simple.

I think the first profiling/navgation implementation would be assigning n number of 
roles to a top-level folder.  Then allow the Profiler to aggregate what Folders a user 
has access to by comparing the roles that user is assigned to the ones required the 
Folders required roles (ACL?)  I think this approach is already somewhat in place but 
it just needs some final implementation details.








-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Resolved: (JS2-108) TreeControl taglib caches PortletURLs thereby causing render parameters (of other portlets) to get lost

[jetspeed-dev]

Message:

   The following issue has been resolved as FIXED.

   Resolver: Jeremy Ford
   Date: Thu, 2 Sep 2004 9:14 AM

Tag changed to substitute action urls dynamically during tree render
-
View the issue:
  http://issues.apache.org/jira/browse/JS2-108

Here is an overview of the issue:
-
Key: JS2-108
Summary: TreeControl taglib caches PortletURLs thereby causing render parameters 
(of other portlets) to get lost
   Type: Bug

 Status: Resolved
   Priority: Major
 Resolution: FIXED

Project: Jetspeed 2
 Components: 
 Other
   Fix Fors:
 2.0-dev/cvs
   Versions:
 2.0-dev/cvs

   Assignee: 
   Reporter: Ate Douma

Created: Sun, 15 Aug 2004 2:58 PM
Updated: Thu, 2 Sep 2004 9:14 AM
Environment: WindowsXP SP1, Tomcat 4.1.30, J2SE 1.4.2_04

Description:
The Portlet Application Manager uses the TreeControl taglib for navigation of the 
Application Tree.
On first usage, the TreeControl is filled with Action URLs for each of the tree nodes 
to render.
Because these are thereafter cached, portlet render parameters (which are stored in 
the saved Portlet URL) are frozen to this initialization time.
Selecting a TreeControl node on a page which also contains other portlets therefore 
results in losing any changed render state (parameter s) of those portlets. 
Because by default SesionNavigationalState is used in J2, window and portlet mode do 
carry over, but if PathNavigationState would be used, those settings also would be 
lost.

In general: Portlet URLs may *never* be cached. Saving render parameters in the 
Portlet Session would fix this, but would not be portable according to the JSR-168 
specification (another serious limitation of the spec I think).

Solution: don't cache Portlet URLs in the TreeControl taglib component.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-jetspeed-2/applications/pam/src/java/org/apache/jetspeed/portlets/pam PortletApplicationBrowser.java

[jford]

jford   2004/09/02 09:10:58

  Modified:applications/pam/src/java/org/apache/jetspeed/portlets/pam
PortletApplicationBrowser.java
  Log:
  Do not cache action urls
  
  PR: JIRA #JS2-108
  
  Revision  ChangesPath
  1.6   +7 -14 
jakarta-jetspeed-2/applications/pam/src/java/org/apache/jetspeed/portlets/pam/PortletApplicationBrowser.java
  
  Index: PortletApplicationBrowser.java
  ===
  RCS file: 
/home/cvs/jakarta-jetspeed-2/applications/pam/src/java/org/apache/jetspeed/portlets/pam/PortletApplicationBrowser.java,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- PortletApplicationBrowser.java6 Jul 2004 16:11:25 -   1.5
  +++ PortletApplicationBrowser.java2 Sep 2004 16:10:58 -   1.6
  @@ -27,7 +27,6 @@
   import javax.portlet.PortletContext;
   import javax.portlet.PortletException;
   import javax.portlet.PortletSession;
  -import javax.portlet.PortletURL;
   import javax.portlet.RenderRequest;
   import javax.portlet.RenderResponse;
   
  @@ -48,6 +47,7 @@
*/
   public class PortletApplicationBrowser extends ServletPortlet
   {
  +private static final String PORTLET_URL = "portlet_url";
   private String template;
   private PortletContext context;
   private PortletRegistryComponent registry;
  @@ -73,8 +73,7 @@
   TreeControl control = (TreeControl) 
request.getPortletSession().getAttribute("j2_tree");
   if(control == null)
   {
  -PortletURL actionURL = response.createActionURL();
  - control = buildTree(apps, actionURL);
  + control = buildTree(apps);
request.getPortletSession().setAttribute("j2_tree", control);
   }
   request.setAttribute("j2_tree", control);
  @@ -86,8 +85,6 @@
   
public void processAction(ActionRequest actionRequest, ActionResponse 
actionResponse) throws PortletException, IOException
{
  - System.out.println("PorletApplicationBrowser: processAction()");
  - 
TreeControl control = (TreeControl) 
actionRequest.getPortletSession().getAttribute("j2_tree");
//assert control != null

  @@ -113,30 +110,26 @@
}   
}

  - private TreeControl buildTree(List apps, PortletURL actionURL) {
  - 
  + private TreeControl buildTree(List apps) {

  - actionURL.setParameter(PortletApplicationResources.REQUEST_SELECT_NODE, 
"ROOT-NODE");
TreeControlNode root =
   new TreeControlNode("ROOT-NODE",
   null, "J2_ROOT",
  -actionURL.toString(),
  +PORTLET_URL,
   null, true, "J2_DOMAIN");

TreeControl control = new TreeControl(root);


  - 
actionURL.setParameter(PortletApplicationResources.REQUEST_SELECT_NODE, "APP_ROOT");
TreeControlNode portletApps = 
  - new TreeControlNode("APP-NODE", null, "APP_ROOT", 
actionURL.toString(), null, false, "J2_DOMAIN");
  + new TreeControlNode("APP_ROOT", null, "APP_ROOT", PORTLET_URL, 
null, false, "J2_DOMAIN");
root.addChild(portletApps);

Iterator it = apps.iterator();
   while (it.hasNext())
   {
   MutablePortletApplication pa = (MutablePortletApplication)it.next();
  -actionURL.setParameter(PortletApplicationResources.REQUEST_SELECT_NODE, 
pa.getName());
  -TreeControlNode appNode = new TreeControlNode(pa.getName(), null, 
pa.getName(), actionURL.toString(), null, false, "PA_APP_DOMAIN"  );
  +TreeControlNode appNode = new TreeControlNode(pa.getName(), null, 
pa.getName(), PORTLET_URL, null, false, "PA_APP_DOMAIN"  );
   portletApps.addChild(appNode);
   }

  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (JS2-113) Decouple Profiler from Page Manager component

[jetspeed-dev]

Message:

  A new issue has been created in JIRA.

-
View the issue:
  http://issues.apache.org/jira/browse/JS2-113

Here is an overview of the issue:
-
Key: JS2-113
Summary: Decouple Profiler from Page Manager component
   Type: Improvement

 Status: Unassigned
   Priority: Major

Project: Jetspeed 2
 Components: 
 Components Core

   Assignee: 
   Reporter: David Sean Taylor

Created: Thu, 2 Sep 2004 8:52 AM
Updated: Thu, 2 Sep 2004 8:52 AM

Description:
The Profiler component is packaged in the same jar as the Page Manager component. To 
improve the componentization of the system, the Profiler should exist as its own 
module.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Assigned: (JS2-113) Decouple Profiler from Page Manager component

[jetspeed-dev]

Message:

   The following issue has been re-assigned.

   Assignee: David Sean Taylor (mailto:[EMAIL PROTECTED])
-
View the issue:
  http://issues.apache.org/jira/browse/JS2-113

Here is an overview of the issue:
-
Key: JS2-113
Summary: Decouple Profiler from Page Manager component
   Type: Improvement

 Status: Open
   Priority: Major

Project: Jetspeed 2
 Components: 
 Components Core

   Assignee: David Sean Taylor
   Reporter: David Sean Taylor

Created: Thu, 2 Sep 2004 8:52 AM
Updated: Thu, 2 Sep 2004 8:52 AM

Description:
The Profiler component is packaged in the same jar as the Page Manager component. To 
improve the componentization of the system, the Profiler should exist as its own 
module.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-jetspeed-2/portal/src/webapp/WEB-INF/decorations/layout/html/jetspeed/css styles.css

[taylor]

taylor  2004/09/02 08:40:56

  Modified:portal/src/webapp/WEB-INF/decorations/layout/html/jetspeed/css
styles.css
  Log:
  Patch from Randy Watler to layout/html/jetspeed/css/styles.css that supresses the 
link decoration/colors within the buttons.
  
  CVS: --
  CVS: PR:
  CVS:   If this change addresses a PR in the problem report tracking
  CVS:   database, then enter the PR number(s) here.
  CVS: Obtained from:
  CVS:   If this change has been taken from another system, such as NCSA,
  CVS:   then name the system in this line, otherwise delete it.
  CVS: Submitted by:
  CVS:   If this code has been contributed to Apache by someone else; i.e.,
  CVS:   they sent us a patch or a new module, then include their name/email
  CVS:   address here. If this is your work then delete this line.
  CVS: Reviewed by:
  CVS:   If we are doing pre-commit code reviews and someone else has
  CVS:   reviewed your changes, include their name(s) here.
  CVS:   If you have not had it reviewed then delete this line.
  
  Revision  ChangesPath
  1.11  +11 -0 
jakarta-jetspeed-2/portal/src/webapp/WEB-INF/decorations/layout/html/jetspeed/css/styles.css
  
  Index: styles.css
  ===
  RCS file: 
/home/cvs/jakarta-jetspeed-2/portal/src/webapp/WEB-INF/decorations/layout/html/jetspeed/css/styles.css,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- styles.css2 Sep 2004 00:42:50 -   1.10
  +++ styles.css2 Sep 2004 15:40:56 -   1.11
  @@ -38,9 +38,19 @@
else it will use the text height
**/
height:25px;
  + color:black;
background:url(content/jetspeed/images/tabmiddle_low.gif);
   }

  +.layout-Jetspeed .LTabLow A:link, 
  +.layout-Jetspeed .LTabLow A:visited,
  +.layout-Jetspeed .LTabLow A:hover, 
  +.layout-Jetspeed .LTabLow A:active
  +{
  + color:black;
  + text-decoration: none;
  +}
  +
   .layout-Jetspeed .LTabRightLow
   {
width:10px;
  @@ -56,6 +66,7 @@
   .layout-Jetspeed .LTab
   {
height:25px;
  + color:black;
background:url(content/jetspeed/images/tabmiddle.gif);
   }

  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-jetspeed-2/taglibs/treecontrol/src/java/org/apache/jetspeed/portlets/tags PortletTreeControlTag.java

[jford]

jford   2004/09/02 08:15:33

  Modified:taglibs/treecontrol/src/java/org/apache/jetspeed/portlets/tags
PortletTreeControlTag.java
  Log:
  Added static image names to prevent modification of parent classes.
  
  Revision  ChangesPath
  1.3   +13 -0 
jakarta-jetspeed-2/taglibs/treecontrol/src/java/org/apache/jetspeed/portlets/tags/PortletTreeControlTag.java
  
  Index: PortletTreeControlTag.java
  ===
  RCS file: 
/home/cvs/jakarta-jetspeed-2/taglibs/treecontrol/src/java/org/apache/jetspeed/portlets/tags/PortletTreeControlTag.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- PortletTreeControlTag.java2 Sep 2004 15:13:32 -   1.2
  +++ PortletTreeControlTag.java2 Sep 2004 15:15:33 -   1.3
  @@ -38,6 +38,19 @@
   private static final String PORTLET_REQUEST = "portlet_request";
   private static final String PORTLET_SESSION = "portlet_session";
   
  +/**
  + * The names of tree state images that we need.
  + * 
  + * Copied from parent
  + */
  +static final String IMAGE_HANDLE_DOWN_LAST ="handledownlast.gif";
  +static final String IMAGE_HANDLE_DOWN_MIDDLE =  "handledownmiddle.gif";
  +static final String IMAGE_HANDLE_RIGHT_LAST =   "handlerightlast.gif";
  +static final String IMAGE_HANDLE_RIGHT_MIDDLE = "handlerightmiddle.gif";
  +static final String IMAGE_LINE_LAST =   "linelastnode.gif";
  +static final String IMAGE_LINE_MIDDLE = "linemiddlenode.gif";
  +static final String IMAGE_LINE_VERTICAL =   "linevertical.gif";
  +
   public void setScope(String scope) {
   if (!PORTLET_REQUEST.equals(scope) &&
   !PORTLET_SESSION.equals(scope)
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-jetspeed-2/taglibs/treecontrol/src/java/org/apache/jetspeed/portlets/tags PortletTreeControlTag.java

[jford]

jford   2004/09/02 08:13:32

  Modified:taglibs/treecontrol/src/java/org/apache/jetspeed/portlets/tags
PortletTreeControlTag.java
  Log:
  Override parent's render method to support dynamic creation of portlet urls since 
they cannot be cached by the nodes.
  
  Revision  ChangesPath
  1.2   +226 -0
jakarta-jetspeed-2/taglibs/treecontrol/src/java/org/apache/jetspeed/portlets/tags/PortletTreeControlTag.java
  
  Index: PortletTreeControlTag.java
  ===
  RCS file: 
/home/cvs/jakarta-jetspeed-2/taglibs/treecontrol/src/java/org/apache/jetspeed/portlets/tags/PortletTreeControlTag.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- PortletTreeControlTag.java5 Jul 2004 17:01:18 -   1.1
  +++ PortletTreeControlTag.java2 Sep 2004 15:13:32 -   1.2
  @@ -15,10 +15,19 @@
*/
   package org.apache.jetspeed.portlets.tags;
   
  +import java.io.IOException;
  +import java.net.URLEncoder;
  +
  +import javax.portlet.PortletConfig;
   import javax.portlet.PortletRequest;
  +import javax.portlet.PortletURL;
  +import javax.portlet.RenderResponse;
  +import javax.servlet.http.HttpServletResponse;
   import javax.servlet.jsp.JspException;
  +import javax.servlet.jsp.JspWriter;
   
   import org.apache.webapp.admin.TreeControl;
  +import org.apache.webapp.admin.TreeControlNode;
   import org.apache.webapp.admin.TreeControlTag;
   
   /**
  @@ -67,5 +76,222 @@
   }
  
   return (TreeControl)treeControl;
  +}
  +
  +/**
  + * Render the specified node, as controlled by the specified parameters.
  + *
  + * @param out The JspWriter to which we are writing
  + * @param node The TreeControlNode we are currently
  + *  rendering
  + * @param level The indentation level of this node in the tree
  + * @param width Total displayable width of the tree
  + * @param last Is this the last node in a list?
  + *
  + * @exception IOException if an input/output error occurs
  + */
  +protected void render(JspWriter out, TreeControlNode node,
  +  int level, int width, boolean last)
  +throws IOException {
  +
  +HttpServletResponse response =
  +(HttpServletResponse) pageContext.getResponse();
  +
  +PortletRequest renderRequest = 
(PortletRequest)pageContext.getRequest().getAttribute("javax.portlet.request");
  +RenderResponse renderResponse = 
(RenderResponse)pageContext.getRequest().getAttribute("javax.portlet.response");
  +PortletConfig portletConfig = 
(PortletConfig)pageContext.getRequest().getAttribute("javax.portlet.config");
  +
  +
  +
  +// if the node is root node and the label value is
  +// null, then do not render root node in the tree.
  +
  +if ("ROOT-NODE".equalsIgnoreCase(node.getName()) &&
  +(node.getLabel() == null)) {
  +// Render the children of this node
  +TreeControlNode children[] = node.findChildren();
  +int lastIndex = children.length - 1;
  +int newLevel = level + 1;
  +for (int i = 0; i < children.length; i++) {
  +render(out, children[i], newLevel, width, i == lastIndex);
  +}
  +return;
  +}
  +
  +// Render the beginning of this node
  +out.println("  ");
  +
  +// Create the appropriate number of indents
  +for (int i = 0; i < level; i++) {
  +int levels = level - i;
  +TreeControlNode parent = node;
  +for (int j = 1; j <= levels; j++)
  +parent = parent.getParent();
  +if (parent.isLast())
  +out.print("");
  +else {
  +out.print("");
  +}
  +out.println();
  +}
  +
  +// Render the tree state image for this node
  +
  +// HACK to take into account special characters like = and &
  +// in the node name, could remove this code if encode URL
  +// and later request.getParameter() could deal with = and &
  +// character in parameter values. 
  +String encodedNodeName = URLEncoder.encode(node.getName());
  +
  +String action = replace(getAction(), "${name}", encodedNodeName);
  +
  +
  +String updateTreeAction =
  +replace(getAction(), "tree=${name}", "select=" + encodedNodeName);
  +updateTreeAction =
  +((HttpServletResponse) pageContext.getResponse()).
  +encodeURL(updateTreeAction);
  +
  +out.print("");
  +if ((action != null) && !node.isLeaf()) {
  +out.print("");
  +}
  +out.print("");
  +if ((action != null) && !node.isLeaf())
  +out.print("");
  

Re: Bread Crumb Navigation Portlet

[Virendra Dhapola]

Hi all,
new to this mailing list. I am not sure if this question is appropriate 
for this list. I am just wondering, are there any professional 
websites/portals which are powered by Jetspeed2. I will appreciate your 
inputs.
Thanks
virendra

Jaq Marit wrote:
A bread crumb in the entire portal is not much of use since the portlets,
panes,
and other components are already organized (and can be customized) in such a
way that navigation is already made very convenient. Besides, you can't expect
that all users will have the same profiles/preferences with regards to the
content of their pages.  I guess, this is one of the major distinctions between
a web site (same content for all users) and a portal (customized content for
every user).  

Ifever you need a bread crumb, that should already be associated directly to a
particular portlet.
Just a thought...
Quoting [EMAIL PROTECTED]:
 

Hello Peoples,
we are looking to implement a "bread crumb" (path) style navigation 
portlet within Jetspeed 1.5 (and then Jetspeed 1.6 with the JSR 168 
adapter when available).

...
This feature is quite common for many web sites with a single view.
Does this style of navigation have a general name ?
Has anybody seen or worked on a general approach (or pattern) for this 
type of problem ?

It would seem this type of portlet could be used for many web sites 
requiring a particular kind of navigation.

Comments and thoughts welcome.
   



This message was sent using IMP, the Internet Messaging Program.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 

Re: Bread Crumb Navigation Portlet

[Jaq Marit]

A bread crumb in the entire portal is not much of use since the portlets,
panes,
and other components are already organized (and can be customized) in such a
way that navigation is already made very convenient. Besides, you can't expect
that all users will have the same profiles/preferences with regards to the
content of their pages.  I guess, this is one of the major distinctions between
a web site (same content for all users) and a portal (customized content for
every user).  

Ifever you need a bread crumb, that should already be associated directly to a
particular portlet.

Just a thought...

Quoting [EMAIL PROTECTED]:

> Hello Peoples,
> 
> we are looking to implement a "bread crumb" (path) style navigation 
> portlet within Jetspeed 1.5 (and then Jetspeed 1.6 with the JSR 168 
> adapter when available).
> 
> ...
> 
> This feature is quite common for many web sites with a single view.
> 
> Does this style of navigation have a general name ?
> 
> Has anybody seen or worked on a general approach (or pattern) for this 
> type of problem ?
> 
> It would seem this type of portlet could be used for many web sites 
> requiring a particular kind of navigation.
> 
> Comments and thoughts welcome.



This message was sent using IMP, the Internet Messaging Program.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]