[JBoss JIRA] (WFLY-1226) Populate repository with metadata from system modules/bundles
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-1226?page=com.atlassian.jira.plugin.... ]
Thomas Diesler resolved WFLY-1226.
----------------------------------
Resolution: Won't Fix
Won't Fix - OSGi is going to get removed
> Populate repository with metadata from system modules/bundles
> -------------------------------------------------------------
>
> Key: WFLY-1226
> URL: https://issues.jboss.org/browse/WFLY-1226
> Project: WildFly
> Issue Type: Task
> Components: OSGi, Server
> Reporter: Thomas Diesler
>
> The OSGi configuration supports ModuleIdentifiers. So for example
> {code}
> <capability name="javax.transaction.api"/>
> {code}
> references the JTA API module. This actually delegates to the repository implementations which in turn delegates to the ModuleIdentityArtifactProvider.
> If the AppServer supports the notion of multiple directories where modules can get loaded from, the ServerEnvironment should reflect that properly. I cannot just load a module on trial/error basis because we use the Repository for impact ananlysis. i.e. Find the modules/bundles that provide the transitive set of capabilities for a given set of requirements (without modifying the runtime).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (WFLY-557) Complete support for Bundle update
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-557?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler resolved WFLY-557.
---------------------------------
Resolution: Won't Fix
Won't Fix - OSGi is going to get removed
> Complete support for Bundle update
> ----------------------------------
>
> Key: WFLY-557
> URL: https://issues.jboss.org/browse/WFLY-557
> Project: WildFly
> Issue Type: Sub-task
> Components: OSGi, Server
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Fix For: 9.0.0.CR1
>
>
> A Bundle can have multiple revisions. A call to Bundle.update(…) creates a new revision. There is only ever one current revision (the latest update) associated with a Bundle. Stale revisions continue to exist in the runtime until an explicit refresh of the transitive dependency graph.
> Approach #1 - bundle revisions are represented as individual deployments
> Each bundle update deploys the revision as a new deployment
> The association of revisions to bundle happens in the OSGi layer only
> Management sees disconnected deployments with no notion of stale/current or belonging together
> Approach #2 - deployment API supports the notion of multiple revisions
> deployments, their revisions and respective mapping would be modelled more closely on OSGi requirements
> some deployment types might not support revisions
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (WFLY-1076) Optimize OSGi subsystem bootstrap
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-1076?page=com.atlassian.jira.plugin.... ]
Thomas Diesler resolved WFLY-1076.
----------------------------------
Resolution: Won't Fix
Won't Fix - OSGi is going to get removed
> Optimize OSGi subsystem bootstrap
> ---------------------------------
>
> Key: WFLY-1076
> URL: https://issues.jboss.org/browse/WFLY-1076
> Project: WildFly
> Issue Type: Feature Request
> Components: OSGi
> Reporter: Thomas Diesler
>
> The OSGi subsystem in AS7 is alrady activated lazily. However, in many cases users only want to deploy a simple artefact that "happens to be" an OSGi bundle (i.e. a JDBC driver) and do not want to deploy a large set of interconnected bundles that make up a complex modular enterprise application. For those cases the OSGi subsystem should bootstrap in a jiffy and we should not see a performance impact that is worth talking about.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (WFLY-163) Some javax.* bundles show version 0.0.0 in AS7
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-163?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler resolved WFLY-163.
---------------------------------
Resolution: Won't Fix
Won't Fix - OSGi is going to get removed
> Some javax.* bundles show version 0.0.0 in AS7
> ----------------------------------------------
>
> Key: WFLY-163
> URL: https://issues.jboss.org/browse/WFLY-163
> Project: WildFly
> Issue Type: Bug
> Components: OSGi
> Reporter: Thomas Diesler
> Assignee: Cheng Fang
> Fix For: 8.0.0.Alpha3
>
>
> Some javax bundles that we configure by default do not show valid bundle version info
> javax.jws.api:0.0.0
> javax.ws.rs.api:0.0.0
> The javax.persistence.api has its metadata defined in jbosgi-xservice.properties like this
> {code}
> Bundle-SymbolicName: hibernate-jpa-2.0-api
> Bundle-Version: 1.0.1.Final
> Export-Package: javax.persistence.spi;version="2.0.0",javax.persistence.criteria;version="2.0.0",javax.persistence;version="2.0.0",javax.persistence.metamodel;version="2.0.0"
> {code}
> This should be replaced by metadata coming from the artefacts manifest.
> Generally, all javax api artefacts should have valid OSGi metadata
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months