July 2013 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] (JBOSGI-669) Cannot update OSGi WebApp

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-669?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-669: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Cannot update OSGi WebApp > ------------------------- > > Key: JBOSGI-669 > URL: https://issues.jboss.org/browse/JBOSGI-669 > Project: JBoss OSGi > Issue Type: Bug > 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-668) Attribute read for uninstalled bundle breaks console

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-668?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-668: ---------------------------------- Labels: (was: Console) > Attribute read for uninstalled bundle breaks console > ---------------------------------------------------- > > Key: JBOSGI-668 > URL: https://issues.jboss.org/browse/JBOSGI-668 > Project: JBoss OSGi > Issue Type: Bug > Reporter: Thomas Diesler > Attachments: unread_bundle_stacktrace.txt, unread_bundle_stacktrace_cli.txt > > -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-668) Attribute read for uninstalled bundle breaks console

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-668?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-668: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Attribute read for uninstalled bundle breaks console > ---------------------------------------------------- > > Key: JBOSGI-668 > URL: https://issues.jboss.org/browse/JBOSGI-668 > Project: JBoss OSGi > Issue Type: Bug > Reporter: Thomas Diesler > Attachments: unread_bundle_stacktrace.txt, unread_bundle_stacktrace_cli.txt > > -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-676) OSGi console allows start/stop on system bundle

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-676?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-676. ----------------------------------- Resolution: Won't Fix > OSGi console allows start/stop on system bundle > ----------------------------------------------- > > Key: JBOSGI-676 > URL: https://issues.jboss.org/browse/JBOSGI-676 > Project: JBoss OSGi > Issue Type: Bug > Reporter: Thomas Diesler > Labels: Console > > Start/Stop on the system bundle are invalid operations -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-675) Cannot replace jar that bundle depends on

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-675?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-675: ---------------------------------- Component/s: WildFly > Cannot replace jar that bundle depends on > ----------------------------------------- > > Key: JBOSGI-675 > URL: https://issues.jboss.org/browse/JBOSGI-675 > Project: JBoss OSGi > Issue Type: Bug > Components: WildFly > Reporter: Thomas Diesler > > With an OSGi webapp that depends on a jar the jar cannot be replaced. > See BundleReplaceTestCase.testDependentJarReplace() -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-675) Cannot replace jar that bundle depends on

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-675?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-675: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Cannot replace jar that bundle depends on > ----------------------------------------- > > Key: JBOSGI-675 > URL: https://issues.jboss.org/browse/JBOSGI-675 > Project: JBoss OSGi > Issue Type: Bug > Reporter: Thomas Diesler > > With an OSGi webapp that depends on a jar the jar cannot be replaced. > See BundleReplaceTestCase.testDependentJarReplace() -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-670) OSGi: "Web-ContextPath" header is not supported to install/start WAB bundle from repository

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-670?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-670. ----------------------------------- Resolution: Duplicate Issue Duplicates JBOSGI-667 > OSGi: "Web-ContextPath" header is not supported to install/start WAB bundle from repository > ------------------------------------------------------------------------------------------- > > Key: JBOSGI-670 > URL: https://issues.jboss.org/browse/JBOSGI-670 > Project: JBoss OSGi > Issue Type: Bug > Reporter: Igor Shulika > > I am using the latest WildFly 8.0.0.Alpha2-SNAPSHOT server to install/start all of my OSGi bundles from Maven repository. The WAB is not starting if I am just declare capability in the standalone-osgi.xml file. > > Here is my capability configuration. > <capability name="org.test.sample.webapp:my-sample-webapp:1.0" startlevel="4"/> > > Note: When I just simply drop my WAB file inside "deployments" directory the web application starting successfully. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-674) Cannot restart ejb3 bundle after activation failure

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-674?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-674: ---------------------------------- Component/s: WildFly > Cannot restart ejb3 bundle after activation failure > --------------------------------------------------- > > Key: JBOSGI-674 > URL: https://issues.jboss.org/browse/JBOSGI-674 > Project: JBoss OSGi > Issue Type: Bug > Components: EJB3, WildFly > Reporter: Thomas Diesler > > {code} > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011030: Could not configure component SampleSFSB > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:91) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > ... 5 more > Caused by: java.lang.IllegalArgumentException: JBAS011085: Can't add org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor$Factory@6f9e0e7b, priority 0x500 is already taken by org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor$Factory@6f9e0e7b > at org.jboss.as.ee.component.interceptors.OrderedItemContainer.add(OrderedItemContainer.java:58) > at org.jboss.as.ee.component.ComponentConfiguration.addComponentInterceptor(ComponentConfiguration.java:181) > at org.jboss.as.ejb3.component.stateful.StatefulComponentDescription$2.configure(StatefulComponentDescription.java:153) > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:80) > {code} -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-674) Cannot restart ejb3 bundle after activation failure

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-674?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-674: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Cannot restart ejb3 bundle after activation failure > --------------------------------------------------- > > Key: JBOSGI-674 > URL: https://issues.jboss.org/browse/JBOSGI-674 > Project: JBoss OSGi > Issue Type: Bug > Components: EJB3, WildFly > Reporter: Thomas Diesler > > {code} > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011030: Could not configure component SampleSFSB > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:91) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > ... 5 more > Caused by: java.lang.IllegalArgumentException: JBAS011085: Can't add org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor$Factory@6f9e0e7b, priority 0x500 is already taken by org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor$Factory@6f9e0e7b > at org.jboss.as.ee.component.interceptors.OrderedItemContainer.add(OrderedItemContainer.java:58) > at org.jboss.as.ee.component.ComponentConfiguration.addComponentInterceptor(ComponentConfiguration.java:181) > at org.jboss.as.ejb3.component.stateful.StatefulComponentDescription$2.configure(StatefulComponentDescription.java:153) > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:80) > {code} -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-671) Cannot get bytes from InputStream for DEPLOYMENT_ROOT VirtualFile.openStream() on second call

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-671?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-671: ---------------------------------- Component/s: WildFly > Cannot get bytes from InputStream for DEPLOYMENT_ROOT VirtualFile.openStream() on second call > --------------------------------------------------------------------------------------------- > > Key: JBOSGI-671 > URL: https://issues.jboss.org/browse/JBOSGI-671 > Project: JBoss OSGi > Issue Type: Bug > Components: WildFly > Reporter: Thomas Diesler > > The effect is that the copy of a installed OSGi bundle is 0bytes in the data/osgi-store area > Digging into this shows that during the first call isDirectory() is false and the file gets mounted. The returned stream works fine. For the second call isDirectory() is true and e read() on the returned InputStream returns -1 > {code} > public InputStream openStream() throws IOException { > if(isDirectory()) { > return new VirtualJarInputStream(this); > } > final VFS.Mount mount = VFS.getMount(this); > return mount.getFileSystem().openInputStream(mount.getMountPoint(), this); > } > {code} > I assume that the root VirtualFile > {code} > VirtualFile virtualFile = deploymentUnit.getAttachment(Attachments.DEPLOYMENT_ROOT).getRoot(); > {code} > should be readable twice. -- 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

12 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues July 2013