[
https://issues.apache.org/jira/browse/ISIS-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andi Huber updated ISIS-1301:
-----------------------------
Summary: [WONT FIX] Support OSGi Containers (was: Support OSGi Containers)
> [WONT FIX] Support OSGi Containers
> ----------------------------------
>
> Key: ISIS-1301
> URL: https://issues.apache.org/jira/browse/ISIS-1301
> Project: Isis
> Issue Type: Wish
> Components: Core
> Reporter: Jörg Rade
> Priority: Minor
> Fix For: 2.1.0
>
>
> 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 ...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)