logo       

RE: site URLs?: msg#00759

cms.sakai.devel

Subject: RE: site URLs?

That makes sense. I will stick with making it up using the same rules
that are used in the sakaisite.jws file for now.

-AZ

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

> -----Original Message-----
> From: Charles Severance [mailto:csev@xxxxxxxxx]
> Sent: Friday, April 28, 2006 2:50 PM
> To: sakai-dev sakai-dev
> Cc: Glenn Golden; Zeckoski, Aaron
> Subject: Re: site URLs?
>
> Aaron,
>
> You might take a look at SakaiSite.jws - It has code (borrowed from
> Charon) that knows the rules and makes the URLs.
>
> Mebbe we should extract this code into a separate place.
>
> Understand that in terms of "abstraction" the URL convention is
> enforced by the portal code - if we were to build a new portal it
> might come up with a different URL convention.
>
> Any code that does URL mapping needs to know that it is not so
> permanent.
>
> /Chuck
>
> On Apr 28, 2006, at 2:08 PM, Zeckoski, Aaron wrote:
>
> > Ahhh... I get it. That makes sense.
> >
> > How about getting the URL to a site or a tool?
> >
> > 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 (without hardcoding text)? (or is there one?)
> >
> > -AZ
> >
> > --
> > Aaron Zeckoski (aaronz@xxxxxx)
> > Lead Developer - Learning Technologies - Virginia Tech
> > ________________________________________
> > From: Glenn R. Golden [mailto:ggolden@xxxxxxxxx]
> > Sent: Friday, April 28, 2006 2:03 PM
> > To: Zeckoski, Aaron
> > Cc: sakai-dev
> > 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.
> >
> >
> > ----------------------
> > 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.
> >
> >
> >

----------------------
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