Hi all, Just bumping up the bit of my previous email (below) that hasn't had a response yet. Does anyone have any ideas on this one? How can a results "table" (if you imagine it as such) with data rows and an arbitrary number of attribute columns be squished into a java List<String>, as the mart xsd is saying the response will be?
Thanks very much! :) Allyson 2009/1/26 Allyson Lister <[email protected]> > > 1. The soap client I'm using is NOT one I've written - it is > autogenerated, via Apache CXF (a freely-available, widely-used SOAP app). > Therefore *anyone* who may wish to use the Biomart SOAP instance you have > via Apache CXF's wsdl2java feature *will* run into exactly the same > problem. > I think the problem may stem from the following part of martxsd: > <xs:element name="queryResponse"> > <xs:complexType> > <xs:sequence> > <xs:element minOccurs="0" > maxOccurs="unbounded" > name="resultsRow" > type="xs:string"/> > </xs:sequence> > </xs:complexType> > </xs:element> > This states that the query response will always be a sequence of > xs:string, or in Java, a List<String>. This does not allow for the varied > types of responses one can get based on the attributes of the query that > they've written. Therefore I think that the java code is trying to fit in > the response (such as the one Syed showed and which I copied a portion of > into #1 above) into a sequence of xs:string, and this just isn't working. I > can create an empty maven project that builds the Java code and runs the > unit tests if it would help - then you could download that project, and > just > run it on your own system to see what the problem is and possible ways of > resolving it. Perhaps there is some way to change the queryResponse? > Because, as it stands, how does the queryResponse element above match the > actual response given by the soap UI? > > Thanks very much! :) > > >
