I defined a fault in my wsdl file for a custom exception. I also use Jibx for the mapping. When I use wsdl2java to generate the code, it doesn't care about the mapping and the custom exception. It always generates an exception class from the wsdl file. Anybody experienced the same problem ?
Thanks John My wsdl file, <?xml version="1.0" encoding="UTF-8"?> <wsdl:definitions name="telecom" targetNamespace="http://www.crsoftwareinc.com/xml/ns/telecom/agent_request_v1_0"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:tcom="http://www.crsoftwareinc.com/xml/ns/telecom/agent_request_v1_0"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsd1="http://www.crsoftwareinc.com/xml/ns/telecom/common_types";> <wsdl:documentation> This document describes the telecom control service for agents. </wsdl:documentation> <wsdl:types> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"; elementFormDefault="qualified" targetNamespace="http://www.crsoftwareinc.com/xml/ns/telecom/agent_request_v1_0"; xmlns:com="http://www.crsoftwareinc.com/xml/ns/telecom/common_types";> <xsd:import namespace="http://www.crsoftwareinc.com/xml/ns/telecom/common_types"; schemaLocation="telecom.xsd" /> <xsd:element name="AgentLoginRequestWrap" type="com:agentLoginType" /> <xsd:element name="AgentLoginResponse" type="com:loginResponseType" /> <xsd:element name="DialerFault" type="com:dialerFaultType" /> </xsd:schema> </wsdl:types> <wsdl:message name="agentLoginRequest"> <wsdl:part name="agentLoginRequest" element="tcom:AgentLoginRequestWrap" /> </wsdl:message> <wsdl:message name="agentLoginResponse"> <wsdl:part name="agentLoginResponse" element="tcom:AgentLoginResponse" /> </wsdl:message> <wsdl:message name="dialerFaultMessage"> <wsdl:part name="fault" element="tcom:DialerFault"/> </wsdl:message> <wsdl:portType name="telecom"> <wsdl:operation name="agentLogin"> <wsdl:input message="tcom:agentLoginRequest" /> <wsdl:output message="tcom:agentLoginResponse" /> <wsdl:fault name="fault" message="tcom:dialerFaultMessage" /> </wsdl:operation> </wsdl:portType> binding file <binding> <namespace uri="http://www.crsoftwareinc.com/xml/ns/telecom/common_types"; prefix="q0" default="elements" /> <namespace uri="http://www.crsoftwareinc.com/xml/ns/telecom/agent_request_v1_0"; prefix="q1" /> <mapping name="AgentLoginRequestWrap" class="com.crsoftwareinc.crs.dialer.dto.AgentLoginRequestDTO" ns="http://www.crsoftwareinc.com/xml/ns/telecom/agent_request_v1_0";> <value name="system" field="system" /> <value name="campaign" field="campaign" /> <value name="extension" field="extension" /> <value name="mode" field="mode" serializer="com.crsoftwareinc.crs.dialer.dto.DialerUsageReference.toString" deserializer="com.crsoftwareinc.crs.dialer.dto.DialerUsageReference.fromString" /> <value name="station" field="station" /> </mapping> <mapping name="AgentLoginResponse" class="com.crsoftwareinc.crs.dialer.dto.AgentLoginResponseDTO" ns="http://www.crsoftwareinc.com/xml/ns/telecom/agent_request_v1_0";> <value name="station" field="station" /> <value name="agentNumber" field="agentNumber" /> <value name="error" usage="optional" field="error" /> </mapping> <mapping name="DialerFault" class="com.crsoftwareinc.crs.dialer.exception.DialerException" ns="http://www.crsoftwareinc.com/xml/ns/telecom/agent_request_v1_0";> <value name="reason" field="reason" /> </mapping> </binding> __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
