Bug #1941

Remove CSRA-specific Functionality out of Engine Core

Added by S. Wrede over 9 years ago. Updated over 9 years ago.

Status:ResolvedStart date:08/19/2014
Priority:ImmediateDue date:
Assignee:S. Wrede% Done:

0%

Category:-
Target version:-

Description

                aListener.addHandler(new Handler() {
                    @Override
                    public void internalNotify(Event event) {
                        log.info("Got " + event.getData().getClass() + " Event");

                        // hack to only register _active_ situation updates
                        if (event.getData().getClass() == rst.classification.SituationType.Situation.class) {
                            List<SituationType.Situation.AspectClassification> aspects = ((rst.classification.SituationType.Situation) event.getData()).getAspectsList();

                            if (!aspects.isEmpty()) {
                                for (SituationType.Situation.AspectClassification aspectClassification : aspects) {
                                    if (aspectClassification.getAspectName().equalsIgnoreCase("Activity_Corridor")) {
                                        if (aspectClassification.getState().getDecidedClass().toStringUtf8().equalsIgnoreCase("active")) {
                                            log.info("Activity_Corridor is found to be active, forwarding!");
                                            triggerRSBeventInSCXML(exec, event);
                                        }
                                    }
                                }

We need to find a different concept to cope with these specific conditions.

History

#1 Updated by J. Wienke over 9 years ago

  • Status changed from New to Resolved

I think I removed everything that was specific on the way to other tickets ;)

Also available in: Atom PDF