Trace:
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
visionx:faq_tech [2021/07/01 07:29] admin |
visionx:faq_tech [2021/09/03 07:18] admin [WAR creation shows compiler errors!] |
||
|---|---|---|---|
| Line 47: | Line 47: | ||
| ==== Out of memory in VisionX ==== | ==== Out of memory in VisionX ==== | ||
| - | If you get an Out of memory exception or a Java heap space problem, simply increase the memory of VisionX in visionx.bat or visionx.sh: | + | If you get an **Out of memory** or a **Java heap space** error, simply increase the memory of VisionX in visionx.bat or visionx.sh: |
| <code> | <code> | ||
| Line 58: | Line 58: | ||
| ==== Additional JVM start parameters ==== | ==== Additional JVM start parameters ==== | ||
| - | On Windows, VisionX is usually started with visionx.exe. To define additional JVM parameters, however, visionx.bat must be used, as any JVM parameters can be set with it, e.g .: | + | On Windows, VisionX is usually started with visionx.exe. To define additional JVM parameters, however, visionx.bat or visionx.sh must be used, as any JVM parameters can be set with it, e.g .: |
| <code> | <code> | ||
| Line 73: | Line 73: | ||
| -Dfile.encoding=UTF-8 | -Dfile.encoding=UTF-8 | ||
| </code> | </code> | ||
| + | |||
| + | ==== How to start VisionX with de_CH language settings ==== | ||
| + | |||
| + | Simply change the start script (visionx.bat, visionx.sh) and add your language settings: | ||
| + | |||
| + | <code> | ||
| + | -Duser.country=CH -Duser.language=de_CH -Dtomcat.arguments=-Duser.country=CH;-Duser.language=de_CH | ||
| + | </code> | ||
| + | |||
| + | Full script: | ||
| + | <file dos visionx_de_CH.bat> | ||
| + | @ECHO OFF | ||
| + | .\runtime\bin\java -Duser.country=CH -Duser.language=de_CH -Dtomcat.arguments=-Duser.country=CH;-Duser.language=de_CH -Xmx512M --add-opens=java.base/jdk.internal.loader=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED -jar lib\visionxloader.jar | ||
| + | </file> | ||
| + | |||
| + | If you use Windows and start VisionX with visionx.exe, it's also possible to create a file with the name visionx.l4j.ini: | ||
| + | <file ini visionx.l4j.ini> | ||
| + | -Duser.country=CH | ||
| + | -Duser.language=de_CH | ||
| + | -Dtomcat.arguments=-Duser.country=CH;-Duser.language=de_CH | ||
| + | </file> | ||
| + | |||
| + | ==== WAR creation shows compiler errors! ==== | ||
| + | |||
| + | Usually such problems occur if you do manual coding with an IDE. To find out what's the compiler error, simply enable logging and add the line | ||
| + | |||
| + | com.sibvisions.visionx.server.ant.AntRunner.level = ALL | ||
| + | | ||
| + | to the file **''<visionx>/lib/logging.properties''**. Read more information about [[visionx:visionx_logging|VisionX logging]]. | ||
| + | |||
| + | To see the output, start visionx with ''visionx.bat''. All problems will be shown in the console. | ||
| + | |||
| + | Another option is to start the WAR creation manually, in your IDE, with included ANT build file: **build.xml**. Every application contains this build file. | ||
| + | The ''start.complete'' task will create the WAR file. | ||