January 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-396) Caused by: java.lang.NoClassDefFoundError: org/drools/event/DebugProcessEventListener

by leonardo lizana (JIRA)

leonardo lizana created DROOLS-396: -------------------------------------- Summary: Caused by: java.lang.NoClassDefFoundError: org/drools/event/DebugProcessEventListener Key: DROOLS-396 URL: https://issues.jboss.org/browse/DROOLS-396 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final Reporter: leonardo lizana Assignee: Mark Proctor Priority: Critical I'm trying to testing latest version of drools 6.0.1.Final version and i have the issue of " java.lang.NoClassDefFoundError: org/drools/event/DebugProcessEventListener" . However, i can see the class is on the the following path "org.drools.core.event.DebugProcessEventListener" and why the context is seeking in org/drools/event/DebugProcessEventListener. is there anything that i'm doing bad? * with drools 5.5 everything is working OK. Here is my pom.xml -------------------------- <dependency> <groupId>org.drools</groupId> <artifactId>knowledge-api</artifactId> <version>${drools.version}</version> </dependency> <dependency> <groupId>org.drools</groupId> <artifactId>drools-core</artifactId> <version>${drools.version}</version> </dependency> <dependency> <groupId>org.drools</groupId> <artifactId>drools-compiler</artifactId> <version>${drools.version}</version> </dependency> <dependency> <groupId>org.drools</groupId> <artifactId>drools-spring</artifactId> <version>5.5.0.Final</version> </dependency> here is the log error: ---------------------------- Caused by: java.lang.NoClassDefFoundError: org/drools/event/DebugProcessEventListener at org.drools.container.spring.namespace.KnowledgeSessionDefinitionParser.parseInternal(KnowledgeSessionDefinitionParser.java:115) at org.springframework.beans.factory.xml.AbstractBeanDefinitionParser.parse(AbstractBeanDefinitionParser.java:59) at org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:73) at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1338) at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1328) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:135) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:93) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:493) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:390) Here is the contex-drools.xml ------------------------------------- <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:context="http://www.springframework.org/schema/context" xmlns:drools="http://drools.org/schema/drools-spring" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.0.xsd http://drools.org/schema/drools-spring http://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-containe..." default-autowire="byName"> <drools:resource id="rulesEnergyUsage" type="DRL" source="classpath:com/aepenergy/b2b/miscpull/rules/rulesEnergyUsage.drl"/> <drools:kbase id="kBaseEnergyUsage"> <drools:resources> <drools:resource ref="rulesEnergyUsage"/> </drools:resources> </drools:kbase> <drools:ksession id="kSessionEnergyUsage" kbase="kBaseEnergyUsage" type="stateful"/> </beans> -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1132) Fix NPE of reauthenticationSupport in OutboundResourceAdapterImpl

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1132?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1132. ------------------------------------ Resolution: Done > Fix NPE of reauthenticationSupport in OutboundResourceAdapterImpl > ----------------------------------------------------------------- > > Key: JBJCA-1132 > URL: https://issues.jboss.org/browse/JBJCA-1132 > Project: IronJacamar > Issue Type: Bug > Components: Common, Deployer > Affects Versions: 1.0.23.Final, 1.1.2.Final > Reporter: Jeff Zhang > Assignee: Jesper Pedersen > Fix For: 1.1.3.Final > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1132) Fix NPE of reauthenticationSupport in OutboundResourceAdapterImpl

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1132?page=com.atlassian.jira.plugin... ] Jesper Pedersen updated JBJCA-1132: ----------------------------------- Summary: Fix NPE of reauthenticationSupport in OutboundResourceAdapterImpl (was: fix NPE of reauthenticationSupport in OutboundResourceAdapterImpl) Assignee: Jesper Pedersen (was: Jeff Zhang) Affects Version/s: 1.0.23.Final Component/s: Deployer > Fix NPE of reauthenticationSupport in OutboundResourceAdapterImpl > ----------------------------------------------------------------- > > Key: JBJCA-1132 > URL: https://issues.jboss.org/browse/JBJCA-1132 > Project: IronJacamar > Issue Type: Bug > Components: Common, Deployer > Affects Versions: 1.0.23.Final, 1.1.2.Final > Reporter: Jeff Zhang > Assignee: Jesper Pedersen > Fix For: 1.1.3.Final > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2484) Revise clustering tests

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2484?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned WFLY-2484: ------------------------------------ Assignee: Radoslav Husar (was: Paul Ferraro) > Revise clustering tests > ----------------------- > > Key: WFLY-2484 > URL: https://issues.jboss.org/browse/WFLY-2484 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.Final > > > Paul pointed out that some of the tests are no longer relevant with the new implementation and some were never actually relevant, e.g. duplicate tests. > We should revise the set of tests to keep the testsuite small and find out missing tests. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-1389) Log API dependencies should be included automatically in deployments

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/AS7-1389?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on AS7-1389: ---------------------------------- JBoss AS and its successor, WildFly, are not Java EE containers, they are containers that happen to support Java EE (and have in the past and will in the future support other things as well, as the industry changes). Given this, and that philosophy is subjective by definition, and community feedback over the years, I stand by this decision; I am sorry it does not hold up for your specific environment though. To this end, there is another open task right now to add a management attribute which disables this behavior in the logging subsystem. Since changing it will then be a simple matter, I think that would resolve this issue. > Log API dependencies should be included automatically in deployments > -------------------------------------------------------------------- > > Key: AS7-1389 > URL: https://issues.jboss.org/browse/AS7-1389 > Project: Application Server 7 > Issue Type: Bug > Components: Logging > Affects Versions: 7.0.0.Final > Reporter: David Lloyd > Assignee: James Perkins > Fix For: 7.1.0.Final > > > The following log APIs should be included by deployments by default: > * {{org.slf4j}} > * {{org.apache.commons.logging}} > * {{org.log4j}} > These dependencies should override the deployment's versions of these libraries unless explicitly excluded by {{jboss-deployment-structure.xml}}. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-783) LdapExtLoginModule's bindCredential requires vault string to be in a slightly different format than other components

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-783?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated SECURITY-783: --------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1051057 > LdapExtLoginModule's bindCredential requires vault string to be in a slightly different format than other components > -------------------------------------------------------------------------------------------------------------------- > > Key: SECURITY-783 > URL: https://issues.jboss.org/browse/SECURITY-783 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: PicketBox > Affects Versions: PicketBox_4_0_19.Final > Reporter: Derek Horton > Assignee: Stefan Guilhen > Priority: Minor > Attachments: SECURITY-783.patch > > > The LdapExtLoginModule requires that the vault string used for the bindCredentials not include the '${' prefix and '}' suffix. This is different than other places in the standalone.xml file where the ${ and } are required. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-783) LdapExtLoginModule's bindCredential requires vault string to be in a slightly different format than other components

by Derek Horton (JIRA)

[ https://issues.jboss.org/browse/SECURITY-783?page=com.atlassian.jira.plug... ] Derek Horton updated SECURITY-783: ---------------------------------- Attachment: SECURITY-783.patch > LdapExtLoginModule's bindCredential requires vault string to be in a slightly different format than other components > -------------------------------------------------------------------------------------------------------------------- > > Key: SECURITY-783 > URL: https://issues.jboss.org/browse/SECURITY-783 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: PicketBox > Affects Versions: PicketBox_4_0_19.Final > Reporter: Derek Horton > Assignee: Stefan Guilhen > Priority: Minor > Attachments: SECURITY-783.patch > > > The LdapExtLoginModule requires that the vault string used for the bindCredentials not include the '${' prefix and '}' suffix. This is different than other places in the standalone.xml file where the ${ and } are required. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-783) LdapExtLoginModule's bindCredential requires vault string to be in a slightly different format than other components

by Derek Horton (JIRA)

[ https://issues.jboss.org/browse/SECURITY-783?page=com.atlassian.jira.plug... ] Derek Horton commented on SECURITY-783: --------------------------------------- I've attached a potential patch to resolve this issue. > LdapExtLoginModule's bindCredential requires vault string to be in a slightly different format than other components > -------------------------------------------------------------------------------------------------------------------- > > Key: SECURITY-783 > URL: https://issues.jboss.org/browse/SECURITY-783 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: PicketBox > Affects Versions: PicketBox_4_0_19.Final > Reporter: Derek Horton > Assignee: Stefan Guilhen > Priority: Minor > Attachments: SECURITY-783.patch > > > The LdapExtLoginModule requires that the vault string used for the bindCredentials not include the '${' prefix and '}' suffix. This is different than other places in the standalone.xml file where the ${ and } are required. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-783) LdapExtLoginModule's bindCredential requires vault string to be in a slightly different format than other components

by Derek Horton (JIRA)

Derek Horton created SECURITY-783: ------------------------------------- Summary: LdapExtLoginModule's bindCredential requires vault string to be in a slightly different format than other components Key: SECURITY-783 URL: https://issues.jboss.org/browse/SECURITY-783 Project: PicketBox Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PicketBox Affects Versions: PicketBox_4_0_19.Final Reporter: Derek Horton Assignee: Stefan Guilhen Priority: Minor The LdapExtLoginModule requires that the vault string used for the bindCredentials not include the '${' prefix and '}' suffix. This is different than other places in the standalone.xml file where the ${ and } are required. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2733) Create PicketLink extension and subsystems

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2733?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2733: ----------------------------- Summary: Create PicketLink extension and subsystems (was: Create PicketLink subsystems) > Create PicketLink extension and subsystems > ------------------------------------------ > > Key: WFLY-2733 > URL: https://issues.jboss.org/browse/WFLY-2733 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Kabir Khan > Fix For: 8.0.0.Final > > > At a minimum IDM and Federation -- 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, 6 months

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 January 2014