Frank,
I am not looking at the J2 source at the moment, so the comments below may be a slight bit off... they are close in any case :)
Frank Villarreal wrote:
generalized profile type used to navigate to a specified path while profiling, typically used to profile on multiple attributes at once, (i.e. role and group)Here's another question(s):
what do the following rule criterion request types signify?
1) navigation
profile one of user, role, or group, (user is almost always defined and normally is chosen).2) group.user.role
3) path.session
appends the request path to the profiling path
4) request.session
appends the request path or request parameter path
I am not sure how to best accomplish this. You may have to write a new rule to pull request attributes. There may be an easier way to do this outside of the Profiler... something like a filter that converts the request attribute to a request parameter that you can use with the existing profiler rules.
Thanks,
Frank
-----Original Message----- From: Frank Villarreal [mailto:[EMAIL PROTECTED] Sent: Friday, April 08, 2005 08:53 AM To: Jetspeed Users List Subject: J2M2 Profiling Rules
Hello all,
I'm trying to set-up a profiling rule in J2-M2 that does the following:
1) routes guest (anonymous) users to a specific subsite based on their host header (the IP/url of their requested site).
Role and media type is a simple combination of the role fallback and j1 rules... try your hand at defining a new profiler rule by extending the role-fallback rule by adding the media type rule at the end.
once logged in ...
2) routes them to a page based on their role / mediatype
Send along your attempt. It is probably just a simple tweek to what you have that will get it to work.
I've tried the "role-group" profiling rule and it works great for simple role-based page selection. However, when I try to combine that with "_mediatype" selection ... doesn't work. Or at least I don't know how to make it work.
As stated above, the user always defined.... thus group.user.role always defaults to the user setting. I am not sure this rule is named the best.
I also noticed the "j1" rule which supports mediatype page selection. However, that rule contains a criterion named "group.user.role" which when set to "role" appears to have no effect ... the page selector still attempts to default to "user" based page selection. Am I missing something or is this by design? If so, is there a way around it?
- Frank
--------------------------------------------------------------------- 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]