Wait a bit for 1.3 Final in the next few weeks, you can put that into
production. But please do try 1.3 RC2 out to make sure everything
*you* need works. An other note, i myself would worry if saw *no*
posts about problems which would mean no one is even bothing to work
with it let alone put it int
I'd like someone to tell me that Axis2 is ready for prime time. I've jumped
on the list partially to see if Axis2 is ready. But I see enough posts about
Axis2 issues to hang tight with Axis1.4 for now.
cara
On 7/27/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
>
> If your Axis 1.x services use
If your Axis 1.x services use document/literal bindings, then the
migration is pretty easy. If you use rpc bindings, though, you must
convert them.
Anne
On 7/26/07, Demetris G <[EMAIL PROTECTED]> wrote:
>
> And thanks much to you David as well for the information below. I was
> expecting that
> s
And thanks much to you David as well for the information below. I was
expecting that
some work at least will need to be done on the client side.
david wrote:
Hello Demetris, Ann Manes (above-the-call-of-duty) rewrote my Axis1.4 WSDL
(rpc-encoded) as so-called to assume the document-literal
Hello Demetris, Ann Manes (above-the-call-of-duty) rewrote my Axis1.4 WSDL
(rpc-encoded) as so-called to assume the document-literal binding.
And, Viola!, the WSDL2JAVA tool migrated the Axis1.4 code to Axis2. The only
caveat is: the client has to be migrated likewise. HTH, David.
Demetris G w
Hi all,
I asked this question once before and although a bit broad I thought
I would
hear something back. I am trying my luck once again - I see and hear poor
souls out there struggling with real old versions of Axis and my guess
is that
migrating to Axis2 is a bit scary for them. Can any
