Recent changes to bugs

Post class missing hashCode implementation

Anonymous — Sat, 30 Oct 2010 06:35:32 -0000

Hello,

The Post class overrides equals and MUST override hashCode() as per java specification.
An implementation of hashCode() that returns href.hashCode() should be ok.

Thanks.

Preemptive authentication

alvins — Mon, 14 May 2007 11:43:57 -0000

Every api call actually does two requests (via httpclient due to http-auth). You can cut this down by prememptively authenticating.

client.getParams().setAuthenticationPreemptive(true);

wrong scope for variable element in delicious.tld

makeSense — Fri, 10 Nov 2006 19:35:37 -0000

I found the following in the
delicious-1.13.jar!/META-INF/delicious.tld

I checked the jsp specification 2.0 and 2.1. Yes,
the valid scopes for variables declared in
tag element are AT_BEGIN, NESTED, AT_END. This scopes
is meant to tell where this variable is visible as a
java variable. It is not the same as the other scope,
which is to tell the scope of an attribute of the
PageContext, "page", "request", "session" or "application".

This bug prevents me from using delicious*.jar on oc4j
since oc4j validates the value of scope tag.

The fix is simple. Just change "page" to "AT_BEGIN", or
"NESTED" or "AT_END", whichever fits. For me, I just
tried with "AT_BEGIN". It seems fine.

Problems with Non-UTF8-Strings

Florian Matthes — Tue, 01 Aug 2006 09:54:31 -0000

I just upgraded to the latest release (delicious-
1.12.jar) and now have problems with postings that
contain non-ASCII characters (like ÄÜäüß)
- in the title
- in the description, or
- in the tags

My Java program is unchanged. It uses the addPost
method with Unicode-Strings:

d.addPost(normalizeURL(t.getLocation()), // URL
t.getName(), // description
brain.getExtended(t.getId()), // extended
brain.getTags(t), // tags
t.getModifiedTimestamp(), // date
true, // replace
true // shared
);

The method does not raise exceptions.

However, when I visit the delicious web site, non-
ASCII characters are distorted / truncated. For
example, see the last postings in:

http://del.icio.us/personalbrain

like: Technische Universit䴠M? - Corporate Design.

The RSS feed for my account

http://del.icio.us/rss/personalbrain

is more helpful and displays the following error
messages (in the title /tags / extended fields):

del.icio.us warning: non-utf8 string! (sorry)
del.icio.us warning: non-utf8 string! (sorry)
del.icio.us warning: non-utf8 string! (sorry)

How can I make sure that non-ASCII characters are
correctly posted to del.icio.us?

Thank you for your assistance
Florian Matthes

getAllPosts and XML parser exception

Otis Gospodnetic — Sun, 11 Dec 2005 21:12:42 -0000

Hi David,

Here is something that looks like a bug:

del.icio.us.DeliciousException: Response parsing
error
at
del.icio.us.Delicious.getAllPosts(Delicious.java:568)
at
......
Caused by: org.xml.sax.SAXParseException: The entity
"nbsp" was referenced, but not declared.
at
org.apache.xerces.parsers.DOMParser.parse(Unknown
Source)
at
org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown
Source)
at
del.icio.us.Delicious.getAllPosts(Delicious.java:532)
... 2 more

The XML being parsed looks like this:

<?xml version='1.0' standalone='yes'?>
<posts update="2005-12-10T20:55:44Z" user="foobar">
<post href="http://something.com/"
description="Fifi.com :: X, Y, and Z"
extended="something.com"
hash="23cde401733d1ebb3849a91343b49454" tag="family"
time="2005-12-10T20:52:47Z" />
</posts>

I don't even see any "nbsp" references above.

I have Xerces 2.6.2 in the classpath (and I see 2.7.1
is the latest version of Xerces)

Ever seen this? Does this look like a delicious-java
bug Xerces or something else? Looks like Xerces, no?

Thanks.

method Post.getDateAsTime() displays wrong timezone

scot mcphee — Fri, 15 Oct 2004 10:22:43 -0000

I was looking at the posting date, and wondering how to
display it in *local time* not GMT as it currently
does. Well, the getDateAsTime() method displays the
date/time component correctly but have a look at the
TimeZone appended to the date object that comes out of it.

In DeliciousUtils you've got a method
getDateFromUTCString() , which the Post uses in it's
getTimeAsDate() method to return a Date.

The problem with that returned Date object is that it
is not in 'UTC' or 'GMT' but actually in the LOCAL
TIMEZONE or the default timezone of the JVM if that's
set to something else. If you do a 'toString()' on the
date object you will see it will print the 'GMT' time
alright but print your local timezone as the Timezone.
So for me it says it posted the links 10 hours earlier
than they were actually posted. A java.util.Date object
is ALWAYS in the default timezone of the JVM.

It then becomes a bigger problem if you want to display
the posting time to the user in the local timezone. You
would have to muck around with offsets and the like and
probably drive you insane with daylight savings time
and what not.

However the fix is pretty simple; java.util.Calendar to
the rescue. Luckily enough the SimpleDateFormat object
can take a Calendar object. This tells SimpleDateFormat
the timezone of the String it's about to parse in. Then
the Date object is returned as the 'correct' date, i.e.
as the default JVM timezone sees it.

This can be done niavely as follows;

public static Date getDateFromUTCString(String time) {
Date result = null;
try {
((SimpleDateFormat)
UTC_DATE_FORMAT_OBJECT.get()).setCalendar(
Calendar.getInstance(TimeZone.getTimeZone("GMT")) );
result = ((SimpleDateFormat)
UTC_DATE_FORMAT_OBJECT.get()).parse(time);
} catch (ParseException e) {
}
return result;
}

Of course it's probably best to set the Calender when
you construct the simple date format in the first place.

At this point the date object will display in LOCAL
TIME but correct vis a vis to the actual GMT time that
the entry was posted.

However now the date is correct, you can convert it
correctly to another date display. for example I could
post something now to delicious, my local time is 20:13
Friday night 15 Oct. Someone on the West Coast of the
USA could now retrieve this date from Delicious and
using the local timezone Calendar and simple date
format, display the date in their local time, or using
another Calendar input to SimpleDateFormat, display it
in some other timezone. Daylight savings issues and
everything taken care of.