>> In step 3) what data types should be supported? byte, short, int, long, >> float, double and String?
> Should simply reuse code from the ReflectionUtils. (Don't remember the > class name right now, but there is existing functionality, which is used > by the AbstractReflectiveXmlRpcHandlerMapping. Thank you for the pointer. I look it up. >> What exception should be thrown (ServletException?) if no matching method >> can be found in step 2) or data type conversion fails in step 3)? >A ServletException mapping the actual exception (for example >IllegalArgumentException). Assume that you with mapping mean wrapping as in new ServletException(someIllegalArgumentException). >> I can provide patches for the above when we have an agreement on the >> solution and if you can a) guarantee that you will accept patches and b) >> create a new snapshot for the Maven repo. >I never agree to anything like a). :-) I am open, as you very well know. We have a deal :) > As for b): Who is running the nightly builds on the Maven snapshot > repository, do you think? Some poor guy that works the night shift :) Jochen, I will start with the patches later today and an issue to Jira for each of the two enhancements. Appreciate your help and input - as always. Regards, Jimisola -- View this message in context: http://www.nabble.com/How-to-setup-and-configure-a-Servlet-solution-programmatically-tf2300489.html#a6406568 Sent from the Apache Xml-RPC - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
