[rules-users] RE: questions on guvnor and drools 5.0

Sorry it's been a few days and I haven't gotten any response on any questions/statements below. I've used drools in the past but am pretty new to some features of drools still and new to Guvnor. I wrote a proof of concept drools/Guvnor app and these are the things I don't like or have questions around. I was wondering if other people have the same problems or am I going about things wrong? Are there work arounds or is there plans to expand/change functionality? Maybe I should ask the dev list? SG -----Original Message----- From: G, S Sent: Monday, June 01, 2009 3:28 PM To: 'rules-users(a)lists.jboss.org' Subject: questions on guvnor and drools 5.0 I was wondering if somebody can help me with some questions: 1) Is there any more detail on how to setup Guvnor with a database? 2) How do you use the test scenarios with complex object structures? -eg Create a fact in working memory that has another Object in it which in turn has a list of Objects in it. -Seems like any Fact in working memory is assumed to only have only primitive values like Strings or numbers. -We would like a more depth of objects where objects have a deep relationship to other objects at least 2-4 levels deep. 3) Why add ruleflow-group to the rule definition instead of adding the rule to a ruleflow-group? If the ruleflow-group is part of the rule then you can't use the same rule in multiple ruleflow-groups and leads to copy and maintaining the rule in two different spots. 4) DSL seems to be very inconvenient to edit in a text box especially when it wraps. Why not a table where you can add rows and each row is a translation. Also there are no examples how to do translation into Drools syntax that is multiple lines long and not just a single line. 5) Is Java 5 Type Enumerations supported? I was assuming I'd get a list of values if a field was an Enumeration. 6) There seems to be a vast functionality difference between the Guvnor decision tables and examples that use spreadsheets. 7) Guvnor lost the ability to select variables for use in other statements. Functionality was in BRMS of drools 4.0.7 8) I was not able to insert a fact using a constructor that needed parameter values. Seems like it assumes everything is a bean but I couldn't find this requirement stated in the documentation anywhere. Examples in documentation show inserting facts with constructor parameters. 9) It would be nice when you upload a domain model jar that you could explore the objects and fields somehow. 10) When you write a rule using one particular editor it would be nice if you could switch to another editor. Switch between Guided, DSL, Technical, etc. 11) It seems hard to reorder the statements in a when or then block. If I put them in the wrong order I have to delete them all. Would be nice if a statement could be moved up or down. 12) When calling a method on an object the choices only showed me public methods that take in one parameter. I had a method with two parameters and it wouldn't show me the method. I had to do a DSL or custom drools statement to get around it. 13) Guvnor seems to limit the drools syntax. I couldn't do a "from $collection" statement without a custom drools statement line. 14) It would be nice if I could declare a global dialect "java" for all the rules. 15) It would be nice to define an existing agenda-group as part of a ruleflow-group without adding the ruleflow-group on the rules in that agenda-group. Thanks, SG -----Message Disclaimer----- This e-mail message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply email to Connect(a)principal.com and delete or destroy all copies of the original message and attachments thereto. Email sent to or from the Principal Financial Group or any of its member companies may be retained as required by law or regulation. Nothing in this message is intended to constitute an Electronic signature for purposes of the Uniform Electronic Transactions Act (UETA) or the Electronic Signatures in Global and National Commerce Act ("E-Sign") unless a specific statement to the contrary is included in this message. While this communication may be used to promote or market a transaction or an idea that is discussed in the publication, it is intended to provide general information about the subject matter covered and is provided with the understanding that The Principal is not rendering legal, accounting, or tax advice. It is not a marketed opinion and may not be used to avoid penalties under the Internal Revenue Code. You should consult with appropriate counsel or other advisors on all matters pertaining to legal, tax, or accounting obligations and requirements.