Sanjiva Weerawarana wrote:
On Tue, 2006-03-28 at 19:33 +1200, Dennis Sosnoski wrote:
+1, which leads me to a quick comment. Currently, the error reporting
in Axis2 is... less than adequate, to say the least. We're building a
toolkit/engine which is supposed to make it easy for developers to
expose and consume arbitrary Web Services in a variety of ways. And
because there are so many moving parts and extensions, it is EXTRA
important for us to provide detailed and useful information when
things go wrong. We can discuss this more on another thread, but I
think this needs some serious attention if we want good uptake.
Are you willing to go along on this, Sanjiva? If so, I'll change the
code to print a warning message to the console when a schema with no
targetNamespace is used.
It doesn't work for direct reference from WSDL even for WSDL 1.1
original: part/@type and part/@element both require QNames. The only use
is for a schema defining one of those to refer to stuff in a schema with
no namespace.
Does WSDL 1.1 define QNames somewhere to require prefixes? This
certainly isn't standard usage of the schema QName type. Schema
considers QNames with no prefix to be using the default namespace for
the context.
Do you know of *any* usecases of this? Can you point me to the WSDL? I'd
like to understand it a bit before saying just print a warning.
I did a quick search earlier in this thread to see if I could find any
discussion of the topic for .NET or other frameworks, but didn't find
anything. But I don't see any justification for considering it an error,
either.
- Dennis
