Java Serialization to XML (JSX) serializes/deserializes Java objects to/from XML, so you can save them, send them - and see them! It correctly handles the many Serializable classes in Java and third-party libraries that use Java's builtin Java Object Serialization (JOS) to customize their serialization (for security, validation, faithful deserialisation, and class evolution).
Test mode needed?
Merry Christmas all!
Thanks a lot Patrick, this is a fantastic addition! Two suggestions:
(1) A very important addition is a "test" mode... you don't want us to learn how to publish a release by trial and error!!
How to implement? Only for things that change the database, so only for:
Idea 1: just add a "test" argument for each of these, since there's only two.
Idea 2: could logon in "test" mode. This is what my online credit card acceptor does, so you can test it out fully, before "going live". You are less likely to forget it, if you need only set it once, and it's easier to change if in just one place. But it might be much more trouble for you, with the database on the server side...
(2) I assume that all arguments are strings for the protocol (apart form the structs, of course)? Specifically, the "release focus ID" might be an int... if so, this could be part of the documentation in the FAQ.
BTW: I grabbed apache's xmlrpc http://ws.apache.org/xmlrpc/ (http://ws.apache.org/xmlrpc/) for Java to do this... seems to work well. They have a nice short example of code, and mappings of XMLRPC types to Java types (eg a struct is a Hashtable).
Finally, in the XMLRPC vs SOAP debate, I really much prefer simpler... but I never get to see the XML in practice, at all (except for the error message, when viewing it with a web-browser). Simple XML would be *great* if you could play with the server manually via telnet, but because HTTP demands that you count the characters to give a length, it's impossible... unless you write a tool to do that, but then you might as well just use a proper tool for XMLRPC... so, XMLRPC or SOAP, it just doesn't matter so far as the protocol is concerned.
Awesomely cool idea!
What an awesomely cool idea! I've been looking for
this, as a way to send email from an application,
without the user having to configure their mailhost
This allows hotmail to be used as a logger of any
information you want.
hmmm... I hope that hotmail don't mind, or else
there might be a bit of an arms race happening....