[Treebase-devel] Introducing JNDI parameters: PurlBase and SiteUrl

[Vladimir G. <vga...@ne...>]

As of rev 664, treebase-web.war expects two more parameters to be  
supplied by Tomcat via JNDI:
     tb2/BasePurl - is now used instead of a parameter that used to be  
in treebase.properties
     tb2/SiteUrl - as requested earlier today, to be used to implement  
redirects to phylowidget.org

Anyone who runs their own instance, should add these parameters into  
their src/main/webapp/META-INF/context.xml.example or $CATALINA_HOME/ 
cong/Catalina/localhost/treebase-web.xml, see src/main/webapp/META-INF/ 
context.xml.example for an example.

Regarding the PURLs, you should also go to www.purl.org, register a  
new PURL that redirects to your server, and put this PURL into tb2/ 
BasePurl in your Tomcat config.  This configuration only works with a  
Treebase server that is addressable from the outside world, i.e. it  
does not work from a personal developer server that runs at localhost  
(unless you run your own PURL service at localhost, I guess...).   
Alternatively, if the developer does not care about proper functioning  
of PURLs, he can use tb2/BasePurl=http://localhost:8080/treebase-web/phylows/

Here are the values of tb2/BasePurl that are will be used on the  
instances at NESCent:
production:  http://purl.org/phylo/treebase/phylows/
staging:   http://purl.org/phylo/treebase/stage/phylows/
development:  http://purl.org/phylo/treebase/dev/phylows/

So far, we have deployed this version (664) on *development* only.

Finally, I have changed several JSP pages that had "http://purl.org/phylo/treebase/phylows 
...."  urls hardwired so that they instead look up the tb2/PurlBase  
parameter.  However, I used <%= ... %>, so someone more knowledgeable  
might want to adjust that syntax.

--Vladimir