> believe ... but, if your XFire service isn't advertising as
> such, the Axis client shouldn't send it as such
Just one point I'd like to clarify here. Quite a few people don't care about
the generated runtime wsdl. They use the same wsdl to create the service and
the client. So at least one possibility is that the source wsdl was rpc
encoded, xfire couldn't handle that and ignored, and the client made from the
same wsdl _could_ craft encoded messages?
Too much focus on the wsdl xfire generates at runtime :)
I've got a few different ways of configuring xfire that _work_ in that I can
build a client from the runtime wsdl, and things behave as I generally expect,
but I can't use a client built from the same source wsdl that the service was
originally generated from. :)
Cheers,
Karl P
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
