如何重新发送 GWT 请求工厂请求

Question

是否可以重新发送 RequestFactory 传输？我想做这个等效的事情：如何在使用RequestFactory时重新发送GWT RPC请求。从以前的请求重新发送相同的有效负载相当简单，但我还需要调用相同的方法。这是我的 RequestTransport 类，我希望在处理完（在本例中）向用户请求登录凭据后"重新触发"原始请求：

package org.greatlogic.rfexample2.client;
import com.google.gwt.http.client.Request;
import com.google.gwt.http.client.RequestBuilder;
import com.google.gwt.http.client.RequestCallback;
import com.google.gwt.http.client.Response;
import com.google.web.bindery.requestfactory.gwt.client.DefaultRequestTransport;
/**
 * Every request factory transmission will pass through the single instance of this class. This can
 * be used to ensure that when a response is received any global conditions (e.g., the user is no
 * longer logged in) can be handled in a consistent manner.
 */
public class RFERequestTransport extends DefaultRequestTransport {
//--------------------------------------------------------------------------------------------------
private IClientFactory _clientFactory;
//==================================================================================================
private final class RFERequestCallback implements RequestCallback {
private RequestCallback _requestCallback;
private RFERequestCallback(final RequestCallback requestCallback) {
  _requestCallback = requestCallback;
} // RFERequestCallback()
@Override
public void onError(final Request request, final Throwable exception) {
  _requestCallback.onError(request, exception);
} // onError()
@Override
public void onResponseReceived(final Request request, final Response response) {
  if (response.getStatusCode() == Response.SC_UNAUTHORIZED) {
    _clientFactory.login();
  }
  else {
    _clientFactory.setLastPayload(null);
    _clientFactory.setLastReceiver(null);
    _requestCallback.onResponseReceived(request, response);
  }
} // onResponseReceived()
} // class RFERequestCallback
//==================================================================================================
@Override
protected void configureRequestBuilder(final RequestBuilder builder) {
  super.configureRequestBuilder(builder);
} // configureRequestBuilder()
//--------------------------------------------------------------------------------------------------
@Override
protected RequestCallback createRequestCallback(final TransportReceiver receiver) {
  return new RFERequestCallback(super.createRequestCallback(receiver));
} // createRequestCallback()
//--------------------------------------------------------------------------------------------------
void initialize(final IClientFactory clientFactory) {
  _clientFactory = clientFactory;
} // initialize()
//--------------------------------------------------------------------------------------------------
@Override
public void send(final String payload, final TransportReceiver receiver) {
  String actualPayload = _clientFactory.getLastPayload();
  TransportReceiver actualReceiver;
  if (actualPayload == null) {
    actualPayload = payload;
    actualReceiver = receiver;
    _clientFactory.setLastPayload(payload);
    _clientFactory.setLastReceiver(receiver);
  }
  else {
    actualReceiver = _clientFactory.getLastReceiver();
  }
  super.send(actualPayload, actualReceiver);
} // send()
//--------------------------------------------------------------------------------------------------
}

Answer 1

根据托马斯的建议，我尝试发送另一个请求，只是替换了RequestTransport.send()方法中的有效载荷和接收器，这奏效了;我想请求工厂没有保留进一步的上下文，并且来自服务器的响应足以让 RF 确定需要做什么来解压缩返回到RequestCallback.onResponseReceived()方法的request和response之外的响应。如果有人有兴趣查看我的代码，请告诉我，我会在这里发布。

Answer 2

这是可能的，但你有很多事情要做。

我也有同样的想法。我花了大约 2 天的时间寻找一个好的解决方案。我试图拦截 RequestContext 和其他类上的服务器调用.java。但是如果你这样做，你必须为几乎每一类的 gwt 请求工厂做你自己的实现。所以我决定采用更简单的方法。

在我触发

请求的任何地方，我都会处理响应并再次触发它。当然，你必须小心，不要陷入循环。