Funny you should ask, I was just asking the same last week when I was in
that position.

However, I was working the client side and you are working the server
side (I think).

On the client side, I had to adjust some package names, and modify all
my code that unmarshalled the response by looking for Maps instead of
Hashtables and Object[]'s instead of Vectors.  Going the other way,
marshalling the requests, it is acceptable and easier to pass Lists
instead of Vectors, or you could continue to use Vectors, I think.

What else you might have to do on the server side someone else will have
to answer.

-----Original Message-----
From: mshillin [mailto:[EMAIL PROTECTED] 
Sent: Friday, October 13, 2006 1:22 PM
To: xmlrpc-user@ws.apache.org
Subject: xmlrpc 2.x to xmlrpc 3.x migration



I am attempting to migrate my app from 2.x to 3.x are there any docs
that
explain how to do this?

Using 2.x my handlers (exposing the methods available to remote clients
)
implemented ContextXmlRpcHandler.  

My handlers would implement 

execute(String methodName, Vector params, XmlRpcContext context)

The context would contain HTTP Session info, and I would just match up
methods/params via reflection.  Easy enough.

The architecture for XML-RPC 3 is signifcantly different and I do not
see a
way to get the session info to the POJO handlers.

I tried to follow the FAQ (
http://ws.apache.org/xmlrpc/faq.html#client_ip
), but it doesn't compile.  Even after I fixed the compile errors, I
could
not get the posted example to work. It ran, but my over ridden methods
were
never called.

Has anyone accomplished this?




The my methods would be called
-- 
View this message in context:
http://www.nabble.com/xmlrpc-2.x-to-xmlrpc-3.x-migration-tf2438953.html#
a6801200
Sent from the Apache Xml-RPC - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to