On 15/07/2010 10:51, Anja Le Blanc wrote:
As you may know Heliophysics is using the VOTable format to exchange data - so do we in HELIO. Our standard wsdl returns therefore structures of the type VOTable, as defined by their standardisation organisation IVOA. Trying to import these web services (e.g. http://msslxw.mssl.ucl.ac.uk:8080/helio-ics/HelioService?wsdl) results in a parsing exception:java.io.IOException: The definition of {http://www.ivoa.net/xml/VOTable/v1.1}OPTION results in a loop.
The offensive section of schema is:
<xs:element name="OPTION">
<xs:complexType>
<xs:sequence>
<xs:element ref="OPTION" minOccurs="0" maxOccurs="unbounded" />
</xs:sequence>
<xs:attribute name="name" type="xs:token" />
<xs:attribute name="valueopt" type="xs:string" use="required" />
</xs:complexType>
</xs:element>
It's legal, but very nasty. This is not a usage that e.g. JAXB can
support (or at least not with java-first tooling); it doesn't like
things *that* incestuous!
I believe that VOTable 1.2 will work with at least JAXB, or at least I
can tool something that looks *extremely* similar with minimal effort.
Donal.
<<attachment: donal_k_fellows.vcf>>
------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________ taverna-users mailing list [email protected] [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/about/contact-us/
