axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russell Butek" <>
Subject Re: Namespace support (was: Re: AXIS chat log for 9 October, 2001)
Date Wed, 10 Oct 2001 17:08:03 GMT
So now that we've got that unravelled, and unless we get a complaint,
someone can grab this handful and implement it (not me; I'm leaving for
vacation in a couple hours; you, Berin?).  This, along with some
suggestions made by Ravi earlier this week, and we should be set for

Russell Butek

Berin Loritsch <> on 10/10/2001 11:55:57 AM

Please respond to

Subject:  Re: Namespace support (was: Re: AXIS chat log for 9 October,

Russell Butek wrote:
> So, to summarize, we agree on:
> 1.  remove --package
> 2.  add [--NStoPkg <namespace>=<package>]* with "-N" as the short form.
> 3.  for test.wsdl, Wsdl2java will look for of the form
> <namespace>=<package>
> 4.  2 takes precedence over 3

+1 we agree on this.

> And as for the other discussion - a lightbulb goes on!  This is the
> infamous difference between import and include that can be sooooo
> confusing.  You've been talking about includes, I've been talking about
> imports.  With respect to imports, we're OK since WSDL4J DOES handle
> With respect to includes, I haven't tried them, so I don't know.  But
> DOES bring up another question:  should --noImports also apply to
> I would vote "no".  Include means (at least it does in C/C++
> that the included stuff is as if it were part of the same file as the
> including file, and I would bet SAX handles it as such.  Therefore it
> be a pain to force the emitter to make a distinction that the parser
> doesn't make just so it can decide not to emit stuff that's been

Your summary is correct.  Of course there is the question of whether to
support XInclude in WSDL at all--esp. since WSDL has a lexical equivalent
that is a bit better suited.

I would vote -1 or at the very least "not yet".  Support for XInclude would
go into the XMLUtils class when/if we choose to support it.

Personally, I would like to see XInclude processing as a switchable option
on the parser itself (e.g. Crimson/Xerces).  That way the document object
and SAX stream is done with no post processing necessary.  But that may be
a story for JAXP 1.2 whenever that comes around.

View raw message