rife2/rife2-hello
rife2/rife2-hello
2
0
Fork 0
mirror of https://github.com/ethauvin/rife2-hello.git synced 2025-04-25 15:37:10 -07:00
Code Activity

Readme updates

Browse source
This commit is contained in:
Geert Bevin 2023-02-13 17:44:44 -05:00
parent 9f0992d9da
commit 0d30132de7
1 changed files with 16 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

19
README.md
View file

@ -44,8 +44,21 @@ The resulting archive will be in:
If you use any of the byte-code instrumented features , like continuations,
metadata merging or lazy-loaded database entities, you'll need to launch your
servlet container with the `-javaagent:[path-to]/rife2-*-agent.jar` argument.
Exactly how is dependent on each servlet container.
servlet container with the `-javaagent:[path-to]/rife2-[version]-agent.jar`
argument. Exactly how is dependent on each servlet container.
For example, for Apache Tomcat this is typically done by customizing the
`CATALINA_OPTS` environment variable, for instance:
```shell
CATALINA_OPTS="-javaagent:[path-to]/rife2-[version]-agent.jar" ./bin/catalina.sh run
```
For Jetty, it could just be an argument of the `java` call:
```shell
java -javaagent:[path-to]/rife2-[version]-agent.jar -jar $JETTY_HOME/start.jar
```
## Making an UberJar
@ -66,7 +79,7 @@ If you use any of the byte-code instrumented features, you'll need to also tell
For example:
```bash
java -javaagent:[path-to]/rife2-*-agent.jar -jar app/build/libs/hello-uber-1.0.jar
java -javaagent:[path-to]/rife2-[version]-agent.jar -jar app/build/libs/hello-uber-1.0.jar
```
## Get in touch