Configure SecurityManager in Tomcat

Since JTalks is an open source project and can be run by anyone and everywhere, we need to be ready to work in environment with SecurityManager set. Usually hostings run their Tomcat instances (especially the shared ones) with the SecurityManager. That's why we need to make sure JTalks can cope with it, so:

• Configure SecurityManager in local Tomcat instance where JCommune runs. If the application fails after setting the SecurityManager, create a bug for 0.6 and link it to this task. It's possible that application fails due to misceleneous security violations like accessing class members with access modifier less than it's allowed (e.g. accessing private method by

  Method#setAccessible(true)

  ; or having hibernate mappings with field access instead of property access; or accessing file system without the proper configuration; etc.

• If/when nothing fails, configure SecurityManager in Tomcat where JCommune runs at jtalks.org.