[#GALAXY-180] URL Encoding docs reference wrong Abdera class and method

Galaxy

URL Encoding docs reference wrong Abdera class and method

Created: 04/Apr/08 03:17 PM Updated: 10/Apr/08 06:30 PM

Component/s:

Documentation

Affects Version/s:

1.0-beta-2

Fix Version/s:

1.0-beta-3

Time Tracking:

Not Specified

Labels:
User impact:	Medium

Description

« Hide

http://www.mulesource.org/display/GALAXY/HTTP+AtomPub+API#HTTPAtomPubAPI-URLEncoding says "If you are using Abdera for your client code, the handy org.apache.abdera.i18n.text.UrlEncoding class has an encode method which can do this for you". That class and method don't exist in the Abdera 0.3.0 client, the correct method now appears to now be EncodingUtil.sanitize().

All

Comments

Work Log

Change History

Transitions

FishEye

Sort Order:

[ Permlink | « Hide ]

Dan Diephouse added a comment - 04/Apr/08 04:48 PM

Thanks. You're right about the class, but you should use the encode method I believe, not the sanitize method.

Hopefully Abdera 0.4.0 will be out next week....

[ Permlink | « Hide ]

Todd Wells added a comment - 04/Apr/08 05:13 PM

Actually, encode() is not what you want here (this is the voice of experience from today) – sanitize() is what you want. Hopefully Abdera 0.4 will have javadocs that include a description of the API, not just the method signatures.

[ Permlink | « Hide ]

Dan Diephouse added a comment - 04/Apr/08 05:42 PM

OK, thats weird. Well I apoligize then.

[ Permlink | « Hide ]

Todd Wells added a comment - 04/Apr/08 06:04 PM

Yeah, the encode() methods on that API are for encoding MIME message headers per RFC 2047.

[ Permlink | « Hide ]

Dan Diephouse added a comment - 10/Apr/08 06:30 PM

Updated docs and 0.4.0 is out today as well.