|
one minute client tutorialThis is a very quick introduction to xws4j. Skim read it to get an idea of how simple it is to invoke a function of a XMPP IO Data service. I'm sure you'll have questions afterwards. IExecutionPipe The client side of xws4j is an XMPP client. A Jabber ID (XMPP client account) is required to create the client. Beside this an "execution pipe" is passed to optionally "inject" listener code from the socket thread into the correct GUI thread. If the meaning of an execution pipe is not patent yet you may directly progress to the next chapter. Example 1: there is no GUI thread, use the socket thread.
Example 2: xws4j is used in an Eclipse Plug-In, listener code is injected in Eclipse's GUI thread.
Client Creating the client requires a JID, resource, password, server name, port, and the execution pipe. Optionally it is possible to define a connection listener that is informed on connect/disconnect events. Example: a client is created and connected for the JID user@myserver.example.net and the resource bio
IFunction To create and invoke a function the created client must be used. Input and output of the function is org.w3c.dom.Element. Example 1: create and invoke a function and wait for the result (block)
Invoking functions without blocking but with listeners is supported, too. Example 2: handle the results of function invocation in a user defined listener
|