This week's book giveaway is in the JavaFX forum.
We're giving away four copies of Introducing JavaFX 8 Programming and have Herbert Schildt on-line!
See this thread for details.
The moose likes Other Application Frameworks and the fly likes Enable/Disable Modules Strategy Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Introducing JavaFX 8 Programming this week in the JavaFX forum!
JavaRanch » Java Forums » Frameworks » Other Application Frameworks
Bookmark "Enable/Disable Modules Strategy" Watch "Enable/Disable Modules Strategy" New topic

Enable/Disable Modules Strategy

Luciano A. Pozzo
Ranch Hand

Joined: Jun 20, 2005
Posts: 112

I have a project divided in several modules (or several spring projects). And some modules can work with and without dependecies. So, the question is: what is the best approach to advise a module that a dependency is enabled or disabled?

Today we are using beans, declared in the spring xml, example:

But we think that it's not a safe approach, because the client can enable the module just changing the spring xml. And we cannot remove the dependency , because dependent modules use the interfaces.

I agree. Here's the link:
subject: Enable/Disable Modules Strategy
It's not a secret anymore!