Re: Thrown by JAXB : undefined element declaration 's:schema'

Hey Guys, Thanks for the various replies on this - If i wanted to add s:import - what would I need to add to the WSDL file? Cheers Tim On 8 Apr 2008, at 21:31, Daniel Kulp wrote: Thus, to get it working for CXF, you would need to modify the schema to put the proper s:import in place to

Re: Thrown by JAXB : undefined element declaration 's:schema'

It goes inside the schema element. Any schema that references another schema needs an import. On Fri, Apr 11, 2008 at 7:18 AM, Tim Perrett [EMAIL PROTECTED] wrote: Hey Guys, Thanks for the various replies on this - If i wanted to add s:import - what would I need to add to the WSDL file?

Re: Thrown by JAXB : undefined element declaration 's:schema'

It shouldn't be too hard to write some xslt to script the edit Dan suggests. For the two errors you report, I think that the second requires -exsh (or one one the other command-line args to the tool) and the other requires a minimal import element that specifies the namespace but no system id.

Re: Thrown by JAXB : undefined element declaration 's:schema'

Hey Glen, Removing the s:schema from the WSDL seems to let wsdl2java work no problem - i did some digging in the w3c schema and it appears that in the s namespace, s:schema would point to the root node of the XSD - which seems to be pretty bizarre. I was wondering if that was some kind

Re: Thrown by JAXB : undefined element declaration 's:schema'

Hey Daniel, Thanks for your interesting reply. Thus, to get it working for CXF, you would need to modify the schema to put the proper s:import in place to import the schema schema, then include the binding file to deal with the duplicate classes. Alternatively, use the workround on that

Re: Thrown by JAXB : undefined element declaration 's:schema'

Am Mittwoch, den 09.04.2008, 10:21 +0100 schrieb Tim Perrett: Hey Daniel, Thanks for your interesting reply. Thus, to get it working for CXF, you would need to modify the schema to put the proper s:import in place to import the schema schema, then include the binding file to

Re: Thrown by JAXB : undefined element declaration 's:schema'

Can you post the wsdl? On Tue, Apr 8, 2008 at 10:46 AM, Tim Perrett [EMAIL PROTECTED] wrote: Hey All, Just trying to get up and running with CXF wsdl2java but I keep getting this error from the service I want to consume: Thrown by JAXB : undefined element declaration 's:schema' Its

Re: Thrown by JAXB : undefined element declaration 's:schema'

This error emerges from the bowels of JAXB's xjc tool, complete with the lack of navigational info. However, What is s:complexType s:sequence s:element ref=s:schema / s:any / /s:sequence /s:complexType

Re: Thrown by JAXB : undefined element declaration 's:schema'

Benson Margulies wrote: What is s:complexType s:sequence s:element ref=s:schema / s:any / /s:sequence /s:complexType supposed to mean? It defines a complex type consisting of an XML schema document

Re: Thrown by JAXB : undefined element declaration 's:schema'

Well, I don't know how hard it is to apply the jaxb customization inside of CXF. My superiors in the secret college of JAXB will, with any luck, pipe up at this point. On Tue, Apr 8, 2008 at 12:15 PM, Ian Roberts [EMAIL PROTECTED] wrote: Benson Margulies wrote: What is

Re: Thrown by JAXB : undefined element declaration 's:schema'

The CXF wsdl2java does support the jaxb binding files as well (-b flag). However, the -b things must be actual jaxb/jaxws binding files, not another schema. That's very strange syntax that I haven't seen before. Interesting. Thus, to get it working for CXF, you would need to modify