| Knowledgebase Home | Contact |
 Search the Knowledgebase |
 Jump to ID |
 Browse by Category |
| What classloaders are involved with an Audium installation? | ||||||||||||
| Categories: Audium OpenSDK | ||||||||||||
This article describes the various classloaders that relate to an Audium installation. SYMPTOMS Developer would like to know which classloaders are related to an Audium installation. RESOLUTION Here is a quick description of the classloaders that are involved in a typical Audium installation. Note that there is nothing a developer can do to change this as it is specified in Java and the application servers. This following list is in the order of creation (each one being the parent classloader of the one that follows): 1) The JVM has its own classloader or classloaders. 2) The application server has its own classloader or classloaders. This is, for example, where Apache Tomcat loads from its common folder. 3) Each web application has its own classloader. The Audium Server, since it is a web application, therefore gets its own classloader. 4) Audium itself creates a new classloader and loads from its common folder. 5) Audium creates a separate classloader for each Audium application. This loads the java/application content. This is the classloader that will be used by developers when they write custom code for Audium. |
Print this page
Post a comment
| Visitor Comments |
| No visitor comments posted. Post a comment |
| Related Questions |
| Attachments |
| No attachments were found. |