Christian Kloner wrote:
ups, it must be like that (I posted my own implementation class of the
Provider Interface, sry):
//We use Axis, set the Axis provider to make sure not to use the soap
provider
WSIFPluggableProviders.overrideDefaultProvider(
"http://schemas.xmlsoap.org/wsdl/soap/";,
new
org.apache.wsif.providers.soap.apacheaxis.WSIFDynamicProvider_ApacheAxis());
Christian,
thanks for you help but your mail answers to the following question: how
can I use the Axis provider instead of the Apache SOAP one for SOAP
calls. Where my question was, once I use the Axis provider, it always
uses the RPC SOAP encoding and provide no space for literal encoding.
Jeff
Christian Kloner schrieb:
You have to specify the Provider for the
http://schemas.xmlsoap.org/wsdl/soap/ namespace explicitly e.g.:
//We use Axis only, set our modified Axis provider
WSIFPluggableProviders.overrideDefaultProvider(
"http://schemas.xmlsoap.org/wsdl/soap/";,
new WSIFDynamicProvider_ICAxis());
lg,
chris
Jeff MAURY (JIRA) schrieb:
Axis provider always uses SOAP encoding style
---------------------------------------------
Key: WSIF-85
URL: http://issues.apache.org/jira/browse/WSIF-85
Project: Axis-WSIF
Type: Bug
Components: Basic Architecture Versions: current (nightly),
2.0 Environment: Windows XP SP2 + Sun JDK 1.4.2
Reporter: Jeff MAURY
Fix For: current (nightly)
When accessing a literal RPC based we service, WSIF, when using the
Axis provider, always use the SOAP encoding style. This lead to
error when running against Axis for example
begin:vcard
fn:Jeff MAURY
n:MAURY;Jeff
org:SCORT
email;internet:[EMAIL PROTECTED]
version:2.1
end:vcard
