[seek-dev] setting schema location port number.

Bing Zhu bzhu at sdsc.edu
Thu Sep 1 11:11:35 PDT 2005

This is my guess.

Digir has many other apps running with port 80. And DiGIR query
service calls those apps to get data, combine them and send
results back to ecogrid query client.


-----Original Message-----
From: seek-dev-bounces at ecoinformatics.org
[mailto:seek-dev-bounces at ecoinformatics.org]On Behalf Of Kevin Ruland
Sent: Thursday, September 01, 2005 6:23 AM
To: seek-dev at ecoinformatics.org
Subject: [seek-dev] setting schema location port number.

On to the last problem, I hope.

The latest problem is when the service is activated, it tries to load
the WSDL.  It does this by envoking the WSDLGenerator.getServiceWSDL()
method.  For some unknown reason, it's trying to pull it from:

The key here is it's looking for port 80 which I don't have running.  On
kuecogrid, it loads it from:


I've inserted some additional debugging messages in the WSDLGenerator
code and it appears that the port number is somehow set correctly in the
kuecogrid deployment (as opposed to not being set and defaulted to 8080).

It doesn't appear to be related to the publishHostName=true parameter.
I turned that on in my test deployment and the url becomes:


I can manually set the port number by using <parameter name="port"
value="8080"/> in the <service> block for
EcoGridQueryInterfaceLevelOne.  Alternatively I can use a System
property named "org.globus.ogsa.schema.root", or a Container Config
property named "schemaRoot".

The really puzzling thing is I don't see either of these being set on

Any ideas?

Seek-dev mailing list
Seek-dev at ecoinformatics.org

More information about the Seek-dev mailing list