[Building Sakai] The Mercury site

[Berg, Alan]

Hi,

I understand the java doc, but is the mercury site being used by developer on this list.

Alan

Alan Berg
QA Director - The Sakai Foundation

Senior Developer / Quality Assurance
Group Education and Research Services
Central Computer Services
University of Amsterdam

http://home.uva.nl/a.m.berg




-----Original Message-----
From: Matthew Buckett [mailto:matthew.buckett at oucs.ox.ac.uk]
Sent: Fri 5/21/2010 15:06
To: Berg, Alan
Cc: sakai-dev at collab.sakaiproject.org
Subject: Re: [Building Sakai] The Mercury site
 
On 21 May 2010 13:36, Berg, Alan <A.M.Berg at uva.nl> wrote:
> Hi all,
>
> I was double checking 2.7.x before going to RC. It occurred to me that I
> could not see a real purpose for the mercury site either in the demo or on
> the QA servers. If there is no reason I  would suggest removing the site
> totally, not for 2.7 as it is late in the game but for 2.7.1. Does this make
> sense to you or has the site value?

My guess is that the mercury site was there to support the mercury
portal. The JavaDoc for the mercury portal says:

Mercury is the Sakai developers portal. It can be used while
developing a new Sakai application to invoke the tool in the way that
the tool will be invoked by any of the Sakai navigation / portal
technologies. Mercury is easier to use in development because you
don't have to setup a Site or build SuperStructure to test your
application.

Mercury supports a few URL patterns, but those give you the ability to:

login to Sakai
see all registered tools
visit any tool complete with context and placement
Mercury is configured to be packaged into the "mercury.war" web
application, so it can be visited with the /mercury URL.

To login, use the /mercury/login URL.

To visit any registered tool, use the URL pattern:
/mercury/TOOL-ID/CONTEXT/path-for-tool
where TOOL_ID is the tool's well known registered tool id (such as
'sakai.chat'), and CONTEXT is the tool context string.
A placement will be created for each tool in the context as needed,
and will be tracked for the duration of the server run.

-- 
  Matthew Buckett
  VLE Developer, LTG, Oxford University Computing Services

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20100521/baac7838/attachment.html