Should I just assume that this is a bug in Axis and that schema, simpleType,
complexType and so on should always be qualified by a namespace, typically
"xsd:"?
Or is there some sneaky implicit arrangement whereby xmlns or something else
being indicated means that I don't need qualification.
<rant>Is there actually anyone out there successfully using this technology
with multiple client types (Axis, gSOAP, WebSphere, .NET)? I don't see how
it's possible for anything more complex than a stock quote lookup
service.</rant>
From: "Jarmo Doc" <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: schema vs. xsd:schema
Date: Tue, 11 Jul 2006 09:21:28 -0700
Axis 1.3 java2wsdl generates 'schema' tags but most WSDL that I see
contains 'xsd:schema' tags. The WSDL spec. also seems to suggest that
'xsd:schema' is the only legal option.
What is the difference between these two tags and why does Axis generate
the former?
Thanks.
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how to
get there! http://lifeevents.msn.com/category.aspx?cid=Retirement
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
