Date: Fri, 29 Mar 2024 12:58:42 +0000 (UTC) Message-ID: <1030050434.143815.1711717122874@ip-10-0-0-39.us-west-2.compute.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_143814_416977028.1711717122869" ------=_Part_143814_416977028.1711717122869 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Build as a standard Java JAR
Plugin classes should be placed in a package name starting with =E2= =80=9Corg.joget=E2=80=9D. (OEM release package are allowed to specify o= ther package names)
Make JAR available in the Java classpath (e.g., place it under WEB-I= NF/lib or application server lib folder).
Requires restarting the JVM for deployment or changes.
May cause library version conflicts with base libraries or other plu= gins.
Easier to develop and test using normal Java classes and libraries.<= /p>
Build as an OSGi (Open Services Gateway initiative framework) JAR bu= ndle.
Deploy JAR using the Manage Plugins in the Web Console.
Supports dynamic loading/unloading/reloading without restarting.
Runs in isolated mode, preventing library version conflict with base= libraries or other plugins.
More difficult to develop and test due to OSGi configuration and iso= lation.
Technology powering this structure: Apache Felix.