[JBoss JIRA] Created: (JBRULES-2079) ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors

[JBoss JIRA] Created:...

Geoffrey De Smet (JIRA)

Monday, 27 April 2009 Mon, 27 Apr '09

3:30 p.m.

ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2079 URL: https://jira.jboss.org/jira/browse/JBRULES-2079 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor Fix For: 5.1.0.M1 After you 've build your package with packageBuilder, you've either called the hasErrors() method and done something about it or you didn't check the hasErrors() method because you didn't know (or want to know) it existed and you expect it to throw an exception because hasErrors() returns true. The principle of least surpise. You don't expect that it continues like everything is cool (while it's not) and crashes the moment you fire your first rules. The exception should be a runtime exception and the message should at least mention the first of the errors. The exception should probably contain a list of all errors of course too as a property. See InvalidStateException in hibernate-validator. -- 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

Show replies by thread

Geoffrey De Smet (JIRA)

Monday, 27 April Mon, 27 Apr

3:35 p.m.

New subject: [JBoss JIRA] Commented: (JBRULES-2079) ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors

[ https://jira.jboss.org/jira/browse/JBRULES-2079?page=com.atlassian.jira.p... ] Geoffrey De Smet commented on JBRULES-2079: ------------------------------------------- This could be a pseudo code implementation on ReteooRuleBase: public void addPackage(final Package newPkg) { if (newPkg.hasErrors()) { throw new InvalidPackageException(newPkg.getErrors()); } // existing code List<Package> list = new ArrayList<Package>(); list.add( newPkg ); super.addPackages( list ); if ( this.getConfig().isSequential() ) { this.reteooBuilder.setOrdered( false ); } } class InvalidPackageException { InvalidPackageException(List<Error> errors) { super("The first error is " +error.get(0).toString()); this.errors = errors; }

...

ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2079 URL: https://jira.jboss.org/jira/browse/JBRULES-2079 Project: JBoss Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor Fix For: 5.1.0.M1 After you 've build your package with packageBuilder, you've either called the hasErrors() method and done something about it or you didn't check the hasErrors() method because you didn't know (or want to know) it existed and you expect it to throw an exception because hasErrors() returns true. The principle of least surpise. You don't expect that it continues like everything is cool (while it's not) and crashes the moment you fire your first rules. The exception should be a runtime exception and the message should at least mention the first of the errors. The exception should probably contain a list of all errors of course too as a property. See InvalidStateException in hibernate-validator.

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

Edson Tirelli (JIRA)

Sunday, 11 October Sun, 11 Oct

3:27 p.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2079) ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors

[ https://jira.jboss.org/jira/browse/JBRULES-2079?page=com.atlassian.jira.p... ] Edson Tirelli updated JBRULES-2079: ----------------------------------- Fix Version/s: 5.1.0.M2 (was: 5.1.0.M1)

...

ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2079 URL: https://jira.jboss.org/jira/browse/JBRULES-2079 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor Fix For: 5.1.0.M2 After you 've build your package with packageBuilder, you've either called the hasErrors() method and done something about it or you didn't check the hasErrors() method because you didn't know (or want to know) it existed and you expect it to throw an exception because hasErrors() returns true. The principle of least surpise. You don't expect that it continues like everything is cool (while it's not) and crashes the moment you fire your first rules. The exception should be a runtime exception and the message should at least mention the first of the errors. The exception should probably contain a list of all errors of course too as a property. See InvalidStateException in hibernate-validator.

Edson Tirelli (JIRA)

Friday, 28 May Fri, 28 May

3:32 p.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2079) ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors

[ https://jira.jboss.org/browse/JBRULES-2079?page=com.atlassian.jira.plugin... ] Edson Tirelli updated JBRULES-2079: ----------------------------------- Fix Version/s: 5.1.0.CR1 (was: 5.1.0.M2)

...

ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2079 URL: https://jira.jboss.org/browse/JBRULES-2079 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor Fix For: 5.1.0.CR1 After you 've build your package with packageBuilder, you've either called the hasErrors() method and done something about it or you didn't check the hasErrors() method because you didn't know (or want to know) it existed and you expect it to throw an exception because hasErrors() returns true. The principle of least surpise. You don't expect that it continues like everything is cool (while it's not) and crashes the moment you fire your first rules. The exception should be a runtime exception and the message should at least mention the first of the errors. The exception should probably contain a list of all errors of course too as a property. See InvalidStateException in hibernate-validator.

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

Mark Proctor (JIRA)

Thursday, 22 July Thu, 22 Jul

5:41 p.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2079) ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors

[ https://jira.jboss.org/browse/JBRULES-2079?page=com.atlassian.jira.plugin... ] Mark Proctor updated JBRULES-2079: ---------------------------------- Fix Version/s: 5.2.0.M1 (was: 5.1.0.CR1)

...

ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2079 URL: https://jira.jboss.org/browse/JBRULES-2079 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor Fix For: 5.2.0.M1 After you 've build your package with packageBuilder, you've either called the hasErrors() method and done something about it or you didn't check the hasErrors() method because you didn't know (or want to know) it existed and you expect it to throw an exception because hasErrors() returns true. The principle of least surpise. You don't expect that it continues like everything is cool (while it's not) and crashes the moment you fire your first rules. The exception should be a runtime exception and the message should at least mention the first of the errors. The exception should probably contain a list of all errors of course too as a property. See InvalidStateException in hibernate-validator.

Mark Proctor (JIRA)

Tuesday, 17 May Tue, 17 May

1:44 a.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2079) ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors

[ https://issues.jboss.org/browse/JBRULES-2079?page=com.atlassian.jira.plug... ] Mark Proctor updated JBRULES-2079: ---------------------------------- Fix Version/s: 5.2.0.CR1 (was: 5.2.0.M1)

...

ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2079 URL: https://issues.jboss.org/browse/JBRULES-2079 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor Fix For: 5.2.0.CR1 After you 've build your package with packageBuilder, you've either called the hasErrors() method and done something about it or you didn't check the hasErrors() method because you didn't know (or want to know) it existed and you expect it to throw an exception because hasErrors() returns true. The principle of least surpise. You don't expect that it continues like everything is cool (while it's not) and crashes the moment you fire your first rules. The exception should be a runtime exception and the message should at least mention the first of the errors. The exception should probably contain a list of all errors of course too as a property. See InvalidStateException in hibernate-validator.

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Geoffrey De Smet (JIRA)

Thursday, 26 May Thu, 26 May

3:36 p.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2079) ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors

[ https://issues.jboss.org/browse/JBRULES-2079?page=com.atlassian.jira.plug... ] Geoffrey De Smet updated JBRULES-2079: -------------------------------------- Fix Version/s: 5.2.0.CR2 (was: 5.2.0.CR1)

...

ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2079 URL: https://issues.jboss.org/browse/JBRULES-2079 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor Fix For: 5.2.0.CR2 After you 've build your package with packageBuilder, you've either called the hasErrors() method and done something about it or you didn't check the hasErrors() method because you didn't know (or want to know) it existed and you expect it to throw an exception because hasErrors() returns true. The principle of least surpise. You don't expect that it continues like everything is cool (while it's not) and crashes the moment you fire your first rules. The exception should be a runtime exception and the message should at least mention the first of the errors. The exception should probably contain a list of all errors of course too as a property. See InvalidStateException in hibernate-validator.

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Geoffrey De Smet (JIRA)

Thursday, 23 June Thu, 23 Jun

2 p.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2079) ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors

...

ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2079 URL: https://issues.jboss.org/browse/JBRULES-2079 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor Fix For: 5.3.0.Beta1 After you 've build your package with packageBuilder, you've either called the hasErrors() method and done something about it or you didn't check the hasErrors() method because you didn't know (or want to know) it existed and you expect it to throw an exception because hasErrors() returns true. The principle of least surpise. You don't expect that it continues like everything is cool (while it's not) and crashes the moment you fire your first rules. The exception should be a runtime exception and the message should at least mention the first of the errors. The exception should probably contain a list of all errors of course too as a property. See InvalidStateException in hibernate-validator.

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Geoffrey De Smet (JIRA)

Tuesday, 9 August Tue, 9 Aug

7:42 a.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2079) ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors

...

ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2079 URL: https://issues.jboss.org/browse/JBRULES-2079 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor Fix For: 5.3.0.CR1 After you 've build your package with packageBuilder, you've either called the hasErrors() method and done something about it or you didn't check the hasErrors() method because you didn't know (or want to know) it existed and you expect it to throw an exception because hasErrors() returns true. The principle of least surpise. You don't expect that it continues like everything is cool (while it's not) and crashes the moment you fire your first rules. The exception should be a runtime exception and the message should at least mention the first of the errors. The exception should probably contain a list of all errors of course too as a property. See InvalidStateException in hibernate-validator.

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Geoffrey De Smet (JIRA)

Sunday, 25 September Sun, 25 Sep

4:04 a.m.

New subject: [JBoss JIRA] Updated: (JBRULES-2079) ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors

...

ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2079 URL: https://issues.jboss.org/browse/JBRULES-2079 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor Fix For: 5.3.0.Final After you 've build your package with packageBuilder, you've either called the hasErrors() method and done something about it or you didn't check the hasErrors() method because you didn't know (or want to know) it existed and you expect it to throw an exception because hasErrors() returns true. The principle of least surpise. You don't expect that it continues like everything is cool (while it's not) and crashes the moment you fire your first rules. The exception should be a runtime exception and the message should at least mention the first of the errors. The exception should probably contain a list of all errors of course too as a property. See InvalidStateException in hibernate-validator.

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Geoffrey De Smet (Updated) (JIRA)

Friday, 21 October Fri, 21 Oct

11:02 a.m.

New subject: [JBoss JIRA] (JBRULES-2079) ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors

...

ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2079 URL: https://issues.jboss.org/browse/JBRULES-2079 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor Fix For: 5.4.0.Beta1 After you 've build your package with packageBuilder, you've either called the hasErrors() method and done something about it or you didn't check the hasErrors() method because you didn't know (or want to know) it existed and you expect it to throw an exception because hasErrors() returns true. The principle of least surpise. You don't expect that it continues like everything is cool (while it's not) and crashes the moment you fire your first rules. The exception should be a runtime exception and the message should at least mention the first of the errors. The exception should probably contain a list of all errors of course too as a property. See InvalidStateException in hibernate-validator.

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

Geoffrey De Smet (Updated) (JIRA)

Tuesday, 20 December Tue, 20 Dec

5:15 a.m.

New subject: [JBoss JIRA] (JBRULES-2079) ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors

...

ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2079 URL: https://issues.jboss.org/browse/JBRULES-2079 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor Fix For: 5.4.0.Beta2 After you 've build your package with packageBuilder, you've either called the hasErrors() method and done something about it or you didn't check the hasErrors() method because you didn't know (or want to know) it existed and you expect it to throw an exception because hasErrors() returns true. The principle of least surpise. You don't expect that it continues like everything is cool (while it's not) and crashes the moment you fire your first rules. The exception should be a runtime exception and the message should at least mention the first of the errors. The exception should probably contain a list of all errors of course too as a property. See InvalidStateException in hibernate-validator.

Geoffrey De Smet (JIRA)

Wednesday, 1 February Wed, 1 Feb

5:27 a.m.

New subject: [JBoss JIRA] (JBRULES-2079) ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors

...

ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2079 URL: https://issues.jboss.org/browse/JBRULES-2079 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor Fix For: 5.4.0.Beta3 After you 've build your package with packageBuilder, you've either called the hasErrors() method and done something about it or you didn't check the hasErrors() method because you didn't know (or want to know) it existed and you expect it to throw an exception because hasErrors() returns true. The principle of least surpise. You don't expect that it continues like everything is cool (while it's not) and crashes the moment you fire your first rules. The exception should be a runtime exception and the message should at least mention the first of the errors. The exception should probably contain a list of all errors of course too as a property. See InvalidStateException in hibernate-validator.

Toni Rikkola (JIRA)

Thursday, 12 April Thu, 12 Apr

3:37 a.m.

New subject: [JBoss JIRA] (JBRULES-2079) ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors

[ https://issues.jboss.org/browse/JBRULES-2079?page=com.atlassian.jira.plug... ] Toni Rikkola updated JBRULES-2079: ---------------------------------- Fix Version/s: 5.4.0.Final (was: 5.4.0.CR1)

...

ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2079 URL: https://issues.jboss.org/browse/JBRULES-2079 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor Fix For: 5.4.0.Final After you 've build your package with packageBuilder, you've either called the hasErrors() method and done something about it or you didn't check the hasErrors() method because you didn't know (or want to know) it existed and you expect it to throw an exception because hasErrors() returns true. The principle of least surpise. You don't expect that it continues like everything is cool (while it's not) and crashes the moment you fire your first rules. The exception should be a runtime exception and the message should at least mention the first of the errors. The exception should probably contain a list of all errors of course too as a property. See InvalidStateException in hibernate-validator.

Toni Rikkola (JIRA)

Tuesday, 15 May Tue, 15 May

8:01 a.m.

New subject: [JBoss JIRA] (JBRULES-2079) ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors

[ https://issues.jboss.org/browse/JBRULES-2079?page=com.atlassian.jira.plug... ] Toni Rikkola updated JBRULES-2079: ---------------------------------- Fix Version/s: 5.5.0.Beta1 (was: 5.4.0.Final)

...

ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2079 URL: https://issues.jboss.org/browse/JBRULES-2079 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor Fix For: 5.5.0.Beta1 After you 've build your package with packageBuilder, you've either called the hasErrors() method and done something about it or you didn't check the hasErrors() method because you didn't know (or want to know) it existed and you expect it to throw an exception because hasErrors() returns true. The principle of least surpise. You don't expect that it continues like everything is cool (while it's not) and crashes the moment you fire your first rules. The exception should be a runtime exception and the message should at least mention the first of the errors. The exception should probably contain a list of all errors of course too as a property. See InvalidStateException in hibernate-validator.

Michael Anstis (JIRA)

Wednesday, 26 September Wed, 26 Sep

5:29 a.m.

New subject: [JBoss JIRA] (JBRULES-2079) ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors

[ https://issues.jboss.org/browse/JBRULES-2079?page=com.atlassian.jira.plug... ] Michael Anstis updated JBRULES-2079: ------------------------------------ Fix Version/s: 5.5.0.CR1 (was: 5.5.0.Beta1)

...

ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2079 URL: https://issues.jboss.org/browse/JBRULES-2079 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor Fix For: 5.5.0.CR1 After you 've build your package with packageBuilder, you've either called the hasErrors() method and done something about it or you didn't check the hasErrors() method because you didn't know (or want to know) it existed and you expect it to throw an exception because hasErrors() returns true. The principle of least surpise. You don't expect that it continues like everything is cool (while it's not) and crashes the moment you fire your first rules. The exception should be a runtime exception and the message should at least mention the first of the errors. The exception should probably contain a list of all errors of course too as a property. See InvalidStateException in hibernate-validator.

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

Michael Anstis (JIRA)

Tuesday, 23 October Tue, 23 Oct

4:43 p.m.

New subject: [JBoss JIRA] (JBRULES-2079) ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors

[ https://issues.jboss.org/browse/JBRULES-2079?page=com.atlassian.jira.plug... ] Michael Anstis updated JBRULES-2079: ------------------------------------ Fix Version/s: 6.0.0.Beta1 (was: 5.5.0.CR1)

...

ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2079 URL: https://issues.jboss.org/browse/JBRULES-2079 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-core Affects Versions: 5.0.0.CR1 Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor Fix For: 6.0.0.Beta1 After you 've build your package with packageBuilder, you've either called the hasErrors() method and done something about it or you didn't check the hasErrors() method because you didn't know (or want to know) it existed and you expect it to throw an exception because hasErrors() returns true. The principle of least surpise. You don't expect that it continues like everything is cool (while it's not) and crashes the moment you fire your first rules. The exception should be a runtime exception and the message should at least mention the first of the errors. The exception should probably contain a list of all errors of course too as a property. See InvalidStateException in hibernate-validator.

4201

days inactive

5476

days old

jboss-jira@lists.jboss.org

Manage subscription

16 comments

6 participants

tags (0)

participants (6)

Edson Tirelli (JIRA)
Geoffrey De Smet (JIRA)
Geoffrey De Smet (Updated) (JIRA)
Mark Proctor (JIRA)
Michael Anstis (JIRA)
Toni Rikkola (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

[JBoss JIRA] Created: (JBRULES-2079) ruleBase.addPackage(packageBuilder.getPackage()); should fail-fast with a clear error message if the packageBuilder has any errors