Kathy, thank you for having a look at the problem! :)
The wscompile task
<wscompile
config="${IN_DIR}/wscompile-config.xml"
verbose="true"
base="${OUT_DIR}/wscompile_output"
define="true"
classpath="."
keep="true"
mapping="${OUT_DIR}/wscompile_output/mapping.xml"
model="${OUT_DIR}/wscompile_output/model.xml.gz"
features="wsi, documentliteral"
/>
The large interface class ;-)
package de.rochade.srap.ws;
import java.rmi.Remote;
import java.rmi.RemoteException;
public interface HelloService extends Remote
{
public String sayHello(String name) throws RemoteException;
}
The WSDL from my .war
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="WSHelloService" targetNamespace="urn:rochade"
xmlns:tns="urn:rochade" xmlns="
http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="
http://www.w3.org/2001/XMLSchema"
xmlns:soap="
http://schemas.xmlsoap.org/wsdl/soap/">
<types>
<schema targetNamespace="urn:rochade" xmlns:tns="urn:rochade"
xmlns:soap11-enc="
http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"
xmlns:wsdl="
http://schemas.xmlsoap.org/wsdl/"
xmlns="
http://www.w3.org/2001/XMLSchema">
<complexType name="sayHello">
<sequence>
<element name="String_1" type="string"
nillable="true"/></sequence></complexType>
<complexType name="sayHelloResponse">
<sequence>
<element name="result" type="string"
nillable="true"/></sequence></complexType>
<element name="sayHello" type="tns:sayHello"/>
<element name="sayHelloResponse"
type="tns:sayHelloResponse"/></schema></types>
<message name="HelloService_sayHello">
<part name="parameters" element="tns:sayHello"/></message>
<message name="HelloService_sayHelloResponse">
<part name="result" element="tns:sayHelloResponse"/></message>
<portType name="HelloService">
<operation name="sayHello">
<input message="tns:HelloService_sayHello"/>
<output
message="tns:HelloService_sayHelloResponse"/></operation></portType>
<binding name="HelloServiceBinding" type="tns:HelloService">
<soap:binding transport="
http://schemas.xmlsoap.org/soap/http"
style="document"/>
<operation name="sayHello">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/></input>
<output>
<soap:body use="literal"/></output></operation></binding>
<service name="WSHelloService">
<port name="HelloServicePort" binding="tns:HelloServiceBinding">
<soap:address
location="REPLACE_WITH_ACTUAL_URL"/></port></service></definitions>
I think the problem could simply be reproduced with the famous
HelloService and features="wsi, documentliteral" wscompile option.
cu
Merten
> -----Original Message-----
> From: kathy walsh [mailto:Kathleen.Walsh_at_Sun.COM]
> Sent: Friday, October 08, 2004 4:34 PM
> To: users_at_jax-rpc.dev.java.net
> Subject: Re: Problems with Dynamic Proxy Client against
> document/literal service
>
> Merten-
> Yes the dynamic proxy client does have problems, however,
> non-wrapper style doc literal is not supported for the dynamic proxy-
> Do you have the wsdl for the web service and the wscompile
> options that you
> used?
> If so, I will test it out and see exactly what the problem is-
> Yes, dynamic proxy clients will improve in the future-
> Kathy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net