New ST spec for publishing to the correct subscriber
jeremydmiller opened this issue · 0 comments
jeremydmiller commented
Replace:
Send a single message to the correct node
Website1
Listens to memory://harness/website1 with
Listens to memory://localhost/Website1/replies with
Publishes to Harness:Service1
* OneMessage
Handles Message, JobRequest`1, JobRequest`1, JobRequest`1, JobRequest`1, SubscriptionRequested, SubscriptionsChanged, SubscriptionsRemoved, TakeOwnershipRequest, TaskHealthRequest, TaskDeactivation
Service1
Listens to memory://harness/service1 with
Listens to memory://localhost/Service1/replies with
Handles OneMessage, Message, JobRequest`1, JobRequest`1, JobRequest`1, JobRequest`1, SubscriptionRequested, SubscriptionsChanged, SubscriptionsRemoved, TakeOwnershipRequest, TaskHealthRequest, TaskDeactivation
Service2
Listens to memory://harness/service2 with
Listens to memory://localhost/Service2/replies with
Handles OneMessage, Message, JobRequest`1, JobRequest`1, JobRequest`1, JobRequest`1, SubscriptionRequested, SubscriptionsChanged, SubscriptionsRemoved, TakeOwnershipRequest, TaskHealthRequest, TaskDeactivation
Service3
Listens to memory://harness/service3 with
Listens to memory://localhost/Service3/replies with
Handles OneMessage, Message, JobRequest`1, JobRequest`1, JobRequest`1, JobRequest`1, SubscriptionRequested, SubscriptionsChanged, SubscriptionsRemoved, TakeOwnershipRequest, TaskHealthRequest, TaskDeactivation
Actions
Node Website1 sends new message of type OneMessage (first message)
Messages are all accounted for
Assertions
Message of type OneMessage (first message) should be received by Service1
Messages Received
* OneMessage received by memory://harness/service1