July 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1125) Karaf configuration through ConfigAdmin

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1125?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened WFLY-1125: ---------------------------------- > Karaf configuration through ConfigAdmin > --------------------------------------- > > Key: WFLY-1125 > URL: https://issues.jboss.org/browse/WFLY-1125 > Project: WildFly > Issue Type: Feature Request > Components: OSGi > Reporter: Thomas Diesler > > Currently we add these props to standalone.conf > {code} > -Dkaraf.home=.../jboss-as-karaf-7.2.0.Alpha1-SNAPSHOT/standalone/data/karaf -Dkaraf.base=.../jboss-as-karaf-7.2.0.Alpha1-SNAPSHOT/standalone/data/karaf -Dkaraf.startRemoteShell=true -Dkaraf.startLocalConsole=false > {code} > For this we should have sensible defaults as well as make the SSH port (and possibly other options) configurable through ConfigAdmin -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1504) Unusable wiring metadata for Apache-CXF

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1504?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened WFLY-1504: ---------------------------------- > Unusable wiring metadata for Apache-CXF > --------------------------------------- > > Key: WFLY-1504 > URL: https://issues.jboss.org/browse/WFLY-1504 > Project: WildFly > Issue Type: Bug > Components: OSGi, Web Services > Reporter: Thomas Diesler > > When integrating the [camel-cxf|http://camel.apache.org/cxf.html] component we see a number of package requirements on cxf > {code} > XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.apache.cxf)(&(version>=2.6.0)(!(version>=2.9.0))))},[org.apache.camel.camel-cxf-transport:2.11.0]] > XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.apache.cxf.binding.soap)(&(version>=2.6.0)(!(version>=2.9.0))))},[org.apache.camel.camel-cxf-transport:2.11.0]] > XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.apache.cxf.common.injection)(&(version>=2.6.0)(!(version>=2.9.0))))},[org.apache.camel.camel-cxf-transport:2.11.0]] > XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.apache.cxf.common.logging)(&(version>=2.6.0)(!(version>=2.9.0))))},[org.apache.camel.camel-cxf-transport:2.11.0]] > XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.apache.cxf.common.util)(&(version>=2.6.0)(!(version>=2.9.0))))},[org.apache.camel.camel-cxf-transport:2.11.0]] > XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.apache.cxf.configuration)(&(version>=2.6.0)(!(version>=2.9.0))))},[org.apache.camel.camel-cxf-transport:2.11.0]] > XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.apache.cxf.configuration.blueprint)(&(version>=2.6.0)(!(version>=2.9.0))))},[org.apache.camel.camel-cxf-transport:2.11.0]] > XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.apache.cxf.configuration.spring)(&(version>=2.6.0)(!(version>=2.9.0))))},[org.apache.camel.camel-cxf-transport:2.11.0]] > XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.apache.cxf.headers)(&(version>=2.6.0)(!(version>=2.9.0))))},[org.apache.camel.camel-cxf-transport:2.11.0]] > XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.apache.cxf.helpers)(&(version>=2.6.0)(!(version>=2.9.0))))},[org.apache.camel.camel-cxf-transport:2.11.0]] > XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.apache.cxf.io)(&(version>=2.6.0)(!(version>=2.9.0))))},[org.apache.camel.camel-cxf-transport:2.11.0]] > XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.apache.cxf.message)(&(version>=2.6.0)(!(version>=2.9.0))))},[org.apache.camel.camel-cxf-transport:2.11.0]] > XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.apache.cxf.service.model)(&(version>=2.6.0)(!(version>=2.9.0))))},[org.apache.camel.camel-cxf-transport:2.11.0]] > XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.apache.cxf.transport)(&(version>=2.6.0)(!(version>=2.9.0))))},[org.apache.camel.camel-cxf-transport:2.11.0]] > XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.apache.cxf.ws.addressing)(&(version>=2.6.0)(!(version>=2.9.0))))},[org.apache.camel.camel-cxf-transport:2.11.0]] > XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.apache.cxf.wsdl)(&(version>=2.6.0)(!(version>=2.9.0))))},[org.apache.camel.camel-cxf-transport:2.11.0]] > {code} > most of these are contained in the org.apache.cxf.impl module, which however takes a "one bucket for all approach" that makes it impossible to use the metadata shipped with the individual cxf artefacts > {code} > <resources> > <resource-root path="cxf-rt-bindings-coloc-2.7.5.jar"/> > <resource-root path="cxf-rt-bindings-object-2.7.5.jar"/> > <resource-root path="cxf-rt-bindings-soap-2.7.5.jar"/> > <resource-root path="cxf-rt-bindings-xml-2.7.5.jar"/> > <resource-root path="cxf-rt-core-2.7.5.jar"/> > <resource-root path="cxf-rt-databinding-aegis-2.7.5.jar"/> > <resource-root path="cxf-rt-databinding-jaxb-2.7.5.jar"/> > <resource-root path="cxf-rt-frontend-jaxws-2.7.5.jar"/> > <resource-root path="cxf-rt-frontend-simple-2.7.5.jar"/> > <resource-root path="cxf-rt-management-2.7.5.jar"/> > <resource-root path="cxf-rt-transports-http-2.7.5.jar"/> > <resource-root path="cxf-rt-transports-jms-2.7.5.jar"/> > <resource-root path="cxf-rt-transports-local-2.7.5.jar"/> > <resource-root path="cxf-rt-ws-addr-2.7.5.jar"/> > <resource-root path="cxf-rt-ws-mex-2.7.5.jar"/> > <resource-root path="cxf-rt-ws-policy-2.7.5.jar"/> > <resource-root path="cxf-rt-ws-rm-2.7.5.jar"/> > <resource-root path="cxf-rt-ws-security-2.7.5.jar"/> > <resource-root path="cxf-rt-ws-security-2.7.5-jandex.jar"/> > <resource-root path="cxf-tools-common-2.7.5.jar"/> > <resource-root path="cxf-tools-java2ws-2.7.5.jar"/> > <resource-root path="cxf-tools-validator-2.7.5.jar"/> > <resource-root path="cxf-tools-wsdlto-core-2.7.5.jar"/> > <resource-root path="cxf-tools-wsdlto-databinding-jaxb-2.7.5.jar"/> > <resource-root path="cxf-tools-wsdlto-frontend-jaxws-2.7.5.jar"/> > <resource-root path="cxf-services-sts-core-2.7.5.jar"/> > <resource-root path="cxf-services-ws-discovery-api-2.7.5.jar"/> > <resource-root path="cxf-xjc-boolean-2.6.1.jar"/> > <resource-root path="cxf-xjc-dv-2.6.1.jar"/> > <resource-root path="cxf-xjc-ts-2.6.1.jar"/> >  > </resources> > {code} > A possible fix would be to separate and reexport the modules that camel-cxf integrates with -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1566) Add test coverage for ResourceProvisioner service

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1566?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened WFLY-1566: ---------------------------------- Assignee: (was: Thomas Diesler) > Add test coverage for ResourceProvisioner service > ------------------------------------------------- > > Key: WFLY-1566 > URL: https://issues.jboss.org/browse/WFLY-1566 > Project: WildFly > Issue Type: Task > Components: OSGi > 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

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1222) Allign deployment phases with OSGi terminology

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1222?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened WFLY-1222: ---------------------------------- > Allign deployment phases with OSGi terminology > ---------------------------------------------- > > Key: WFLY-1222 > URL: https://issues.jboss.org/browse/WFLY-1222 > Project: WildFly > Issue Type: Task > Components: OSGi, Server > Reporter: Thomas Diesler > > In OSGi we have > * INSTALLED > * RESOLVED > * ACTIVE > * UNINSTALLED > It'd be useful to talk about modules and osgi bundles in the same jagon - i.e > If a deployment is INSTALLED it has valid metadata > If a deployment is RESOLVED it has Module/ClassLoader associated > If a deployment is ACTIVE it can perform its normal operation > If a deployment is UNINSTALLED it can be removed from the system > The task here is mainly to rename/revisit the deployment phases -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1342) Separate feature provisioning service from OSGi

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1342?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened WFLY-1342: ---------------------------------- Assignee: (was: Thomas Diesler) > Separate feature provisioning service from OSGi > ------------------------------------------------ > > Key: WFLY-1342 > URL: https://issues.jboss.org/browse/WFLY-1342 > Project: WildFly > Issue Type: Task > Components: OSGi > 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

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1226) Populate repository with metadata from system modules/bundles

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1226?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened WFLY-1226: ---------------------------------- > Populate repository with metadata from system modules/bundles > ------------------------------------------------------------- > > Key: WFLY-1226 > URL: https://issues.jboss.org/browse/WFLY-1226 > Project: WildFly > Issue Type: Task > Components: OSGi, Server > Reporter: Thomas Diesler > > The OSGi configuration supports ModuleIdentifiers. So for example > {code} > <capability name="javax.transaction.api"/> > {code} > references the JTA API module. This actually delegates to the repository implementations which in turn delegates to the ModuleIdentityArtifactProvider. > If the AppServer supports the notion of multiple directories where modules can get loaded from, the ServerEnvironment should reflect that properly. I cannot just load a module on trial/error basis because we use the Repository for impact ananlysis. i.e. Find the modules/bundles that provide the transitive set of capabilities for a given set of requirements (without modifying the runtime). -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1187) Allow OSGi configuration to get modified before subsystem start

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1187?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened WFLY-1187: ---------------------------------- > Allow OSGi configuration to get modified before subsystem start > --------------------------------------------------------------- > > Key: WFLY-1187 > URL: https://issues.jboss.org/browse/WFLY-1187 > Project: WildFly > Issue Type: Feature Request > Components: OSGi > Reporter: Thomas Diesler > > It should be possible to > * start the server > * modify framework properties > * start the osgi subsystem with the updated properties -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1567) Add ability to provision adapted modules

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1567?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened WFLY-1567: ---------------------------------- Assignee: (was: Thomas Diesler) > Add ability to provision adapted modules > ---------------------------------------- > > Key: WFLY-1567 > URL: https://issues.jboss.org/browse/WFLY-1567 > Project: WildFly > Issue Type: Feature Request > Components: OSGi > 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

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-992) Cannot restart ejb3 bundle after activation failure

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-992?page=com.atlassian.jira.plugin.s... ] Thomas Diesler reopened WFLY-992: --------------------------------- Assignee: (was: Bartosz Baranowski) > Cannot restart ejb3 bundle after activation failure > --------------------------------------------------- > > Key: WFLY-992 > URL: https://issues.jboss.org/browse/WFLY-992 > Project: WildFly > Issue Type: Bug > Components: EJB, OSGi > 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

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1257) Http Service TCK testLongRegistrationName() failing

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1257?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened WFLY-1257: ---------------------------------- > Http Service TCK testLongRegistrationName() failing > --------------------------------------------------- > > Key: WFLY-1257 > URL: https://issues.jboss.org/browse/WFLY-1257 > Project: WildFly > Issue Type: Sub-task > Components: OSGi > Reporter: David Bosschaert > > The OSGi HTTP Service TCK test testLongRegistrationName() fails with the following exception: > java.io.FileNotFoundException: http://localhost:8080/abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxy... > Apparently there is an issue with long registration names. -- 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

13 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2013