logo       

Re: Using ServerConfigurationService.getPortalUrl and site URLs?: msg#00749

cms.sakai.devel

Subject: Re: Using ServerConfigurationService.getPortalUrl and site URLs?

That is the right way. And the system is doing just what you asked it to do. If you want /mercury to be your portal URL base, change your sakai.properties. The default is:

portalPath=/portal

The actually code for getPortalUrl is:

return getServerUrl() + (String) m_properties.get("portalPath");

Trust the configuration service!

- Glenn

Glenn R. Golden
Software Architect, University Of Michigan
ggolden@xxxxxxxxx



On Apr 28, 2006, at 12:30 PM, Zeckoski, Aaron wrote:

This does not seem to actually return the portal URL correctly. It seems
to return ServerConfigurationService.getServerUrl() + "/portal" which
does not work correctly in the mercury portal.

I suspect I am doing something wrong but that's nothing new.

The goal here is to get the URL to a site or a tool within a site. All
the examples I have been able to find seem to generate a URL which has
things hardcoded into it (like "/portal/" or "/tool/").

What is the right way to generate the URL to a site or a tool within a
site?
-AZ

--
Aaron Zeckoski (aaronz@xxxxxx)
Lead Developer - Learning Technologies - Virginia Tech

----------------------
This automatic notification message was sent by Sakai Collab (http://collab.sakaiproject.org/portal) from the DG: Development site.
You can modify how you receive notifications at My Workspace > Preferences.


[see attachment: "message0.html", size: 6124 bytes]


Attachments:

message0.html
http://collab.sakaiproject.org/access/content/attachment/a28f4e8a-3d8c-4614-00f3-7c9b977684f4/message0.html

----------------------
This automatic notification message was sent by Sakai Collab
(http://collab.sakaiproject.org/portal) from the DG: Development site.
You can modify how you receive notifications at My Workspace > Preferences.




<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise