Trace: • Configuring Timeouts • Environment Information • Using Styles • Application and Server Zones • What are Life Cycle Objects? • Using Client/Server Properties
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
jvx:common:setup:zones [2018/02/02 10:04] admin created |
jvx:common:setup:zones [2026/04/21 11:23] (current) admin |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ~~NOTRANS~~ | ~~NOTRANS~~ | ||
| - | ~~Title: Application and Server zones~~ | + | ~~Title: Application and Server Zones~~ |
| - | We recommend a specific file-structure for JVx applications because every JVx projects should use the same structure. This makes it easier to maintain applications because everything is standardized. | + | We recommend a specific file structure for JVx applications because every JVx projects should use the same structure. This makes it easier to maintain applications as everything is standardized. |
| Our recommended structure is: | Our recommended structure is: | ||
| Line 31: | Line 31: | ||
| </file> | </file> | ||
| - | The problem with above structure is that you need a lot of directories and the project itself is in the last level. The advantage is that you can manage multiple applications with one server configuration. But usually you havew at least one application. | + | The problem with the above structure is that you need a lot of directories and the project itself is in the last level. The advantage is that you can manage multiple applications with one server configuration. However, usually you have at least one application. |
| We introduced a new search strategy for application and server configuration files. Before JVx 2.1, everything was file based. Every config.xml had to be available as physical file. With 2.1 this is not needed. | We introduced a new search strategy for application and server configuration files. Before JVx 2.1, everything was file based. Every config.xml had to be available as physical file. With 2.1 this is not needed. | ||
| Line 37: | Line 37: | ||
| The new search strategy is as follows. | The new search strategy is as follows. | ||
| - | == Application zone == | + | == Application Zone == |
| <file script> | <file script> | ||
| Line 47: | Line 47: | ||
| 3: JNDI: java:/comp/env/jvx/<appname_lowercase>/config | 3: JNDI: java:/comp/env/jvx/<appname_lowercase>/config | ||
| (String as resource path), InputStream or IVirtualZone implementation) | (String as resource path), InputStream or IVirtualZone implementation) | ||
| - | 4: Classpath: /rad/apps/<appname_lowercase>/config.xml (can be disabled) | + | 4: Classpath: Use system property: -Drad.apps.<appname_lowercase>.config=/path/to/config.xml (must be enabled via system property) |
| - | 5: Classpath: /config.xml (can be disabled) | + | 5: Classpath: /rad/apps/<appname_lowercase>/config.xml (must be enabled via system property) |
| - | 6: EXCEPTION | + | 6: Classpath: /<appname_lowercase>.xml (must be enabled via system property) |
| + | 7: Classpath: /config.xml (must be enabled via system property) | ||
| + | 8: EXCEPTION | ||
| </file> | </file> | ||
| - | == Server zone == | + | == Server Zone == |
| <file script> | <file script> | ||
| Line 62: | Line 64: | ||
| 3: JNDI: java:/comp/env/jvx/server/config | 3: JNDI: java:/comp/env/jvx/server/config | ||
| (String as resource path), InputStream or IVirtualZone implementation) | (String as resource path), InputStream or IVirtualZone implementation) | ||
| - | 4: Classpath: /rad/server/config.xml (can be disabled) | + | 4: Classpath: /rad/server/config.xml (must be enabled via system property) |
| - | 5: Classpath: /server.xml (can be disabled) | + | 5: Classpath: /server.xml (must be enabled via system property) |
| 6: EMPTY configuration | 6: EMPTY configuration | ||
| </file> | </file> | ||
| - | But be careful, because ApplicationZone and ServerZone have methods for accessing files and directories: | + | To enable Classpath search strategy, set the system property: ''-DConfiguration.search.classpath=true'' otherwise it won't work. |
| + | |||
| + | Be careful because ApplicationZone and ServerZone have methods for accessing files and directories: | ||
| <file java> | <file java> | ||