[ http://issues.apache.org/jira/browse/WICKET-57?page=comments#action_12452563 ] Johan Compagner commented on WICKET-57: ---------------------------------------
isn't this then a common issue for all javascript event methods that have urls in them? Can't we do this then on a single point where we call escape markup? > XHTML validator complains about RadioChoice markup > -------------------------------------------------- > > Key: WICKET-57 > URL: http://issues.apache.org/jira/browse/WICKET-57 > Project: Wicket > Issue Type: Bug > Components: wicket > Affects Versions: 1.2.3 > Reporter: Gili > > Wicket generates the following code for a RadioChoice: > <input name="taskType" type="radio" value="0" id="taskType_0" > onclick="location.href='/RequestMOBIUser/RequestMOBIserverAdmin?wicket:interface=:0:taskType:1:IOnChangeListener&taskType=0';"/> > but the XHTML validator complains: > ------------------------ > Line 50 column 237: cannot generate system identifier for general entity > "taskType". > ...face=:0:taskType:1:IOnChangeListener&taskType=0';"/><label > for="taskType_0">U > An entity reference was found in the document, but there is no reference by > that name defined. Often this is caused by misspelling the reference name, > unencoded ampersands, or by leaving off the trailing semicolon (;). The most > common cause of this error is unencoded ampersands in URLs as described by > the WDG in "Ampersands in URLs". > Entity references start with an ampersand (&) and end with a semicolon (;). > If you want to use a literal ampersand in your document you must encode it as > "&" (even inside URLs!). Be careful to end entity references with a > semicolon or your entity reference may get interpreted in connection with the > following text. Also keep in mind that named entity references are > case-sensitive; &Aelig; and æ are different characters. > If this error appears in some markup generated by PHP's session handling > code, this article has explanations and solutions to your problem. > Note that in most documents, errors related to entity references will trigger > up to 5 separate messages from the Validator. Usually these will all > disappear when the original problem is fixed. > ------------------------ > and it highlights the error as the "&taskType=0" in the URL. Any idea on > how to fix this? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
