It is alpha software. In other words, it is not yet sufficiently mature. Most possibly, lots of details will change in the near future. Give it a try, if you like, but do not expect to use it without modifications in the medium term.
| [top] |
That's simple: Set the properties "enabledForExtensions" and "gzipCompressing". That said, note the following hints:
| [top] |
That's as simple as enabling request compression: Set the properties "enabledForExtensions" and "gzipRequesting". That said, note the following hints:
| [top] |
Yes, use the class TimingOutCallback.
<![CDATA[
// Wait for 10 seconds.
TimingOutCallback callback = new TimingOutCallback(10 * 1000);
XmlRpcClient client = new XmlRpcClient(url);
client.executeAsync(methodName, params, callback);
try {
return callback.waitForResponse();
} catch (TimeoutException e) {
System.out.println("No response from server.");
} catch (Exception e) {
System.out.println("Server returned an error message.");
}
]]>| [top] |
Set the property "enabledForExtensions". Note, that enabling the streaming mode doesn't mean, that all responses are served in streaming mode. It depends on the clients:
| [top] |
Set the property "enabledForExtensions". Note, that enabling the streaming mode doesn't mean, that all responses are served in streaming mode. It depends on the clients:
| [top] |
The PropertyHandlerMapping assumes, that handlers are POJO's (plain old java objects). However, this is not always desirable. For example, sometimes it is assumed that handlers need to be initialized by the servlet, which is configured through parameters.
The recommended solution is to create a subclass of the XmlRpcServlet, which in turn uses a subclass of the PropertyHandlerMapping:
<![CDATA[
public interface InitializableHandler {
void init(HttpServlet pServlet) throws XmlRpcException;
}
public class MyXmlRpcServlet extends XmlRpcServlet {
protected PropertyHandlerMapping newPropertyHandlerMapping(URL url) throws IOException, XmlRpcException {
return new PropertyHandlerMapping(getClass().getClassLoader(), url){
protected Object newHandlerObject(ClassLoader pClassLoader, String pClassName)
throws XmlRpcException {
Object o = super.newHandlerObject(pClassLoader, pClassName);
((InitializableHandler) o).init(MyXmlRpcServlet.this);
return o;
}
};
}
}
]]>| [top] |
That's a similar question than the question on initializing handlers. The main difference is, that in this case you want to initialize the handler with any request. So, here's how to do it: First of all, we assume that all handlers will implement an interface RequestInitializableHandler. This interface has an init method, which is being called to receive an object with the clients IP address:
<![CDATA[
public class MyConfig extends XmlRpcHttpRequestConfigImpl {
private String clientIpAddress;
public String getClientIpAddress() {
return clientIpAddress;
}
public void setClientIpAddress(String pClientIpAddress) {
clientIpAddress = pClientIpAddress;
}
}
public interface RequestInitializableHandler {
public void init(MyConfig pConfig);
}
public class MyXmlRpcServlet extends XmlRpcServlet {
protected XmlRpcServletServer newXmlRpcServer(ServletConfig pConfig)
throws XmlRpcException {
return new XmlRpcServletServer(){
protected XmlRpcHttpRequestConfigImpl newConfig(HttpServletRequest pRequest) {
MyConfig config = new MyConfig();
config.setClientIpAddress(pRequest.getRemoteAddr());
return config;
}
};
}
protected PropertyHandlerMapping newPropertyHandlerMapping(URL url) throws IOException, XmlRpcException {
PropertyHandlerMapping result = super.newPropertyHandlerMapping(url);
result.setInitializableHandler(new InitializableHandler(){
public void init(XmlRpcRequest pRequest, Object pObject)
throws XmlRpcException {
((RequestInitializableHandler) pObject).init((MyConfig) pRequest.getConfig());
}
});
return result;
}
}
]]>| [top] |