This turns out to be specific to java2wsdl usage. I'm running the tool
from ant, with:
<java classname="org.apache.cxf.tools.java2wsdl.JavaToWSDL"
fork="true">
<arg value="-quiet"/>
<arg value="-o"/>
<arg value="NameIndex.wsdl"/>
<arg
value="com.basistech.rnm.index.ws.impl.NameIndexServiceImpl"/>
<classpath>
<path refid="src-compile-classpath"/>
</classpath>
</java>
The classpath there should contain all the relevant impediment. I guess
the first step is to change 'quiet' to 'verbose'.
> -----Original Message-----
> From: Benson Margulies [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 23, 2007 2:53 PM
> To: [email protected]
> Subject: Migrating enums
>
> In the interests of a less eventful life, I moved my production code
to
> JAXB from Aegis. My doc guy just pointed out to me that our WSDL has
> rather less schema elements than expected. Indeed, there seems to have
a
> been a giant migration to the service TNS, at least of enums.
>
> In the wsdl that is coming out of java2wsdl, I've got one schema.
>
> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema";
> xmlns:btrni="http://index.rnm.basistech.com";
> xmlns:btrniws="http://ws.index.rnm.basistech.com";
> xmlns:btrnm="http://rnm.basistech.com";
> attributeFormDefault="unqualified" elementFormDefault="unqualified"
> targetNamespace="http://ws.index.rnm.basistech.com";>
>
> I then have a reference to an enum type:
>
> <xs:element minOccurs="0" name="script" type="btrniws:iso15924"/>
>
> This already looks wrong, insofar as that enum lives in
> com.basistech.util, not com.basistech.rnm.index.ws.
>
> But it's at least consistent, since that is the tns and, sure enough,
> the enum complexType is just sitting in the tns.
>
> However, I now notice that the same thing is happening to all of the
> beans. Everything is in the TNS, regardless of package-of-origin.
>
