Hi Dennis, thanks very much for your reply. The significance of the order of the messages in porttype is certainly a good info.
For some reason my binding is failing. Here is my wsdl: =========================== <wsdl:definitions xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:ns="http://SOASecurity.sec.gov/SOASecurity/wsdl/1.0/SOASecurity.wsdl"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:SECxsd="http://SOASecurity.sec.gov/SOASecurity/schema/1.0/SOASecurity.xsd"; targetNamespace="http://SOASecurity.sec.gov/SOASecurity/wsdl/1.0/SOASecurity.wsdl";> <wsdl:types> <xsd:schema elementFormDefault="qualified" targetNamespace="http://SOASecurity.sec.gov/SOASecurity/wsdl/1.0/SOASecurity.wsdl"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> <xsd:import namespace="http://SOASecurity.sec.gov/SOASecurity/schema/1.0/SOASecurity.xsd"/> <xsd:element name="authenticateResponseType"> <xsd:complexType> <xsd:sequence> <xsd:element name="type" type="xsd:string"/> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:schema> <xsd:schema elementFormDefault="qualified" targetNamespace="http://SOASecurity.sec.gov/SOASecurity/schema/1.0/SOASecurity.xsd"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> <xsd:element name="AuthenticationKey"> <xsd:complexType> <xsd:sequence> <xsd:element name="applicationID" type="xsd:decimal"/> <xsd:element name="employeeID" type="xsd:string"/> <xsd:element name="userID" type="xsd:string"/> <xsd:element name="password" type="xsd:string"/> <xsd:element name="tokenID" type="xsd:string"/> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:schema> </wsdl:types> <wsdl:message name="authenticateRequest"> <wsdl:part name="authenticationKey" element="ns:AuthenticationKey"/> </wsdl:message> <wsdl:message name="authenticateResponse"> <wsdl:part name="authenticateResponse" element="ns:authenticateResponseType"/> </wsdl:message> <wsdl:portType name="SOASecurityServicePortType"> <wsdl:operation name="authenticate"> <wsdl:input message="ns:authenticateRequest"/> <wsdl:output message="ns:authenticateResponse"/> </wsdl:operation> </wsdl:portType> <wsdl:binding name="SOASecurityServiceSOAP12Binding" type="ns:SOASecurityServicePortType"> <soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> <wsdl:operation name="authenticate"> <soap12:operation soapAction="ns:authenticate"/> <wsdl:input> <soap12:body use="literal"/> </wsdl:input> <wsdl:output> <soap12:body use="literal"/> </wsdl:output> </wsdl:operation> </wsdl:binding> <wsdl:service name="SOASecurityService"> <wsdl:port name="SOASecurityServiceSOAP12port" binding="ns:SOASecurityServiceSOAP12Binding"> <soap12:address location="http://localhost:8080/axis2/services/SOASecurityService"/> </wsdl:port> </wsdl:service> </wsdl:definitions> ======================= my binding xml: ================ <?xml version="1.0" encoding="windows-1252" ?> <binding> <mapping name="authenticationkey" class="AuthenticationKey"> <value name="applicationID" field="applicationID"/> <value name="employeeID" field="employeeID"/> <value name="userID" field="userID"/> <value name="password" field="password"/> <value name="tokenID" field="tokenID"/> </mapping> </binding> ================= Exception: Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: No ma pping defined for element {http://SOASecurity.sec.gov/SOASecurity/wsdl/1.0/SOASecurity.wsdl}AuthenticationKey at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: java.lang.RuntimeException: No mapping defined for element {http://SOASecurity.sec.gov/SOASecurity/wsdl/ 1.0/SOASecurity.wsdl}AuthenticationKey at org.apache.axis2.jibx.CodeGenerationUtility.mapQName(CodeGenerationUtility.java:928) at org.apache.axis2.jibx.CodeGenerationUtility.mapMessage(CodeGenerationUtility.java:914) at org.apache.axis2.jibx.CodeGenerationUtility.engage(CodeGenerationUtility.java:384) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.wsdl.codegen.extension.JiBXExtension.engage(JiBXExtension.java:74) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:177) ... 2 more ==================== Not sure why this is failing.....any help is greatly appreciated..thanks very much in advance.. All the files are in the same directory. we are developing a prototype for SOA security services..which will lead to a enterprise wide implementation using SOA... I am planning to use axis2 with jibx... regards Yugandhar -- View this message in context: http://www.nabble.com/Strange-behaviour-of-WSDL2Java---axis2---Jibx-tf3598083.html#a10058563 Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
