THe CLIENTHTTPSENDER is an invisible component that opens up an http connection from the browser side to another program when triggered. It is typically used to integrate the browser client into some other client side programs, that provide an http-interface.
The URL-attribute contains the URL-String that is called. You may execute a POST-request and append additional parameters by using attribute URLPOSTDATA. You may also send back the response of calling the URL from the client back to the server by setting attribute URLCALLBACK to "true".
Please note: if the URL that you call is not in the domain of your server, then the browser security policy typically will deny to process the communication successfully. Browsers always are "willed" to communicate back to their server, but are "not willed" to communicate to several endpoints in parallel. You have to explicitly check the CORS policy of the servers that you communicate to. They have to explicitly allow (e.g. via http header-parameter "Access-Control-Allow-Origin") what type of browser content can open up the communication.
Typically used attributes
All attributes are
General attributes are
Used inside: BEANPROCESSING
Binding to server side method that processes the events coming from this component.
| #{methodBinding} | Method binding |
Special binding to component adapter object instance on server side. The component adapter must be an instance of IComponentAdapterBinding. For some components (e.g. FIXGRID) there is an extended interface (e.g. IFIXGRIDComponentAdapterBinding).
| #{tobedefined} | Binding to IComponentAdapter instance |
Name of macro that is used for generating certain attributes of this component. Please pay attention: the value of this attribute is read one time for each control and cannot be changed afterwards.
Comment that can be asigned to any component. The comment is not operationally used.
| Any text | Any text |
Configuration information that is attached to this component. This information is not functionally used by CaptainCasa, but may be used for any application specific purpose.
Http header parameters that are sent with the request. You may pass a semicolon separated list of parameters, each one consisting out of the name of the parameter, followed by the value.
| name;value | One parameter... |
| name1;value1;name2;value2 | Two parameters... |
| content-type;text/html | Concrete parameter example |
Reference to an outside object that is the content behind the component. E.g. a field is representing a certain field of a database table: in this case you could define the value table;column. The reference plays a siginficant role within the attributemacro management.
| ref | One reference |
| ref1;ref2 | Two references |
| ref1;ref2;ref3 | Three references |
Flag that indicated if this component is rendered at all. If set to false then the component is not rendered - there is no component data sent to the client.
| true | Component is rendered (default) |
| false | Component is not rendered |
Delay in ms which the client waits with sending the http request after being triggered.
| 0 | Imediately (default) |
| 1000 | 1000ms (1 second) |
| 2000 | 2000ms (1 second) |
Trigger value: if the value changes then the component's activity is executed on client side. Use class Trigger on server side for implementations of this property.
URL that is loaded. Either an absolute address, or relative to the jsp starting page.
If set to true then the response of the URL call that is triggered is transferred back to the client.
| true | Call back the server. |
| false | No call back to server (default) |
If defined then an http-post is executed instead of an http-get. The post data is transferred accordingly.