Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Google Groups by Twitterati, 1 year ago
FWK005 parse may not be called > >> while parsing. at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse > >> (DOMParser.java:253) at > >> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse > >> (DocumentBuilderImpl.java:283) at javax.xml.parsers.DocumentBuilder.parse > >> (DocumentBuilder.java:124)
org.xml.sax.SAXException: FWK005 parse may not be called
> >> while parsing.
 at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse
> >> (DOMParser.java:253)
 at
> >> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse
> >> (DocumentBuilderImpl.java:283)
 at javax.xml.parsers.DocumentBuilder.parse
> >> (DocumentBuilder.java:124)	at twitter4j.http.Response.asDocument(Response.java:119)