Re: "urn:" vs. "http://" namespace

[Max Reider]

Okay, the schema with targetNamespace="urn:bar.foo" contains all my array types:
<complexType name="ArrayOf_xsd_string">
...
<complexType name="ArrayOf_tns2_MyClass">

The unexpected http://bar.foo schema contains all my original bean-ified classes:
<complexType name="PrimaryData">
...

So why is the namespace I specified for Java2WSDL only being used for array types?

From: "Max Reider" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: "urn:" vs. "http://"; namespace
Date: Fri, 22 Nov 2002 11:45:45 -0800

I run Java2WSDL with these arguments among others:
-lhttp://localhost:8080/axis/foo -n urn:bar.foo -p"foo.bar"
urn:bar.foo

The Java interface that serves as the input to Java2WSDL exposes
various bean-ified classes residing in the package foo.bar.

What's odd is that under <wsdl:types>, Java2WSDL creates two separate schemas:
<schema xmlns="http://www.w3.org/2001/XMLSchema";
targetNamespace="urn:bar.foo">
<schema xmlns="http://www.w3.org/2001/XMLSchema";
targetNamespace="http://bar.foo";>

Note the difference between urn:bar.foo and http://bar.foo. What's
odder is that some of the complexType entries (corresponding to my
classes) get placed in the one schema and some in the other. And I
can't quite notice a pattern of which goes where.

Anyone recognize why this is happening? Is there some way to enforce
the single namespace, or is that not desirable?



_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus