On Sep 2, 2009, at 10:15 AM, David Just wrote:
If you could point me in the right direction on how I would go about
defining and using said Profiling rule that would be a great help.
Profiling rules are defined either using the administrative portlet,
programmatically, or with the Jetspeeed seed data as a part of your
initial build. I prefer the seed approach, as I rarely change
profiling rules once configured. Take a look at the j2-seed.xml:
<ProfilingRule id="user-role-fallback" standardRule="false">
<description value="A role based fallback algorithm based on
Jetspeed-1 role-based fallback"/>
<Criteria>
<Criterion name="user">
<type value="user"/>
<fallBackOrder value="0"/>
<fallBackType value="2"/>
</Criterion>
<Criterion name="navigation">
<type value="navigation"/>
<value value="/"/>
<fallBackOrder value="1"/>
<fallBackType value="2"/>
</Criterion>
<Criterion name="role">
<type value="role"/>
<fallBackOrder value="2"/>
<fallBackType value="2"/>
</Criterion>
<Criterion name="page">
<type value="path.session"/>
<value value="default-page"/>
<fallBackOrder value="3"/>
<fallBackType value="1"/>
</Criterion>
</Criteria>
</ProfilingRule>
I could describe how rules work here, but its already been explained
here:
http://portals.apache.org/jetspeed-2/devguide/guide-profiler.html
Rules are associated with users in the seed data:
<User name="user">
<credentials password="user" enabled="TRUE"
requiresUpdate="FALSE"/>
<roles>user</roles>
<groups>marketing</groups>
<preferences/>
<userinfo/>
<Rules>
<Rule locator="menu" rule="role-group"/>
<Rule locator="page" rule="j2"/>
</Rules>
</User>
or you can default to the system wide default rule defined in the
profiler.xml (2nd parameter) Profiler component bean definition
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
