You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Philipp Kronberger (JIRA)" <ji...@apache.org> on 2012/12/05 18:05:58 UTC

[jira] [Updated] (WICKET-4913) HtmlDocumentParser does not support tags containing number (e.g. h1-h6)

     [ https://issues.apache.org/jira/browse/WICKET-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Philipp Kronberger updated WICKET-4913:
---------------------------------------

    Attachment: document-parser-error.tar.gz

simple maven-project containg a test producing the described error
                
> HtmlDocumentParser does not support tags containing number (e.g. h1-h6)
> -----------------------------------------------------------------------
>
>                 Key: WICKET-4913
>                 URL: https://issues.apache.org/jira/browse/WICKET-4913
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 6.3.0
>            Reporter: Philipp Kronberger
>            Priority: Minor
>              Labels: patch
>         Attachments: document-parser-error.tar.gz
>
>
> When a html-document is parsed, that contains a headline (h1-h6), following exception is thrown:
> {code}
> java.lang.StringIndexOutOfBoundsException: String index out of range: -3
> 	at java.lang.String.substring(String.java:1937)
> 	at org.apache.wicket.protocol.http.documentvalidation.HtmlDocumentParser.processDirective(HtmlDocumentParser.java:251)
> 	at org.apache.wicket.protocol.http.documentvalidation.HtmlDocumentParser.getNextToken(HtmlDocumentParser.java:120)
> 	at HtmlDocumentParserTest.testGetNextToken(HtmlDocumentParserTest.java:16)
> 	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:597)
> 	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> 	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> 	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> 	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> 	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
> 	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> 	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
> 	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
> 	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
> 	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
> 	at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> 	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira