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

[JBoss JIRA] (JBOSGI-747) Apache Felix iPojo integration warnings/errors in WildFly 8 Alpha 4

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-747?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-747: ---------------------------------- Assignee: (was: Thomas Diesler) > Apache Felix iPojo integration warnings/errors in WildFly 8 Alpha 4 > ------------------------------------------------------------------- > > Key: JBOSGI-747 > URL: https://issues.jboss.org/browse/JBOSGI-747 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: WildFly 8 Alpha4 > Reporter: Mathilde Ffrench > > Seems to be a regretion between JBoss AS 7.2 and Widlfly 8 with iPojo integration. The problem is discribed in the following forum thread : > https://community.jboss.org/thread/232486 -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-748) EntityManagerFactory doesn't get registered for Persistence Bundles

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-748?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-748: ---------------------------------- Assignee: (was: Thomas Diesler) > EntityManagerFactory doesn't get registered for Persistence Bundles > ------------------------------------------------------------------- > > Key: JBOSGI-748 > URL: https://issues.jboss.org/browse/JBOSGI-748 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jpa > Affects Versions: JBossOSGi 2.1.0 > Environment: linux version 3.8.0-31 > java version "1.7.0_25" OpenJDK > wildfly-8.0.0.Alpha4 > jboss-osgi-2.1.0 > Reporter: Umberto Cappellini > > If I deploy a persistence bundle (i.e. a bundle having a META-INF/persistence.xml, and relative <Meta-Persistence> tag in the manifest), the framework correctly exposes EntityManagerFactory OSGi service. > Two Problems: > A) At startup, the em service is not anymore exposed. I found this happens because the persistence bundle starts up before the PersistenceUnitProcessor is registered as BundleListener, and therefore it doesn't receive the event START. > If I set "org.jboss.osgi" log level to TRACE, the time lost to trace logs is enough for the framework to start up properly and register the listener. In this case the event is received and the em service registered. > This is reproducible all the times: put the log level to INFO or DEBUG and no em service, put it to TRACE, and you have the service. > B) If I install the persistence bundle in the "bundle" folder of Wildfly and reference it as capability in the OSGi subsystem, the method PersistenceUnitProcessor.deploy is never invoked, and therefore the em service never exposed. > *edit* > OSGi Enterprise 5 standard requires the JPA provider to always expose the emf service for each persistence bundle: «A JPA Provider must register an Entity Manager Factory service for each assigned Persistence Unit that is complete. Complete means that it is a configured Persistence Unit, including the reference to the relational database.» -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-751) Fragment deployment fails in 8.0.0.Beta1

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-751: ------------------------------------- Summary: Fragment deployment fails in 8.0.0.Beta1 Key: JBOSGI-751 URL: https://issues.jboss.org/browse/JBOSGI-751 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: wildfly Reporter: 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-750) DeferredResolveTestCase fails in 8.0.0.Beta1

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-750: ------------------------------------- Summary: DeferredResolveTestCase fails in 8.0.0.Beta1 Key: JBOSGI-750 URL: https://issues.jboss.org/browse/JBOSGI-750 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: wildfly Reporter: 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-749) ConfigAdminIntegrationTestCase fails in 8.0.0.Beta1

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-749?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-749: ---------------------------------- Assignee: (was: Thomas Diesler) > ConfigAdminIntegrationTestCase fails in 8.0.0.Beta1 > --------------------------------------------------- > > Key: JBOSGI-749 > URL: https://issues.jboss.org/browse/JBOSGI-749 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: wildfly > Reporter: 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-749) ConfigAdminIntegrationTestCase fails in 8.0.0.Beta1

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-749: ------------------------------------- Summary: ConfigAdminIntegrationTestCase fails in 8.0.0.Beta1 Key: JBOSGI-749 URL: https://issues.jboss.org/browse/JBOSGI-749 Project: JBoss OSGi Issue Type: Bug 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-748) EntityManagerFactory doesn't get registered for Persistence Bundles

by Umberto Cappellini (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-748?page=com.atlassian.jira.plugin... ] Umberto Cappellini updated JBOSGI-748: -------------------------------------- Description: If I deploy a persistence bundle (i.e. a bundle having a META-INF/persistence.xml, and relative <Meta-Persistence> tag in the manifest), the framework correctly exposes EntityManagerFactory OSGi service. Two Problems: A) At startup, the em service is not anymore exposed. I found this happens because the persistence bundle starts up before the PersistenceUnitProcessor is registered as BundleListener, and therefore it doesn't receive the event START. If I set "org.jboss.osgi" log level to TRACE, the time lost to trace logs is enough for the framework to start up properly and register the listener. In this case the event is received and the em service registered. This is reproducible all the times: put the log level to INFO or DEBUG and no em service, put it to TRACE, and you have the service. B) If I install the persistence bundle in the "bundle" folder of Wildfly and reference it as capability in the OSGi subsystem, the method PersistenceUnitProcessor.deploy is never invoked, and therefore the em service never exposed. *edit* OSGi Enterprise 5 standard requires the JPA provider to always expose the emf service for each persistence bundle: «A JPA Provider must register an Entity Manager Factory service for each assigned Persistence Unit that is complete. Complete means that it is a configured Persistence Unit, including the reference to the relational database.» was: If I deploy a persistence bundle (i.e. a bundle having a META-INF/persistence.xml, and relative <Meta-Persistence> tag in the manifest), the framework correctly exposes EntityManagerFactory OSGi service. Two Problems: A) At startup, the em service is not anymore exposed. I found this happens because the persistence bundle starts up before the PersistenceUnitProcessor is registered as BundleListener, and therefore it doesn't receive the event START. If I set "org.jboss.osgi" log level to TRACE, the time lost to trace logs is enough for the framework to start up properly and register the listener. In this case the event is received and the em service registered. This is reproducible all the times: put the log level to INFO or DEBUG and no em service, put it to TRACE, and you have the service. B) If I install the persistence bundle in the "bundle" folder of Wildfly and reference it as capability in the OSGi subsystem, the method PersistenceUnitProcessor.deploy is never invoked, and therefore the em service never exposed. *edit* OSGi Enterprise 5 standard requires the JPA provider to always expose the emf service for each persistence bundle: «A JPA Provider must register an Entity Manager Factory service for each assigned Persistence Unit that is complete. Complete means that it is a configured Persistence Unit, including the reference to the relational database.» > EntityManagerFactory doesn't get registered for Persistence Bundles > ------------------------------------------------------------------- > > Key: JBOSGI-748 > URL: https://issues.jboss.org/browse/JBOSGI-748 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jpa > Affects Versions: JBossOSGi 2.1.0 > Environment: linux version 3.8.0-31 > java version "1.7.0_25" OpenJDK > wildfly-8.0.0.Alpha4 > jboss-osgi-2.1.0 > Reporter: Umberto Cappellini > Assignee: Thomas Diesler > > If I deploy a persistence bundle (i.e. a bundle having a META-INF/persistence.xml, and relative <Meta-Persistence> tag in the manifest), the framework correctly exposes EntityManagerFactory OSGi service. > Two Problems: > A) At startup, the em service is not anymore exposed. I found this happens because the persistence bundle starts up before the PersistenceUnitProcessor is registered as BundleListener, and therefore it doesn't receive the event START. > If I set "org.jboss.osgi" log level to TRACE, the time lost to trace logs is enough for the framework to start up properly and register the listener. In this case the event is received and the em service registered. > This is reproducible all the times: put the log level to INFO or DEBUG and no em service, put it to TRACE, and you have the service. > B) If I install the persistence bundle in the "bundle" folder of Wildfly and reference it as capability in the OSGi subsystem, the method PersistenceUnitProcessor.deploy is never invoked, and therefore the em service never exposed. > *edit* > OSGi Enterprise 5 standard requires the JPA provider to always expose the emf service for each persistence bundle: «A JPA Provider must register an Entity Manager Factory service for each assigned Persistence Unit that is complete. Complete means that it is a configured Persistence Unit, including the reference to the relational database.» -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-748) EntityManagerFactory doesn't get registered for Persistence Bundles

by Umberto Cappellini (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-748?page=com.atlassian.jira.plugin... ] Umberto Cappellini updated JBOSGI-748: -------------------------------------- Description: If I deploy a persistence bundle (i.e. a bundle having a META-INF/persistence.xml, and relative <Meta-Persistence> tag in the manifest), the framework correctly exposes EntityManagerFactory OSGi service. Two Problems: A) At startup, the em service is not anymore exposed. I found this happens because the persistence bundle starts up before the PersistenceUnitProcessor is registered as BundleListener, and therefore it doesn't receive the event START. If I set "org.jboss.osgi" log level to TRACE, the time lost to trace logs is enough for the framework to start up properly and register the listener. In this case the event is received and the em service registered. This is reproducible all the times: put the log level to INFO or DEBUG and no em service, put it to TRACE, and you have the service. B) If I install the persistence bundle in the "bundle" folder of Wildfly and reference it as capability in the OSGi subsystem, the method PersistenceUnitProcessor.deploy is never invoked, and therefore the em service never exposed. *edit* OSGi Enterprise 5 standard requires the JPA provider to always expose the emf service for each persistence bundle: «A JPA Provider must register an Entity Manager Factory service for each assigned Persistence Unit that is complete. Complete means that it is a configured Persistence Unit, including the reference to the relational database.» was: If I deploy a persistence bundle (i.e. a bundle having a META-INF/persistence.xml, and relative <Meta-Persistence> tag in the manifest), the framework correctly exposes EntityManagerFactory OSGi service. Two Problems: A) At startup, the em service is not anymore exposed. I found this happens because the persistence bundle starts up before the PersistenceUnitProcessor is registered as BundleListener, and therefore it doesn't receive the event START. If I set "org.jboss.osgi" log level to TRACE, the time lost to trace logs is enough for the framework to start up properly and register the listener. In this case the event is received and the em service registered. This is reproducible all the times: put the log level to INFO or DEBUG and no em service, put it to TRACE, and you have the service. B) If I install the persistence bundle in the "bundle" folder of Wildfly and reference it as capability in the OSGi subsystem, the method PersistenceUnitProcessor.deploy is never invoked, and therefore the em service never exposed. --edit-- OSGi Enterprise 5 standard requires the JPA provider to always expose the emf service for each persistence bundle: «A JPA Provider must register an Entity Manager Factory service for each assigned Persistence Unit that is complete. Complete means that it is a configured Persistence Unit, including the reference to the relational database.» > EntityManagerFactory doesn't get registered for Persistence Bundles > ------------------------------------------------------------------- > > Key: JBOSGI-748 > URL: https://issues.jboss.org/browse/JBOSGI-748 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jpa > Affects Versions: JBossOSGi 2.1.0 > Environment: linux version 3.8.0-31 > java version "1.7.0_25" OpenJDK > wildfly-8.0.0.Alpha4 > jboss-osgi-2.1.0 > Reporter: Umberto Cappellini > Assignee: Thomas Diesler > > If I deploy a persistence bundle (i.e. a bundle having a META-INF/persistence.xml, and relative <Meta-Persistence> tag in the manifest), the framework correctly exposes EntityManagerFactory OSGi service. > Two Problems: > A) At startup, the em service is not anymore exposed. I found this happens because the persistence bundle starts up before the PersistenceUnitProcessor is registered as BundleListener, and therefore it doesn't receive the event START. > If I set "org.jboss.osgi" log level to TRACE, the time lost to trace logs is enough for the framework to start up properly and register the listener. In this case the event is received and the em service registered. > This is reproducible all the times: put the log level to INFO or DEBUG and no em service, put it to TRACE, and you have the service. > B) If I install the persistence bundle in the "bundle" folder of Wildfly and reference it as capability in the OSGi subsystem, the method PersistenceUnitProcessor.deploy is never invoked, and therefore the em service never exposed. > *edit* > OSGi Enterprise 5 standard requires the JPA provider to always expose the emf service for each persistence bundle: «A JPA Provider must register an Entity Manager Factory service for each assigned Persistence Unit > that is complete. Complete means that it is a configured Persistence Unit, including the reference to the relational database.» -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-748) EntityManagerFactory doesn't get registered for Persistence Bundles

by Umberto Cappellini (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-748?page=com.atlassian.jira.plugin... ] Umberto Cappellini updated JBOSGI-748: -------------------------------------- Description: If I deploy a persistence bundle (i.e. a bundle having a META-INF/persistence.xml, and relative <Meta-Persistence> tag in the manifest), the framework correctly exposes EntityManagerFactory OSGi service. Two Problems: A) At startup, the em service is not anymore exposed. I found this happens because the persistence bundle starts up before the PersistenceUnitProcessor is registered as BundleListener, and therefore it doesn't receive the event START. If I set "org.jboss.osgi" log level to TRACE, the time lost to trace logs is enough for the framework to start up properly and register the listener. In this case the event is received and the em service registered. This is reproducible all the times: put the log level to INFO or DEBUG and no em service, put it to TRACE, and you have the service. B) If I install the persistence bundle in the "bundle" folder of Wildfly and reference it as capability in the OSGi subsystem, the method PersistenceUnitProcessor.deploy is never invoked, and therefore the em service never exposed. --edit-- OSGi Enterprise 5 standard requires the JPA provider to always expose the emf service for each persistence bundle: «A JPA Provider must register an Entity Manager Factory service for each assigned Persistence Unit that is complete. Complete means that it is a configured Persistence Unit, including the reference to the relational database.» was: If I deploy a persistence bundle (i.e. a bundle having a META-INF/persistence.xml, and relative <Meta-Persistence> tag in the manifest), the framework correctly exposes EntityManagerFactory OSGi service. Two Problems: A) At startup, the em service is not anymore exposed. I found this happens because the persistence bundle starts up before the PersistenceUnitProcessor is registered as BundleListener, and therefore it doesn't receive the event START. If I set "org.jboss.osgi" log level to TRACE, the time lost to trace logs is enough for the framework to start up properly and register the listener. In this case the event is received and the em service registered. This is reproducible all the times: put the log level to INFO or DEBUG and no em service, put it to TRACE, and you have the service. B) If I install the persistence bundle in the "bundle" folder of Wildfly and reference it as capability in the OSGi subsystem, the method PersistenceUnitProcessor.deploy is never invoked, and therefore the em service never exposed. > EntityManagerFactory doesn't get registered for Persistence Bundles > ------------------------------------------------------------------- > > Key: JBOSGI-748 > URL: https://issues.jboss.org/browse/JBOSGI-748 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jpa > Affects Versions: JBossOSGi 2.1.0 > Environment: linux version 3.8.0-31 > java version "1.7.0_25" OpenJDK > wildfly-8.0.0.Alpha4 > jboss-osgi-2.1.0 > Reporter: Umberto Cappellini > Assignee: Thomas Diesler > > If I deploy a persistence bundle (i.e. a bundle having a META-INF/persistence.xml, and relative <Meta-Persistence> tag in the manifest), the framework correctly exposes EntityManagerFactory OSGi service. > Two Problems: > A) At startup, the em service is not anymore exposed. I found this happens because the persistence bundle starts up before the PersistenceUnitProcessor is registered as BundleListener, and therefore it doesn't receive the event START. > If I set "org.jboss.osgi" log level to TRACE, the time lost to trace logs is enough for the framework to start up properly and register the listener. In this case the event is received and the em service registered. > This is reproducible all the times: put the log level to INFO or DEBUG and no em service, put it to TRACE, and you have the service. > B) If I install the persistence bundle in the "bundle" folder of Wildfly and reference it as capability in the OSGi subsystem, the method PersistenceUnitProcessor.deploy is never invoked, and therefore the em service never exposed. > --edit-- > OSGi Enterprise 5 standard requires the JPA provider to always expose the emf service for each persistence bundle: «A JPA Provider must register an Entity Manager Factory service for each assigned Persistence Unit > that is complete. Complete means that it is a configured Persistence Unit, including the reference to the relational database.» -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-748) EntityManagerFactory doesn't get registered for Persistence Bundles

by Umberto Cappellini (JIRA)

Umberto Cappellini created JBOSGI-748: ----------------------------------------- Summary: EntityManagerFactory doesn't get registered for Persistence Bundles Key: JBOSGI-748 URL: https://issues.jboss.org/browse/JBOSGI-748 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: jpa Affects Versions: JBossOSGi 2.1.0 Environment: linux version 3.8.0-31 java version "1.7.0_25" OpenJDK wildfly-8.0.0.Alpha4 jboss-osgi-2.1.0 Reporter: Umberto Cappellini Assignee: Thomas Diesler If I deploy a persistence bundle (i.e. a bundle having a META-INF/persistence.xml, and relative <Meta-Persistence> tag in the manifest), the framework correctly exposes EntityManagerFactory OSGi service. Two Problems: A) At startup, the em service is not anymore exposed. I found this happens because the persistence bundle starts up before the PersistenceUnitProcessor is registered as BundleListener, and therefore it doesn't receive the event START. If I set "org.jboss.osgi" log level to TRACE, the time lost to trace logs is enough for the framework to start up properly and register the listener. In this case the event is received and the em service registered. This is reproducible all the times: put the log level to INFO or DEBUG and no em service, put it to TRACE, and you have the service. B) If I install the persistence bundle in the "bundle" folder of Wildfly and reference it as capability in the OSGi subsystem, the method PersistenceUnitProcessor.deploy is never invoked, and therefore the em service never exposed. -- 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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues October 2013