Some comments on Jeff's recommendations... On Nov 29, 2007 10:14 AM, Walker, Jeff <[EMAIL PROTECTED]> wrote: > Hi Fatima, > I don't know the exact answer, but I have a few recommendations. > > 1. Try reducing the wsdl down to importing just one schema, and get that to > work before attempting all of the others.
Always a smart idea. > > 2. Some of the schema files have a '1' at the end of their file extension, > such as *.xsd1 instead of *.xsd. This may be a problem, not sure. Those were the namespace URIs, not the file names. They shouldn't be a problem. > > 3. You use the notation namespace="urn:oasis:names:tc:SAML:2.0:protocol" for > namespaces. Can you edit the schema files you import to use the more familiar > http format, such as namespace="http://oasis.names.tc.SAML2.0.protocol"; ? I > know the other notation is theoretically allowed, but many tools actually > look up the schema using the http protocol, so the xx:xx:xx notation may not > resolve. Not a problem. Besides, given that you're using a standard, you must maintain the standard's namespace URIs. Any tool that uses a namespace URI in place of the URL specified in the schemaLocation attribute is broken. > > 4. The schemaLocation attribute ends up having a whitespace in it, where you > assign to it "C:\Documents and > Settings\Fatima\Bureau\svn\xacmlpolicytransfer\saml-schema-protocol-2.0.xsd". > Again, this may or may not be a problem but should probably be edited to > remove the whitespace. (That would mean moving the scjema file from the > Documents and Settings folder, of course). This is almost certainly your problem. > > 5. Your defined prefix xmlns:tns points to an actual wsdl file? i.e. > xmlns:tns="http://policytransfer.authorization.security.evidian.com/xacmlpolicytransfer.wsdl"; > This seems strange to me as well. Normally, I think it would be just a unique > namespace. (This may also not be a problem since its still possible to regard > this string as a unique name). > Not a problem. That's the same URI as the targetNamespace. > 6. What is name="xacmlpolicytransfer" ?? That's the name of the WSDL. (an optional attribute in the <wsdl:definitions> element) Anne > -jeff > > > > -----Original Message----- > From: Fátima Milla Olaya [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 29, 2007 6:15 AM > To: [email protected] > Subject: Problem with the imports in the WSDL > > Hi, I want to import the schemas to my wsdl: > <?xml version="1.0" encoding="UTF-8"?> > <wsdl:definitions xmlns:import1="urn:oasis:names:tc:SAML:2.0:protocol" > xmlns:import2="urn:oasis:names:tc:xacml:2.0:profile:saml2.0:v2:schema:protocol" > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:tns="http://policytransfer.authorization.security.evidian.com/xacmlpolicytransfer.wsdl"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsd1="http://policytransfer.authorization.security.evidian.com/xacmlpolicytransfer.xsd1"; > name="xacmlpolicytransfer" > targetNamespace="http://policytransfer.authorization.security.evidian.com/xacmlpolicytransfer.wsdl";> > <wsdl:documentation > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";>Created using Cape Clear > Studio SOA Editor - http://www.capeclear.com</wsdl:documentation> > <wsdl:types> > <xsd:schema > targetNamespace="http://policytransfer.authorization.security.evidian.com/xacmlpolicytransfer.xsd1"; > xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsd1="http://policytransfer.authorization.security.evidian.com/xacmlpolicytransfer.xsd1";> > <xsd:import namespace="urn:oasis:names:tc:SAML:2.0:protocol" > schemaLocation="C:\Documents and > Settings\Fatima\Bureau\svn\xacmlpolicytransfer\saml-schema-protocol-2.0.xsd"/> > <xsd:import > namespace="urn:oasis:names:tc:xacml:2.0:profile:saml2.0:v2:schema:protocol" > schemaLocation="C:\Documents and > Settings\Fatima\Bureau\svn\xacmlpolicytransfer\xacml-2.0-profile-saml2.0-v2-schema-protocol-wd-5.xsd"/> > </xsd:schema> > </wsdl:types> > <wsdl:message name="Request"> > <wsdl:part name="policyquery" element="import2:XACMLPolicyQuery"/> > </wsdl:message> > <wsdl:message name="Response"> > <wsdl:part name="policystatement" element="import1:Response"/> > </wsdl:message> > <wsdl:portType name="xacmlpolicytransferPortType"> > <wsdl:operation name="transfer"> > <wsdl:input message="tns:Request"/> > <wsdl:output message="tns:Response"/> > </wsdl:operation> > </wsdl:portType> > <wsdl:binding name="xacmlpolicytransferBinding" > type="tns:xacmlpolicytransferPortType"> > <soap:binding style="document" > transport="http://schemas.xmlsoap.org/soap/http"/> > <wsdl:operation name="transfer"> > <soap:operation > soapAction="capeconnect:xacmlpolicytransfer:xacmlpolicytransferPortType#transfer"/> > <wsdl:input> > <soap:body parts="policyquery" use="literal"/> > </wsdl:input> > <wsdl:output> > <soap:body parts="policystatement" use="literal"/> > </wsdl:output> > </wsdl:operation> > </wsdl:binding> > <wsdl:service name="xacmlpolicytransfer"> > <wsdl:port name="xacmlpolicytransferPort" > binding="tns:xacmlpolicytransferBinding"> > <soap:address > location="http://localhost:8080/axis2/services/xacmlpolicytransfer"/> > </wsdl:port> > </wsdl:service> > </wsdl:definitions> > > and I get this: > > > Warning : 1003 : WSDLException: faultCode=PARSER_ERROR: failed parsing > schemas into object model - failed loading import in schema > http://policytransfer.authorization.security.evidian.com/xacmlpolicytransfer.xsd1 > for namespace=urn:oasis:names:tc:SAML:2.0:protocol, > schemaLocation=C:\Documents and > Settings\Fatima\Bureau\svn\xacmlpolicytransfer\saml-schema-protocol-2.0.xsd: > failed loading import in schema > http://policytransfer.authorization.security.evidian.com/xacmlpolicytransfer.xsd1 > for namespace=urn:oasis:names:tc:SAML:2.0:protocol, > schemaLocation=C:\Documents and > Settings\Fatima\Bureau\svn\xacmlpolicytransfer\saml-schema-protocol-2.0.xsd > > --------------------------------------------------------------------- > 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]
