fail fast if jms is not configured properly

zanata · Mar 10, 2015 · 6531ac9 · 6531ac9
1 parent d97eee2
commit 6531ac9
Showing 1 changed file with 14 additions and 0 deletions.
diff --git a/zanata-war/src/main/java/org/zanata/notification/NotificationManager.java b/zanata-war/src/main/java/org/zanata/notification/NotificationManager.java
@@ -30,6 +30,7 @@
 import lombok.extern.slf4j.Slf4j;
 
 import org.jboss.seam.ScopeType;
+import org.jboss.seam.annotations.Create;
 import org.jboss.seam.annotations.In;
 import org.jboss.seam.annotations.Name;
 import org.jboss.seam.annotations.Observer;
@@ -59,6 +60,19 @@ public class NotificationManager implements Serializable {
     @In
     private QueueSession queueSession;
 
+
+    @Create
+    public void onCreate() {
+        try {
+            mailQueueSender.getQueue();
+        } catch (JMSException e) {
+            // it will never reach this block. As long as you call getQueue()
+            // and if the queue is not defined, seam will terminate:
+            // org.jboss.seam.jms.ManagedQueueSender.getQueue(ManagedQueueSender.java:45
+            Throwables.propagate(e);
+        }
+    }
+
     @Observer(LanguageTeamPermissionChangedEvent.LANGUAGE_TEAM_PERMISSION_CHANGED)
     public
             void onLanguageTeamPermissionChanged(