You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2005/08/04 05:03:35 UTC
[jira] Updated: (GERONIMO-640) Remove dependency on Sun internals code for URL decoding
[ http://issues.apache.org/jira/browse/GERONIMO-640?page=all ]
Aaron Mulder updated GERONIMO-640:
----------------------------------
Fix Version: 1.0-M5
Description:
[Looking at 1.0-M3 source code]
The Geronimo types:
org.apache.geronimo.system.url.file.Handler
and
org.apache.geronimo.system.url.file.FileURLConnection
both import and use the Sun non-API type "sun.net.www.ParseUtil". It appears that the usage is quite trivial, and can easily be replaced by API calls on URLDecoder. This will remove a JRE-implementation dependency.
The only caveat is that simple tests show that URLDecoder decodes 'more' than the ParseUtil, so while both methods will convert "a%20b" to "a b"; the URLDecoder will convert "a+b" to "a b" whereas ParseUtil leaves it as "a+b". Is this difference in decoding behavior expected by Geronimo?
was:
[Looking at 1.0-M3 source code]
The Geronimo types:
org.apache.geronimo.system.url.file.Handler
and
org.apache.geronimo.system.url.file.FileURLConnection
both import and use the Sun non-API type "sun.net.www.ParseUtil". It appears that the usage is quite trivial, and can easily be replaced by API calls on URLDecoder. This will remove a JRE-implementation dependency.
The only caveat is that simple tests show that URLDecoder decodes 'more' than the ParseUtil, so while both methods will convert "a%20b" to "a b"; the URLDecoder will convert "a+b" to "a b" whereas ParseUtil leaves it as "a+b". Is this difference in decoding behavior expected by Geronimo?
Environment:
Still a problem for M4 and HEAD as of today
> Remove dependency on Sun internals code for URL decoding
> --------------------------------------------------------
>
> Key: GERONIMO-640
> URL: http://issues.apache.org/jira/browse/GERONIMO-640
> Project: Geronimo
> Type: Improvement
> Versions: 1.0-M3
> Reporter: Tim Ellison
> Fix For: 1.0-M5
> Attachments: decode-patch.txt
>
> [Looking at 1.0-M3 source code]
> The Geronimo types:
> org.apache.geronimo.system.url.file.Handler
> and
> org.apache.geronimo.system.url.file.FileURLConnection
> both import and use the Sun non-API type "sun.net.www.ParseUtil". It appears that the usage is quite trivial, and can easily be replaced by API calls on URLDecoder. This will remove a JRE-implementation dependency.
> The only caveat is that simple tests show that URLDecoder decodes 'more' than the ParseUtil, so while both methods will convert "a%20b" to "a b"; the URLDecoder will convert "a+b" to "a b" whereas ParseUtil leaves it as "a+b". Is this difference in decoding behavior expected by Geronimo?
--
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