Github user aledsage commented on a diff in the pull request:
https://github.com/apache/incubator-brooklyn/pull/83#discussion_r15519752
--- Diff:
software/webapp/src/main/java/brooklyn/entity/webapp/DynamicWebAppClusterImpl.java
---
@@ -127,4 +158,140 @@ protected boolean calculateServiceUp() {
}
return up;
}
+
+ // TODO this will probably be useful elsewhere ... but where to put it?
+ /** Waits for the given target to report service up, then runs the
given task
+ * (often an invocation on that entity), with the given name.
+ * If the target goes away, this task marks itself inessential
+ * before failing so as not to cause a parent task to fail. */
+ static <T> Task<T> whenServiceUp(final Entity target, final
TaskAdaptable<T> task, String name) {
+ return Tasks.<T>builder().name(name).dynamic(true).body(new
Callable<T>() {
+ @Override
+ public T call() {
+ try {
+ while (true) {
+ if (!Entities.isManaged(target)) {
+ Tasks.markInessential();
+ throw new IllegalStateException("Target
"+target+" is no longer managed");
+ }
+ if (target.getAttribute(Attributes.SERVICE_UP)) {
+ Tasks.resetBlockingDetails();
+ TaskTags.markInessential(task);
+ DynamicTasks.queue(task);
+ try {
+ return task.asTask().getUnchecked();
+ } catch (Exception e) {
+ if (Entities.isManaged(target)) {
+ throw Exceptions.propagate(e);
+ } else {
+ Tasks.markInessential();
+ throw new
IllegalStateException("Target "+target+" is no longer managed", e);
+ }
+ }
+ } else {
+ Tasks.setBlockingDetails("Waiting on
"+target+" to be ready");
+ }
+ // TODO replace with subscription?
+ Time.sleep(Duration.ONE_SECOND);
+ }
+ } finally {
+ Tasks.resetBlockingDetails();
+ }
+ }
+ }).build();
+ }
+
+ @Override
+ @Effector(description="Deploys the given artifact, from a source URL,
to a given deployment filename/context")
--- End diff --
Do we really need the `@Effector` and `@EffectorParam` annotations here? We
have them on the interface's method that this `@Override`s so that should be
enough I'd have thought?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
