list archives . users mailing list

Subject: RE: Building OGSA-DAI 1.5

Date view Thread view Subject view Author view Attachment view

From: M.Jackson (michaelj@epcc.ed.ac.uk)
Date: Mar 14, 2003 13:31

Hi Brian,

Check that within your Tomcat installation you have the following
directories:

 <TOMCAT>/webapps/ROOT/schema/

Within this directory there should be the following directories, from
Globus Tk3 and OGSA-DAI installations:

  base/ core/ generated/ ogsadai/ samples/ security/

Within the ogsadai directory there should be:

  gds/ gdsr/ ogsadai-types/

Within gdsr/ should be a file gdsr_service.wsdl
Within ogsadai-types/ there should be a file ogsadai-service-data.xsd

In addition, within the <TOMCAT>/webapps/ogsa/WEB-INF/server-config.wsdd
file the deployment descriptor for the GDSR should include:

   <service
    name="uk/org/ogsadai/wsdl/GridDataServiceRegistry" provider="Handler"
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    style="wrapped">
   ...
     <parameter name="schemaPath"
                value="schema/ogsadai/gdsr/gdsr_service.wsdl"/>
   ... ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   </service>

If all these conditions hold, then let me know...

Regards

mike

PS Just to check, you _are_ using GT3 Alpha 2 and not Alpha 3 ?!

On Fri, 14 Mar 2003, Brian Hills wrote:

> Thanks, that was the answer, I had a wrong ogsa.jar. I have started
> again and reinstalled tomcat and things seem to be going better.
> I've got to the stage of loading the service WSDL into a browser.
>
> This works fine for "GridDataServiceFactoryP2R1" but I get an error when
> I try to load the WSDL for "GridDataServiceRegistry":
>
> Fault - [java.rmi.RemoteException] java.rmi.RemoteException: Could not
> find path uk/org/ogsadai/wsdl/GridDataServiceRegistry:
> [org.globus.ogsa.repository.ServiceActivationException]
> [org.globus.ogsa.GridServiceException] Emitter failure. There is an
> undefined binding (NotificationSourceSOAPBinding) in the WSDL document.
>
> Hint: make sure &amp;amp;lt;port
> binding=&amp;amp;quot;..&amp;amp;quot;&amp;amp;gt; is fully qualified.
> [chained: Emitter failure. There is an undefined binding
> (NotificationSourceSOAPBinding) in the WSDL document.
>
> Does anyone have any ideas?
>
> Thanks
>
> Brian


Date view Thread view Subject view Author view Attachment view
webperson@nesc.ac.uk