Hello out there, 1. sorry for the following question... but where can I find a public mailing list archive of these mailing lists?
xmlrpc-dev-help xmlrpc-user-help 2. I think I have an idea for an improvement of the Invoker.class. Currently all incoming xmlrpc requests are converted to "general purpose" Types (http://ws.apache.org/xmlrpc/types.html). e.g. <struct> => java.util.Hashtable. Wouldn't it be nice if the invoker not only searches for methods with these "unhandy" types as parameters but also for methods with JavaBeans as parameters? Hm, bad english ;-) Little example for "old" and "new" styled Invokers: Let's suppose, that I have a guestbook and want to add an "Entry" to it. An "Entry" should consist of the following properties: String name, String comment. "old": // "easy" way public boolean addEntry(String guestbookId, String name, String comment); // "flexible" way public boolean addEntry(String guestbookId, Hashtable entry); "new": // "desirable" way public boolean addEntry(String guestbookId, Entry entry); I think this would be great. With this flexibility the methods defined in the handlers could be used in other ways, too (not only for this xmlrpc-case-stuff). The problem is quite evident. The invoker needs to "guess" which method he has to call. But in my mind there's hovering an idea. Maybe some "BeanUtils" magic could be created to solve this... What do you think? greets from germany, marcel
