Nadeem, I assume these WSDLs are generated by the AXIS2. There currently is a bug in how AXIS2 sets the target namespace for the schemas (see http://issues.apache.org/jira/browse/AXIS2-3301).
However, we have gotten around the problem as follows. Assuming the package name for the POJO is: wsbeans.converttemp, then add the following line in services.xml: <schema schemaNamespace="http://converttemp.wsbeans/xsd"; /> You rmileage may vary, but this worked for me..... Nadir K. Amra "Hoda, Nadeem [USA]" <[EMAIL PROTECTED]> wrote on 12/17/2007 04:31:55 PM: > > > 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: [email protected] > Cc: [email protected] > 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) > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
