[CAUSEWAY-1301] [WONT FIX] Support OSGi Containers

• Type: Wish
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Fix Version/s: 2.0.0-M3
• Component/s: Core
• Assignee: Unassigned
• Reporter: Jörg Rade
• Created: 31/Jan/16 10:38
• Updated: 02/May/19 08:52
• Resolved: 02/May/19 08:52

Description

Currently the war artifact contains all jars the application depends on.

• Repackeging these unchanged jars over and over takes some time (in my case this is at par with compiling dom).
• The footprint of the war when redeploying it over thin connections requires more bandwidth.
• Supporting OSGi containers would have the addional benefit that only changed artifacts would have to exchanged in the running container. Production systems could benefit from the possibility of the OSGi lifecycle, ie. replacing artifacts without downtime.

This will involve multiple steps, eg.

• Using more bundled versions of dependencies (where available - Wicket, DataNucleus, Jetty already are bundled)
• Building a bundled war (wab)
• Making isis libs conform to OSGi's class loader requirements
• Bridging the OSGi ServiceRegistry to use its Servies as DomainServices
  tbc ...

Sub-Tasks

• [WONT FIX] Use bundled JARs instead of plain ones: Closed