[rules-dev] quick design questions to mull over - regarding the repo

[Felipe Piccolini]

Hi Michael,

   Iv been following your work in the brms/repository very closely  
because Im working in something very similar by
my self for a project using JBossRules, and as I cant wait much  
longer I decided to use your work as a base to
put something on production until you guys do the "real-cool" thing.

   About your questions, IMHO,
-Q1: I think dsl should be an attribute (as far as I know, you can  
put only 1 dsl expander on drl files) and
there should be only one reference to expand the rule sentences, if  
you have multiple dsl, then have mutiple drl (packages).
-Q2: I think object models (or business models to use as facts for  
your rules) should be assets, so u can organize your model/classes
not thinking in drools or any other framework, so you can extend your  
model or rules with just a pointer as a dependency, just as you
can put or remove jars from your classpath.

  One thing I wanted to tell you for some time about drools-brms is  
that for some reason I dont know, the gwt ui looks awfull on mac (OS X),
I made it works changing some things on the .launcher and .shell  
files, but its looks like no modal window has a background, or complete
messed up.. can you check it out? or help me to guiding me what to  
check to see it right? Thanks.


On 01-02-2007, at 3:23, Michael Neale wrote:

> BUT this also applies to the file structure for "packages" in a  
> file system/IDE (forget monolothic DRL for a moment - but instead  
> imagine a folder which is a rule package containing lots of rules).
>
> (in no particular order);
>
> Q1: Should DSL "language configurations" be stored as an "asset"  
> inside a package (ie a file, perhaps multiple ones of them?) - or  
> are they an attribute of a package?
> Q2: The object model: should this be stored as an attribute of a  
> package - or just another asset of which there can be muliple ones  
> uploaded (as a jar, for instance).
> This is needed for validation/tooling. Obviously in the IDE the  
> classes will be on the classpath, but in the repo they have to be  
> stored somewhere.
>
> Note versioning works well in all scenarios (subtle differences  
> between a package attribute and asset for versioning, but ignore  
> them for now).
>
> I have opinions, but wanted some discussion (attachment screenshot  
> shows the package managment screen).
> <Screenshot-JBoss Business Rules Management System .png>
> _______________________________________________
> rules-dev mailing list
> rules-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev


Felipe Piccolini M.
felipe.piccolini at bluesoft.cl




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-dev/attachments/20070201/c2d8325d/attachment.html