[nvo-techwg] Re: Axis 1.3 and VOTable 1.1 schema

[Gretchen Greene]

The only problem with this that I found last year was that it would not
work with the later Tomcat versions...Be wary.

-----Original Message-----
From: techwg-bounces at us-vo.org [mailto:techwg-bounces at us-vo.org] On
Behalf Of Guy Rixon
Sent: Tuesday, April 18, 2006 12:36 PM
To: Matthew Graham
Cc: grid at ivoa.net; feedback at us-vo.org; nvoss at us-vo.org; techwg at us-vo.org
Subject: [nvo-techwg] Re: Axis 1.3 and VOTable 1.1 schema


Matthew,

I sympathise. Axis 1.3 can be nasty when it turns on you.

My experience in AstroGrid is that you can "compile" your WSDL to Java
stubs and beans using Axis 1.2.1 and then use those classes with Axis
1.3. I.e. the WSDL2java stage is treated as part of the coding, not part
of the build process.

However, it may be better not to use Axis 1.3 at all. It has fatal
problems when doing digital signatures (corrupts the messages during
deserialization s.t. the signatures are invalidated); the Axis and WSS4J
teams don't seem to have any solution yet.

Cheers,
Guy

On Thu, 13 Apr 2006, Matthew Graham wrote:

> Hi,
>
> Sorry if you get multiple copies of this but this is a bit of a
> showstopper: whereas Axis 1.2.1 handled the VOTable 1.1 schema without

> any complaints so you could generate Java clients to Skynode and other

> services which use it, Axis 1.3 bombs out with the old recursion 
> error:
>
> java.io.IOException: The definition of 
> {http://vizier.u-strasbg.fr/xml/VOTable-1.1.xsd}OPTION results in a 
> loop.
>
> i.e. OPTION can contain OPTION ad infinitum.
>
> The workaround is to use a hacked version of the WSDL importing a 
> hacked version of the VOTable schema which is not ideal and certainly 
> not for real astronomers.
>
>     Cheers,
>
>     Matthew
>

Guy Rixon 				        gtr at ast.cam.ac.uk
Institute of Astronomy   	                Tel: +44-1223-337542
Madingley Road, Cambridge, UK, CB3 0HA		Fax: +44-1223-337523