May 2010 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] Created: (JBOSGI-213) Unexpected dependee state changes

by Thomas Diesler (JIRA)

Unexpected dependee state changes --------------------------------- Key: JBOSGI-213 URL: https://jira.jboss.org/jira/browse/JBOSGI-213 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler B --> X install(X) install(B) start(B) B == ACTIVE X == RESOLVED uninstall(X) B == ACTIVE The MC framework unexpectedly changes the state of B to RESOLVED -- 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

13 years, 10 months

2
8
0 / 0

[JBoss JIRA] Created: (JBOSGI-323) DynamicImport-Package takes presendence over embedded classes

by Thomas Diesler (JIRA)

DynamicImport-Package takes presendence over embedded classes ------------------------------------------------------------- Key: JBOSGI-323 URL: https://jira.jboss.org/jira/browse/JBOSGI-323 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
6
0 / 0

[JBoss JIRA] Created: (JBOSGI-328) Merge framework vfs30 support with core

by Thomas Diesler (JIRA)

Merge framework vfs30 support with core --------------------------------------- Key: JBOSGI-328 URL: https://jira.jboss.org/jira/browse/JBOSGI-328 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 Support for VFS21 can be discontinued because all supported target containers for the MC framework use VFS30 -- 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

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-327) Add support for JBossAS-6.0.0.M3

by Thomas Diesler (JIRA)

Add support for JBossAS-6.0.0.M3 -------------------------------- Key: JBOSGI-327 URL: https://jira.jboss.org/jira/browse/JBOSGI-327 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 Beta8 -- 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

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-306) Invalic classloader policy created

by Thomas Diesler (JIRA)

Invalic classloader policy created ---------------------------------- Key: JBOSGI-306 URL: https://jira.jboss.org/jira/browse/JBOSGI-306 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: Framework 1.0.0 Alpha4 * OSGiClassLoaderFactory.createClassLoader() sets the ClassLoaderPolicyFactory on the Module * ClassLoaderPolicyModule.registerClassLoaderPolicy() calls getPolicy() on itself * getPolicy() should call policyFactory.createClassLoaderPolicy() on the factory that was set above However the policyFactory is null so it falls back to ClassLoaderPolicyModule.createClassLoaderPolicy(), which results in the wrong policy being created. Caused by: java.lang.IllegalArgumentException: Invalid policy: VFSClassLoaderPolicy@190d536{vfs:///home/tdiesler/svn/jboss-osgi/trunk/reactor/framework/bundle/target/osgi-store/bundle-0/bundle-1269577893252.jar/} at org.jboss.osgi.framework.classloading.OSGiBundleClassLoader.<init>(OSGiBundleClassLoader.java:46) at org.jboss.osgi.framework.classloading.OSGiClassLoaderSystem.createClassLoader(OSGiClassLoaderSystem.java:71) at org.jboss.classloader.spi.base.BaseClassLoaderSystem$1.run(BaseClassLoaderSystem.java:126) at org.jboss.classloader.spi.base.BaseClassLoaderSystem$1.run(BaseClassLoaderSystem.java:123) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.classloader.spi.base.BaseClassLoaderSystem.registerClassLoaderPolicy(BaseClassLoaderSystem.java:122) at org.jboss.classloader.spi.ClassLoaderSystem.registerClassLoaderPolicy(ClassLoaderSystem.java:494) at org.jboss.classloader.spi.ClassLoaderSystem.registerClassLoaderPolicy(ClassLoaderSystem.java:436) at org.jboss.classloading.spi.dependency.policy.ClassLoaderPolicyModule.registerClassLoaderPolicy(ClassLoaderPolicyModule.java:147) at org.jboss.osgi.framework.classloading.OSGiClassLoaderFactory.createClassLoader(OSGiClassLoaderFactory.java:88) -- 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

13 years, 12 months

1
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-235) Verify system classpath access

by Thomas Diesler (JIRA)

Verify system classpath access ------------------------------ Key: JBOSGI-235 URL: https://jira.jboss.org/jira/browse/JBOSGI-235 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Create a test case that verifies that bundle classes cannot access packages that are not defined by the framework system packages. Non OSGi deployments need to see packages on the default domain. -- 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

13 years, 12 months

1
5
0 / 0

[JBoss JIRA] Created: (JBOSGI-318) Linkage error for javax.servlet.Servlet in AS600

by Thomas Diesler (JIRA)

Linkage error for javax.servlet.Servlet in AS600 ------------------------------------------------ Key: JBOSGI-318 URL: https://jira.jboss.org/jira/browse/JBOSGI-318 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Integration (JBoss) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 Caused by: java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "org.ops4j.pax.web.service.internal.HttpServiceProxy.registerServlet(Ljava/lang/String;Ljavax/servlet/Servlet;Ljava/util/Dictionary;Lorg/osgi/service/http/HttpContext;)V" the class loader (instance of org/jboss/osgi/framework/classloading/OSGiBundleClassLoader) of the current class, org/ops4j/pax/web/service/internal/HttpServiceProxy, and the class loader (instance of org/jboss/osgi/framework/classloading/OSGiBundleClassLoader) for interface org/osgi/service/http/HttpService have different Class objects for the type javax/servlet/Servlet used in the signature at org.ops4j.pax.web.service.internal.Activator$2.createService(Activator.java:104) at org.ops4j.pax.web.service.internal.HttpServiceFactoryImpl.getService(HttpServiceFactoryImpl.java:34) at org.jboss.osgi.framework.bundle.OSGiServiceState.getService(OSGiServiceState.java:391) ... 20 more -- 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

13 years, 12 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-326) MC service does not provide properties through JMX

by Thomas Diesler (JIRA)

MC service does not provide properties through JMX -------------------------------------------------- Key: JBOSGI-326 URL: https://jira.jboss.org/jira/browse/JBOSGI-326 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 There are multiple failures when the testsuite is run against the AS. The client API uses context.getServiceReferences("javax.management.MBeanServer", null) which discovers multiple MBeanServers one of which it cannot obtain the properties from. See forum for details: http://community.jboss.org/thread/151661 -- 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

13 years, 12 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-319) LinkageError for the type javax/servlet/Servlet

by Thomas Diesler (JIRA)

LinkageError for the type javax/servlet/Servlet ------------------------------------------------ Key: JBOSGI-319 URL: https://jira.jboss.org/jira/browse/JBOSGI-319 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Integration (JBoss) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 Caused by: java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "org.ops4j.pax.web.service.internal.HttpServiceProxy.registerServlet(Ljava/lang/String;Ljavax/servlet/Servlet;Ljava/util/Dictionary;Lorg/osgi/service/http/HttpContext;)V" the class loader (instance of org/jboss/osgi/framework/classloading/OSGiBundleClassLoader) of the current class, org/ops4j/pax/web/service/internal/HttpServiceProxy, and the class loader (instance of org/jboss/osgi/framework/classloading/OSGiBundleClassLoader) for interface org/osgi/service/http/HttpService have different Class objects for the type javax/servlet/Servlet used in the signature at org.ops4j.pax.web.service.internal.Activator$2.createService(Activator.java:104) at org.ops4j.pax.web.service.internal.HttpServiceFactoryImpl.getService(HttpServiceFactoryImpl.java:34) at org.jboss.osgi.framework.bundle.OSGiServiceState.getService(OSGiServiceState.java:391) ... 20 more -- 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

13 years, 12 months

1
5
0 / 0

[JBoss JIRA] Created: (JBOSGI-315) Integrate jboss-osgi-http in distribution

by Thomas Diesler (JIRA)

Integrate jboss-osgi-http in distribution ----------------------------------------- Key: JBOSGI-315 URL: https://jira.jboss.org/jira/browse/JBOSGI-315 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: jboss-osgi-http Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues May 2010