[EMAIL PROTECTED] wrote:
Thanks for your input David!
Well, it seems I have solved the problem already by giving unique IDs to
fragments which is mandatory (but I didn't pay attention at that time).
I think J2 checks in the DB for the fragment ID and must have pulled out
the wrong layout ?
Editing PSML by hand does lead to problems. We're finding its best to
let the system assign them. Once customization is strong enough, we
won't have to rely on editing the XML by hand. This will also encourage
database storage of pages.
A feature which could be needed IMO is a way to better manipulate PSMLs
through Administrative GUI (like cloning) just like in J1...
We're developing a new Site Manager admin portlet that will make use of
the same portlet/clientside framework as the Permission Manager and
Security Constraints admin portlets.
Watch the dev list for commits
Its documented in the profiler guide (above)
"j2" is the default rule. It locates pages by path and name, and also
considers the media type of the request for finding mime type specific
resources. It is only the default for the demo system. You are free to
choose the default profiling rule in your portal. take a look at the
profiler spring configuration, constructor arg #1
Can you confirm that line is what I'm looking for if I want to change the
default profiling rule : profiler.rule.values.default = j2
(from /WEB-INF/conf/jetspeed.properties) ?
Um, no. Thats confusing, sorry. I'll remove that setting
Its actually in WEB-INF/assembly/, constructor-arg #1
<!-- Profiler -->
<bean id="profilerImpl"
class="org.apache.jetspeed.profiler.impl.JetspeedProfilerImpl"
name="profilerImpl" init-method="init">
<constructor-arg index="0">
<value>JETSPEED-INF/ojb/profiler_repository.xml</value>
</constructor-arg>
<constructor-arg index="1">
<value>j2</value>
</constructor-arg>
<constructor-arg index="2">
<ref bean="ProfileResolvers" />
</constructor-arg>
</bean>
Mkay, I just have a couple of questions now :
1) whenever I create a new user, nowhere is mentionned "j2" which is
supposedly the default profile rule. Is it normal that I have to
specifically set it ?
Two different default profiling rules are available:
1. the Profiler Component's default profiling rule, see spring assembly
above. this is system wide. If a user does not have a profile rule
assigned, then the rule configured in the spring assembly above will be
used.
2. the User Administration portlet's default profiling rule. This
preference is *only* applied when creating new users from the User
Administration portlet.
2) don't I just need to clean _user/template/ if I don't want J2 to copy
the (empty) content to _user/myNewUser/ ?
Well, it throws an exception when you do this.
Last time I checked, I thought it was printing an error message in the
User Administration portlet's window. I could be wrong, but it will log
errors. Prefer to more formerly solve this issue, thus the new JIRA issue
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
