April 2013 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] (JBOSGI-260) Initial JPA implementation

by Jignesh Patel (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-260?page=com.atlassian.jira.plugin... ] Jignesh Patel commented on JBOSGI-260: -------------------------------------- Is this fix part of JBoss7.1.1? > Initial JPA implementation > -------------------------- > > Key: JBOSGI-260 > URL: https://issues.jboss.org/browse/JBOSGI-260 > Project: JBoss OSGi > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JPA/JDBC > 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-645) Cannot resolve Import-Package: org.acme.foo; version="0"

by Aaron Whiteside (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-645?page=com.atlassian.jira.plugin... ] Aaron Whiteside edited comment on JBOSGI-645 at 4/18/13 11:08 AM: ------------------------------------------------------------------ Any idea which JBoss AS8 build this will be part of? It looks like a build hasn't been scheduled in two days https://ci.jboss.org/hudson/view/All/job/JBoss-AS-latest-master/ was (Author: Aaron.Whiteside): Any idea which JBoss AS8 build this will be part of? > Cannot resolve Import-Package: org.acme.foo;version="0" > ------------------------------------------------------- > > Key: JBOSGI-645 > URL: https://issues.jboss.org/browse/JBOSGI-645 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 2.0.0 > > > Cannot resolve > {code} > // Bundle-SymbolicName: packageexportnoversion > // Export-Package: org.acme.foo > // Bundle-SymbolicName: packageimportversionzero > // Import-Package: org.acme.foo;version="0" > {code} > gives > {code} > Unable to resolve AbstractBundleRevision[packageimportversionzero:0.0.0]: missing requirement XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.acme.foo)(version>=0.0.0))},[packageimportversionzero:0.0.0]] > {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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-645) Cannot resolve Import-Package: org.acme.foo; version="0"

by Aaron Whiteside (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-645?page=com.atlassian.jira.plugin... ] Aaron Whiteside commented on JBOSGI-645: ---------------------------------------- Any idea which JBoss AS8 build this will be part of? > Cannot resolve Import-Package: org.acme.foo;version="0" > ------------------------------------------------------- > > Key: JBOSGI-645 > URL: https://issues.jboss.org/browse/JBOSGI-645 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 2.0.0 > > > Cannot resolve > {code} > // Bundle-SymbolicName: packageexportnoversion > // Export-Package: org.acme.foo > // Bundle-SymbolicName: packageimportversionzero > // Import-Package: org.acme.foo;version="0" > {code} > gives > {code} > Unable to resolve AbstractBundleRevision[packageimportversionzero:0.0.0]: missing requirement XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.acme.foo)(version>=0.0.0))},[packageimportversionzero:0.0.0]] > {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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-645) Cannot resolve Import-Package: org.acme.foo; version="0"

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-645?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-645. ----------------------------------- Resolution: Done Fixed in jbosgi-framework-3.0.0.CR17 > Cannot resolve Import-Package: org.acme.foo;version="0" > ------------------------------------------------------- > > Key: JBOSGI-645 > URL: https://issues.jboss.org/browse/JBOSGI-645 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 2.0.0 > > > Cannot resolve > {code} > // Bundle-SymbolicName: packageexportnoversion > // Export-Package: org.acme.foo > // Bundle-SymbolicName: packageimportversionzero > // Import-Package: org.acme.foo;version="0" > {code} > gives > {code} > Unable to resolve AbstractBundleRevision[packageimportversionzero:0.0.0]: missing requirement XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.acme.foo)(version>=0.0.0))},[packageimportversionzero:0.0.0]] > {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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-645) Cannot resolve Import-Package: org.acme.foo; version="0"

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-645?page=com.atlassian.jira.plugin... ] Work on JBOSGI-645 started by Thomas Diesler. > Cannot resolve Import-Package: org.acme.foo;version="0" > ------------------------------------------------------- > > Key: JBOSGI-645 > URL: https://issues.jboss.org/browse/JBOSGI-645 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 2.0.0 > > > Cannot resolve > {code} > // Bundle-SymbolicName: packageexportnoversion > // Export-Package: org.acme.foo > // Bundle-SymbolicName: packageimportversionzero > // Import-Package: org.acme.foo;version="0" > {code} > gives > {code} > Unable to resolve AbstractBundleRevision[packageimportversionzero:0.0.0]: missing requirement XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.acme.foo)(version>=0.0.0))},[packageimportversionzero:0.0.0]] > {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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-645) Cannot resolve Import-Package: org.acme.foo; version="0"

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-645?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-645: ---------------------------------- Description: Cannot resolve {code} // Bundle-SymbolicName: packageexportnoversion // Export-Package: org.acme.foo // Bundle-SymbolicName: packageimportversionzero // Import-Package: org.acme.foo;version="0" {code} gives {code} Unable to resolve AbstractBundleRevision[packageimportversionzero:0.0.0]: missing requirement XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.acme.foo)(version>=0.0.0))},[packageimportversionzero:0.0.0]] {code} was: Cannot resolve {code} // Bundle-SymbolicName: packageexportnoversion // Export-Package: org.acme.foo Archive<?> assemblyA = assembleArchive("resourceA", "/resolver/packageexportnoversion"); XResource resourceA = createResource(assemblyA); // Bundle-SymbolicName: packageimportversionzero // Import-Package: org.acme.foo;version="0" Archive<?> assemblyB = assembleArchive("resourceB", "/resolver/packageimportversionzero"); XResource resourceB = createResource(assemblyB); {code} gives {code} Unable to resolve AbstractBundleRevision[packageimportversionzero:0.0.0]: missing requirement XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.acme.foo)(version>=0.0.0))},[packageimportversionzero:0.0.0]] {code} > Cannot resolve Import-Package: org.acme.foo;version="0" > ------------------------------------------------------- > > Key: JBOSGI-645 > URL: https://issues.jboss.org/browse/JBOSGI-645 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 2.0.0 > > > Cannot resolve > {code} > // Bundle-SymbolicName: packageexportnoversion > // Export-Package: org.acme.foo > // Bundle-SymbolicName: packageimportversionzero > // Import-Package: org.acme.foo;version="0" > {code} > gives > {code} > Unable to resolve AbstractBundleRevision[packageimportversionzero:0.0.0]: missing requirement XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.acme.foo)(version>=0.0.0))},[packageimportversionzero:0.0.0]] > {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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-645) Cannot resolve Import-Package: org.acme.foo; version="0"

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-645?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-645: ---------------------------------- Description: Cannot resolve {code} // Bundle-SymbolicName: packageexportnoversion // Export-Package: org.acme.foo Archive<?> assemblyA = assembleArchive("resourceA", "/resolver/packageexportnoversion"); XResource resourceA = createResource(assemblyA); // Bundle-SymbolicName: packageimportversionzero // Import-Package: org.acme.foo;version="0" Archive<?> assemblyB = assembleArchive("resourceB", "/resolver/packageimportversionzero"); XResource resourceB = createResource(assemblyB); {code} gives {code} Unable to resolve AbstractBundleRevision[packageimportversionzero:0.0.0]: missing requirement XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.acme.foo)(version>=0.0.0))},[packageimportversionzero:0.0.0]] {code} > Cannot resolve Import-Package: org.acme.foo;version="0" > ------------------------------------------------------- > > Key: JBOSGI-645 > URL: https://issues.jboss.org/browse/JBOSGI-645 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 2.0.0 > > > Cannot resolve > {code} > // Bundle-SymbolicName: packageexportnoversion > // Export-Package: org.acme.foo > Archive<?> assemblyA = assembleArchive("resourceA", "/resolver/packageexportnoversion"); > XResource resourceA = createResource(assemblyA); > // Bundle-SymbolicName: packageimportversionzero > // Import-Package: org.acme.foo;version="0" > Archive<?> assemblyB = assembleArchive("resourceB", "/resolver/packageimportversionzero"); > XResource resourceB = createResource(assemblyB); > {code} > gives > {code} > Unable to resolve AbstractBundleRevision[packageimportversionzero:0.0.0]: missing requirement XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.acme.foo)(version>=0.0.0))},[packageimportversionzero:0.0.0]] > {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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-645) Cannot resolve Import-Package: org.acme.foo; version="0"

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-645: ------------------------------------- Summary: Cannot resolve Import-Package: org.acme.foo;version="0" Key: JBOSGI-645 URL: https://issues.jboss.org/browse/JBOSGI-645 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 2.0.0 -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-573) Check equals() for adapted caps/reqs

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-573?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-573. ----------------------------------- Fix Version/s: (was: JBossOSGi 2.0.0) Resolution: Out of Date > Check equals() for adapted caps/reqs > ------------------------------------ > > Key: JBOSGI-573 > URL: https://issues.jboss.org/browse/JBOSGI-573 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Assignee: Thomas Diesler > > An adapted XCapability/XRequirement is not the same object as the original. Client code must use equals() instead of '=='. Make sure equals returns true for all cases. -- 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, 6 months

1
0
0 / 0

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

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-604?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-604. ----------------------------------- Fix Version/s: (was: JBossOSGi 2.0.0) Resolution: Cannot Reproduce Bug Cannot reproduce with framework-3.0.0.CR17 and aries-blueprint-1.0.0 > 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: Core 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

12 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues April 2013