In answer to you questions, I am not sure how the Group attribute on categories was originally supposed to work. You assessment of how it should work seems plausible to me, but unfortunately, that is not how it works currently. I believe that David Sean Taylor helped with the category implementation and may have more insight.
When I wrote the portlet browsing filter functionality, I intentionally set it up to work this way. The reason is that is the way the customizer's category filter has worked in the past. I did not want to change the behavior of the customizer filter and did not want to have a filter that did not work the same way in the portlet browser.
If you wish to change it, I would suggest doing the following (off the top of my head). Add a new filterPortlets method to the PortletFilter that takes a user as a parameter. Change both CustomizerSetAction and PortletBrowserAction to make use of this.
If you do make any changes and wish to seem them incorporated into Jetspeed, please create a bug/enhancement report in JIRA (http://nagoya.apache.org/jira) and add a patch file with you changes.
Thanks.
Jeremy Ford. [EMAIL PROTECTED]
From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: PortletBrowseAction.java Date: Fri, 4 Jun 2004 13:47:51 -0400
Mr. Ford:
I'm a devloper working with Jetspeed, and I'm curious about an implementation issue with PortletBrowseAction.java. I've been attempting to configure my copy of Jetspeed as follows: I have a series of portlets who are defined in the portlet registry with a category entry of <category group="Unity">Unity</category> or <category group="Unity">Unity.admin</category>. However, when I try to filter for portlets in the "Unity" or "Unity.admin" categories, I don't get any results back.
I traced the issue, and discovered that in PortletBrowseAction, it eventually calls PortletFilter.isFilteredIn, which calls BasePortletEntry.hasCategory with one-argument. This version of the hasCategory method calls the two-argument version with a default group of "Jetspeed". So, the end result is that you can't set a different group name on any portlets and have the category filter work.
I thought that the group attribute of the category element corresponded to the Group attribute of a user, so that you would filter and only see portlets that you had group access to. Is this how it's supposed to work?
I've been looking at how to change this, but I'm pretty new to Jetspeed internals, so I can't see the correct approach. I think it should probably try the two-argument hasCategory method for every group a user is in, but I don't see how to get the group information from the JetspeedUser object at the time the filtering is done. Do you have any thoughts on this?
I apologize if this is the wrong way to go about discussing this.
Dan Price
_________________________________________________________________ Check out the coupons and bargains on MSN Offers! http://youroffers.msn.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
