-
1. Re: So confused, portal's not making any sense.
meetoblivion Jan 20, 2009 10:29 PM (in response to meetoblivion)just noticed something.
if i go here:
http://localhost:8080/auth/portal/jimmy
it works fine. But I really want http://localhost:8080/jimmy to work, since this portal in particular will not require any auth. -
2. Re: So confused, portal's not making any sense.
meetoblivion Jan 21, 2009 9:28 PM (in response to meetoblivion)No one at all? That's sort of disappointing.
-
3. Re: So confused, portal's not making any sense.
prabhat.jha Jan 21, 2009 11:14 PM (in response to meetoblivion)This is a community forum and people are going to respond when they have time. Have you gone through the document first?
See the customizing portal section in reference guide on what you need to do access http://host:port/your_portal instead of http://host:port/portal/your_portal -
4. Re: So confused, portal's not making any sense.
meetoblivion Jan 21, 2009 11:33 PM (in response to meetoblivion)prabhat
If you read my original post, you would see that I am not attempting to turn /portal/myportal into /myportal (which I already know I need to change the context setting in jboss-web.xml; I have already done this and the results are consistent with the rest of my findings). Yes, I have already been through all of the documents.
My issue is that the urls /portal/myportal do not work at all. When I visit them they always render as default; which seems to imply to me that it's not trying to direct to my portal instead the default portal. the results seem consistent in that if i change the theme on default, these urls show the new theme. as i pointed out, I can find my portal by going to /portal/auth/portal/myportal which implies that it's always going through the auth bracket, even when logged out (in fact, in "my portal" i do not require auth yet when i go to myportal it brings me to the login screen as if it's trying to render my default portal, which does in fact require login.
If there is another channel where I should send presales support requests to, for periods during product trials, I'd be happy to hear about it.
Thanks. -
5. Re: So confused, portal's not making any sense.
prabhat.jha Jan 21, 2009 11:53 PM (in response to meetoblivion)This I tried on 2.7.1.GA.
I created a new portal called "prabhat" using admin ui. Saw the default security was view-recursive and personalize-recursive for "role unchecked". I made "prabhat" portal the default portal. I signed out as admin.
I am taken to the page http://host:8080/portal/portal/prabhat. As you can see there is no "auth" in url and I was able to access it without logging in.
I am too tired to dig more but this is a very common use case. -
6. Re: So confused, portal's not making any sense.
meetoblivion Jan 22, 2009 7:52 AM (in response to meetoblivion)I agree it's common. Maybe I'm misunderstanding the documentation then, because it implies that I should not need the second portal.
Based on what I see here, from the reference manual.
http://docs.jboss.com/jbportal/v2.7.1/referenceGuide/html/urls.html
In 7.2 accessing a portal
The default portal is used when no portal is specified. How selection is done:
* /portal/ points to the default page of the default portal.
* /portal/portal-name/ points to the default page of the portal-name portal.
Which implies that when I start up my container from scratch, without changing the context path, I should be able to go to
http://localhost:8080/portal and get the default.
In addition, the documentation seems to say if I go to http://localhost:8080/portal/jimmy i should be taken to the jimmy portal. I can accept if you're going to say "no" but maybe the documentation should be clearer? -
7. Re: So confused, portal's not making any sense.
peterj Jan 22, 2009 12:07 PM (in response to meetoblivion)The whole "why do I need 'portal' twice in my URL?" question was discussed in detail in a topic some time ago. Unfortunately I can't seem to find it - using 'portal' as a search keyword is useless ;-)
Anyway, if I recall correctly, the first 'portal' gets you into the portal container. The second 'portal' distinguishes the request between one for a portal page and something from the CMS ('/portla' vs '/content')
If you really want to let you users use http://hostname:8080/jimmy, then create a jimmy.war containing an index.jsp that redirects to /portal/portal/jimmy. That's what I did for my portal. -
8. Re: So confused, portal's not making any sense.
meetoblivion Jan 22, 2009 9:28 PM (in response to meetoblivion)actually i was thinking about it, i could probably use tuckey's url rewriting to do it. especially considering what it'll take given our environment (mind you, jimmy's just "one" of many I can identify)