org.xml.sax.SAXParseException

Attribute "type" is not declared for element "action".

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 web3382

  • via strutstestcase by nobody
    , 1 year ago
    Attribute "type" is not declared for element "action".
  • via Coderanch by Seetharaman Venkatasamy, 7 months ago
    Attribute "calcellable" must be declared for element type "action".
  • via Oracle Community by 843830, 1 year ago
    Attribute "validation" must be declared for element type "action".
  • Stack trace

    • org.xml.sax.SAXParseException: Attribute "type" is not declared for element "action". at org.apache.crimson.parser.Parser2.error(Parser2.java:3354) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1595) at org.apache.crimson.parser.Parser2.content(Parser2.java:1963) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691) at org.apache.crimson.parser.Parser2.content(Parser2.java:1963) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691) at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667) at org.apache.crimson.parser.Parser2.parse(Parser2.java:337) at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448) at org.apache.commons.digester.Digester.parse(Digester.java:1572) at org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionServlet.java:738) at org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet.java:687) at org.apache.struts.action.ActionServlet.init(ActionServlet.java:333) at javax.servlet.GenericServlet.init(GenericServlet.java:211) at servletunit.struts.MockStrutsTestCase.getActionServlet(MockStrutsTestCase.java:326) at servletunit.struts.MockStrutsTestCase.actionPerform(MockStrutsTestCase.java:394) at cactus.TestCactusLoginAction.testFailedLogin(TestCactusLoginAction.java:67) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:421) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:305) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:186)

    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.