- From: Petr Kremen <kremen@labe.felk.cvut.cz>
- Date: Fri, 7 Sep 2007 23:40:59 +0200 (CEST)
- To: eric@w3.org
- Cc: "Seaborne, Andy" <andy.seaborne@hp.com>
first, sorry for late response. >>> I reverted the changes to the schema imports that were in >>> http://www.w3.org/2001/sw/DataAccess/rf1/result2.xsd >>> Could y'all try this out before I reply to the comments list? >>> - <xs:import namespace="http://www.w3.org/XML/1998/namespace" >>> schemaLocation="xml.xsd"/> >>> - <xs:import namespace="http://www.w3.org/2001/XMLSchema-instance" >>> schemaLocation="xsi.xsd"/> >>> + <xs:import namespace="http://www.w3.org/XML/1998/namespace" >>> schemaLocation="http://www.w3.org/2001/xml.xsd"/> >> This changed helped - I now have a service skeleton in source code for the >> service using Axis2 on the WSDL2. A change to sparql-protocol-types.xsd is >> needed as well to point to this version of results2.xsd, not the TR >> version. > > We may as well just republish XMLResults next week, fixing > http://www.w3.org/TR/rdf-sparql-XMLres/result2.xsd > in the process. I need to research timing of this. I guess > some trivial transition request is in order. > Excellent. > Petr, does this patch work for you (noting that > http://www.w3.org/2001/sw/DataAccess/proto-wd/sparql-protocol-types.xsd > still points at an unfixed version)? Yes, similar experience to Andy's - now, the code generation works well for me as well + changes needed in the xsd, as Andy has already written. Unfortunately my generated ADB service is not compilable (Andy ?!? - Have You succeeded ? I get 'cannot be resolved' on org.apache.axiom.om.OMElement.MY_QNAME) - prob. an AXIS2 problem. However, I haven't tried another binding methodyet, like xmlbeans, etc. cheers, Petr
Received on Friday, 7 September 2007 21:41:25 UTC