January 2014 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] (JBOSGI-757) WildFly OSGi web console is empty of data

by Darryl Miles (JIRA)

Darryl Miles created JBOSGI-757: ----------------------------------- Summary: WildFly OSGi web console is empty of data Key: JBOSGI-757 URL: https://issues.jboss.org/browse/JBOSGI-757 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: webapp Reporter: Darryl Miles This has the best picture of the console: http://stackoverflow.com/questions/20569178/wildfly-8-0-0-beta1-not-showi... Also the "undefined" information in the Management console, is that correct ? I tested with EAP 6.x and found that also to say "undefined" but the web console works. So the two issues maybe unrelated. It would be good to get whatever fix is needed into OSGi of WindFly 8 before GA is released. If this is not the correct project with the problem please point me to the GIT source tree to look at to diagnose this issue. Thanks. -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-756) DEFAULT_INTEGRATION_PACKAGES versions maybe too strict for WF8 ?

by Darryl Miles (JIRA)

Darryl Miles created JBOSGI-756: ----------------------------------- Summary: DEFAULT_INTEGRATION_PACKAGES versions maybe too strict for WF8 ? Key: JBOSGI-756 URL: https://issues.jboss.org/browse/JBOSGI-756 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: wildfly Reporter: Darryl Miles Priority: Minor o.j.as.osgi.service.SystemPackagesIntegration#DEFAULT_INTEGRATION_PACKAGES might list too strict a version for WildFly 8: org.jboss.dmr;version=1.1.1 BUT: wildfly-8.0.0.CR1/modules/system/layers/base/org/jboss/dmr/main/jboss-dmr-1.2.0.Final.jar org.jboss.logging;version=3.1.0 BUT: wildfly-8.0.0.CR1/modules/system/layers/base/org/jboss/logging/main/jboss-logging-3.1.3.GA.jar The above two projects do not have a jbosgi-xservice.properties file ? is this also a concern ? org.slf4f.impl has a file jbosgi-xservice.properties but other org.slf4j.* org.slf4j.spi.* org.slf4j.helpers.* do not have this file, is this a concern ? If this is indeed a problem. Could this be unit tested ? Load up a test-case bundle, pass the String[] from DEFAULT_INTEGRATION_PACKAGES into the test-case bundle. Then have it ensure any version was resolved for each package, from inside the test-case bundle execution context. -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-604) FactoryConfigurationError: Provider __redirected.__DocumentBuilderFactory not found

by Pascal Alich (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-604?page=com.atlassian.jira.plugin... ] Pascal Alich commented on JBOSGI-604: ------------------------------------- I have had a similar issue with an OSGi container started within a web application that is deployed to JBoss. It is not a JBoss bug. Please see my stackoverflow question (and answer) for details and a solution: http://stackoverflow.com/a/21096562/3181425 > FactoryConfigurationError: Provider __redirected.__DocumentBuilderFactory not found > ----------------------------------------------------------------------------------- > > Key: JBOSGI-604 > URL: https://issues.jboss.org/browse/JBOSGI-604 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: framework > Reporter: Thomas Diesler > Assignee: Thomas Diesler > > {code} > 2012-09-14 12:25:33,183 | ERROR | rint Extender: 1 | BlueprintContainerImpl | 9 - org.apache.aries.blueprint - 0.3.2 | Unable to start blueprint container for bundle org.apache.aries.blueprint > javax.xml.parsers.FactoryConfigurationError: Provider __redirected.__DocumentBuilderFactory not found > at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:129)[:1.6.0_33] > at org.apache.aries.blueprint.container.Parser.getDocumentBuilderFactory(Parser.java:1345)[9:org.apache.aries.blueprint:0.3.2] > at org.apache.aries.blueprint.container.Parser.parse(Parser.java:203)[9:org.apache.aries.blueprint:0.3.2] > at org.apache.aries.blueprint.container.Parser.parse(Parser.java:219)[9:org.apache.aries.blueprint:0.3.2] > at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:254)[9:org.apache.aries.blueprint:0.3.2] > at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:230)[9:org.apache.aries.blueprint:0.3.2] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)[:1.6.0_33] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)[:1.6.0_33] > at java.util.concurrent.FutureTask.run(FutureTask.java:138)[:1.6.0_33] > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)[:1.6.0_33] > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)[:1.6.0_33] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)[:1.6.0_33] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)[:1.6.0_33] > at java.lang.Thread.run(Thread.java:662)[:1.6.0_33] > {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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-754) Update to WildFly-8.0.0.CR1

by Alexander Willner (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-754?page=com.atlassian.jira.plugin... ] Alexander Willner commented on JBOSGI-754: ------------------------------------------ Ok. So the current workaround is to use 8.0.0.Beta1 instead of 8.0.0.CR1. > Update to WildFly-8.0.0.CR1 > --------------------------- > > Key: JBOSGI-754 > URL: https://issues.jboss.org/browse/JBOSGI-754 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: wildfly > Reporter: Thomas Diesler > Assignee: Thomas Diesler > -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-755) Update to WildFly-8.0.0.Final

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-755?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-755: ---------------------------------- Fix Version/s: JBossOSGi 2.1.2 > Update to WildFly-8.0.0.Final > ----------------------------- > > Key: JBOSGI-755 > URL: https://issues.jboss.org/browse/JBOSGI-755 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: distribution > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 2.1.2 > > -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-755) Update to WildFly-8.0.0.Final

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-755: ------------------------------------- Summary: Update to WildFly-8.0.0.Final Key: JBOSGI-755 URL: https://issues.jboss.org/browse/JBOSGI-755 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: distribution Reporter: Thomas Diesler Assignee: Thomas Diesler -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-754) Update to WildFly-8.0.0.CR1

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-754?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-754. ----------------------------------- Resolution: Won't Fix WildFly-8.0.0.CR1 is not usable. It got released without providing a fix for WFLY-2641 > Update to WildFly-8.0.0.CR1 > --------------------------- > > Key: JBOSGI-754 > URL: https://issues.jboss.org/browse/JBOSGI-754 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: wildfly > Reporter: Thomas Diesler > Assignee: Thomas Diesler > -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-754) Update to WildFly-8.0.0.CR1

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-754: ------------------------------------- Summary: Update to WildFly-8.0.0.CR1 Key: JBOSGI-754 URL: https://issues.jboss.org/browse/JBOSGI-754 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: wildfly Reporter: Thomas Diesler Assignee: Thomas Diesler -- 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

10 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues January 2014