Talking to Oblix Services

[J Chambers]

hey all,

i'm having some troubles in the class generation (client) for some oblix web
services.

here's the scenario:
we have two configs that we're dealing with in this particular case, one a
test bed (for spike solutions, completely isolated), one for dev.

as far as we know, we have the same software, servers and patches up and
running, but this is something that is difficult to verify.

in the test bed, we are able to specify an oblix-provided wsdl file from the
IDE, and the corresponding client is successfully generated.

in the dev environment, this is not the case. the server contains the exact
same directory structure (it is a direct copy), but we get the following
error:
Custom tool error: Unable to import WebService/Schema. A schema with the
namespace 'http://www.oblix.com/' has already been added.

subsequently, there is an error for every schema or contract reference that
the disco tool drums up, specifically along these lines:
Custom tool warning: Ignore duplicate schema document [schema location,
server info] with TargetNamespace 'http://www.oblix.com/'

so the question is, where do we start? could this be botched IDE tools? is
there something about the server or client that would trip this?

what's puzzling to me is that in a blank solution where i add one project (a
class library) and add only one reference (the web reference to the wsdl) i'm
getting duplicate schema reference errors from the same wsdl's that exist and
work happily when downloaded/generated from a different server.

any direction would be greatly appreciated.

cheers

[J Chambers]

i just verified that the wsdl and disco tools are running the same versions
in both test and dev. is there any other tools i should verify to establish
differences?

Cheers

"J Chambers" wrote:

hey all,

i'm having some troubles in the class generation (client) for some oblix web
services.

here's the scenario:
we have two configs that we're dealing with in this particular case, one a
test bed (for spike solutions, completely isolated), one for dev.

as far as we know, we have the same software, servers and patches up and
running, but this is something that is difficult to verify.

in the test bed, we are able to specify an oblix-provided wsdl file from the
IDE, and the corresponding client is successfully generated.

in the dev environment, this is not the case. the server contains the exact
same directory structure (it is a direct copy), but we get the following
error:
Custom tool error: Unable to import WebService/Schema. A schema with the
namespace 'http://www.oblix.com/' has already been added.

subsequently, there is an error for every schema or contract reference that
the disco tool drums up, specifically along these lines:
Custom tool warning: Ignore duplicate schema document [schema location,
server info] with TargetNamespace 'http://www.oblix.com/'

so the question is, where do we start? could this be botched IDE tools? is
there something about the server or client that would trip this?

what's puzzling to me is that in a blank solution where i add one project (a
class library) and add only one reference (the web reference to the wsdl) i'm
getting duplicate schema reference errors from the same wsdl's that exist and
work happily when downloaded/generated from a different server.

any direction would be greatly appreciated.

cheers

[J Chambers]

sorry to keep responding to myself here, but maybe a shared thought might
trigger someone else.

my original comment about the duplicate reference is unfounded, at least
from an IDE standpoint. as the error indicates, it's a custom tool that is
barfing, not the IDE. i've verified from the command prompt that it is wsdl
that is the problem. disco seems to work a-okay.

just some findings i thought i'd share.

cheers

"J Chambers" wrote:

i just verified that the wsdl and disco tools are running the same versions
in both test and dev. is there any other tools i should verify to establish
differences?

Cheers

"J Chambers" wrote:

hey all,

i'm having some troubles in the class generation (client) for some oblix web
services.

here's the scenario:
we have two configs that we're dealing with in this particular case, one a
test bed (for spike solutions, completely isolated), one for dev.

as far as we know, we have the same software, servers and patches up and
running, but this is something that is difficult to verify.

in the test bed, we are able to specify an oblix-provided wsdl file from the
IDE, and the corresponding client is successfully generated.

in the dev environment, this is not the case. the server contains the exact
same directory structure (it is a direct copy), but we get the following
error:
Custom tool error: Unable to import WebService/Schema. A schema with the
namespace 'http://www.oblix.com/' has already been added.

subsequently, there is an error for every schema or contract reference that
the disco tool drums up, specifically along these lines:
Custom tool warning: Ignore duplicate schema document [schema location,
server info] with TargetNamespace 'http://www.oblix.com/'

so the question is, where do we start? could this be botched IDE tools? is
there something about the server or client that would trip this?

what's puzzling to me is that in a blank solution where i add one project (a
class library) and add only one reference (the web reference to the wsdl) i'm
getting duplicate schema reference errors from the same wsdl's that exist and
work happily when downloaded/generated from a different server.

any direction would be greatly appreciated.

cheers

[J Chambers]

dig, dig, dig. okay here's what i've found:

1) both development machines are running vs.net 2003 with fw 1.1
2) the dev machine in test (the one that works) has the hotfix specified
here installed: http://support.microsoft.com/?id=822411
3) the dev machine in dev (doesn't work) cannot install this hotfix
4) the dev/dev machine has VS.NET SP1 installed, the dev/test machine does not

so, it appears that the hotfix that is to resolve the problem:
1) cannot be installed if SP1 is installed, and
2) is not included in SP1

we have replicated the install problem and success on other machines...i'm
fairly confident at this point that this is the source of the problem.

anyone from MS out there that could confirm this? is there a version of the
hotfix that can install on VS.NET SP1?

tia.

cheers

"J Chambers" wrote:

sorry to keep responding to myself here, but maybe a shared thought might
trigger someone else.

my original comment about the duplicate reference is unfounded, at least
from an IDE standpoint. as the error indicates, it's a custom tool that is
barfing, not the IDE. i've verified from the command prompt that it is wsdl
that is the problem. disco seems to work a-okay.

just some findings i thought i'd share.

cheers

"J Chambers" wrote:

i just verified that the wsdl and disco tools are running the same versions
in both test and dev. is there any other tools i should verify to establish
differences?

Cheers

"J Chambers" wrote:

hey all,

i'm having some troubles in the class generation (client) for some oblix web
services.

here's the scenario:
we have two configs that we're dealing with in this particular case, one a
test bed (for spike solutions, completely isolated), one for dev.

as far as we know, we have the same software, servers and patches up and
running, but this is something that is difficult to verify.

in the test bed, we are able to specify an oblix-provided wsdl file from the
IDE, and the corresponding client is successfully generated.

in the dev environment, this is not the case. the server contains the exact
same directory structure (it is a direct copy), but we get the following
error:
Custom tool error: Unable to import WebService/Schema. A schema with the
namespace 'http://www.oblix.com/' has already been added.

subsequently, there is an error for every schema or contract reference that
the disco tool drums up, specifically along these lines:
Custom tool warning: Ignore duplicate schema document [schema location,
server info] with TargetNamespace 'http://www.oblix.com/'

so the question is, where do we start? could this be botched IDE tools? is
there something about the server or client that would trip this?

what's puzzling to me is that in a blank solution where i add one project (a
class library) and add only one reference (the web reference to the wsdl) i'm
getting duplicate schema reference errors from the same wsdl's that exist and
work happily when downloaded/generated from a different server.

any direction would be greatly appreciated.

cheers