This week's book giveaway is in the Java in General forum. We're giving away four copies of Think Java: How to Think Like a Computer Scientist and have Allen B. Downey & Chris Mayfield on-line! See this thread for details.
In its WebSphere Application server IBM implements some of the WS-Security standard. Yet it uses the declaretive model, i.e. the aliases, passwords(encrypted) and names of certificates and keys are stored in the deployment descriptor XML file. Every time when a new certificate or private key is added, the descriptor file needs to be updated and the project has to be redeployed, needless to say the server has to be restarted. How does this approach can handle a broad consumer-based Web Service?