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

[JBoss JIRA] Created: (JBOSGI-178) Support for JBoss TM

by Frederic Conrotte (JIRA)

Support for JBoss TM -------------------- Key: JBOSGI-178 URL: https://jira.jboss.org/jira/browse/JBOSGI-178 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Integration (JBoss) Reporter: Frederic Conrotte I would like to see JBoss TM avaialable for JBoss OSGi framework -- 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

14 years, 7 months

2
9
0 / 0

[JBoss JIRA] Created: (JBOSGI-157) JTA (RFC-98) - Initial Implemantion

by Thomas Diesler (JIRA)

JTA (RFC-98) - Initial Implemantion ----------------------------------- Key: JBOSGI-157 URL: https://jira.jboss.org/jira/browse/JBOSGI-157 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Provide an initial JTA implementation with samples -- 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

14 years, 7 months

2
6
0 / 0

[JBoss JIRA] Created: (JBOSGI-137) Cannot parse Bundle-SymbolicName

by Thomas Diesler (JIRA)

Cannot parse Bundle-SymbolicName -------------------------------- Key: JBOSGI-137 URL: https://jira.jboss.org/jira/browse/JBOSGI-137 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Reporter: Thomas Diesler Fix For: Framework 1.0.0 Alpha1 The AbstractOSGiMetaData.parseSymbolicName() cannot always parse the symbolic name Currently there is a hack in place falls back to the main attribute public String getBundleSymbolicName() { String symbolicName = null; ParameterizedAttribute parameters = parseSymbolicName(); if (parameters != null) symbolicName = parameters.getAttribute(); // [TODO] Remove this fall back if (symbolicName == null) symbolicName = getMainAttribute(Constants.BUNDLE_SYMBOLICNAME); if (symbolicName == null) throw new IllegalStateException("Cannot obtain " + Constants.BUNDLE_SYMBOLICNAME); return symbolicName; } -- 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

14 years, 7 months

2
6
0 / 0

[JBoss JIRA] Created: (JBOSGI-153) Cannot parse Import Package parameters

by Thomas Diesler (JIRA)

Cannot parse Import Package parameters -------------------------------------- Key: JBOSGI-153 URL: https://jira.jboss.org/jira/browse/JBOSGI-153 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Reporter: Thomas Diesler Assignee: Adrian Brock Fix For: Framework 1.0.x The AbstractOSGiMetaData.parseSymbolicName() cannot always parse the symbolic name Currently there is a hack in place falls back to the main attribute public String getBundleSymbolicName() { String symbolicName = null; ParameterizedAttribute parameters = parseSymbolicName(); if (parameters != null) symbolicName = parameters.getAttribute(); // [TODO] Remove this fall back if (symbolicName == null) symbolicName = getMainAttribute(Constants.BUNDLE_SYMBOLICNAME); if (symbolicName == null) throw new IllegalStateException("Cannot obtain " + Constants.BUNDLE_SYMBOLICNAME); return symbolicName; } -- 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

14 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBOSGI-187) Husky SocketInvocation may block forever

by Thomas Diesler (JIRA)

Husky SocketInvocation may block forever ---------------------------------------- Key: JBOSGI-187 URL: https://jira.jboss.org/jira/browse/JBOSGI-187 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-osgi-husky Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Hudson hanging on this java.lang.Thread.State: RUNNABLE at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2266) at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2279) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2750) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780) at java.io.ObjectInputStream.<init>(ObjectInputStream.java:280) at org.jboss.osgi.husky.internal.SocketInvocation.invoke(SocketInvocation.java:79) at org.jboss.osgi.husky.internal.OSGiInvoker.invoke(OSGiInvoker.java:58) at org.jboss.osgi.husky.internal.AbstractBridge.run(AbstractBridge.java:66) at org.jboss.osgi.husky.internal.AbstractBridge.run(AbstractBridge.java:52) at org.jboss.test.osgi.example.blueprint.BlueprintTestCase.testBlueprintContainerAvailable(BlueprintTestCase.java:103) -- 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

14 years, 7 months

1
2
0 / 0

[JBoss JIRA] Deleted: (JBOSGI-186) Inject BundleContext in non-static field

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBOSGI-186?page=com.atlassian.jira.plu... ] Thomas Diesler deleted JBOSGI-186: ---------------------------------- > Inject BundleContext in non-static field > ---------------------------------------- > > Key: JBOSGI-186 > URL: https://jira.jboss.org/jira/browse/JBOSGI-186 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > > Currently injection works like this > @ProvideContext > public static BundleContext context; > which requires to have the context reset manually (i.e. there is no garbage collection of the context) -- 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

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBOSGI-190) Allign getting started guide with latest release

by Thomas Diesler (JIRA)

Allign getting started guide with latest release ------------------------------------------------ Key: JBOSGI-190 URL: https://jira.jboss.org/jira/browse/JBOSGI-190 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta5 There is a getting stared guide by Anesh Kumar http://www.jboss.org/community/wiki/OSGiGettingStartedWithOSGiDevelopment -- 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

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-125) Add ManagedFrameworkService

by Thomas Diesler (JIRA)

Add ManagedFrameworkService --------------------------- Key: JBOSGI-125 URL: https://jira.jboss.org/jira/browse/JBOSGI-125 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: SPI Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta4 -- 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

14 years, 8 months

1
6
0 / 0

[JBoss JIRA] Created: (JBOSGI-188) Separate DeployerService from SPI

by Thomas Diesler (JIRA)

Separate DeployerService from SPI --------------------------------- Key: JBOSGI-188 URL: https://jira.jboss.org/jira/browse/JBOSGI-188 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: jboss-osgi-spi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta5 The DeployerService http://jbmuc.dyndns.org/jboss-osgi-1.0.0.Beta4/apidocs/org/jboss/osgi/spi... and associated classes are currently part of the SPI. The DeployerService is related to [JBOSGI-183] OSGi Interceptors and should be able to evolve independently of the SPI -- 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

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-180) Consolidate the deployers

by Thomas Diesler (JIRA)

Consolidate the deployers ------------------------- Key: JBOSGI-180 URL: https://jira.jboss.org/jira/browse/JBOSGI-180 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Integration (JBoss) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta5 The deployers are currently spread over several modules, please consolidate. -- 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

14 years, 8 months

1
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues October 2009