java.lang.IllegalAccessError

try to access field org.w3c.tidy.ParserImpl._parseHead from class org.w3c.tidy.ParserImpl$ParseHTML

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 web1853

  • via jtidy by timkington
    , 1 year ago
    try to access field org.w3c.tidy.ParserImpl.\_parseHead from class org.w3c.tidy.ParserImpl$ParseHTML
  • try to access field org.w3c.tidy.ParserImpl.\_parseHead from class org.w3c.tidy.ParserImpl$ParseHTML
  • via httpunit by *anonymous
    , 1 year ago
    try to access field org.w3c.tidy.ParserImpl.\_parseHead from class org.w3c.tidy.ParserImpl$ParseHTML
  • Stack trace

    • java.lang.IllegalAccessError: try to access field org.w3c.tidy.ParserImpl._parseHead from class org.w3c.tidy.ParserImpl$ParseHTML at org.w3c.tidy.ParserImpl$ParseHTML.parse(ParserImpl.java) at org.w3c.tidy.ParserImpl.parseDocument(ParserImpl.java) at org.w3c.tidy.Tidy.parse(Tidy.java) at org.w3c.tidy.Tidy.parseDOM(Tidy.java) at oracle.portal.provider.v2.render.XmlFilter.getXMLDocumentForHTMLContent(Unknown Source) at oracle.portal.provider.v2.render.XmlFilter.filterContent(Unknown Source) at oracle.portal.provider.v2.render.http.URLRenderer.renderBody(Unknown Source) at oracle.portal.provider.v2.render.RenderManager.render(Unknown Source) at oracle.portal.provider.v2.DefaultPortletInstance.render(Unknown Source) at oracle.webdb.provider.v2.adapter.soapV1.ProviderAdapter.showPortlet(Unknown Source) at oracle.webdb.provider.v2.adapter.soapV1.ProviderAdapter.handleHttp(Unknown Source) at java.lang.reflect.Method.invoke(Native Method) at oracle.webdb.provider.v2.adapter.SOAPServlet.doHTTPCall(Unknown Source) at oracle.webdb.provider.v2.adapter.SOAPServlet.service(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

    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.