[jboss-jira] [JBoss JIRA] (JBRULES-3328) Add an API to allow access to the constraint occurrences of a solution

[David Glassborow (JIRA)]

    [ https://issues.jboss.org/browse/JBRULES-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665677#comment-12665677 ] 

David Glassborow commented on JBRULES-3328:
-------------------------------------------

Geoffrey,
      I've pushed an example change to allow access to constraint occurrences inside the new best solution event.

https://github.com/davidglassborow/drools-planner/commit/781f8e8dbe6792215f46c8a4ef3070bbc3e2678a

My use case:
- real time planning, so solver continuously running
- on new best solution I need to persist the solution details, and all the scoring for the solution, into another system

I've extended the event object to including a working memory. I'm suggesting this is a final solution, just a work in progress to prove the idea. Currently the actually working memory is the wrong one, looks like the working memory of the last best solution as far as I can see. Any help on what I'm doing wrong would be appreciated. I'll also understand if you don't want to change the API like this, I'm happy to keep a private patch for my own system.



                
> Add an API to allow access to the constraint occurrences of a solution
> ----------------------------------------------------------------------
>
>                 Key: JBRULES-3328
>                 URL: https://issues.jboss.org/browse/JBRULES-3328
>             Project: Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: drools-planner
>    Affects Versions: FUTURE
>            Reporter: David Glassborow
>            Assignee: Geoffrey De Smet
>
> For a given solution, I'd like to show what constraint occurrences are in the working memory, and ideally which occurrences for each planning entity.
> This allows end users to understand the schedule, in my experience otherwise they stop trusting the system.
> Currently the demo harness uses an internal API to get this information, and I think it maybe getting the wrong WM, the values looked out of step with the solver last time I looked

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