[
https://issues.apache.org/jira/browse/ISIS-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andi Huber closed ISIS-1301.
----------------------------
Resolution: Won't Fix
Fix Version/s: (was: 2.1.0)
2.0.0-M3
While OSGi might have its advantages, it seems more likely that we will utilize
Java's module system in future releases of Apache Isis.
Closing this, as it appears unlikely, that any of the current Isis developers
is gonna tackle this.
(Feel free to reopen, if I'm wrong.)
> [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.0.0-M3
>
>
> 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)
