David Bosschaert created JBOSGI-582:
---------------------------------------
Summary: Update Aries JMX to 1.1.0
Key: JBOSGI-582
URL: https://issues.jboss.org/browse/JBOSGI-582
Project: JBoss OSGi
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JMX
Reporter: David Bosschaert
Assignee: David Bosschaert
Fix For: JBossOSGi 2.0.0
The JMX integration should be updated to version 1.1.0 which maps to the jmx-next work done in Apache Aries.
The jmx-next work implements the OSGi Enterprise 5.0 JMX specification.
--
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
David Bosschaert created JBOSGI-581:
---------------------------------------
Summary: Update Aries Blueprint to 1.0.0
Key: JBOSGI-581
URL: https://issues.jboss.org/browse/JBOSGI-581
Project: JBoss OSGi
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Blueprint
Reporter: David Bosschaert
Assignee: David Bosschaert
Fix For: JBossOSGi 2.0.0
Update the Blueprint integration to use Aries Blueprint 1.0.0.
--
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
David Bosschaert created JBOSGI-579:
---------------------------------------
Summary: FileBasedRepositoryStorage.removeResource() is unable to delete the content file
Key: JBOSGI-579
URL: https://issues.jboss.org/browse/JBOSGI-579
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Repository
Environment: Exposed on Windows
Reporter: David Bosschaert
Assignee: Thomas Diesler
The FileBasedRepositoryStorageTestCase.testAddResourceFromStream() checks that the FileBasedRepositoryStorage.removeResource() method actually deletes the resource. However, on Windows it is unable to delete the 'content' file.
Windows is more picky about being able to delete resources when someone still has an open file handle to it. Most likely there is still a stream open on the 'content' file.
--
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