[JBoss JIRA] (JBOSGI-591) CLONE - Allow WAR deployments as OSGi bundles
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-591?page=com.atlassian.jira.plugin... ]
Thomas Diesler moved AS7-5455 to JBOSGI-591:
--------------------------------------------
Workflow: jira (was: GIT Pull Request workflow )
Project: JBoss OSGi (was: Application Server 7)
Key: JBOSGI-591 (was: AS7-5455)
Component/s: (was: OSGi)
(was: Web)
Fix Version/s: (was: 7.2.0.Alpha1)
> CLONE - Allow WAR deployments as OSGi bundles
> ---------------------------------------------
>
> Key: JBOSGI-591
> URL: https://issues.jboss.org/browse/JBOSGI-591
> Project: JBoss OSGi
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
>
> It should be possible to deploy webapps running on JBossWeb as OSGi bundles. The webapp can then be broken up in functional units (modularized in a standard way) which can be maintained separately.
> Needless to say that such webapps can natively integrate, make use of and provide OSGi services. Functionality can be turned on/off depending on service availability.
--
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
11 years, 8 months
[JBoss JIRA] (JBOSGI-588) ConcurrentModificationException with services using the same class name
by Thomas Diesler (JIRA)
Thomas Diesler created JBOSGI-588:
-------------------------------------
Summary: ConcurrentModificationException with services using the same class name
Key: JBOSGI-588
URL: https://issues.jboss.org/browse/JBOSGI-588
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.2.0
{code}
java.util.ConcurrentModificationException
at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
at java.util.AbstractList$Itr.next(AbstractList.java:343)
at java.util.AbstractCollection.addAll(AbstractCollection.java:305)
at org.jboss.osgi.framework.internal.ServiceManagerPlugin.getServiceReferencesInternal(ServiceManagerPlugin.java:215)
at org.jboss.osgi.framework.internal.ServiceManagerPlugin.getServiceReferences(ServiceManagerPlugin.java:202)
at org.jboss.osgi.framework.internal.AbstractBundleContext.getServiceReferences(AbstractBundleContext.java:327)
{code}
--
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
11 years, 8 months
[JBoss JIRA] (JBOSGI-560) NullPointerException in AbstractBundleState#ensureResolved if debug logging is enabled
by Rico Neubauer (JIRA)
Rico Neubauer created JBOSGI-560:
------------------------------------
Summary: NullPointerException in AbstractBundleState#ensureResolved if debug logging is enabled
Key: JBOSGI-560
URL: https://issues.jboss.org/browse/JBOSGI-560
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Rico Neubauer
Assignee: Thomas Diesler
Occurs with JBoss 7.1.2.Final (EAP) running with jbosgi-framework 1.3.0.Final
If debug logging is enabled, method org.jboss.osgi.framework.internal.AbstractBundleState#ensureResolved may throw a NullPointerException in case of "wiring" being null. See stacktrace below.
Will add a pull request, doing the missing check for null.
{noformat}
Caused by: java.lang.NullPointerException
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:558)
at org.jboss.osgi.framework.internal.FallbackLoader.findInUnresolvedModules(FallbackLoader.java:230)
at org.jboss.osgi.framework.internal.FallbackLoader.findModuleDynamically(FallbackLoader.java:156)
at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:85)
at org.jboss.modules.Module.loadModuleClass(Module.java:535)
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_31]
at java.lang.Class.forName(Class.java:247) [rt.jar:1.6.0_31]
at com.company.sth.ConnectionPool.<init>(ConnectionPool.java:131)
{noformat}
--
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
11 years, 8 months