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

[JBoss JIRA] (JBOSGI-727) Add support for Framework restart

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-727?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-727: ---------------------------------- Fix Version/s: Awaiting Volunteers > Add support for Framework restart > --------------------------------- > > Key: JBOSGI-727 > URL: https://issues.jboss.org/browse/JBOSGI-727 > Project: JBoss OSGi > Issue Type: Task > Components: Core Framework, WildFly > Reporter: Thomas Diesler > Fix For: Awaiting Volunteers > > > It should be possible to modify the framework configuration and restart the framework in AS7. This is especially important for a Framework instance running in OpenShift. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-697) Complete support for OSGi JPA

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-697?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-697: ---------------------------------- Fix Version/s: Awaiting Volunteers > Complete support for OSGi JPA > ----------------------------- > > Key: JBOSGI-697 > URL: https://issues.jboss.org/browse/JBOSGI-697 > Project: JBoss OSGi > Issue Type: Feature Request > Components: Enterprise OSGi > Reporter: Thomas Diesler > Labels: jdbc, jpa > Fix For: Awaiting Volunteers > > > h6. 127.3.1 Services > _Entity Manager Factory Builder service_ - The Entity Manager Factory Builder service provides the capability of creating an EntityManagerFactory object with additional configuration properties > Add EntityManagerFactory service properties > * osgi.unit.name - The name of the Persistence Unit (done) > * osgi.unit.version - The version of the associated Persistence Bundle > * osgi.unit.provider - The implementation class name of the JPA Provider > h6. 127.3.4 Custom Configured Entity Manager > If a Client Bundle needs to provide configuration properties for the creation of an Entity Manager Factory it should use the Entity Manager Factory Builder service. This can for example be used to provide the database selection properties when the Persistence Unit is incomplete or if the database selection needs to be overridden. > Once an Entity Manager Factory is created the specified Data Source becomes associated with the Entity Manager Factory. It is therefore not possible to re-associate an Entity Manager Factory with another Data Source by providing different properties. A JPA Provider must throw an Exception when an attempt is made to re-specify the database properties. > h6. 127.4.2 Meta Persistence Header > Support non-default persistence descriptors through the Meta-Persistence header > For example: _Meta-Persistence: META-INF/jpa.xml, persistence/jpa.xml_ > h6. 127.4.3 Processing > The JPA Provider must validate the Persistence Bundle. A valid Persistence Bundle must: > * Have no parsing errors of the Persistence Descriptors > * Validate all Persistence Descriptors against their schemas > * Have at least one assigned Persistence Unit > * Have all entity classes mentioned in the assigned Persistence Units on the Persistence Bundles JAR. > If any validation fails, then this is an error and should be logged. Such a bundle is ignored completely even if it also contains valid assigned Persistence Units. Only a bundle update can recover from this > state. > h6. 127.4.8 Stopping > If a Persistence Bundle is being stopped, then the JPA Provider must ensure that any resources allocated on behalf of the Persistence Bundle are cleaned up and all open connections are closed. This cleanup must happen synchronously with the STOPPING event. Any Exceptions being thrown while cleaning up should be logged but must not stop any further clean up. > If the JPA Provider is being stopped, the JPA Provider must unregister all JPA Services that it registered through the Persistence Bundles and clean up as if those bundles were stopped. > h6. 127.5.3 Data Source Factory Service Matching > Providers must use the javax.persistence.jdbc.driver property, as defined in JDBC Access in JPA on page 406, to obtain a Data Source Factory service. The Data Source Factory is specified in JDBC Service Specification on page 375. The javax.persistence.jdbc.driver property must be matched with the value of the Data Source Factory service property named osgi.jdbc.driver.class. > h6. 127.5.4 Rebinding > In this specification, the Entity Manager Factory service is only registered when the Persistence Unit is complete and a matching Data Source Factory service is available. However, the API of the Entity > Manager Factory allows the creation of an Entity Manager with configuration properties. Those configuration properties could contain the JDBC properties to bind to another Data Source Factory service than it had already selected. > This case must not be supported by a JPA Provider, an Illegal Argument Exception must be thrown. > h6. 127.6 Static Access > A Static Persistence Bundle must provide static access from the Persistence class to the JPA Services. > This issue is complete when the TCK passes -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-741) Make the root context of all HttpService-registered entities configurable

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-741?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-741: ---------------------------------- Fix Version/s: Awaiting Volunteers > Make the root context of all HttpService-registered entities configurable > ------------------------------------------------------------------------- > > Key: JBOSGI-741 > URL: https://issues.jboss.org/browse/JBOSGI-741 > Project: JBoss OSGi > Issue Type: Sub-task > Components: Enterprise OSGi, WildFly > Reporter: David Bosschaert > Fix For: Awaiting Volunteers > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-735) HttpService MimeType, ContentLength, etc

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-735?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-735: ---------------------------------- Fix Version/s: Awaiting Volunteers > HttpService MimeType, ContentLength, etc > ---------------------------------------- > > Key: JBOSGI-735 > URL: https://issues.jboss.org/browse/JBOSGI-735 > Project: JBoss OSGi > Issue Type: Sub-task > Components: Enterprise OSGi, WildFly > Reporter: Thomas Diesler > Fix For: Awaiting Volunteers > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-500) Pass JNDI CT

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-500?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-500: ---------------------------------- Fix Version/s: Awaiting Volunteers > Pass JNDI CT > ------------ > > Key: JBOSGI-500 > URL: https://issues.jboss.org/browse/JBOSGI-500 > Project: JBoss OSGi > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Enterprise OSGi, WildFly > Reporter: David Bosschaert > Labels: jndi > Fix For: Awaiting Volunteers > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-703) Integration of EventAdmin with AS7 components

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-703?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-703: ---------------------------------- Fix Version/s: Awaiting Volunteers > Integration of EventAdmin with AS7 components > --------------------------------------------- > > Key: JBOSGI-703 > URL: https://issues.jboss.org/browse/JBOSGI-703 > Project: JBoss OSGi > Issue Type: Feature Request > Components: Enterprise OSGi, WildFly > Reporter: Thomas Diesler > Fix For: Awaiting Volunteers > > > Non-OSGi components should be able to publish/receive events through EventAdmin > and vice versa of course -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-695) Complete support for OSGi JDBC

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-695?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-695: ---------------------------------- Fix Version/s: Awaiting Volunteers > Complete support for OSGi JDBC > ------------------------------ > > Key: JBOSGI-695 > URL: https://issues.jboss.org/browse/JBOSGI-695 > Project: JBoss OSGi > Issue Type: Feature Request > Components: Enterprise OSGi, WildFly > Reporter: Thomas Diesler > Labels: jdbc, jpa > Fix For: Awaiting Volunteers > > > R5 TCK compliance for JDBC -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-551) Initial Core implementation for mobile platform

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-551?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-551: ---------------------------------- Fix Version/s: Awaiting Volunteers > Initial Core implementation for mobile platform > ----------------------------------------------- > > Key: JBOSGI-551 > URL: https://issues.jboss.org/browse/JBOSGI-551 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Android/Mobile > Reporter: Thomas Diesler > Fix For: Awaiting Volunteers > > > As part of our 3D strategy, I'd like to investigate in OSGi on mobile platforms. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-720) Complete support for HttpService

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-720?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-720: ---------------------------------- Fix Version/s: Awaiting Volunteers > Complete support for HttpService > -------------------------------- > > Key: JBOSGI-720 > URL: https://issues.jboss.org/browse/JBOSGI-720 > Project: JBoss OSGi > Issue Type: Task > Components: Enterprise OSGi, WildFly > Reporter: Thomas Diesler > Labels: roadmap > Fix For: Awaiting Volunteers > > > #1 Add support for MimeType, Content-Lenght, etc > #2 Delegate authentication/authorisation to HttpContext > #3 Add support for "/" root context > #4 Make HttpService an optional capability > #5 Make virtual host/port configurable > This issue is complete when the TCK passes -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-739) Http Service TCK testLongRegistrationName() failing

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-739?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-739: ---------------------------------- Fix Version/s: Awaiting Volunteers > Http Service TCK testLongRegistrationName() failing > --------------------------------------------------- > > Key: JBOSGI-739 > URL: https://issues.jboss.org/browse/JBOSGI-739 > Project: JBoss OSGi > Issue Type: Sub-task > Components: Enterprise OSGi, WildFly > Reporter: David Bosschaert > Fix For: Awaiting Volunteers > > > The OSGi HTTP Service TCK test testLongRegistrationName() fails with the following exception: > java.io.FileNotFoundException: http://localhost:8080/abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxy... > Apparently there is an issue with long registration names. -- 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, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues July 2013