org.xml.sax.SAXException

FWK005 parse may not be called >>> while parsing. >>> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) [na:na] >>> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown >>> Source) [na:na] >>> at javax.xml.parsers.DocumentBuilder.parse(Unknown Source) [na:1.3.04] >>> at org.opensaml.xml.parse.BasicParserPool$DocumentBuilderProxy.parse(BasicParserPool.java:602)

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web650

  • via nabble.com by Unknown author, 10 months ago
    FWK005 parse may not be called >> while parsing. >>         at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) [na:na] >>         at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown >> Source) [na:na] >>         at
  • via Google Groups by Adam Lantos, 10 months ago
    FWK005 parse may not be called >>>> while parsing. >>>> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) [na:na] >>>> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown >>>> Source) [na:na] >>>> at
  • via java-forums.org by Unknown author, 10 months ago
    FWK005 parse may not be called while parsing. at com.sun.org.apache.xerces.internal.parsers.DOMPars er.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.DocumentBu ilderImpl.parse(Unknown Source) at
  • Stack trace

    • org.xml.sax.SAXException: FWK005 parse may not be called >>> while parsing. >>> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) [na:na] >>> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown >>> Source) [na:na] >>> at javax.xml.parsers.DocumentBuilder.parse(Unknown Source) [na:1.3.04] >>> at org.opensaml.xml.parse.BasicParserPool$DocumentBuilderProxy.parse(BasicParserPool.java:602) at org.opensaml.xml.parse.BasicParserPool.parse(BasicParserPool.java:206)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.