-
That's a brilliant solution, and I learned something new. Thanks alot.
Lars.
2009-01-12 11:55:41 UTC in Redstone XML-RPC Library
-
Just found out that the IntrospectingSerializer is the cause of this...it seems to just see all 'get' methods as properties to be put in the XML-RPC response. That's weird, though, since it should be serializing RPCProject, not Project. Any ideas?.
2009-01-12 11:00:56 UTC in Redstone XML-RPC Library
-
I want to limit the amount of data sent to the client. I did this by doing, for example
public class Project extends RPCProject
{
private String someVarUsedInternally;
}
public class RPCProject
{
protected String what;
protected int I;
protected ArrayList want;
protected String client;
protected String toSee;
}
// RPC Exposed method
public RPCProject...
2009-01-12 10:45:58 UTC in Redstone XML-RPC Library
-
I already sent you an email to let you know, but let me post here for other people:
This solution works for me. Thanks alot.
By the way, have you thought about replacing the Simple + XML RPC package with the one you just linked?
Lars.
2009-01-09 22:30:54 UTC in Redstone XML-RPC Library
-
Hello,
Sending the project structure would be nice. I'm on a deadline, by the end of this month basically so this could save me some time. Also, I heard that using a servlet for this kind of stuff is better anyway - thanks!
Lars.
2009-01-09 13:34:01 UTC in Redstone XML-RPC Library
-
Okay, kinda cheated here and there - in Server.java, I changed
Writer responseWriter = new PrintStream(response.getOutputStream()); to
Writer responseWriter = new StringWriter();
I then did System.out.println(responseWriter.toString()); after the serialization was done. The XML is perfectly valid! Then I thought I'd send that string to the client, by simply doing:
OutputStream stream =...
2009-01-09 12:32:13 UTC in Redstone XML-RPC Library
-
Hello,
After poking through the code a bit, it almost seems like it's streaming the responses to the client? I mean, I can see the writer.write() calls everywhere, and it is flushed in the execute command..it's not like a packet is constructed - it seems to be streamed?
Also, is there some way to print the response of the server before it is sent? Since it seems to be streamed, I would...
2009-01-09 10:35:44 UTC in Redstone XML-RPC Library
-
Hey,
Thanks for giving this a try, and I'm glad you got the same stacktrace, however, I don't think I have that many structs. Let's see. About 27 structs, and all of em have one struct in there. That'd be 54 structs. I'll give you more information on the invocation that fails, like how many structs there actually were.
Thanks!
Lars.
2009-01-08 07:28:19 UTC in Redstone XML-RPC Library
-
1) I did it in two ways, the first way is the actual client I wrote. It uses the PHP-XMLRPC library, and it has the ability to print out the complete response before it is interpreted by the library. That response already contains the errors. So that response looked something like (if I recall correctly)
HTTP 1/1.1 OK
Connection close
<the xml data>
2) Yes, lots of structs, in...
2009-01-07 22:35:37 UTC in Redstone XML-RPC Library
-
I'm using the Simple + Redstone XML-RPC libraries to provide a server. Now, everything went fine, until I started returning some big sets of data...The responses are incorrect XML and seem to be mixed up. Here's a small part of the incorrect format found in the returned XML response:
<value><string>bkabka</string>ing>Co-Worker...
2009-01-07 13:01:23 UTC in Redstone XML-RPC Library
