this is not settle down yet, they might be thirdparty webservices provided by other company. i have to find out these possible issues first, any possible known issues for axis1 client consuming CXF ws
At 2011-05-31 21:58:10，"Benson Margulies" <[email protected]> wrote: >rpc/literal? > >2011/5/31 Damon <[email protected]>: >> Hi, >> >> sorry i didn't make myself clear. >> Using axis1 is mainly for old webservices writen in axis1 >> But i have to consider using axis1 to consume upcoming new webservices which >> are provided by CXF >> >> >> >> >> At 2011-05-31 21:47:03，"Freeman Fang" <[email protected]> wrote: >> >>>Hi, >>> >>>Cxf doesn't support rpc/encoded, so if you chose Axis1 mainly for rpc/ >>>encoded feature, then I think there's no way you can use cxf to talk >>>to Axis1with rpc/encoded. >>> >>>Freeman >>>On 2011-5-31, at 下午9:41, Damon wrote: >>> >>>> Hi all: >>>> The reason i have to use Axis1 is for old services using rpc/ >>>> encoded. >>>> Now i have to consider the interoperable problems, and CXF seems >>>> like the most popular web services framework for now, so any >>>> possible issues would happen if i use Axis1 to consume CXF >>>> webservices? >>>> I only found one in google: using Axis1 consume XPOM/XOT CXF >>>> webservices.. >>>> And just in case, is there any solution for CXF support rpc/ >>>> encoded binding? >>>> >>>> Regards >>> >>>--------------------------------------------- >>>Freeman Fang >>> >>>FuseSource >>>Email:[email protected] >>>Web: fusesource.com >>>Twitter: freemanfang >>>Blog: http://freemanfang.blogspot.com >>>Connect at CamelOne May 24-26 >>>The Open Source Integration Conference >>> >>> >>> >>> >>> >>> >>> >>> >>
