Jersey Client - Using ContainerListener
By Pavel Bucek-Oracle on May 05, 2009
I would like to introduce a possibility to monitor connections made within jersey client api. Monitoring in this case means have knowledge about amount of transferred bytes.
This functionality is provided (as many others) as a client filter, concretely ConnectionListenerFilter. To create ConnectionListenerFilterinstance, you have to implement OnStartConnectionListener. It might look as follows:
Looks simple (and it is). This factory creates ContainerListener instance based on ClientRequest. Important note: ClientRequest instance here may be used only for getting values. Any attempt to change anything will produce UnsupportedOperationException.
Ok. Now we need ContainerListener implementation. This class is defined as:
Parameters should be easy to understand, delta is always difference to previous call, bytes is sum of sent/received bytes so far and totalBytes is value from http header (if present, otherwise is set to -1).
Every request has a simple "lifecycle":
1) Send request
2) Receive response
Method onSent is called during step one only when request has some entity. When request is sent and response has no entity, onFinish() is called and that's it. More interesting scenario is when response contains some entity - onReceiveStart is called after sending a request and onReceived during data receiving. Method onFinish is called after whole entity is read.
You will probably have some nice GUI progress bar but I'm going to do only plain text log for now to keep it simple.
And we're almost done! Last thing to do is register our ListenerFactory as a client filter:
and actually do a request:
Output should look like this:
You can experiment with some requests containing entity (so you will see that onSent method is called during sending).
For more information about project Jersey visit http://jersey.dev.java.net