Rolf Rander Naess <[EMAIL PROTECTED]> writes:
> However, Java2WSDL doesn't seem to grok the included wsdl correctly.
> The generated wsdl seems to include the xmlns-declarations from the
> <definitions> tag in the included wsdl directly with little or no
> interpretation of this information. I have observed that if i provide
> no xmlns-declarations, or with other prefixes than tns[1-9] (such as
> xmlns:somens="http://..."; which might be easier to interpret by a
> human than "tns1"), there is simply no appllicable
> namespace-declarations put into the generated wsdl.
After hacking some more on this, I have realized:
- the included wsdl-file must:
- declare prefixes for all namespaces defined
- name these as tns1, tns2 etc.
the last point seems to me as poorly documented magic, if the
included wsdl defines one namespace, the generated will start
making namespace-prefixes called tns2, even if my custom prefix is
called tns1 or foobar.
- It seems that extra-classes is probably the root of most of my
trouble. In some cases references to types actually defined in
tns2 are written as tns3:SomeOtherType. This problem disapears if
I remove the extra-classes-spesification, and I suspect the problem
occurs if a class is both referenced in the API for the class I'm
generating a wsdl for, *and* in extra-classes. If this is the
case, it means I have to hand-code the list of extra-classes for
each wsdl-file (not as now, when I try to use the same
extra-classes-specification for all java2wsdl-tasks).
If someone has similar experiences with input-wsdl or extra-classes,
it would be interresting to hear you observations.
Rolf Rander
--
tlf: +47 92820227 (c) 2002 Rolf Rander N�ss
http://www.pvv.org/~rolfn/
In a world without fences, there's no need for Gates.
