-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
URLs with query parameters in generated Javadoc should use &, not & #7
Comments
comment Comment 1 by MatrixFrog, Aug 3, 2011
And I haven't done extensive testing but it seems to work. This patch was created against the 0.9.0 tag. |
Index: doclets/src/main/java/com/lunatech/doclets/jax/jaxrs/model/ResourceMethod.java--- doclets/src/main/java/com/lunatech/doclets/jax/jaxrs/model/ResourceMethod.java (revision 138)
|
comment Comment 2 by project member stephane.epardaud, Aug 15, 2011 |
(10453ca is the same patch I posted on Google Code, just wanted to make it available as an actual git commit.) |
Fixed now, thanks a lot. |
Reported by MatrixFrog, Aug 2, 2011
What steps will reproduce the problem?
@path("resource")
@get
public void getResource(@QueryParam("status") String status, @QueryParam("regex") String regex) {...}
What is the expected output? What do you see instead?
You expect the output to include something like "GET /resource?status=�®ex=�" but instead you see "GET /resource?status=�®ex=�"
What version of the product are you using? On what operating system?
0.9.0, Windows 7
Please provide any additional information below.
When you "view source" on the page, you see "GET /resource?status=�®ex=�" as expected. The browser (I'm using the Aurora build of Firefox, but I assume most other browsers will do the same thing -- I can try them out if you want) sees "®" and it assumes the author meant to write "®" which is the HTML entity for ®, so it displays ®. I would argue the browser is technically wrong, but if the HTML contained "GET /resource?status=�®ex=�" then there would be no ambiguity.
Alternatively, maybe using a particular HTML doctype declaration or something like that, will tell the browser not to be "clever" and only interpret entities that are written properly?
The text was updated successfully, but these errors were encountered: