I've updated the Mule support to HiveMind as a container for its managed components to be able to use the HiveMind service-id as a reference.
This is far more concise the the full class name and overall lets you abuse of it and have (under different service-id) different implementation of the same interface.
After stressing this in my current project i would like to consider having Mule to embrace a Registry supplied by an external entity.
Yep, i can already hear someone thinking to Tapestry...
No comments:
Post a Comment