Upgrade to IzPack 4.3.0
-----------------------
Key: JBOSGI-71
URL: https://jira.jboss.org/jira/browse/JBOSGI-71
Project: JBossOSGi
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Other
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta2
--
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
Expose bundle headers through JMX
---------------------------------
Key: JBOSGI-70
URL: https://jira.jboss.org/jira/browse/JBOSGI-70
Project: JBossOSGi
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Core
Reporter: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta2
--
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
Support more attributes and operations in the Bundle Mbeans
-----------------------------------------------------------
Key: JBOSGI-69
URL: https://jira.jboss.org/jira/browse/JBOSGI-69
Project: JBossOSGi
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: JBossOSGi 1.0.0 Alpha3
Reporter: Heiko W. Rupp
Attachments: Some_possible_additions____.patch
Support more attributes in the MBean -- best would be the whole list of information that
the webconsole shows at http://localhost:8090/jboss-osgi/bundles/XYZ with XYZ being the bundle id
See also JBOSGI-55
--
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
JMX operation getProperty() always returns null
-----------------------------------------------
Key: JBOSGI-68
URL: https://jira.jboss.org/jira/browse/JBOSGI-68
Project: JBossOSGi
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossOSGi 1.0.0 Alpha3
Reporter: Heiko W. Rupp
The MBean-operation getProperty(key) on a bundle always returns null.
--
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
Release 1.0.0 Beta1
-------------------
Key: JBOSGI-57
URL: https://jira.jboss.org/jira/browse/JBOSGI-57
Project: JBossOSGi
Issue Type: Release
Security Level: Public (Everyone can see)
Components: Productization
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Alpha3
--
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/jira/browse/JBOSGI-67?page=com.atlassian.jira.plug... ]
Thomas Diesler deleted JBOSGI-67:
---------------------------------
> Support bundle deployment through web console
> ---------------------------------------------
>
> Key: JBOSGI-67
> URL: https://jira.jboss.org/jira/browse/JBOSGI-67
> Project: JBossOSGi
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Thomas Diesler
>
> Currently the web console allows you to install a bundle directly into the OSGi Runtime without going through the defined set of bundle deployers.
> As a result, the newly installed bundle does not get processed by the BundleManagementDeployer and hence does not get registered with JMX
> The preferred fix is to replace the provided upload functionality with one that delegates to the MainDeployer.
--
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/jira/browse/JBOSGI-67?page=com.atlassian.jira.plug... ]
Thomas Diesler updated JBOSGI-67:
---------------------------------
> Support bundle deployment through web console
> ---------------------------------------------
>
> Key: JBOSGI-67
> URL: https://jira.jboss.org/jira/browse/JBOSGI-67
> Project: JBossOSGi
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Thomas Diesler
>
> Currently the web console allows you to install a bundle directly into the OSGi Runtime without going through the defined set of bundle deployers.
> As a result, the newly installed bundle does not get processed by the BundleManagementDeployer and hence does not get registered with JMX
> The preferred fix is to replace the provided upload functionality with one that delegates to the MainDeployer.
--
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
Disable bundle deployment through web console
---------------------------------------------
Key: JBOSGI-67
URL: https://jira.jboss.org/jira/browse/JBOSGI-67
Project: JBossOSGi
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: JBossOSGi 1.0.0 Alpha3
Reporter: Thomas Diesler
Currently the web console allows you to install a bundle directly into the OSGi Runtime without going through the defined set of bundle deployers.
As a result, the newly installed bundle does not get processed by the BundleManagementDeployer and hence does not get registered with JMX
The preferred fix is to replace the provided upload functionality with one that delegates to the MainDeployer.
--
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/jira/browse/JBOSGI-27?page=com.atlassian.jira.plug... ]
Thomas Diesler updated JBOSGI-27:
---------------------------------
Attachment: JBW_MC.pdf
JBoss Microcontainer meets OSGi
Scott Stark & Ales Justin
JBoss World Orlando
JBW_MC.pdf
> JBoss OSGi Presentations
> ------------------------
>
> Key: JBOSGI-27
> URL: https://jira.jboss.org/jira/browse/JBOSGI-27
> Project: JBossOSGi
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Productization
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Fix For: Continuing
>
> Attachments: JBW_MC.pdf
>
>
--
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
Update to Felix 1.6.0
---------------------
Key: JBOSGI-65
URL: https://jira.jboss.org/jira/browse/JBOSGI-65
Project: JBossOSGi
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Integration (Felix)
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta1
--
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