Details
-
New Feature
-
Status: Closed
-
Minor
-
Resolution: Won't Fix
-
3.2.5
-
None
-
Currently running under Merlin 3.2.4 on Sun's JDK 1.4.2 (also 1.5 beta) on RedHat 9.
Description
Can we have a way to disable Merlin's automatic discovery of components?
I have quite a number of distinct instances of a single component (a work queue). Each work queue represents a different stage of processing within my application. Each queue is serviced by a different component, usually resulting in further work items being enqueued to other queues. My block.xml specifies which components service which queues, and then which subsequent queues receive the output work items.
Unfortunately, if I forget to explicitly put the output queue mappings into the block.xml, the system begins to fail in mysterious ways. Merlin has simply chosen one of the two dozen work queues in some arbitrary fashion and enqueued the item there where it's not expected.
I'd really rather be able to put something in my block.xml - perhaps on a <container/> tag to indicate that the automatic component discovery should be disabled within that component and that dependencies which aren't explicitly filled by entries in the block.xml should result in a failure to deploy.