[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 reopened WFLY-1076:
----------------------------------
> 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
13 years
[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 reopened WFLY-163:
---------------------------------
Assignee: (was: Cheng Fang)
> 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
>
> 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
13 years
[JBoss JIRA] (WFLY-793) Invalid bundle deployment does not fail in domain
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-793?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler reopened WFLY-793:
---------------------------------
> Invalid bundle deployment does not fail in domain
> -------------------------------------------------
>
> Key: WFLY-793
> URL: https://issues.jboss.org/browse/WFLY-793
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, OSGi
> Reporter: Thomas Diesler
> Priority: Minor
>
> Running org.jboss.as.test.integration.domain.suites.OSGiBundleLifecyleTestCase
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 35.653 sec <<< FAILURE!
> on the server I see
> {code}
> 15:20:28,619 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit.bad-bundle.STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit.bad-bundle.STRUCTURE: Failed to process phase STRUCTURE of deployment "bad-bundle"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29]
> Caused by: java.lang.NumberFormatException: For input string: "bogus"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) [rt.jar:1.6.0_29]
> at java.lang.Integer.parseInt(Integer.java:449) [rt.jar:1.6.0_29]
> at java.lang.Integer.parseInt(Integer.java:499) [rt.jar:1.6.0_29]
> at org.osgi.framework.Version.<init>(Version.java:125)
> at org.osgi.framework.Version.parseVersion(Version.java:218)
> at org.jboss.osgi.spi.BundleInfo.validateBundleManifest(BundleInfo.java:204)
> at org.jboss.osgi.spi.BundleInfo.isValidBundleManifest(BundleInfo.java:153)
> at org.jboss.as.osgi.deployment.OSGiManifestStructureProcessor.deploy(OSGiManifestStructureProcessor.java:63)
> {code}
--
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
13 years