Hi folks,
I was able to track this down to a few lines in the
JetspeedProfilerService class. Apparently, this only supports role
merging for the default.psml page.
Here is the change I made, which allows role merging for pages other
than default.psml. I'm not sure how to go about submitting this, or
even whether the jetspeed 1.5 codebase is still under development.
$ diff JetspeedProfilerService.java
jetspeed-1.5/src/java/org/apache/jetspeed/services/profiler/JetspeedProfilerService.java
381,386c381
< String page = data.getParameters().getString(
Profiler.PARAM_PAGE );
< //String page = rundata.getParameters.get("page");
< if (page == null || "".equals(page) ) {
< page = this.resourceDefault + this.resourceExt;
< }
< locator.setName(page);
---
> locator.setName(this.resourceDefault +
this.resourceExt);
Also, please not that I tested this, but might have missed some larger
ramification of this change.
Dan
PS To answer my own question below, the
services.Profiler.newuser.template isn't checked when a new user is
added via the db and logs in. Not sure when it is.
--- Dan Moore <[EMAIL PROTECTED]> wrote:
> Hi folks,
>
> I have a portal which has two pages.
> default.psml
> and
> instruments.psml
>
> I have two requirements of these pages.
> 1. They have to start off from a common template
> and
> 2. They must be customizable.
>
> I've thought about using the services.Profiler.newuser.template
> property, but we're not goint to be adding users via Jetspeed's
> interface (too many of them). Will this property work without using
> the user admin piece of jetspeed? Looking at the code, I'm not sure.
>
> Anyway, I think I have #1 taken care of--I'm setting
>
> services.Profiler.rolemerge=true
> services.Profiler.rolefallback=true
>
> and using the OneColumn controller and ClearPortletControl control
> (since I can guarentee that users will only have one role). If
> there's
> a better way to do this, I'd love to hear it.
>
> So for a first time user, neither of these pages exist under
> WEB-INF/psml/user. When I customize the default.psml page, it gets
> written to that directory. However, the instrument.psml page does
> not.
> There are two scenarios. When I navigate to the instrument.psml
> page
> via a forward like this:
> <forward name="ins">
> <page name="instruments" role="user">
> </forward>
> I end up editing the role page for the user role; thus, changes to
> this
> psml get propagated to other users. Not what I want.
>
> When I navigate via this forward:
> <forward name="ins">
> <page name="instruments" user="turbine">
> </forward>
> I end up editing default.psml for the turbine user, not
> instruments.psml.
> Even when I edit the url to be
> teleportal/portal/media-type/html/page/instruments.psml/user/turbine
> when I look at the URL for the customizer, I see default.psml as the
> page.
>
> I've looked at
> http://portals.apache.org/jetspeed-1/config_guide.html
> and
> http://portals.apache.org/jetspeed-1/forwards.html
> but couldn't see anything helpful.
>
> Also, I've looked through the mailing list. This message
>
(http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgId=1854321)
> seems to help a bit. But no one seems to have the problem I'm
> having.
>
> I'm using Jetspeed 1.5 with the file based PSML service. Nothing
> really of interest in the WEB-INF/log directory that I can see.
>
> Thanks for your time.
> Dan
>
> ---------------------------------------------------------------------
> 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]
