Michael Neale | 1 Aug 2010 05:12
Picon
Gravatar

Re: [rules-dev] Slot Specific and Refraction

Slot specific stuff would have a HUGE impact in usability for people (even experienced people are tripped up by accidental recursion - especially for more monolithic models - which are convenient to program but more prone to this). Totally makes sense that jess would do it. 

On Sun, Aug 1, 2010 at 4:53 AM, Mark Proctor <mproctor <at> codehaus.org> wrote:
 http://blog.athico.com/2010/07/slot-specific-and-refraction.html

_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev



--
Michael D Neale
home: www.michaelneale.net
blog: michaelneale.blogspot.com
_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
Wolfgang Laun | 2 Aug 2010 11:11
Picon

[rules-dev] 5.1.0CR1

The Expert documentation contains unresolved docbook tags <kw>...</kw> in many places.

The new "calendars" rule attribute isn't mentioned. There's no indication that "duration" is now deprecated (as written in http://blog.athico.com/2010/07/drools-51-m2-release-notes.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+DroolsRSS+(Drools+-+RSS)

Nothing is said about "Live queries". And the javadoc for openLiveQuery describes neither its function, nor parameters or return type.

Javadoc's main page (the top-level index.html) compes up with

Drools 5.0.0 Javadocs

Best
-W


_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
Geoffrey De Smet | 2 Aug 2010 13:05
Picon
Gravatar

Re: [rules-dev] 5.1.0CR1

 > The Expert documentation contains unresolved docbook tags <kw>...</kw>
 > in many places.

I replace all <kw> instances with <literal> on trunk last monday, did 
that make the 5.1.0.CR1 release?
Just checked: there are no <kw>'s any more on trunk.

With kind regards,
Geoffrey De Smet

Op 02-08-10 11:11, Wolfgang Laun schreef:
> The Expert documentation contains unresolved docbook tags <kw>...</kw>
> in many places.
>
> The new "calendars" rule attribute isn't mentioned. There's no
> indication that "duration" is now deprecated (as written in
> http://blog.athico.com/2010/07/drools-51-m2-release-notes.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+DroolsRSS+(Drools+-+RSS)
> <http://blog.athico.com/2010/07/drools-51-m2-release-notes.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+DroolsRSS+%28Drools+-+RSS%29>
>
> Nothing is said about "Live queries". And the javadoc for openLiveQuery
> describes neither its function, nor parameters or return type.
>
> Javadoc's main page (the top-level index.html) compes up with
>
>
>   Drools 5.0.0 Javadocs
>
> Best
> -W
>
>
>
>
> _______________________________________________
> rules-dev mailing list
> rules-dev <at> lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev

_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev

Mauricio Salatino | 4 Aug 2010 06:00
Picon
Gravatar

[rules-dev] some problems with the trunk

Hi guys.. I just want inform that I'm having some dependency problem with a fresh trunk.
If I remove all my .m2/repository/org/drools dir and try to build the trunk with:
mvn clean install -Dmaven.test.skip -o
I'm getting:

salaboy:trunk salaboy$ mvn clean install -Dmaven.test.skip -o
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your local
repository will be inaccessible.

[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).


Project ID: null:org.drools.osgi.wrapper.jxls-reader:jar:0.9.8

Reason: Cannot find parent: org.drools:drools for project: null:org.drools.osgi.wrapper.jxls-reader:jar:0.9.8 for project null:org.drools.osgi.wrapper.jxls-reader:jar:0.9.8


[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.drools:drools for project: null:org.drools.osgi.wrapper.jxls-reader:jar:0.9.8 for project null:org.drools.osgi.wrapper.jxls-reader:jar:0.9.8
    at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:404)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
    at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: org.drools:drools for project: null:org.drools.osgi.wrapper.jxls-reader:jar:0.9.8 for project null:org.drools.osgi.wrapper.jxls-reader:jar:0.9.8
    at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396)
    at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823)
    at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:508)
    at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200)
    at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:604)
    at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:487)
    at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:560)
    at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:560)
    at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:391)
    ... 12 more
Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.drools:drools' not found in repository: System is offline.

  org.drools:drools:pom:5.1.0.SNAPSHOT


 for project org.drools:drools
    at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:605)
    at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1392)
    ... 20 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: System is offline.

  org.drools:drools:pom:5.1.0.SNAPSHOT



    at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:203)
    at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90)
    at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:558)
    ... 21 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 seconds
[INFO] Finished at: Wed Aug 04 00:54:38 GMT-03:00 2010
[INFO] Final Memory: 13M/81M
[INFO] ------------------------------------------------------------------------


Probably a bad version number somewhere.. I don't have time right now to take a look on this.. that's why I'm putting this here..
Let me know if someone has the same problem with a fresh trunk and without having old jars in the repo.
 

--
 - CTO <at> http://www.plugtree.com 
 - MyJourney <at> http://salaboy.wordpress.com
 - Co-Founder <at> http://www.jbug.com.ar
 
 - Salatino "Salaboy" Mauricio -

_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
Wolfgang Laun | 4 Aug 2010 10:34
Picon

[rules-dev] ActivationCancelledEvent / ActivationCancelledCause

The enum type defines three values as indication for an activation's cancellation.
WME_MODIFY, FILTER and CLEAR. Since I was missing something, I looked
and found that CLEAR is used for two very much different reasons:
- due to Agenda.clear()
- when deleting a rule.

Is this intentional?

-W

_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
Mark Proctor | 4 Aug 2010 10:51

Re: [rules-dev] ActivationCancelledEvent / ActivationCancelledCause

On 04/08/2010 09:34, Wolfgang Laun wrote:
The enum type defines three values as indication for an activation's cancellation.
WME_MODIFY, FILTER and CLEAR. Since I was missing something, I looked
and found that CLEAR is used for two very much different reasons:
- due to Agenda.clear()
- when deleting a rule.
Filter is the result of the agenda-filter causing the activation to cancel:
                        if ( filter == null || filter.accept( item ) ) {
                            // fire it
                            fireActivation( item );
                            result = true;
                        } else {
                            // otherwise cancel it and try the next
                            final EventSupport eventsupport = (EventSupport) this.workingMemory;

                            eventsupport.getAgendaEventSupport().fireActivationCancelled( item,
                                                                                          this.workingMemory,
                                                                                          ActivationCancelledCause.FILTER );
                            tryagain = true;
                        }

WME_MODIFY is the result of any wme action that causes an activation to be cancelled.

CLEAR is the result of a forced cancellation of an activation, either be explicitely calling clear or removing a rule.

I agree we could probably split that out and have a KB_MODIFY, so that if the activation is cancelled as a result the rule being removed we get a different event.

Mark

Is this intentional?

-W

_______________________________________________ rules-dev mailing list rules-dev <at> lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev

_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
Wolfgang Laun | 4 Aug 2010 10:57
Picon

Re: [rules-dev] ActivationCancelledEvent / ActivationCancelledCause

On 4 August 2010 10:51, Mark Proctor <mproctor <at> codehaus.org> wrote:


CLEAR is the result of a forced cancellation of an activation, either be explicitely calling clear or removing a rule.

I agree we could probably split that out and have a KB_MODIFY, so that if the activation is cancelled as a result the rule being removed we get a different event.


Just wanted to point this out - removing rules is not what *we* here need to do. It probably only matters when you want to write a nit-picking event logger.

-W

 
Mark

Is this intentional?

-W

_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
Wolfgang Laun | 4 Aug 2010 12:46
Picon

Re: [rules-dev] Slot Specific and Refraction

A remark on the proposed syntax:
   onChange == [name1, name2, name3]
defines a set of slots by explicit enumeration, whereas
   onchange == [ ! name1, !name2, *]
defines a set my subtracting the enumerated slots from the full set.

I think that using
   onChange == [ ! name1, *, name2 ]
doesn't make sense, since "name2" is already in '*'. This means that
only negated slot names make sense in combination with '*'. This,
in turn, means that '*' in addition to a list of negated slots is
redundant.

Therefore, only a list of all positive or all negated slot names makes
sense. Thus, all possible sets can be defined by permitting nothing
but one of these forms:
   onChange == [<name>,...]
   onChange == [*]
   onChange != [<name>,...]   // subtract all enumerated from full set

One can also permit these two identical forms:
   onChange == []
   onChange != [*]
and
   onChange != []
which is the same as
   onChange == [*]

Best
-W




On 31 July 2010 20:53, Mark Proctor <mproctor <at> codehaus.org> wrote:
 http://blog.athico.com/2010/07/slot-specific-and-refraction.html

_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev

_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
Mark Proctor | 4 Aug 2010 13:02

Re: [rules-dev] Slot Specific and Refraction

On 04/08/2010 11:46, Wolfgang Laun wrote:
A remark on the proposed syntax:
   onChange == [name1, name2, name3]
defines a set of slots by explicit enumeration, whereas
   onchange == [ ! name1, !name2, *]
defines a set my subtracting the enumerated slots from the full set.

I think that using
   onChange == [ ! name1, *, name2 ]
doesn't make sense, since "name2" is already in '*'. This means that
only negated slot names make sense in combination with '*'. This,
in turn, means that '*' in addition to a list of negated slots is
redundant.
That is true, the * could be considered explicit if you have one ore more negated slots.

Therefore, only a list of all positive or all negated slot names makes
sense. Thus, all possible sets can be defined by permitting nothing
but one of these forms:
   onChange == [<name>,...]
   onChange == [*]
   onChange != [<name>,...]   // subtract all enumerated from full set
agreed

One can also permit these two identical forms:
   onChange == []
   onChange != [*]
and
   onChange != []
which is the same as
   onChange == [*]
yup, I like those ideas too. I'll get the wiki updated with them.

Mark

Best
-W




On 31 July 2010 20:53, Mark Proctor <mproctor <at> codehaus.org> wrote:
 http://blog.athico.com/2010/07/slot-specific-and-refraction.html

_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev

_______________________________________________ rules-dev mailing list rules-dev <at> lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev

_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
Mauricio Salatino | 4 Aug 2010 16:46
Picon
Gravatar

[rules-dev] another weird problem with the trunk

I'm fixing some of the drools-grid problems right now in the trunk and I wanna comment here that
I need to comment out in the parent pom file all the thing related with wagon. For some reason,
my IDE is not able to deal with it. When I run the build from the console everything goes fine.
I can also run the build from my IDE, but for some reason the dependency with the wagon plugin cannot be resolved.
Any one experiencing this problem? I'm with JDK 1.6

--
 - CTO <at> http://www.plugtree.com 
 - MyJourney <at> http://salaboy.wordpress.com
 - Co-Founder <at> http://www.jbug.com.ar
 
 - Salatino "Salaboy" Mauricio -

_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev

Gmane