[4suite-dev] Aliases in the repository

[Michael Olson]

Todays effort started off as working on the bug Uche found with  
DefaultXslt and aliases.  It turned into implementing the new alias  
traversal scheme that we have talked about.  The changes are many but  
for the most part unobtrusive.

The stem from now being able to add that URI parameters ";traverse" and  
";no-traverse" to a repo path.  The meanings I hope are self  
explainitory.

 From this, all of the SCore and CCore interfaces that took a  
"traverseAliases" were no longer needed.  If "traverseAlises" is  
specified, a Depricated error is raised (but the code will still work).  
  Example, fetchResource, deleteResource, the XSLT extension element  
DeleteResourceElement.

Once this work was done I got all of the Server test harnesses working  
again.

Then, I went on to alot of the other alias related bugs including:

* 4ss fetch container now properly displays aliases
* dashboard now knows how to properly display and manage alaises
* from the command line, you can now specify URL params (ie 4ss fetch  
resource /;metadata or 4ss fetch document /some/alias;no-traverse) and  
get back the correct results (remember UNIX command line escaping)
* params are now supported in the Http server (the original bug).   So,  
if we assume there is an alias in / called "/foo.alias" which  
references "/foo" and XML document.  Then

   http://localhost/foo.alias  will resolve to the XML document, and all  
Rules, defaults, etc will be based on the XML Document.
    http://localhost/foo.alias;no-traverse will resolve to the alias and  
all Rules, defaulf, etc will be based on the Alias.
   http://localhost/foo.alias;no-traverse;metadata will resolve to the  
metadata of the alias and all Rules, defaults, etc will be based on the  
MetaData


   I've run all of the test harnesses, dashboard, and most of the demos  
and all seems to be working well.

   So let me know what I broke :)

Mike


------------------------------------------------------------------------ 
-----------------
Mike Olson                                                Principal  
Consultant
mike.olson at fourthought.com                +1 303 583 9900
Fourthought, Inc.                                       
http://Fourthought.com
PO Box 270590,                                       http://4Suite.org
Louisville, CO 80027-5009, USA
XML strategy, XML tools, knowledge management