#20 url.case.folding problem

[John Thorhauer]

I have determined that we need to set the
url.case.folding property in the TR.props file to
'none' instead of 'lower'. If it is set to lower it
can cause problems when trying to do exact database
matches based on variables that have been passed as url
paramters.

However, when folding is set to 'none' Tambora has
problems in a couple of areas. Mainly the problem is
in the .vm files and thier corresponding classes on the
storage server where we specify a userID or a companyID
in the url as a parameter.

In these cases the variable needs to be changed to
userid or companyid and the corresponding .getParameter
call in the .java file needs to be changed as well.

Here is a list of files that I think need to be checked:

Storage Server:

storage/templates/screens/admin/company/custompo/CustomPOForm.vm
storage/templates/screens/admin/company/custompo/CustomPOList.vm
storage/templates/screens/admin/company/CompanyCertificateForm.vm
storage/templates/screens/admin/company/CompanyDataOwnerMapSetForm.vm
storage/templates/screens/admin/company/CompanyCreateDataOwnerMap.vm
storage/templates/screens/admin/company/CompanyRuleSetForm.vm
storage/templates/screens/admin/company/CompanyForm.vm
storage/templates/screens/admin/company/CompanyList.vm
storage/templates/screens/admin/user/usercompany/UserCompanyForm.vm
storage/templates/screens/admin/user/usercompany/UserCompanyList.vm
storage/templates/screens/po/record/HistorySummary.vm
storage/templates/screens/po/record/RecordDetail.vm
storage/templates/screens/po/record/RecordSummary.vm
storage/templates/screens/po/POSummary.vm

Transport Server:
transport/templates/screens/po/record/HistorySummary.vm
transport/templates/screens/po/record/RecordDetail.vm
transport/templates/screens/po/record/RecordSummary.vm