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

[Max Reider <th...@hotmail.com>]

This one goes down in the "Why should that make a difference?" file.

The dual namespaces were produced by the Java2WSDL argument of:
-p"foo.bar" urn:bar.foo

Then I changed the argument to:
-pfoo.bar urn:bar.foo
That is, I just removed the quotes around the package. That fixed it. No 
more http://bar.foo. Just urn:bar.foo.

Picked up the double-quotes usage from the OnJava.com article from back in 
May.

>From: "Max Reider" <th...@hotmail.com>
>Reply-To: axis-user@xml.apache.org
>To: axis-user@xml.apache.org
>Subject: Re: "urn:" vs. "http://" namespace
>Date: Fri, 22 Nov 2002 14:06:10 -0800

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" <th...@hotmail.com>
>Reply-To: axis-user@xml.apache.org
>To: axis-user@xml.apache.org
>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?



_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online 
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963