javax.xml.crypto.NoSuchMechanismException: Mechanism type DOM not available at javax.xml.crypto.dsig.XMLDSigSecurity.getEngineClassName(Unknown Source)

xml-security-dev | Nayan Hajratwala | 9 years ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    Mechanism type DOM not available

    xml-security-dev | 9 years ago | Nayan Hajratwala
    javax.xml.crypto.NoSuchMechanismException: Mechanism type DOM not available at javax.xml.crypto.dsig.XMLDSigSecurity.getEngineClassName(Unknown Source)
  2. 0

    users-cxf-apache - Re: WSSJ Interceptor invoked instead of Policy - msg#00158 - Recent Discussion OSDir.com

    osdir.com | 1 year ago
    javax.xml.crypto.NoSuchMechanismException: class configured for > XMLSignatureFactory: org.jcp.xml.dsig.internal.dom.DOMXMLSignatureFactory > not a XMLSignatureFactory

    Root Cause Analysis

    1. javax.xml.crypto.NoSuchMechanismException

      Mechanism type DOM not available at javax.xml.crypto.dsig.XMLDSigSecurity.getEngineClassName(Unknown Source)

      at javax.xml.crypto.dsig.XMLDSigSecurity.getImpl()
    2. Java RT
      XMLDSigSecurity.getImpl
      1. javax.xml.crypto.dsig.XMLDSigSecurity.getImpl(Unknown Source)
      2. javax.xml.crypto.dsig.XMLDSigSecurity.getImpl(Unknown Source)
      2 frames