-
If an argument is a string with tags inside (like ), XmlRpcSerializer does not serialize the character >, which may lead to server errors.
The fix consists in adding a case statement :
case '>' :
writer.write(">");
break;.
2009-10-20 13:46:52 UTC by nobody
-
Hi,
Question 1
--------------
I cannot understand principles of adding Content-Lenght by server....
<init-param> <!-- Optional, defaults to 0 -->
<param-name>streamMessages</param-name>
<param-value>1</param-value>
...
if this param equal to 0 (by default - server must return Content-Lenght, am I right? How to force return...
2009-09-14 20:36:08 UTC by vinnitu
-
Hi Max,
You're right, it appears that the 1.1.1 has not been released separately yet. I will get on it and create a separate release for that one. The Simple-package is a combination of the Redstome XML-RPC library and the Simple HTTP server for those who do not already run a separate server like Jetty. In many cases, people just use the regular release and publish their services using the...
2009-09-08 13:15:19 UTC by gregerohlson
-
The proxy-based example on the redstone webpage looks very nice - however I find it *seriously* off-putting when an open-source project fails to publish its own sourcecode clearly.
The current redstone 1.1.1 as contained within the redstone/simple/demo bundle doesn't seem to have a source package anywhere in the files area.
2009-09-08 12:25:02 UTC by maxb
-
Oh cool! I knew there was probably a better way hehe.
That makes sense. Thanks Greger!
2009-07-15 22:59:22 UTC by jfreeman88
-
This patch makes XmlRpcClient to explicitly encode the XML data as UTF-8 before sending to the server, otherwise it may raise an error when your environment has a different encoding. Maybe you developers use Linux and have not noticed yet that getBytes() may return non-utf8 bytes depending on the environment. Please see https://bugs.launchpad.net/bzr-eclipse/+bug/388300/comments/20.
2009-07-04 10:27:28 UTC by nobody
-
Hi Joel!
Thanks for your interest in the XML-RPC library. I've been away from the keyboard for a few days on vacation, so I haven't been able to respond until now.
Another way of solving the problem would be to encapsulate your array in the "arguments array". In other words, the serialization mechanism will serialize the objects you pass to invoke() as they come in the arguments...
2009-06-22 11:52:50 UTC by gregerohlson
-
I used the "Simple + XML-RPC" implementation of Redstone, where instead of having to hook up the system to a webserver you can just generate a makeshift java webserver.
It has worked well for me, but one issue I had was that every time the Simple webserver received an RPC, it would print information about the call. Turns out that the current version (version 1.0) always has...
2009-06-18 20:01:08 UTC by jfreeman88
-
Shalakazai!!!
The Simple+XML-RPC combo contains 3 JAR files. One of them is almost 50 kb, another almost 200kb, and one is 4 kb. Ironically the problem was in the 4kb one...lol. I spent all that time trying to learn how everything worked too :(
The solution is to download the source code for the smallest JAR file, make a few changes, compile, and then JAR it into a replacement JAR. The...
2009-06-18 19:54:08 UTC by jfreeman88
-
Thought I'd share this in case anyone had a similar problem. My solution is idiotic but it is easy to do and it does work...
When using Redstone RMI, I found that I had trouble remotely invoking on a method that takes in an arbitrary number of objects. From the client I might call a invoke a method in this manner:
Object[] objs = {"Hello", "Goodbye"}
client.invoke(...
2009-06-17 18:29:02 UTC by jfreeman88
