Jervisliu | 1 May 20:21 2010
Picon

Re: [rules-dev] Fwd: Eclipse Plugin: JBoss Rules

Hi Mic, which Eclipse plugin are we referring to? I also cced this email 
to BRMS Eclipse tooling guys. They are the experts.

Cheers,
Jervis

Michael Neale wrote:
> Do we need to bother?
>
> ---------- Forwarded message ----------
> From: Lynn Gayowski <lynn.gayowski <at> eclipse.org>
> Date: Thursday, April 29, 2010
> Subject: Eclipse Plugin: JBoss Rules
> To: michael.neale <at> gmail.com
>
>
>
>
>
>
>
>
>
> Hi Michael!  I noticed that your plugin on
> http://marketplace.eclipse.org <http://www.eclipseplugincentral.com/>
> has not been updated since November 15, 2006.  Is your plugin
> still
> active?  We moved all plugins from
> Eclipse PlugIn Central to Marketplace December, 2009 and we are now
> planning to remove old content.  We ask that you please update it
(Continue reading)

Michael Neale | 2 May 00:15 2010
Picon

Re: [rules-dev] Eclipse Plugin: JBoss Rules

The main drools plugin.

On Sunday, May 2, 2010, Jervisliu <jliu <at> redhat.com> wrote:
> Hi Mic, which Eclipse plugin are we referring to? I also cced this email
> to BRMS Eclipse tooling guys. They are the experts.
>
> Cheers,
> Jervis
>
> Michael Neale wrote:
>> Do we need to bother?
>>
>> ---------- Forwarded message ----------
>> From: Lynn Gayowski <lynn.gayowski <at> eclipse.org>
>> Date: Thursday, April 29, 2010
>> Subject: Eclipse Plugin: JBoss Rules
>> To: michael.neale <at> gmail.com
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Hi Michael!  I noticed that your plugin on
>> http://marketplace.eclipse.org <http://www.eclipseplugincentral.com/>
>> has not been updated since November 15, 2006.  Is your plugin
>> still
(Continue reading)

Wolfgang Laun | 5 May 07:53 2010
Picon

[rules-dev] Reference to Drools in an article

Dear Drools Developers:

Drools is mentioned and actually presented in several sample rules in
the (German) article that has appeared in
"Regelorientiertes Programmieren in der Bahntechnik", in SIGNAL +
DRAHT, 4, April 2010. The English summary:

Rule-based Programming in Railway-Oriented Applications

Using rule-based systems is a well established software
technology, successfully deployed in numerous application areas.
The article presents a short introduction in their basic
workings and a survey of applications, both overall and
focussing on the railway business, and it showcases existing
railway-oriented applications and current developments at
Thales Austria.

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

Mauricio Salatino | 5 May 14:17 2010
Picon

Re: [rules-dev] Reference to Drools in an article

awesome!

On Wed, May 5, 2010 at 1:53 AM, Wolfgang Laun <wolfgang.laun <at> gmail.com> wrote:
Dear Drools Developers:

Drools is mentioned and actually presented in several sample rules in
the (German) article that has appeared in
"Regelorientiertes Programmieren in der Bahntechnik", in SIGNAL +
DRAHT, 4, April 2010. The English summary:

Rule-based Programming in Railway-Oriented Applications

Using rule-based systems is a well established software
technology, successfully deployed in numerous application areas.
The article presents a short introduction in their basic
workings and a survey of applications, both overall and
focussing on the railway business, and it showcases existing
railway-oriented applications and current developments at
Thales Austria.

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



--
- http://salaboy.wordpress.com
- 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
billhainaut | 6 May 22:24 2010
Picon

[rules-dev] Rule syntax to accumulate time segments over a limited set of date ranges

Drools Experts:

I have a list of the following fact objects sent to my rules:

CrewSegment
Date startDate
Date endDate
double crewHours
int personId

along with an object to designate seats:

SeatAssignment
int seatId
int personId

Here is the rule I want to enforce in English: No crew member (uniquely identified by personId) can have more than 56 hours of total crewHours in any 7 day period. The rule I've written so far is:

when
$s : SeatAssignment ( )
$total : Number( doubleValue > 56 )
from accumulate( CrewSegment( personId == $s.personId, $crewHours : crewHours ),
sum( $crewHours ) )

This rule nicely catches any instance where more than 56 hours are committed by a person, but does not limit the time period to 7 days.

How do I limit the search to be sure that it is 56 hours WITHIN 7 days, and not just 56 hours total over ANY time period?

Thanks in advance for any help you can provide!!!

Bill

_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
Mauricio Salatino | 6 May 22:32 2010
Picon

Re: [rules-dev] Rule syntax to accumulate time segments over a limited set of date ranges

you have the start and end date, you can filter with that information?
CrewSegment( personId == $s.personId, $crewHours : crewHours, startDate <= "<date>", endDate => "<date>" ),

Greetings.

On Thu, May 6, 2010 at 4:24 PM, <billhainaut <at> gmail.com> wrote:
Drools Experts:

I have a list of the following fact objects sent to my rules:

CrewSegment
Date startDate
Date endDate
double crewHours
int personId

along with an object to designate seats:

SeatAssignment
int seatId
int personId

Here is the rule I want to enforce in English: No crew member (uniquely identified by personId) can have more than 56 hours of total crewHours in any 7 day period. The rule I've written so far is:

when
$s : SeatAssignment ( )
$total : Number( doubleValue > 56 )
from accumulate( CrewSegment( personId == $s.personId, $crewHours : crewHours ),
sum( $crewHours ) )

This rule nicely catches any instance where more than 56 hours are committed by a person, but does not limit the time period to 7 days.

How do I limit the search to be sure that it is 56 hours WITHIN 7 days, and not just 56 hours total over ANY time period?

Thanks in advance for any help you can provide!!!

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




--
- http://salaboy.wordpress.com
- 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
Bill Hainaut | 6 May 22:45 2010
Picon

Re: [rules-dev] Rule syntax to accumulate time segments over a limited set of date ranges


The date range is somewhat arbitrary (not necessarily under my control),
therefore, I don't know what "date" to enter in this part:

startDate <= "<date>"

The "<date>" is not really a factor, as long as the latest CrewSegment end
date is within 7 days of the earliest CrewSegment start date.

Am I making sense with this explanation?

salaboy wrote:
> 
> you have the start and end date, you can filter with that information?
> CrewSegment( personId == $s.personId, $crewHours : crewHours, startDate <=
> "<date>", endDate => "<date>" ),
> 
> 

--

-- 
View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Rule-syntax-to-accumulate-time-segments-over-a-limited-set-of-date-ranges-tp782165p782190.html
Sent from the Drools - Dev mailing list archive at Nabble.com.
_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev

Bill Hainaut | 7 May 18:13 2010
Picon

Re: [rules-dev] Rule syntax to accumulate time segments over a limited set of date ranges


This seems to do the trick.  I hate the ugly date math, but otherwise, I'm
satisfied:

	$s : SeatAssignment ( )
	$mission : CrewSegment( taskBeingTested == true )
        $total : Number( doubleValue > 56 ) 
               from accumulate( CrewSegment( personId == $s.personId,
endDate.time <= $mission.endDate.time, startDate.time >
($mission.endDate.time - (7L * 24L * 60L * 60L * 1000L)), $crewHours :
crewHours ),
                                sum( $crewHours ) )

Bill Hainaut wrote:
> 
> Drools Experts:
> 
> I have a list of the following fact objects sent to my rules:
> 
> CrewSegment
> Date startDate
> Date endDate
> double crewHours
> int personId
> 
> along with an object to designate seats:
> 
> SeatAssignment
> int seatId
> int personId
> 
> Here is the rule I want to enforce in English: No crew member (uniquely  
> identified by personId) can have more than 56 hours of total crewHours in  
> any 7 day period. The rule I've written so far is:
> 
> when
> $s : SeatAssignment ( )
> $total : Number( doubleValue > 56 )
> from accumulate( CrewSegment( personId == $s.personId, $crewHours :  
> crewHours ),
> sum( $crewHours ) )
> 
> This rule nicely catches any instance where more than 56 hours are  
> committed by a person, but does not limit the time period to 7 days.
> 
> How do I limit the search to be sure that it is 56 hours WITHIN 7 days,
> and  
> not just 56 hours total over ANY time period?
> 
> Thanks in advance for any help you can provide!!!
> 
> Bill
> 
> _______________________________________________
> rules-dev mailing list
> rules-dev <at> lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev
> 
> 

--

-- 
View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Rule-syntax-to-accumulate-time-segments-over-a-limited-set-of-date-ranges-tp782165p784099.html
Sent from the Drools - Dev mailing list archive at Nabble.com.
_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev

Greg Barton | 7 May 18:59 2010
Picon

Re: [rules-dev] Rule syntax to accumulate time segments over a limited set of date ranges

Two suggestions:

1) Use the joda time library for representing date/time if possible.  It's bundled with droole because of
fusion and is much easier to work with.

2) If you use some "ugly" pattern often, define a custom operator to makw the syntax cleaner. 

GreG

On May 7, 2010, at 11:13, Bill Hainaut <billhainaut <at> gmail.com> wrote:

This seems to do the trick.  I hate the ugly date math, but otherwise, I'm
satisfied:

   $s : SeatAssignment ( )
   $mission : CrewSegment( taskBeingTested == true )
       $total : Number( doubleValue > 56 ) 
              from accumulate( CrewSegment( personId == $s.personId,
endDate.time <= $mission.endDate.time, startDate.time >
($mission.endDate.time - (7L * 24L * 60L * 60L * 1000L)), $crewHours :
crewHours ),
                               sum( $crewHours ) )

Bill Hainaut wrote:

Drools Experts:

I have a list of the following fact objects sent to my rules:

CrewSegment
Date startDate
Date endDate
double crewHours
int personId

along with an object to designate seats:

SeatAssignment
int seatId
int personId

Here is the rule I want to enforce in English: No crew member (uniquely  
identified by personId) can have more than 56 hours of total crewHours in  
any 7 day period. The rule I've written so far is:

when
$s : SeatAssignment ( )
$total : Number( doubleValue > 56 )
from accumulate( CrewSegment( personId == $s.personId, $crewHours :  
crewHours ),
sum( $crewHours ) )

This rule nicely catches any instance where more than 56 hours are  
committed by a person, but does not limit the time period to 7 days.

How do I limit the search to be sure that it is 56 hours WITHIN 7 days,
and  
not just 56 hours total over ANY time period?

Thanks in advance for any help you can provide!!!

Bill

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

--

-- 
View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Rule-syntax-to-accumulate-time-segments-over-a-limited-set-of-date-ranges-tp782165p784099.html
Sent from the Drools - Dev mailing list archive at Nabble.com.
_______________________________________________
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

Randy Secrist | 8 May 05:25 2010
Picon

[rules-dev] .classpath files within drools trunk

There are a number of references to M2_REPO in eclipse .classpath files which are appear to no longer be used by the MVN build (for at least the test case + install phase).  I'm assuming it is because the CI loop is fine but the eclipse stuff has not been maintained.


Would any committers here be interested if I patched out the artifacts within the .classpath files which I don't think we need anymore and sent up the diff?

or - 

should we remove the .classpath and .project?

or - 

should we enable the sonatype maven plugin within the .project files?

Some examples are:
drools-decisiontables/.classpath has
 - antlr
 - cglib
 - stringtemplate
 - hamcrest-core
 - hamcrest-library
 - jmock-legacy
 - jmock
 - objenesis

Let me know what you guys think ...

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

Gmane