Johannes Wagener
11-18-2008, 02:37 PM
Hello,
some months ago we introduced our "web service" protocol proposal to you
that was finally accepted as "XEP-0244 IO Data" in June. XEP-0244 IO
Data enables machine-to-machine communication over XMPP with the
features listed here:
* The services, functions and communication semantics (function
input/output XML Schemata) are fully discoverable over XMPP
* Long lasting remote jobs are session based (optional), thus they
can be continued after the client disconnected and reconnected
* Asynchronous client notification, thus a client must not
indefinitely poll for the result.
The XEP is available at:
http://xmpp.org/extensions/xep-0244.html
Here we want to introduce xws4j, an an implementation of XEP-0244 IO
Data for Java.
A preview of the project is available at:
http://xws4j.sourceforge.net/preview/
The project covers:
* Client and server side implementations compatible with all current
XMPP Server implementations (server side is an XMPP connecting component)
* Auto-generation of client stub code via a batch binder (creates
Java XML bindings for functions input/output XML Schemata)
* Auto-generation and loading of client stub libraries at runtime
dynamically and on-the-fly (for scripting engines, see the links below)
* Optional service discovery performed at runtime dynamically and
on-the-fly
* Listener based as well as blocking API calls
Egon recently blogged about xws4j and XEP-0244:
http://chem-bla-ics.blogspot.com/2008/10/next-generation-asynchronous.html
http://chem-bla-ics.blogspot.com/2008/11/next-generation-asynchronous.html
You are welcome to read the blog entries to get an impression about what
xws4j is supposed to do and can do.
best regards
Johannes
some months ago we introduced our "web service" protocol proposal to you
that was finally accepted as "XEP-0244 IO Data" in June. XEP-0244 IO
Data enables machine-to-machine communication over XMPP with the
features listed here:
* The services, functions and communication semantics (function
input/output XML Schemata) are fully discoverable over XMPP
* Long lasting remote jobs are session based (optional), thus they
can be continued after the client disconnected and reconnected
* Asynchronous client notification, thus a client must not
indefinitely poll for the result.
The XEP is available at:
http://xmpp.org/extensions/xep-0244.html
Here we want to introduce xws4j, an an implementation of XEP-0244 IO
Data for Java.
A preview of the project is available at:
http://xws4j.sourceforge.net/preview/
The project covers:
* Client and server side implementations compatible with all current
XMPP Server implementations (server side is an XMPP connecting component)
* Auto-generation of client stub code via a batch binder (creates
Java XML bindings for functions input/output XML Schemata)
* Auto-generation and loading of client stub libraries at runtime
dynamically and on-the-fly (for scripting engines, see the links below)
* Optional service discovery performed at runtime dynamically and
on-the-fly
* Listener based as well as blocking API calls
Egon recently blogged about xws4j and XEP-0244:
http://chem-bla-ics.blogspot.com/2008/10/next-generation-asynchronous.html
http://chem-bla-ics.blogspot.com/2008/11/next-generation-asynchronous.html
You are welcome to read the blog entries to get an impression about what
xws4j is supposed to do and can do.
best regards
Johannes