Hi All,
The issue pertaining to naming conflict when auto-magically Java classes
are generated from WSDL, is now resolved. BioMart Central Portal
reflects the updated code and branch 0.7 also contains the patch. Please
do a 'cvs updat'e on your biomart-perl code and remove the corresponding
Hi Arek,
I'd be happy to wait until I'm finished, but as you can see from my other
posts, I have run into problems along the way. I think I've hit a wall with
the latest one dealing with the response from the SOAP service having plain
text as well as XML. I think this one has me stumped, in that
JAXB by default will attempt to create a Java class for each type
defined in the XSD, with the same name but with the first letter
upper-cased. In the case of 'dataset', it will try and make 'Dataset',
which then clashes with the existing 'Dataset' declared elsewhere in the
XSD.
The only way to
Yes I agree with you there. But I have no control over the XSD (I don't
work for BioMart any more) and so I can only propose end-user
workarounds. My preference would of course be to modify the XSD, but
that's not my decision to make.
cheers,
Richard
Steffen Neumann wrote:
Hi,
On Thu,
Hi all,
Thanks for all the tips - I agree that modifying the XSD would seem to be
the best long-term fix. Otherwise, I'll have a look into some JAXB
modifications, like the one already suggested. There's also class
customization (see
