I'm looking into this thing...good education for me....
Well, none of the following seem to work...
http://twitter.com/statuses/friends_timeline/138312412.rss (copied from
RSS link on my home page in twitter)
http://twitter.com/statuses/user_timeline/imtiazahmedhe.atom
I constantly get exceptions in the Tomcat window....
INFO - basic authentication scheme selected
INFO - No credentials available for BASIC 'Twitter API'@twitter.com:80
WARN - Cookie rejected: "$Version=0; k=122.166.132.49.1283416574217413;
$Path=/;
$Domain=.twitter.com". Illegal domain attribute ".twitter.com". Domain of
origi
n: "twitter.com"
WARN - Cookie rejected: "$Version=0;
_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCBLJl
tEqAToHaWQiJWUzNmM2MDJlMzAwYWI0%250ANDgwZTI1YzQyMTM1ZWZmNTUxIgpmbGFzaElDOidBY3Rp
b25Db250cm9sbGVy%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--f444c2f2e03a6cf82
db8c3808bc0a27bfdd26066; $Path=/; $Domain=.twitter.com". Illegal domain
attribut
e ".twitter.com". Domain of origin: "twitter.com"
INFO - basic authentication scheme selected
INFO - No credentials available for BASIC 'Twitter API'@twitter.com:80
ERROR - Actor threw an exception
java.lang.StringIndexOutOfBoundsException: String index out of range: -3
at java.lang.String.charAt(String.java:686)
at org.apache.esme.external.Feed.fixDateString(Feed.scala:94)
at org.apache.esme.external.Feed.parseInternetDate(Feed.scala:86)
at org.apache.esme.external.AtomFeed.getDate(AtomFeed.scala:66)
at
org.apache.esme.external.Feed$$anonfun$apply$1$$anonfun$apply$3.apply
(Feed.scala:54)
at
org.apache.esme.external.Feed$$anonfun$apply$1$$anonfun$apply$3.apply
(Feed.scala:48)
at scala.Seq$class.map(Seq.scala:280)
at
scala.RandomAccessSeq$Mutable$$anon$11.map(RandomAccessSeq.scala:109)
at
org.apache.esme.external.Feed$$anonfun$apply$1.apply(Feed.scala:48)
at
org.apache.esme.external.Feed$$anonfun$apply$1.apply(Feed.scala:47)
at scala.List.flatMap(List.scala:1132)
at org.apache.esme.external.Feed.apply(Feed.scala:47)
at org.apache.esme.external.Feed.apply(Feed.scala:37)
at
org.apache.esme.actor.MessagePullActor$MessagePullActor$$anonfun$mess
ageHandler$2.apply(MessagePullActor.scala:85)
at
org.apache.esme.actor.MessagePullActor$MessagePullActor$$anonfun$mess
ageHandler$2.apply(MessagePullActor.scala:71)
at
net.liftweb.actor.LiftActor$class.execTranslate(LiftActor.scala:354)
at
org.apache.esme.actor.MessagePullActor$MessagePullActor.execTranslate
(MessagePullActor.scala:66)
at
net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$Specia
lizedLiftActor$$proc2(LiftActor.scala:244)
at
net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$Spe
cializedLiftActor$$processMailbox$1.apply(LiftActor.scala:165)
at
net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$Spe
cializedLiftActor$$processMailbox$1.apply(LiftActor.scala:165)
at
net.liftweb.actor.SpecializedLiftActor$class.around(LiftActor.scala:1
79)
at
org.apache.esme.actor.MessagePullActor$MessagePullActor.around(Messag
ePullActor.scala:66)
at
net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$Specia
lizedLiftActor$$processMailbox(LiftActor.scala:164)
at
net.liftweb.actor.SpecializedLiftActor$$anonfun$3$$anonfun$apply$1.ap
ply(LiftActor.scala:128)
at
net.liftweb.actor.SpecializedLiftActor$$anonfun$3$$anonfun$apply$1.ap
ply(LiftActor.scala:128)
at
net.liftweb.actor.LAScheduler$$anonfun$1$$anon$1$$anon$2.run(LiftActo
r.scala:44)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908)
at java.lang.Thread.run(Thread.java:619)
Imtiaz
----- Original Message -----
From: "Ethan Jewett" <[email protected]>
To: <[email protected]>
Sent: Thursday, September 02, 2010 1:15 PM
Subject: Re: ESME - 266 - my fix in progress, hopefully...
On Thu, Sep 2, 2010 at 8:33 AM, Vassil Dichev <[email protected]> wrote:
There's something I don't understand, why are you using the search
timeline instead of the standard API, e.g.
http://twitter.com/statuses/user_timeline/esjewett.atom
Hmmm, I'm not sure. I just originally had it set up as the search
timeline and then it stopped working.
Does it work with this?
I'll try, hopefully later today.
Also, I don't understand the Jira description- does it put the whole
content of the search page as one tweet?
No, you and Imtiaz are right: the Jira description is misleading. At
most it puts part of the page into the ESME message. I'm beginning to
think that it's actually putting the title of the page into the
message. Really not sure.
Ethan
