[JBoss JIRA] Created: (JBRULES-1812) Add rule inheritance to Core DRL support
by Michael Rhoden (JIRA)
Add rule inheritance to Core DRL support
----------------------------------------
Key: JBRULES-1812
URL: https://jira.jboss.org/jira/browse/JBRULES-1812
Project: JBoss Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 5.0.0.M2
Reporter: Michael Rhoden
Assignee: Mark Proctor
Fix For: 5.0.0.M3
added "Extends" keyword to DRL grammar. When a rule extends another, it will pull the entire LHS from its parent, to the current rule before execution. An example:
rule "test rule 1"
enabled false
when
c: Cheese( type == "stilton" )
then
list.add( new String ("rule 1") );
end
rule "test rule 2" extends "test rule 1"
enabled false
when
Cheese( price <= 6.00) from c
then
list.add( new String ("rule 2") );
end
rule "test rule 3" extends "test rule 2"
when
Cheese( price > 1.00 ) from c
then
list.add( new String ("rule 3") );
end
Test is in MiscTest.java
--
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
15 years, 10 months
[JBoss JIRA] Created: (JBRULES-1539) Support enum fields as drop-downs in BRMS
by Harlan Iverson (JIRA)
Support enum fields as drop-downs in BRMS
-----------------------------------------
Key: JBRULES-1539
URL: http://jira.jboss.com/jira/browse/JBRULES-1539
Project: JBoss Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-brms
Environment: n/a
Reporter: Harlan Iverson
Assigned To: Mark Proctor
Priority: Optional
It would be nice if enum [real Java 5+] fields were first class citizens, and the BRMS UI had the same functionality as the BRMS-defined enums described in JBRULES-1090.
For example, if Driver.locationRiskProfile in the insurance example were changed to a RiskLevel enum, the BRMS would use reflection (or similar) to create a drop-down box based on the RiskLevel members.
Another optional extension of that would be the ability to assign displayed text for enums in the same way that JBRULES-1090 describes:
RiskLevel : ['LOW=Low Risk', 'MED=Medium Risk']
where LOW and MED would correspond to enum values.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 10 months
[JBoss JIRA] Created: (JBRULES-1865) Build package throws NPE if first line in drl starts with #
by Seegler Ittyavirah (JIRA)
Build package throws NPE if first line in drl starts with #
-------------------------------------------------------------
Key: JBRULES-1865
URL: https://jira.jboss.org/jira/browse/JBRULES-1865
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-guvnor
Affects Versions: 5.0.0.M2
Reporter: Seegler Ittyavirah
Assignee: Mark Proctor
Import a drl file that has some rules and functions, by adding following line at the top. The line start with '#'
#created on: May 31, 2008
package com.mycompany.app.rules;
Click on Build Package button.
Server throws NPE
Caused by: java.lang.NullPointerException
at org.drools.compiler.PackageBuilder.validateUniqueRuleNames(PackageBui
lder.java:508)
at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:353
)
at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.j
ava:258)
at org.drools.guvnor.server.builder.ContentPackageAssembler.addDrl(Conte
ntPackageAssembler.java:244)
at org.drools.guvnor.server.builder.ContentPackageAssembler.preparePacka
ge(ContentPackageAssembler.java:173)
at org.drools.guvnor.server.builder.ContentPackageAssembler.<init>(Conte
ntPackageAssembler.java:86)
at org.drools.guvnor.server.builder.ContentPackageAssembler.<init>(Conte
ntPackageAssembler.java:96)
at org.drools.guvnor.server.ServiceImplementation.buildPackage(ServiceIm
plementation.java:1238)
at org.drools.guvnor.server.ServiceImplementation.buildPackage(ServiceIm
plementation.java:1228)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocation
Context.java:31)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocation
Context.java:56)
at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackI
nterceptor.java:28)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocation
Context.java:68)
at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterc
eptor.java:39)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocation
Context.java:68)
--
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
15 years, 10 months
[JBoss JIRA] Created: (JBRULES-1214) drools-server should not have .settings commited into svn
by Geoffrey De Smet (JIRA)
drools-server should not have .settings commited into svn
---------------------------------------------------------
Key: JBRULES-1214
URL: http://jira.jboss.com/jira/browse/JBRULES-1214
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-brms
Affects Versions: 4.0.1
Reporter: Geoffrey De Smet
Assigned To: Mark Proctor
Priority: Trivial
Fix For: FUTURE
See JBRULES-834.
As far as I can tell, the commit of /drools-server/.settings is an error because the other server modules explicitly svn:ignore the .settings directory.
The svn ignore was probably forgotten, which might have given our good friend eclipse the opportunity to commit it.
I could be wrong though.
If I am right though, the .settings directory should be deleted in svn, which will cause havoc when everyone updates who's relying on .settings in drools-server, and the svn:ignore should be edited to contain these 3 items:
.metadata
.settings
.wtpmodules
This way it uses standardized svn ignores just like the other modules.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 10 months
[JBoss JIRA] Created: (JBAS-5563) Deployment from deploy-hasingleton broken
by Brian Stansberry (JIRA)
Deployment from deploy-hasingleton broken
-----------------------------------------
Key: JBAS-5563
URL: http://jira.jboss.com/jira/browse/JBAS-5563
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-5.0.0.Beta4
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.CR2
JBAS-5562 shows that deployment via the deploy-hasingleton dir isn't working properly. If it were, the broken jbossmq-httpil.sar would be failing to deploy and would be obvious for all to see.
In any case, the current HASingletonDeployer impl of starting a VFSDeploymentScanner isn't really appropriate with the full ProfileService impl.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 10 months