RE: schema imports

[Anne Thomas Manes]

I would say that the toolkits are interpreting invalid Schema -- but the 
toolkits probably don't attempt to perform schema validation before 
interpreting the types information, and since it has already cached the 
namespace information, it doesn't throw a fault.

At 02:28 PM 8/21/2003 -0500, you wrote:
Steve,

I'm actually dealing with another product that will remain unnamed -- but 
I'll concur that BEA is a strange beast.  I'm curious as to why the Axis, 
.NET, WebMethods, SOAP Lite toolkits (and XMethods) all have no issue with 
my WSDL.

Does this really boil down to toolkit implementation.  Are the toolkits 
actually successfully interpreting my "invalid" WSDL?

Perhaps we should meet at the bar,
Cory


-----Original Message-----
From: Steve Maring [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 21, 2003 2:15 PM
To: [EMAIL PROTECTED]
Subject: Re: schema imports
Cory,

Gee, you wouldn't be talking about BEA would you?
I've had similar problems with them and namespaces.
My WSDLs are properly validated by OmniOpera
http://www.omniopera.com/viewer.html , but the BEA Ant
tasks hack a fur ball when you specify multiple
namespaces.  Specifically, they complain that the
namespaces are not imported.  Then you import them
with the wsdl:import and it still complains.
Gotta love management mandates!

I feel your pain man.

Cheers.
Steve Maring


--- Cory Wilkerson <[EMAIL PROTECTED]> wrote:
> Given the following WSDL document (obviously
> paraphrased):
>
> <definitions xmlns:foo="foo" xmlns:bar="bar">
>       <types>
>               <schema targetNamespace="foo">
>                       <complexType name="complexFoo">
>                               <element name="elementFoo"
> type="bar:complexBar"/>
>                       </complexType>
>               </schema>
>               <schema targetNamespace="bar">
>                       <complexType name="complexBar">
>                               ...
>                       </complexType>
>               <schema>
>       </types>
>       ...
> <definitions>
>
> Is the reference to element complexBar from
> namespace "bar" valid in namespace "foo" (when
> elementFoo is of type complexBar) or do I need an
> explicit schema import declaration and if so -- how
> is that done here?  I'm working with a vendor who is
> disputing the validity of WSDL formed much like this
> but Axis and .Net swallow the WSDL just fine and
> interact with my service just as I would expect.
>
> Futhermore, they're attempting to tell me that the
> namespace must reference something concrete.  Their
> assertions seem a bit cracked induced but I'm
> looking for someone to back me up here before I act
> the fool.
>
> Thanks,
> Cory Wilkerson
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com