[JBoss JIRA] Created: (AS7-861) resource-description for root-logger in subsystem=looging is incomplete
by Heiko Rupp (JIRA)
resource-description for root-logger in subsystem=looging is incomplete
-----------------------------------------------------------------------
Key: AS7-861
URL: https://issues.jboss.org/browse/AS7-861
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Reporter: Heiko Rupp
Assignee: Jason Greene
[domain@localhost:9999 subsystem=logging] :read-resource-description(recursive=true)
{
"outcome" => "success",
"result" => {
"description" => "The configuration of the logging subsystem.",
"head-comment-allowed" => true,
"tail-comment-allowed" => true,
"namespace" => "urn:jboss:domain:logging:1.0",
"operations" => undefined,
"children" => {
"root-logger" => {"description" => "Defines the root logger for this log context."},
and
[domain@localhost:9999 subsystem=logging] :read-resource(recursive=true)
{
"outcome" => "success",
"result" => {
"root-logger" => {
"level" => "INFO",
"handlers" => [
"CONSOLE",
"FILE"
]
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (AS7-1004) "failed to resolve interface default" if default interface inet-address value set to a local address other than 127.0.0.1
by Marek Schmidt (JIRA)
"failed to resolve interface default" if default interface inet-address value set to a local address other than 127.0.0.1
-------------------------------------------------------------------------------------------------------------------------
Key: AS7-1004
URL: https://issues.jboss.org/browse/AS7-1004
Project: Application Server 7
Issue Type: Bug
Environment: Fedora 15, Sun JDK 1.6.0_24-b07, jboss-7.0.0.Beta4-SNAPSHOT-1194, standalone
Reporter: Marek Schmidt
Setting the "default" interface to, e.g.:
{code}
<interface name="default">
<inet-address value="127.0.1.1"/>
</interface>
{code}
throws the following exception at startup, even if the 127.0.1.1 address is set up in /etc/hosts (not that it should matter)
I have noticed there exists a loopback-address element which seems to work, but I fail to see why this one shouldn't.
{quote}
12:06:18,660 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.network.default: org.jboss.msc.service.StartException in service jboss.network.default: failed to resolve interface default
at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:106) [jboss-as-server-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (JBAS-8132) Utility to report on differences in domain configuration between domains
by Brian Stansberry (JIRA)
Utility to report on differences in domain configuration between domains
------------------------------------------------------------------------
Key: JBAS-8132
URL: https://jira.jboss.org/browse/JBAS-8132
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Fix For: Unscheduled
This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010:
One of the motivations for the domain controller was to help customers manage drift in their JBoss configurations. Because of operational concerns, specifically datacenter isolation, some customers expect to need to run multiple identical domain controllers. They would then still be faced with drift across domain controllers. A utility to detect this drift would be helpful.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (AS7-2394) Deployment of a bundle that imports javax.servlet [2.3, 2.6) fails while the bundle itself exports javax.servlet 2.5
by David Bosschaert (Created) (JIRA)
Deployment of a bundle that imports javax.servlet [2.3,2.6) fails while the bundle itself exports javax.servlet 2.5
-------------------------------------------------------------------------------------------------------------------
Key: AS7-2394
URL: https://issues.jboss.org/browse/AS7-2394
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.1.0.Beta1
Reporter: David Bosschaert
Assignee: Thomas Diesler
Deploy the pax-web-service ( https://issues.jboss.org/secure/attachment/12348289/pax-web-service-0.5.1... ) into a default build of AS7 and you get the following exception:
{code}14:08:30,891 DEBUG [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Deployment scan of [/Users/david/clones/bosschaert_jboss-as_171011/build/target/jboss-as-7.1.0.Alpha2-SNAPSHOT/standalone/deployments] found update action [{
"operation" => "composite",
"address" => undefined,
"steps" => [
{
"operation" => "add",
"address" => [("deployment" => "pax-web-service-0.5.1.jar")],
"content" => [{
"path" => "deployments/pax-web-service-0.5.1.jar",
"relative-to" => "jboss.server.base.dir",
"archive" => true
}],
"persistent" => false
},
{
"operation" => "deploy",
"address" => [("deployment" => "pax-web-service-0.5.1.jar")]
}
]
}]
14:08:30,900 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) Starting deployment of "pax-web-service-0.5.1.jar"
14:08:31,000 DEBUG [org.jboss.as.server.deployment.module] (MSC service thread 1-2) Found Extension-Name manifest entry null in /content/pax-web-service-0.5.1.jar
14:08:31,015 DEBUG [org.jboss.as.jpa] (MSC service thread 1-6) added javax.persistence.api dependency to pax-web-service-0.5.1.jar
14:08:31,035 DEBUG [org.jboss.as.osgi] (MSC service thread 1-13) Starting: service jboss.osgi.deployment."pax-web-service-0.5.1.jar" in mode ACTIVE
14:08:31,044 DEBUG [org.jboss.osgi.framework.internal.AbstractBundleService] (MSC service thread 1-8) Starting: service jbosgi.bundle.23."org.ops4j.pax.web.service"."0.5.1".INSTALLED in mode ACTIVE
14:08:31,047 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-8) Install bundle: org.ops4j.pax.web.service:0.5.1
14:08:31,057 DEBUG [org.jboss.osgi.resolver.felix.LoggerDelegate] (MSC service thread 1-16) Conflict between imports: org.apache.felix.framework.resolver.ResolveException: Constraint violation for package 'javax.servlet' when resolving module Module[org.ops4j.pax.web.service:0.5.1] between existing import Module[org.ops4j.pax.web.service:0.5.1].javax.servlet BLAMED ON [[Module[org.ops4j.pax.web.service:0.5.1]] package; (&(package=javax.servlet)(version>=2.3.0)(!(version>=2.6.0)))] and uses constraint Module[javax.servlet.api:0.0.0].javax.servlet BLAMED ON [[Module[org.ops4j.pax.web.service:0.5.1]] package; (&(package=org.ops4j.pax.web.service)(version>=0.5.1)), [Module[jbosgi-http:1.0.5]] package; (&(package=javax.servlet)(version>=2.5.0)(!(version>=4.0.0)))]
at org.apache.felix.framework.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1013) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.apache.felix.framework.resolver.ResolverImpl.resolve(ResolverImpl.java:106) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.ResolverExt.resolve(ResolverExt.java:48) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:140) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:110) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148) [jbosgi-resolver-spi-1.0.10.jar:1.0.10]
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:144) [jboss-as-osgi-service-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:119) [jboss-as-osgi-service-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1429) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl.access$2600(ServiceControllerImpl.java:49) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1952) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_26]
14:08:31,059 DEBUG [org.jboss.osgi.resolver.felix.LoggerDelegate] (MSC service thread 1-16) [org.ops4j.pax.web.service:0.5.1] Current candidate permutation failed, will try another if possible.: org.apache.felix.framework.resolver.ResolveException: Constraint violation for package 'javax.servlet' when resolving module Module[org.ops4j.pax.web.service:0.5.1] between existing import Module[org.ops4j.pax.web.service:0.5.1].javax.servlet BLAMED ON [[Module[org.ops4j.pax.web.service:0.5.1]] package; (&(package=javax.servlet)(version>=2.3.0)(!(version>=2.6.0)))] and uses constraint Module[javax.servlet.api:0.0.0].javax.servlet BLAMED ON [[Module[org.ops4j.pax.web.service:0.5.1]] package; (&(package=org.ops4j.pax.web.service)(version>=0.5.1)), [Module[jbosgi-http:1.0.5]] package; (&(package=javax.servlet)(version>=2.5.0)(!(version>=4.0.0)))]
at org.apache.felix.framework.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1013) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.apache.felix.framework.resolver.ResolverImpl.resolve(ResolverImpl.java:106) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.ResolverExt.resolve(ResolverExt.java:48) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:140) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:110) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148) [jbosgi-resolver-spi-1.0.10.jar:1.0.10]
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:144) [jboss-as-osgi-service-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:119) [jboss-as-osgi-service-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1429) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl.access$2600(ServiceControllerImpl.java:49) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1952) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_26]
14:08:31,064 DEBUG [org.jboss.osgi.resolver.felix.LoggerDelegate] (MSC service thread 1-16) Conflict between imports: org.apache.felix.framework.resolver.ResolveException: Constraint violation for package 'javax.servlet' when resolving module Module[org.ops4j.pax.web.service:0.5.1] between existing import Module[org.ops4j.pax.web.service:0.5.1].javax.servlet BLAMED ON [[Module[org.ops4j.pax.web.service:0.5.1]] package; (&(package=javax.servlet)(version>=2.3.0)(!(version>=2.6.0)))] and uses constraint Module[javax.servlet.api:0.0.0].javax.servlet BLAMED ON [[Module[org.ops4j.pax.web.service:0.5.1]] package; (&(package=org.osgi.service.http)(version>=1.0.0)(!(version>=2.0.0))), [Module[osgi.cmpn:4.2.0.200908310645]] package; (package=javax.servlet)]
at org.apache.felix.framework.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1013) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.apache.felix.framework.resolver.ResolverImpl.resolve(ResolverImpl.java:106) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.ResolverExt.resolve(ResolverExt.java:48) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:140) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:110) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148) [jbosgi-resolver-spi-1.0.10.jar:1.0.10]
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:144) [jboss-as-osgi-service-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:119) [jboss-as-osgi-service-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1429) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl.access$2600(ServiceControllerImpl.java:49) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1952) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_26]
14:08:31,065 DEBUG [org.jboss.osgi.resolver.felix.LoggerDelegate] (MSC service thread 1-16) [org.ops4j.pax.web.service:0.5.1] Current candidate permutation failed, will try another if possible.: org.apache.felix.framework.resolver.ResolveException: Constraint violation for package 'javax.servlet' when resolving module Module[org.ops4j.pax.web.service:0.5.1] between existing import Module[org.ops4j.pax.web.service:0.5.1].javax.servlet BLAMED ON [[Module[org.ops4j.pax.web.service:0.5.1]] package; (&(package=javax.servlet)(version>=2.3.0)(!(version>=2.6.0)))] and uses constraint Module[javax.servlet.api:0.0.0].javax.servlet BLAMED ON [[Module[org.ops4j.pax.web.service:0.5.1]] package; (&(package=org.osgi.service.http)(version>=1.0.0)(!(version>=2.0.0))), [Module[osgi.cmpn:4.2.0.200908310645]] package; (package=javax.servlet)]
at org.apache.felix.framework.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1013) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.apache.felix.framework.resolver.ResolverImpl.resolve(ResolverImpl.java:106) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.ResolverExt.resolve(ResolverExt.java:48) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:140) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:110) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148) [jbosgi-resolver-spi-1.0.10.jar:1.0.10]
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:144) [jboss-as-osgi-service-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:119) [jboss-as-osgi-service-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1429) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl.access$2600(ServiceControllerImpl.java:49) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1952) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_26]
14:08:31,067 ERROR [org.jboss.osgi.framework.internal.FrameworkEventsPlugin] (MSC service thread 1-16) Framework ERROR: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [org.ops4j.pax.web.service:0.5.1]
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:157) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:144) [jboss-as-osgi-service-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:119) [jboss-as-osgi-service-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1429) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl.access$2600(ServiceControllerImpl.java:49) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1952) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_26]
Caused by: org.jboss.osgi.resolver.XResolverException: Constraint violation for package 'javax.servlet' when resolving module Module[org.ops4j.pax.web.service:0.5.1] between existing import Module[org.ops4j.pax.web.service:0.5.1].javax.servlet BLAMED ON [[Module[org.ops4j.pax.web.service:0.5.1]] package; (&(package=javax.servlet)(version>=2.3.0)(!(version>=2.6.0)))] and uses constraint Module[javax.servlet.api:0.0.0].javax.servlet BLAMED ON [[Module[org.ops4j.pax.web.service:0.5.1]] package; (&(package=org.osgi.service.http)(version>=1.0.0)(!(version>=2.0.0))), [Module[osgi.cmpn:4.2.0.200908310645]] package; (package=javax.servlet)]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148) [jbosgi-resolver-spi-1.0.10.jar:1.0.10]
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155) [jbosgi-framework-core-1.0.1.jar:1.0.1]
... 11 more
14:08:31,068 ERROR [org.jboss.as.osgi] (MSC service thread 1-16) JBAS011912: Cannot start bundle: org.ops4j.pax.web.service:0.5.1: org.osgi.framework.BundleException: Cannot resolve bundle: org.ops4j.pax.web.service:0.5.1
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:212) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:144) [jboss-as-osgi-service-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:119) [jboss-as-osgi-service-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1429) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl.access$2600(ServiceControllerImpl.java:49) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1952) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_26]
14:08:31,068 ERROR [org.ops4j.pax.web.service] (Thread-27) FrameworkEvent ERROR: org.apache.felix.log.LogException: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [org.ops4j.pax.web.service:0.5.1]
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:157)
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551)
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211)
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494)
at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:144)
at org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:119)
at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1429)
at org.jboss.msc.service.ServiceControllerImpl.access$2600(ServiceControllerImpl.java:49)
at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1952)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_26]
Caused by: org.apache.felix.log.LogException: org.jboss.osgi.resolver.XResolverException: Constraint violation for package 'javax.servlet' when resolving module Module[org.ops4j.pax.web.service:0.5.1] between existing import Module[org.ops4j.pax.web.service:0.5.1].javax.servlet BLAMED ON [[Module[org.ops4j.pax.web.service:0.5.1]] package; (&(package=javax.servlet)(version>=2.3.0)(!(version>=2.6.0)))] and uses constraint Module[javax.servlet.api:0.0.0].javax.servlet BLAMED ON [[Module[org.ops4j.pax.web.service:0.5.1]] package; (&(package=org.osgi.service.http)(version>=1.0.0)(!(version>=2.0.0))), [Module[osgi.cmpn:4.2.0.200908310645]] package; (package=javax.servlet)]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117)
at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148)
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155)
... 11 more
{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
13 years
[JBoss JIRA] (JBRULES-3271) Make rule context available to enumeration loaders
by G Patel (Created) (JIRA)
Make rule context available to enumeration loaders
--------------------------------------------------
Key: JBRULES-3271
URL: https://issues.jboss.org/browse/JBRULES-3271
Project: Drools
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: G Patel
Assignee: Mark Proctor
Currently, only fact field names are passed into data enumeration loaders. Sometimes, the enumeration list might need to change based on details about the rule being edited, like rule metadata or package name, etc. The request is to make the Rule object (along with all of it's metadata) available to data enumeration loaders. Perhaps have loaders implement the following interface:
public interface EnumLoader{
public List<String> loadEnum(Rule r, String... dependentFields);
}
This will enable support for more contextual enum lists. Very helpful for folks trying to integrate the standalone rule editor into applications.
--
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
13 years