Nadir,
Thanks. Our services fail Basic Profile 1.1 compliance due to the following WSDL constructs: First Service WSDL: Fails BP2120 No assertion from ws-i test tool. Fails BP2122 Assertion: BP2122 Result failed Failure Message A wsdl:types element contained a data type definition that is not an XML schema definition. Failure Detail Message Error: s4s-elt-schema-ns: The namespace of element 'import' must be from the schema namespace, 'http://www.w3.org/2001/XMLSchema'. Error: s4s-elt-schema-ns: The namespace of element 'import' must be from the schema namespace, 'http://www.w3.org/2001/XMLSchema'. Error: s4s-elt-schema-ns: The namespace of element 'import' must be from the schema namespace, 'http://www.w3.org/2001/XMLSchema'. Error: s4s-elt-schema-ns: The namespace of element 'import' must be from the schema namespace, 'http://www.w3.org/2001/XMLSchema'. Element Location: lineNumber=4 Second Service WSDL: Fails BP2122 Assertion: BP2122 Result failed Failure Message A wsdl:types element contained a data type definition that is not an XML schema definition. Failure Detail Message Error: s4s-elt-schema-ns: The namespace of element 'import' must be from the schema namespace, 'http://www.w3.org/2001/XMLSchema'. Error: s4s-elt-schema-ns: The namespace of element 'import' must be from the schema namespace, 'http://www.w3.org/2001/XMLSchema'. Error: s4s-elt-schema-ns: The namespace of element 'import' must be from the schema namespace, 'http://www.w3.org/2001/XMLSchema'. Element Location: lineNumber=4 Any pointers would be appreciated as compliance is a requirement for our system. Since we have gone this far with POJO services, reverting to contract-first would be time consuming and additional work. I have attached the wsdls. Thanks, Nadeem -----Original Message----- From: Nadir Amra [mailto:[EMAIL PROTECTED] Sent: Sunday, December 16, 2007 7:02 PM To: axis-user@ws.apache.org Cc: axis-user@ws.apache.org Subject: RE: Removing SOAP 1.2 and HTTP for POJO services Nadeem, Can you explain more about "WS-I Basic Profile 1.1 compliance from POJO Services"? Why did it fail? As for excluding operations, you can add the following in services.xml file for the service: <excludeOperations> <operation>findcustomers</operation> <operation>disablecustomers</operation> </excludeOperations> The above excludes two operations.... Nadir K. Amra "Hoda, Nadeem [USA]" <[EMAIL PROTECTED]> wrote on 12/16/2007 03:20:12 AM: > > > Thank you Nadir. That worked perfectly. > > Two additional questions: > > - Is there a way to get WS-I Basic Profile 1.1 compliance from POJO > Services? > (currently, my particular service fails) > > - Is there a way to exclude certain public methods from the WSDL for a > POJO Service? > (e.g., excluding public getters/setters) > > Thanks, > > Nadeem > > > > -----Original Message----- > From: Nadir Amra [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 13, 2007 10:19 PM > To: axis-user@ws.apache.org > Subject: Re: Removing SOAP 1.2 and HTTP for POJO services > > Nadeem > > You will need to get the latest code (a nightly build) to use these, > but in axis2.xml config file, you can do the following: > > <!-- Following parameter will completely disable REST handling in Axis2--> > <parameter name="disableREST" locked="true">true</parameter> > > <!-- Following parameter will suppress generation of SOAP 1.2 > bindings in auto-generated WSDL files --> > <parameter name="disableSOAP12" locked="true">true</parameter> > > This will disable it for all services...there currently no way to > selectively do this on a per service basis. There is a JIRA for this > enhancement. > > Nadir K. Amra > > > "Hoda, Nadeem [USA]" <[EMAIL PROTECTED]> wrote on 12/13/2007 > 05:17:49 > AM: > > > > > > > In a simple POJO service with no WSDL file (only relying on the > > ServiceClass in services.xml), how do you disable/get rid of SOAP 1. > > 2 and HTTP bindings and ports if you only want the SOAP 1.1 port and > binding? > > > > Is there a simple config/options/parameter for this? > > > > Thanks, > > > > Nadeem > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WSDL1.wsdl
Description: WSDL1.wsdl
WSDL2.wsdl
Description: WSDL2.wsdl
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
