[ https://jira.jboss.org/jira/browse/JBOSGI-260?page=com.atlassian.jira.plu... ] Thomas Diesler reassigned JBOSGI-260: ------------------------------------- Assignee: Thomas Diesler -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBOSGI-260?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated JBOSGI-260: ---------------------------------- Fix Version/s: JBossOSGi 1.0.x (was: JBossOSGi 1.0.0 Beta8) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBOSGI-260?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-260: ---------------------------------- Fix Version/s: Community Pickup Area (was: Approved and Unscheduled) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBOSGI-260?page=com.atlassian.jira.plugin... ] Aaron Whiteside commented on JBOSGI-260: ---------------------------------------- Any idea on a timeline for this? JBoss AS 7.1.Final would be awesome ;) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBOSGI-260?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-260: ---------------------------------- Assignee: Thomas Diesler Fix Version/s: JBossOSGi 1.0.2 (was: Community Pickup) Moving back to the roadmap to get this rolling again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBOSGI-260?page=com.atlassian.jira.plugin... ] Thomas Diesler commented on JBOSGI-260: --------------------------------------- Not realy, this task is about providing OSGi access to the already existing JPA provider in AS7. We are most definitely not going to support multiple competing JPA providers in AS7. If you are only interested in JPA for OSGi, you could always drop in the [JPA provider from Aries|http://aries.apache.org/modules/jpaproject.html] or from [Gemini|http://www.eclipse.org/gemini/jpa/] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBOSGI-260?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-260: ---------------------------------- Component/s: JPA/JDBC (was: Other) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBOSGI-260?page=com.atlassian.jira.plugin... ] Scott Marlow commented on JBOSGI-260: ------------------------------------- If HHH-7527 is about adding OSGi support to Hibernate ORM and AS7-5405 is about supporting the OSGi Enterprise JPA specification. Which work is this jira for? Can OSGi Enterprise JPA use EE JPA (container) support or do we need a new subsystem for OSGi JPA? Does OSGi require a dynamic implementation of PersistenceProviderResolver (that could change Hibernate/EclipseLink/OpenJPA/other providers on the fly)? I thought that was required but I don't see it in the OSGi Enterprise Release 5 pdf that I'm looking at. {quote}We are most definitely not going to support multiple competing JPA providers in AS7.{quote} I assume you mean with respect to what is possible with OSGi. On the EE side, we need to support different persistence providers for various reasons (e.g. EE TCK compliance testing). Another reason to support EclipseLink, is for migrations. It is easier to migrate an application to run on JBoss AS, if you don't have to switch persistence providers right away. -- 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

[ https://issues.jboss.org/browse/JBOSGI-260?page=com.atlassian.jira.plugin... ] Thomas Diesler edited comment on JBOSGI-260 at 8/30/12 9:40 AM: ---------------------------------------------------------------- {quote} Which work is this jira for? {quote} It documents the availability of OSGi JPA in the JBossOSGi umbrella project. You can ignore it for your Hibernate & AS7 work. For the other questions, see [this comment|https://issues.jboss.org/browse/AS7-5405?focusedCommentId=1271486...] was (Author: thomas.diesler): {quote} Which work is this jira for? {quote} It documents the availability of OSGi JPA in the JBossOSGi umbrella project. You can ignore it for your Hibernate & AS7 work. -- 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