Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
jvx:server:security:server_jndi [2018/02/02 08:25] admin |
jvx:server:security:server_jndi [2020/06/25 10:47] (current) cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ~~Title: Addressing the Server via JNDI~~ | ~~Title: Addressing the Server via JNDI~~ | ||
| - | The server for JVx clients is instantiated either at the current JVM or at the application server (e.g. Tomcat, JBoss). In the current VM the call | + | The server for JVx clients is instantiated either at the current JVM or at the application server (e.g., Tomcat, JBoss). In the current VM, the call |
| <file java> | <file java> | ||
| Line 13: | Line 13: | ||
| </file> | </file> | ||
| - | In doing so we additionally attempt to address a server instance via JNDI | + | In doing so, we additionally attempt to address a server instance via JNDI. |
| A new instance of the server is created at the application server using ServletServer. This is accomplished by the following call: | A new instance of the server is created at the application server using ServletServer. This is accomplished by the following call: | ||
| Line 93: | Line 93: | ||
| **<fs 20px>Note</fs>** | **<fs 20px>Note</fs>** | ||
| - | If the server is configured globally, we also have to provide all of the application data, such as the rad directory, .class files, etc., globally, since the applications class loader is not used! | + | If the server is configured globally, we have to provide all of the application data -- such as the rad directory, .class files, etc. -- also globally since the applications class loader is not used! |