Before using this project you must download the dsu, osjee and osjee.dropins project's code and run
mvn install
for each of them. They will be properly packaged in a near future to avoid this requirement
OSJEe Dropins Example
This project specifies the behavior provided by the osjee.dropins project
Run mvn post-clean verify
to
- install an Open Liberty server with the Java Servlets (4.0) and OSGi Debug Console features
- build the
/dynamic
web context (WAR) and deploy it to the server dropins directory - build the bundle (JAR) providing the
/dynamic/hello
servlet and deploy it to the directory selected for bundle dropins - build and deploy the
/static
web context with its/static/hello
servlet (for comparison purposes only) - start the server with a dropins aware OSGi framework attached to the
/dynamic
context
After changing (Hello by Hi?) the source code of any of the servlets you must run mvn clean package
- from
./bundle
to update the dynamic servlet JAR - from
./contexts/static
to update the static servlet WAR
To check how changes affect running clients run (bash required) ./loop.sh dynamic
or ./loop.sh static
before updating the corresponding component. You should never get errors from the former on updates to the dynamic servlet while the latter could, frequently, show HTTP 404 errors on updates to the static one