AW: (Again) J2 navigation set-up and portlet instances

[Florian Theurich <fl...@x-cell.com>]

Hi Randy,

That's allright, no need to apologize. Just sometimes when you got stuck,
mails sound more desperate than you really are...:-) Thanks for your
comprehensive explanations!!

I'm still having a hard time to completely understand the Jetspeed profiling
stuff and I'm probably going to ask a few more questions the next days. For
now I'd just like to know the following: 

1. When is M4 going to be released? 

2. I can now edit/customize the portlets (when adding the
security-constraint 'public-edit'), but the whole page can be customized as
well. This is something the users should not be allowed to do though. How
can I let users customize portlets but not the entire page?

Thanks again for your help
Cheers

Florian


-----Ursprüngliche Nachricht-----
Von: Randy Watler [mailto:watler@wispertel.net] 
Gesendet: Dienstag, 31. Mai 2005 23:50
An: Jetspeed Users List
Betreff: Re: (Again) J2 navigation set-up and portlet instances

Florian Theurich wrote:

>I posted two questions in the past days but unfortunately I did not receive
>any answers. The mailing list archive helped a lot to clarify some points
>but I am still struggling with different instance of portlets (see previous
>posting copied in below).
>
Sorry, I have been very busy and some of the team are on vacation.

> 
>When I copy a customizable portlet instance (the BookmarkPortlet in this
>case) and paste it into another page's psml file this particular instance
is
>no longer customizable.
>
This is probably due to the portlet.xml setting or access security in 
the pages.

>As I can't find any references in the database I assume that it must have
to
>do with the page the portlet resides in. Is it because the one page
(without
>customization) is the default-page.psml accessible by everyone whereas the
>other page (p004.psml) is accessible by user 'user' only?
>
Yes, look at the <security-constraints> tags in the pages, folders, or 
/page.security. See the website for more general info.

>I do not want any breadcrumbs that allow users to go back to the parent
>folder, I'd rather want a two level structure (completely visible
regardless
>of where you are) as displayed below
>  
>
This will be more easily done in M4. See: 
http://people.apache.org/~rwatler/portal-navigations-component.html

In the interim, you can hard code the menus you want in the 
decorator-top.vm files or utilize DocumentSets. DocumentSets will be 
deprecated in M4, but should more or less be convertable to the proposed 
<menu> tags.

>The navigation should look different dependent on the group (accounting,
>sales, hr) the user belongs to. I guess I need to adapt the Velocity
>decorator macros to achieve that but how must the folder/page structure
look
>like for such an scenario? Do I have to set up a custom Profiling Rule?
>  
>
Yes, this is an obvious use case for the Profiler. You may or may not 
need to define your own rules: J2 comes with several that work for most 
cases. I can certainly help you if you get stuck, but take a long look 
at the examples and the group-fallback rule. BTW, groups and roles are 
symmetric within the Profiler itself, so role use cases work 
identically, (i.e. role-fallback rule based profiling).

>
>1) Is it important how the instances are actually named or in other words
>what is the specific meaning of for instance dp-4
>
The various ids can be anything, but they are used to identify unique 
pages, fragments, and cached portlet definitions in the DB... consider 
them OIDs. The individual portlets, fragments, and pages are considered 
unique, even if they ultimately reference the same portlet definitions.

>2) I found the 'Bookmark' portlet on four different pages (or let's say in
>four different PSML files). Two different instances are referenced but the
>remaining settings in the PSML are the same for all instances. On one page
i
>see the little pencil in the upper right corner whereas on the other you do
>not have the possibility to customize. So where can I define whether a
>particular instance of a portlet should display 'edit' and 'help' icons or
>not? 
>
This is done within the portlet.xml supported modes and is refined using 
security settings for view and/or edit permissions.

>3)  In the portlet.xml I can define for example the edit page for a
>particular portlet. but where can I define which pages should be displayed
>for the different instances of this portlet (edit_A.jsp for instance A, and
>edit_B.jsp for instance B)?
>  
>
AFAIK, you need two portlet definitions that use the same portlet class. 
Once you have that in place, you can use init params, preferences, etc. 
There have also been some relatively new ideas for parameterization of 
portlet.xml, but I am not sure where it stands at the moment. Perhaps 
Ate or David can shed more light here, (I am not exactly a portlet 
expert, but I do work on the portal itself :-)).

HTH,

Randy



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org





---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org

Re: AW: (Again) J2 navigation set-up and portlet instances

[Randy Watler <wa...@wispertel.net>]

Florian,

Florian Theurich wrote:

>1. When is M4 going to be released?
>
I think Ate gave a fair answer to this question... :-).

> 
>
>2. I can now edit/customize the portlets (when adding the
>security-constraint 'public-edit'), but the whole page can be customized as
>well. This is something the users should not be allowed to do though. How
>can I let users customize portlets but not the entire page?
>  
>
IIRC, you need to use one of the "NoActions" Layout portlets: <fragment 
... name="jetspeed-layouts::VelocityTwoColumnNoActions"/>

HTH,

Randy



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org