The schema is picked up from the classpath automatically. Do you have all the jars in $G_L/lib and $G_L/lib/common on your classpath?

Rachana

On Jul 5, 2009, at 10:29 PM, Giacomo Victor Mc Evoy Valenzano wrote:

Dear all,

I am testing client-side security with Globus 4.2.1. I tried to follow the documentation in http://www.globus.org/toolkit/docs/4.2/4.2.1/security/wsaajava/descriptor/wsaajavaDescriptorGuide.pdf and have the following client code:

// Client security descriptor file
String CLIENT_DESC =
       "some_path/client/client-security-config.xml";
//Set descriptor on Stub
((Stub)portType)._setProperty(Constants.CLIENT_DESCRIPTOR_FILE, CLIENT_DESC);

The descriptor is as follows:

<?xml version="1.0" encoding="UTF-8"?>
<clientSecurityConfig xmlns="http://www.globus.org/security/descriptor/client ">

    <authz value="none"/>
    <GSISecureConversation>
        <integrity/>
    </GSISecureConversation>

</clientSecurityConfig>

When running the client I get the following error in the client:

[ERROR] digester.Digester - Parse Error at line 2 column 80: schema_reference.4: Failed to read schema document 'client_security_descriptor.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.

and after that

AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/ envelope/}Server.userException
 faultSubcode:
faultString: org.globus.wsrf.config.ConfigException: [JWSSEC-245] Error parsing file: &quot;some_path/client/client-security- config.xml&quot; [Caused by: schema_reference.4: Failed to read schema document 'client_security_descriptor.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not &lt;xsd:schema&gt;.]

Am I doing something wrong? The client complains about not finding the schema, but where am I supposed to put it? All plausible paths (the descriptor path, the execution path, $GLOBUS_LOCATION, even "/") fail with the same error.

After a bit of searching it seems that schema locations in Xerces are supposed to be well-formed URIs, so I am wondering if anybody else got this error.

Thanks in advance,
Giacomo

Reply via email to