[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
13 years
[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
13 years
[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
13 years