2010-01-13 46 views
2

我在GAE/J上使用Twitter4J API。當用戶刷新頁面時重用OAuth請求令牌 - GAE上的Twitter4j

我想在用戶訪問我的頁面時使用請求令牌。 (回叫URL)。然後按刷新按鈕。我爲此編寫下面的代碼。但是當用戶按刷新按鈕。我收到驗證憑據錯誤。請參閱stacktrance。當用戶第一次使用該標記時,它工作正常。

HomeServlet.java代碼:

HttpSession session = request.getSession(); 

      twitter.setOAuthConsumer(FFConstants.CONSUMER_KEY, 
        FFConstants.CONSUMER_SECRET); 
      String token = (String) session.getAttribute("token"); 
      String authorizedToken = (String)session.getAttribute("authorizedToken"); 

      User user = null; 
      if (!token.equals(authorizedToken)){ 
       AccessToken accessToken = twitter.getOAuthAccessToken(
         token, (String) session 
           .getAttribute("tokenSecret")); 
       twitter.setOAuthAccessToken(accessToken); 
       user = twitter.verifyCredentials(); 
       session.setAttribute("authorizedToken", token); 
       session.setAttribute("user", user); 
      }else{ 
       user = (User)session.getAttribute("user"); 
      } 

      TwitterUser twitterUser = new TwitterUser(); 
      twitterUser.setFollowersCount(user.getFollowersCount()); 
      twitterUser.setFriendsCount(user.getFriendsCount()); 
      twitterUser.setFullName(user.getName()); 
      twitterUser.setScreenName(user.getScreenName()); 
      twitterUser.setLocation(user.getLocation()); 

請建議我怎麼能做到這一點。我在很多網站上看到過。它們以相同的標記保留用戶。即使用戶一次又一次按瀏覽器刷新。

請幫忙。

異常堆棧跟蹤:

Reason: twitter4j.TwitterException: 401:Authentication credentials were missing or incorrect. /friends/ids.xml This method requires authentication. 
at twitter4j.http.HttpClient.httpRequest(HttpClient.java:469) 
at twitter4j.http.HttpClient.get(HttpClient.java:412) at twitter4j.Twitter.get(Twitter.java:276) 
at twitter4j.Twitter.get(Twitter.java:228) at twitter4j.Twitter.getFriendsIDs(Twitter.java:1819) 
at com.tff.servlet.HomeServlet.doGet(HomeServlet.java:86) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) 
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487) 
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093) at com.google.apphosting.utils.servlet.ParseBlobUploadFilter.doFilter(ParseBlobUploadFilter.java:97) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084) at com.google.apphosting.runtime.jetty.SaveSessionFilter.doFilter(SaveSessionFilter.java:35) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084) at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) at com.google.apphosting.runtime.jetty.AppVersionHandlerMap.handle(AppVersionHandlerMap.java:238) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:313) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:830) at com.google.apphosting.runtime.jetty.RpcRequestParser.parseAvailable(RpcRequestParser.java:76) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381) at com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:135) at com.google.apphosting.runtime.JavaRuntime.handleRequest(JavaRuntime.java:235) at com.google.apphosting.base.RuntimePb$EvaluationRuntime$6.handleBlockingRequest(RuntimePb.java:5235) at com.google.apphosting.base.RuntimePb$EvaluationRuntime$6.handleBlockingRequest(RuntimePb.java:5233) at com.google.net.rpc.impl.BlockingApplicationHandler.handleRequest(BlockingApplicationHandler.java:24) at com.google.net.rpc.impl.RpcUtil.runRpcInApplication(RpcUtil.java:363) at com.google.net.rpc.impl.Server$2.run(Server.java:838) at com.google.tracing.LocalTraceSpanRunnable.run(LocalTraceSpanRunnable.java:56) at com.google.tracing.LocalTraceSpanBuilder.internalContinueSpan(LocalTraceSpanBuilder.java:536) at com.google.net.rpc.impl.Server.startRpc(Server.java:793) at com.google.net.rpc.impl.Server.processRequest(Server.java:368) at com.google.net.rpc.impl.ServerConnection.messageReceived(ServerConnection.java:448) at com.google.net.rpc.impl.RpcConnection.parseMessages(RpcConnection.java:319) at com.google.net.rpc.impl.RpcConnection.dataReceived(RpcConnection.java:290) at com.google.net.async.Connection.handleReadEvent(Connection.java:466) at com.google.net.async.EventDispatcher.processNetworkEvents(EventDispatcher.java:759) at com.google.net.async.EventDispatcher.internalLoop(EventDispatcher.java:205) at com.google.net.async.EventDispatcher.loop(EventDispatcher.java:101) at com.google.net.rpc.RpcService.runUntilServerShutdown(RpcService.java:251) at com.google.apphosting.runtime.JavaRuntime$RpcRunnable.run(JavaRuntime.java:394) at java.lang.Thread.run(Unknown Source) 

回答

1

我已經確定了問題。

我再次使用請求令牌,如果我想獲取用戶的twitter信息。那是錯的。我必須改用訪問令牌。我寫了一篇博文here