October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBRULES-3063) Drools should not allow set two rules with the same name for the same package

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3063?page=com.atlassian.jira.plug... ] Edson Tirelli closed JBRULES-3063. ---------------------------------- > Drools should not allow set two rules with the same name for the same package > ----------------------------------------------------------------------------- > > Key: JBRULES-3063 > URL: https://issues.jboss.org/browse/JBRULES-3063 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: drools-compiler > Affects Versions: 5.1.1.FINAL > Reporter: Alessandro Lazarotti > Assignee: Edson Tirelli > Priority: Minor > Fix For: 5.3.0.Final > > > Drools should not allow set two rules with the same name for the same package > As expected, Drools does not allow us to define two rules with the same name in a same DRL file. > But if there are two rules with the same name, in the same package, but in separate files, no exception or warning is issued, just one rule overrides the other in silence. > From documentation: > "A rule must have a name, unique within its rule package. If a rule is defined twice in a single DRL, an error will appear when one loads it. If a DRL that includes a rule name already in the package is added, the previous rule is repalced."[1] > [1] http://docs.redhat.com/docs/en-US/JBoss_Enterprise_SOA_Platform/5/html/JB... > Different behavior for a similar action is not good. Both should alert user about a rule name repeated. > For large projects using a lot of DRL files can be hard to track mistakes occurred by rules override . It is really necessary provide an ERROR message for this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-3124) Compiler should be able to report warnings

by Mikael Lönneberg (JIRA)

Compiler should be able to report warnings ------------------------------------------ Key: JBRULES-3124 URL: https://issues.jboss.org/browse/JBRULES-3124 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.2.0.Final Reporter: Mikael Lönneberg Assignee: Mark Proctor Fix For: FUTURE 1) add warnings list to packagebuilder 2) add hasWarnings and getWarnings, in mirror of errors. 3) allow hashWarnings and getWarnings to take positive/negative warnings. i.e. ignore duplicate resource (hasWarnings would return false), report duplicate file (is returned in list). This should be some sort of chainable or compositable filter, with sane defaults. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1362) FULL_XA infinispan caches need to properly register with TransactionManager for recovery.

by Paul Ferraro (JIRA)

FULL_XA infinispan caches need to properly register with TransactionManager for recovery. ----------------------------------------------------------------------------------------- Key: AS7-1362 URL: https://issues.jboss.org/browse/AS7-1362 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.1.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3230) Add ruleflow-group hyperlinks in DRL editor

by Jérémie Lagarde (JIRA)

Add ruleflow-group hyperlinks in DRL editor -------------------------------------------- Key: JBRULES-3230 URL: https://issues.jboss.org/browse/JBRULES-3230 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-eclipse Reporter: Jérémie Lagarde Assignee: Mark Proctor It would be nice to have hyperlinks on "ruleflow-group" declaration in DRL editor to jump into appropriate bpmn or rf files. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3215) NPE when calling PackageBuilder.addPackageFromDrl(Reader)

by Jean-Marc Vanel (JIRA)

NPE when calling PackageBuilder.addPackageFromDrl(Reader) --------------------------------------------------------- Key: JBRULES-3215 URL: https://issues.jboss.org/browse/JBRULES-3215 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.3.0.Beta1 Environment: % uname -a Linux oem-laptop 2.6.32-5-amd64 #1 SMP Fri Sep 9 20:23:16 UTC 2011 x86_64 GNU/Linux % java -version java version "1.7.0" Java(TM) SE Runtime Environment (build 1.7.0-b147) Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode) Reporter: Jean-Marc Vanel Assignee: Mark Proctor Daemon Thread [SwingWorker-pool-3-thread-1] (Suspended (breakpoint at line 89 in ClassUtils)) ClassUtils.canonicalName(Class) line: 89 DeclarationTypeFixer.fix(Declaration) line: 11 JavaRuleBuilderHelper.createVariableContext(String, String, RuleBuildContext, Declaration[], Declaration[], Map<String,Class<?>>) line: 158 JavaRuleBuilderHelper.createConsequenceContext(RuleBuildContext, String, String, String, Map<String,Declaration>, BoundIdentifiers) line: 94 ASMConsequenceStubBuilder(AbstractASMConsequenceBuilder).consequenceContext(RuleBuildContext, String) line: 47 ASMConsequenceStubBuilder(AbstractASMConsequenceBuilder).build(RuleBuildContext, String) line: 17 RuleBuilder.build(RuleBuildContext) line: 99 PackageBuilder.addRule(RuleDescr) line: 1993 PackageBuilder.addPackage(PackageDescr) line: 793 PackageBuilder.addPackageFromDrl(Reader) line: 355 NOTE: with the debugger, I saw that variable $JTEXT_FIELD is causing the problem; see the DRL below in "how to reproduce" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (AS7-1992) The names of a number of elements within the core configuration are not checked to ensure they are correct.

by Darran Lofthouse (JIRA)

The names of a number of elements within the core configuration are not checked to ensure they are correct. ----------------------------------------------------------------------------------------------------------- Key: AS7-1992 URL: https://issues.jboss.org/browse/AS7-1992 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.0.Alpha1 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Beta1 The names of a number of elements in the core configuration are not checked to ensure they are correct. We should be checking the names and reporting them as unexpected elements if the names are not correct. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1209) Xa-datasource:add requires a non-empty map "xa-data-source-properties", which is not documented

by Heiko Rupp (JIRA)

Xa-datasource:add requires a non-empty map "xa-data-source-properties", which is not documented ----------------------------------------------------------------------------------------------- Key: AS7-1209 URL: https://issues.jboss.org/browse/AS7-1209 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.CR1 Reporter: Heiko Rupp Assignee: Brian Stansberry [domain@localhost:9999 subsystem=datasources] ./xa-data-source=xa-ds:read-operation-description(name=add) does not list a (required) property "xa-data-source-properties", but when this is not provided, adding a xa-datasource fails and console shows [Server:server-two] 15:25:52,983 WARN [org.jboss.as.controller] (pool-1-thread-35) Operation ("add") failed - address: ([ [Server:server-two] ("subsystem" => "datasources"), [Server:server-two] ("xa-data-source" => "postgres") [Server:server-two] ]): java.lang.IllegalArgumentException Adding an empty xa-data-source-properties map also makes the :add fail. It only works when this property is present and some (dummy!) values are given. 1) the requirement for this xa-da.. should be documented 2) it should be optional 3) an empty map should be allowed (if no xa-props are needed) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1924) XaDataSourceService does not set UserTransactionJndiName during deployment

by Bob McWhirter (JIRA)

XaDataSourceService does not set UserTransactionJndiName during deployment -------------------------------------------------------------------------- Key: AS7-1924 URL: https://issues.jboss.org/browse/AS7-1924 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.0.2.Final Reporter: Bob McWhirter Assignee: Jesper Pedersen The XaDataSourceService doesn't set the UserTransactionJndiName, so it defaults to java:/UserTransaction, which seems invalid within the context of AS7. In-line commit comment here: https://github.com/jbossas/jboss-as/commit/7fd76db27e89e40e9a16243fc05846... Additionally, setting up the URL delimeter uses the dataSourceConfig instead of the xaDataSourceConfig, but that seems harmless, so far. In TorqueBox, we hacked around: https://github.com/torquebox/torquebox/blob/7f51e360749d8093fc291fbf238b7... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1991) Regression in ra.xml loading - required in/outbound configuration

by Karel Piwko (JIRA)

Regression in ra.xml loading - required in/outbound configuration ----------------------------------------------------------------- Key: AS7-1991 URL: https://issues.jboss.org/browse/AS7-1991 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.0.Alpha1 Reporter: Karel Piwko Assignee: Jesper Pedersen There is a regression from EAP5 support of ra.xml descriptor inside of a RAR archive. Suppose following META-INF/ra.xml {code:xml} <?xml version="1.0" encoding="UTF-8"?> <connector xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd" version="1.5"> <vendor-name>Spring Framework</vendor-name> <eis-type>Spring Connector</eis-type> <resourceadapter-version>1.0</resourceadapter-version> <resourceadapter> <resourceadapter-class>org.springframework.jca.context.SpringContextResourceAdapter</resourceadapter-class> <config-property> <config-property-name>ContextConfigLocation</config-property-name> <config-property-type>java.lang.String</config-property-type> <config-property-value>META-INF/applicationContext.xml</config-property-value> </config-property> </resourceadapter> </connector> {code} This will fail on AS7 with following exception, however it was working with JBoss 5: {code} 11:58:46,719 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."spring-jmx-rar.rar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."spring-jmx-rar.rar".INSTALL: Failed to process phase INSTALL of deployment "spring-jmx-rar.rar" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_27] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_27] at java.lang.Thread.run(Thread.java:662) [:1.6.0_27] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.jca.common.api.validator.ValidateException: The resource adapter metadata must contain either an outbound or inbound configuration at org.jboss.as.connector.deployers.processors.ParsedRaDeploymentProcessor.deploy(ParsedRaDeploymentProcessor.java:134) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1] ... 5 more Caused by: org.jboss.jca.common.api.validator.ValidateException: The resource adapter metadata must contain either an outbound or inbound configuration at org.jboss.jca.common.metadata.ra.common.ResourceAdapter1516Impl.validate(ResourceAdapter1516Impl.java:333) at org.jboss.jca.common.metadata.ra.common.ConnectorAbstractmpl.validate(ConnectorAbstractmpl.java:305) at org.jboss.as.connector.deployers.processors.ParsedRaDeploymentProcessor.deploy(ParsedRaDeploymentProcessor.java:110) ... 6 more 11:58:46,727 INFO [org.jboss.as.server.controller] (pool-1-thread-1) Deployment of "spring-jmx-rar.rar" was rolled back with failure message {"Failed services" => {"jboss.deployment.unit.\"spring-jmx-rar.rar\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"spring-jmx-rar.rar\".INSTALL: Failed to process phase INSTALL of deployment \"spring-jmx-rar.rar\""}} {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-1227) Discovery protocol based on GoGrid

by Bela Ban (JIRA)

Discovery protocol based on GoGrid ---------------------------------- Key: JGRP-1227 URL: https://jira.jboss.org/browse/JGRP-1227 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 Similar to S3_PING (Amazon), create a discovery protocol (extending FILE_PING) which uses Rackspace's distributed store -- 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

11 years, 3 months

1
3
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2011