0 Replies Latest reply on Jan 2, 2007 2:30 PM by starksm64

    SecurityDeployer needs to be more selective about what is pr

    starksm64

      Starting the all configuration is producing a duplicate mbean problem as mentioned here:
      http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997313

      The SecurityDeployer needs to be looking for some security related metadata to trigger its behavior.