[JBoss JIRA] (JBOSGI-761) WAB fragment deployment fails
by Harald Wellmann (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-761?page=com.atlassian.jira.plugin... ]
Harald Wellmann updated JBOSGI-761:
-----------------------------------
Issue Type: Bug (was: Feature Request)
> WAB fragment deployment fails
> -----------------------------
>
> Key: JBOSGI-761
> URL: https://issues.jboss.org/browse/JBOSGI-761
> Project: JBoss OSGi
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: JBossOSGi 2.1.1
> Environment: WildFly 8.0.0.CR1, jbosgi-2.1.2-SNAPSHOT
> Reporter: Harald Wellmann
>
> When deploying a fragment bundle attached to a WAB, there is a NullPointerException in {{WebBundleFragmentProcessor.deploy()}}, caused by {{hostRef.getWiring()}} being null.
> I suppose this processor should only be run on web bundles, not on fragments.
> After patching this class to do an early exit
> {code}
> if (hostRev.isFragment()) {
> return;
> }
> {code}
> the exception is gone, but then I'm running into JBOSGI-751.
--
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-761) WAB fragment deployment fails
by Harald Wellmann (JIRA)
Harald Wellmann created JBOSGI-761:
--------------------------------------
Summary: WAB fragment deployment fails
Key: JBOSGI-761
URL: https://issues.jboss.org/browse/JBOSGI-761
Project: JBoss OSGi
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: JBossOSGi 2.1.1
Environment: WildFly 8.0.0.CR1, jbosgi-2.1.2-SNAPSHOT
Reporter: Harald Wellmann
When deploying a fragment bundle attached to a WAB, there is a NullPointerException in {{WebBundleFragmentProcessor.deploy()}}, caused by {{hostRef.getWiring()}} being null.
I suppose this processor should only be run on web bundles, not on fragments.
After patching this class to do an early exit
{code}
if (hostRev.isFragment()) {
return;
}
{code}
the exception is gone, but then I'm running into JBOSGI-751.
--
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-751) Fragment deployment fails in 8.0.0.Beta1
by Harald Wellmann (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-751?page=com.atlassian.jira.plugin... ]
Harald Wellmann commented on JBOSGI-751:
----------------------------------------
Presumably, this is the same issue I'm seeing on 8.0.0.CR1:
{noformat}
18:13:47,100 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."service-impl-bundle-0.0.1-SNAPSHOT.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."service-impl-bundle-0.0.1-SNAPSHOT.jar".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "service-impl-bundle-0.0.1-SNAPSHOT.jar"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.CR1.jar:8.0.0.CR1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.CR1.jar:1.2.0.CR1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.CR1.jar:1.2.0.CR1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
Caused by: java.lang.NullPointerException
at org.jboss.as.ee.concurrent.deployers.EEConcurrentContextProcessor.processModuleDescription(EEConcurrentContextProcessor.java:71)
at org.jboss.as.ee.concurrent.deployers.EEConcurrentContextProcessor.deploy(EEConcurrentContextProcessor.java:54)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.CR1.jar:8.0.0.CR1]
{noformat}
The NPE is caused by {{deploymentUnit.getAttachment(MODULE)}} being null.
> Fragment deployment fails in 8.0.0.Beta1
> ----------------------------------------
>
> Key: JBOSGI-751
> URL: https://issues.jboss.org/browse/JBOSGI-751
> Project: JBoss OSGi
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: wildfly
> Reporter: Thomas Diesler
>
--
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-760) Include configadmin subsystem
by Harald Wellmann (JIRA)
Harald Wellmann created JBOSGI-760:
--------------------------------------
Summary: Include configadmin subsystem
Key: JBOSGI-760
URL: https://issues.jboss.org/browse/JBOSGI-760
Project: JBoss OSGi
Issue Type: Task
Security Level: Public (Everyone can see)
Components: wildfly
Affects Versions: JBossOSGi 2.1.1
Reporter: Harald Wellmann
The configadmin subsystem has been deleted from WildFly between 8.0.0.CR1 and 8.0.0.Final.
It should be included in the JBossOSGi-WildFly integration.
--
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-759) PackageAdmin fails to return exported packages
by Harald Wellmann (JIRA)
Harald Wellmann created JBOSGI-759:
--------------------------------------
Summary: PackageAdmin fails to return exported packages
Key: JBOSGI-759
URL: https://issues.jboss.org/browse/JBOSGI-759
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: framework
Affects Versions: JBossOSGi 2.1.1
Reporter: Harald Wellmann
PackageAdmin always returns null for getExportedPackages(...).
This breaks Felix Webconsole and other consumers of PackageAdmin.
--
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-758) Java Activation API Module prevents use of Java Mail API in JBoss OSGI
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-758?page=com.atlassian.jira.plugin... ]
Tomaz Cerar moved WFLY-927 to JBOSGI-758:
-----------------------------------------
Project: JBoss OSGi (was: WildFly)
Key: JBOSGI-758 (was: WFLY-927)
Workflow: classic default workflow (was: GIT Pull Request workflow )
> Java Activation API Module prevents use of Java Mail API in JBoss OSGI
> ----------------------------------------------------------------------
>
> Key: JBOSGI-758
> URL: https://issues.jboss.org/browse/JBOSGI-758
> Project: JBoss OSGi
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: jdk-u32, jboss-as-7.1.1.Final, Windows XP
> Reporter: Ed Roberts
> Labels: activation, mistake, module, osgi
>
> The module.xml content for javax.activation.api prevents the ability to expose it and the javax.mail.api modules to the JBoss OSGi container.
> Inside the module.xml there is a dependency declaration on javax.mail and an embedded import statement that includes everything beneath META-INF. This statement is including the Manifest.mf which causes the OSGi container to believe the activation bundle is the mail bundle.
> Adding additional exclude or exclude-set statements does not alter the include in any way. Some documentation explaining the relation between these sibling elements within the module schema would help, and inclusion of the module schema in the jboss as distribution also.
> 2012-07-17 10:11:47,182 ERROR [org.eclipse.gemini.blueprint.extender.internal.activator.ContextLoaderListener](EclipseGeminiBlueprintExtenderThread-5) Application context refresh failed (OsgiBundleXmlApplicationContext(bundle=my-svc, config=osgibundle:/META-INF/spring/*.xml)): org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'myService': Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'myBean' defined in URL [bundle://my.svc-44-0-0/META-INF/spring/osgi.xml]: Instantiation of bean failed; nested exception is java.lang.NoClassDefFoundError: javax/mail/MessagingException
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1455)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
> at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)
> at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)
> at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)
> at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
> at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:567)
> at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:913)
> at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecutionApplicationContext.java:60)
> at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:325)
> at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
> at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:290)
> at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:137)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'myBean' defined in URL [bundle://my.svc-44-0-0/META-INF/spring/osgi.xml]: Instantiation of bean failed; nested exception is java.lang.NoClassDefFoundError: javax/mail/MessagingException
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:997)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:943)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
> at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)
> at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)
> at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)
> at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
> at org.eclipse.gemini.blueprint.service.exporter.support.OsgiServiceFactoryBean.afterPropertiesSet(OsgiServiceFactoryBean.java:198)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1514)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1452)
> ... 14 more
> Caused by: java.lang.NoClassDefFoundError: javax/mail/MessagingException
> at java.lang.Class.getDeclaredConstructors0(Native Method)
> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
> at java.lang.Class.getConstructor0(Class.java:2699)
> at java.lang.Class.getDeclaredConstructor(Class.java:1985)
> at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:67)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:990)
> ... 24 more
> Caused by: java.lang.ClassNotFoundException: javax.mail.MessagingException from [Module "deployment.my-svc:1.0.0.SNAPSHOT" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
> 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)
> ... 30 more
--
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