Trace: • Database Connection via JNDI • User-Defined Session Manager and Object Provider • Password Policy Integration
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
jvx:server:security:server_jndi [2020/06/15 11:08] cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation) |
jvx:server:security:server_jndi [2020/06/25 10:47] (current) cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation) |
||
|---|---|---|---|
| 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 as well 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! |