Hmm, I'm not sure at this late date if anyone wanted to burden the CXF project with that old JAX-RPC stuff they would indeed get "support and encouragement". Who would want to maintain and support that? Unless there is a paid need from one of CXF's sponsors for such functionality, there are legacy products (XFire, Axis1, Sun's JWSDP) that can be used for solve legacy problems such as these without needing to weigh down CXF with yesterday's technology. JAX-WS Dispatch can also be used within CXF for JAX-RPC calls.
Glen bimargulies wrote: > > Karthik, > > Once upon a time, we had an active contributor to CXF who was working > toward JAX-RPC support. He wrote code to support SOAP-encoded > representation in the Aegis data binding. Sadly, he got too busy with > his real job, and never finished. > > There is no plan to work on this. If someone comes to the project who > wants to do it, they will get support and encouragement, but I do not > believe that any of the current contributors have any plans. > > --benson > > > On Thu, Feb 11, 2010 at 2:10 AM, Karthik K <[email protected]> wrote: >> Hi >> >> This is realted to your development metioned in one of the forum. I found >> the its required that CXF supports JAX-RPC as many system is still not >> migrated to JAX-WS and we may required to build atleast a click to our >> legacy systems via CXF. >> >> Kindly confirm me which release of CXF is supporting JAX-RPC. If you can >> pass me an example that would be great. >> >> Thanks and Regards >> Karthik > > -- View this message in context: http://old.nabble.com/Re%3A-VOTE%3A-Extend-CXF-to-support-JAX-RPC---Good-work-tp27547385p27561396.html Sent from the cxf-user mailing list archive at Nabble.com.
