Re: wsdl2java -- Resolving imported schemas with relative paths

2009-03-24 Thread Andrew Clegg
I'm not sure I follow you -- the service-specific schema ws_spindlep_2_0_ws0.xsd has this line as the first element in its schema: xsd:import namespace=http://www.cbs.dtu.dk/ws/ws-common; schemaLocation=../common/ws_common_1_0b.xsd/ ... which is also imported into the WSDL. I just noticed last

Re: wsdl2java -- Resolving imported schemas with relative paths

2009-03-24 Thread Daniel Kulp
An xsd:schema ... element needs to be completely valid by itself. Thus, if it references types outside of itself, it MUST import the other schemas. In a WSDL, if another xsd:schema defines the types, you just need: xsd:import namespace=./ without a location. This allows the schema

wsdl2java -- Resolving imported schemas with relative paths

2009-03-23 Thread Andrew Clegg
Hi, I'm trying to write a JAXB/JAXWS client for this service: http://www.cbs.dtu.dk/ws/SpindleP/ws_spindlep_2_0_ws0.xsd Just using wsdl2java on that URL with no extra parameters gives this error: WSDLToJava Error: Thrown by JAXB : undefined simple or complex type 'spindlep:seqlookup' ...

Re: wsdl2java -- Resolving imported schemas with relative paths

2009-03-23 Thread Andrew Clegg
Actually, I think my previous suspicion about the cause of the problem may be a red herring. I've downloaded all three files: http://www.cbs.dtu.dk/ws/SpindleP/SpindleP_2_0_ws0.wsdl http://www.cbs.dtu.dk/ws/SpindleP/ws_spindlep_2_0_ws0.xsd http://www.cbs.dtu.dk/ws/common/ws_common_1_0b.xsd and

Re: wsdl2java -- Resolving imported schemas with relative paths

2009-03-23 Thread Daniel Kulp
JAXB is correct here.The scheme in question (the second in the wsdl), doesn't have any imports. Thus, it cannot reference anything outside of itself. There should be an import in there. Dan On Mon March 23 2009 3:40:22 pm Andrew Clegg wrote: Actually, I think my previous suspicion