Not knowing anything about Twitter4J, but I believe normally once
authorised you would have to persist/save the following values for re-
use on signing any future requests.
* access pin
* access token
* access token secret
* consumer key
* consumer secret

The authorisation process only needs to be done once, to obtain these
values, so perhaps you can set the values into the class and call a
different method to sign any future requests.

Reply via email to