[ https://issues.jboss.org/browse/JBRULES-3331?page=com.atlassian.jira.plug... ] Geoffrey De Smet updated JBRULES-3331: -------------------------------------- Summary: IsDoableFilter: For generic moves, provide option to disable them under certain conditions (was: For generic moves, provide option to disable them under certain conditions) Description: Once generic move factories are actually generic selectors, we'd have something like this: {code} <selector> <type>CHANGE_MOVE</> <planningEntityClassIncludes>...</> <planningVariableIncludes>...</> <isDoableFilterClass>...MyIsDoableFilterClass</> {code} Old description: This feature would be done for the same purpose as JBRULES-3330 and also implemented in very much the same way - the Move.isMoveDoable() checks for the existence of any filters and runs all of them. If any of them returns false, the move is not doable. Perhaps JBRULES-3330 and this one could even share the interface - MoveFilter.filter(Solution s, Move m) and newly added MoveFilter.isMoveDoable(Move m). was: This feature would be done for the same purpose as JBRULES-3330 and also implemented in very much the same way - the Move.isMoveDoable() checks for the existence of any filters and runs all of them. If any of them returns false, the move is not doable. Perhaps JBRULES-3330 and this one could even share the interface - MoveFilter.filter(Solution s, Move m) and newly added MoveFilter.isMoveDoable(Move m). -- 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