January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3375) Deployment of resource adapters embedded in an ear does not work

by Robert Panzer (JIRA)

Robert Panzer created AS7-3375: ---------------------------------- Summary: Deployment of resource adapters embedded in an ear does not work Key: AS7-3375 URL: https://issues.jboss.org/browse/AS7-3375 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.0.CR1b Environment: Win7, JBoss 7.1.0.Final-SNAPSHOT, JDK 1.6.0_29 64Bit Reporter: Robert Panzer Assignee: Jesper Pedersen Fix For: 7.1.0.Final The ParsedRADeploymentProcessor gets the MUTABLE_REGISTRATION_ATTACHMENT from the deployment unit in line 106, that is not set, so it is null. Then later in line 176 it tries to register statistics for this resource adapter and calls registration.isAllowsOverride() so that a NPE occurs. I have posted a pull request that omits this registration in case registration is null. So for every embedded resource adapter statistics will not be available. Maybe there is a better was to do this but at least it works for me. -- 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

14 years, 3 months

2
3
0 / 0

[JBoss JIRA] (AS7-3381) Add extension points to web subsystem deployment processors

by Siamak Sadeghianfar (JIRA)

Siamak Sadeghianfar created AS7-3381: ---------------------------------------- Summary: Add extension points to web subsystem deployment processors Key: AS7-3381 URL: https://issues.jboss.org/browse/AS7-3381 Project: Application Server 7 Issue Type: Enhancement Components: Web Affects Versions: 7.1.0.CR1b Reporter: Siamak Sadeghianfar Assignee: Remy Maucherat Attachments: web.patch Due to certain checks in the web subsystem, it is not possible to extend and reuse the deployment processors in custom subsystems. The deployment processors need to be refactored to allow more access to the sub-classes for overriding certain functionality while reusing the deployment logic. -- 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

14 years, 3 months

1
3
0 / 0

[JBoss JIRA] (JBRULES-3357) The constructor ValueError(Value, String, String) is undefined

by Christoph Linder (JIRA)

Christoph Linder created JBRULES-3357: ----------------------------------------- Summary: The constructor ValueError(Value, String, String) is undefined Key: JBRULES-3357 URL: https://issues.jboss.org/browse/JBRULES-3357 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse Reporter: Christoph Linder Assignee: Mark Proctor I do get the message "The constructor ValueError(String, String, String) is undefined" in the Eclipse-Problems tab when compiling the project. The projects actually runs as expected. This happens when a) the class name is "ValueError". Might hit other class names, too. But ValueError is what I used :) b) I use glob imports, e.g. import foo.bar.*; -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-3352) Enable JAAS support for the SASL Realms

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3352: ------------------------------------- Summary: Enable JAAS support for the SASL Realms Key: AS7-3352 URL: https://issues.jboss.org/browse/AS7-3352 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Final -- 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

14 years, 3 months

1
1
0 / 0

[JBoss JIRA] (AS7-3370) Parsing of thread pools is broken

by Heiko Braun (JIRA)

Heiko Braun created AS7-3370: -------------------------------- Summary: Parsing of thread pools is broken Key: AS7-3370 URL: https://issues.jboss.org/browse/AS7-3370 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.Final The recent upstream changes broke some subsystems: {noformat} [ERROR] java.lang.IllegalArgumentException [ERROR] at org.jboss.dmr.client.ModelValue.getChild(ModelValue.java:102) [ERROR] at org.jboss.dmr.client.ModelNode.get(ModelNode.java:710) [ERROR] at org.jboss.dmr.client.ModelNode.get(ModelNode.java:1131) [ERROR] at org.jboss.as.console.client.widgets.forms.EntityAdapter.fromDMR(EntityAdapter.java:147) [ERROR] at org.jboss.as.console.client.shared.subsys.jca.LoadWorkmanagerCmd.parseThreadPool(LoadWorkmanagerCmd.java:102) [ERROR] at org.jboss.as.console.client.shared.subsys.jca.LoadWorkmanagerCmd.access$1(LoadWorkmanagerCmd.java:97) [ERROR] at org.jboss.as.console.client.shared.subsys.jca.LoadWorkmanagerCmd$1.onSuccess(LoadWorkmanagerCmd.ja {noformat} -- 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

14 years, 3 months

1
1
0 / 0

[JBoss JIRA] (JBRULES-3351) Settings a termination config list will not create the Termination instance

by Patrik Dufresne (JIRA)

Patrik Dufresne created JBRULES-3351: ---------------------------------------- Summary: Settings a termination config list will not create the Termination instance Key: JBRULES-3351 URL: https://issues.jboss.org/browse/JBRULES-3351 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-planner Affects Versions: 5.3.1.Final Environment: N/A Reporter: Patrik Dufresne Assignee: Geoffrey De Smet Setting a sub termination config list using TerminationConfig.setTerminationConfigList(List<TerminationConfig>) will not create the termination when buildTermination is called. The problem is due to an error in TerminationConfig.java:179. if (terminationConfigList != null && terminationConfigList.isEmpty()) { for (TerminationConfig terminationConfig : terminationConfigList) { Termination termination = terminationConfig.buildTermination(scoreDefinition); if (termination != null) { terminationList.add(termination); } } } The boolean expression terminationConfigList.isEmpty() should become !terminationConfigList.isEmpty(). -- 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

14 years, 3 months

2
1
0 / 0

[JBoss JIRA] (JBRULES-3356) Accumulate function cannot be used directly from lhs

by Edson Tirelli (JIRA)

Edson Tirelli created JBRULES-3356: -------------------------------------- Summary: Accumulate function cannot be used directly from lhs Key: JBRULES-3356 URL: https://issues.jboss.org/browse/JBRULES-3356 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.4.0.Beta1, 5.3.1.Final Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.3.2.Final, 5.4.0.Beta2 Description of problem: Since support to multi-function accumulate has been added in 5.2, it would be nice to be able to use accumulate directly in lhs in Rule API like newRule().name("whatever").lhs().accumulate() which is impossible now. -- 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

14 years, 3 months

1
2
0 / 0

[JBoss JIRA] (JBRULES-3354) Unable to construct expressions containing 'from' using Rules API

by Edson Tirelli (JIRA)

Edson Tirelli created JBRULES-3354: -------------------------------------- Summary: Unable to construct expressions containing 'from' using Rules API Key: JBRULES-3354 URL: https://issues.jboss.org/browse/JBRULES-3354 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.4.0.Beta1, 5.3.1.Final Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.3.2.Final, 5.4.0.Beta2 Description of problem: When trying to construct a new rule containing 'from' I can't continue constructing the rule due to error: "The method rhs(String) is undefined for the type capture#3-of ?" -- 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

14 years, 3 months

2
4
0 / 0

[JBoss JIRA] (JBRULES-3353) Drools Grid: Remote KnowledgeBuilderConfiguration throws NullPointerException

by Jens Rohloff (JIRA)

Jens Rohloff created JBRULES-3353: ------------------------------------- Summary: Drools Grid: Remote KnowledgeBuilderConfiguration throws NullPointerException Key: JBRULES-3353 URL: https://issues.jboss.org/browse/JBRULES-3353 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.4.0.Beta1 Reporter: Jens Rohloff Assignee: Mark Proctor Adding a AccumulateFunctionOption to a GridNode throws NullPointerException. java.lang.NullPointerException at org.drools.command.runtime.KBuilderSetPropertyCommand.execute(KBuilderSetPropertyCommand.java:42) at org.drools.command.runtime.KBuilderSetPropertyCommand.execute(KBuilderSetPropertyCommand.java:27) at org.drools.grid.impl.GridNodeServer$1$1.execute(GridNodeServer.java:74) at org.drools.grid.impl.GridNodeServer.messageReceived(GridNodeServer.java:48) at org.drools.grid.impl.MultiplexSocket.messageReceived(MultiplexSocket.java:25) at org.drools.grid.remote.mina.MinaIoHandler.messageReceived(MinaIoHandler.java:67) at org.apache.mina.core.filterchain.DefaultIoFilterChain$TailFilter.messageReceived(DefaultIoFilterChain.java:716) at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434) at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46) at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:796) at org.apache.mina.filter.codec.ProtocolCodecFilter$ProtocolDecoderOutputImpl.flush(ProtocolCodecFilter.java:427) at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:245) at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434) at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46) at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:796) at org.apache.mina.core.filterchain.IoFilterAdapter.messageReceived(IoFilterAdapter.java:119) at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434) at org.apache.mina.core.filterchain.DefaultIoFilterChain.fireMessageReceived(DefaultIoFilterChain.java:426) at org.apache.mina.core.polling.AbstractPollingIoProcessor.read(AbstractPollingIoProcessor.java:692) at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:645) at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:634) at org.apache.mina.core.polling.AbstractPollingIoProcessor.access$400(AbstractPollingIoProcessor.java:66) at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:1078) at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) -- 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1880) Can fire rules after disposing the Stateful session

by Sravanthi Tipirneni (JIRA)

Can fire rules after disposing the Stateful session --------------------------------------------------- Key: JBRULES-1880 URL: https://jira.jboss.org/jira/browse/JBRULES-1880 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.7 Reporter: Sravanthi Tipirneni Assignee: Mark Proctor Priority: Minor I can access the session and fire rules even after the session is disposed using the dispose method -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
5
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 2012