Originally posted by DJDON:
This restore view is usefull when you are switching from faces-page to non-faces page and again back to faces-page.
Originally posted by Roger Chung-Wee:
The developer writes code like this.
Originally posted by Ulf Dittmer:
There is no general answer. It depends on where you want to process the information. If the data is in the SOAP header, you can have a JAX-RPC handler examine it, and maybe reject it. Same on the client side, a handler could add a SOAP header, but shouldn't alter the actual request.
Another consideration is how fine-grained you need the access control to be. If it's just a yes/no thing, a header would do nicely, but if different users have different permissions you might want to have that information in the service, so that you can use it for your access control.
Generally, if it feels like actual information, it goes into the request. If it feels like meta-information, that's what the SOAP headers are for. (Going off-topic, it's a similar decision as to what should be an element, and what should be an attribute in an XML document.)