Each have their own schema generation frameworks. We just dump the output of the JAXB schema gen right into the WSDL.
I can try to fix this tomorrow or saturday if you don't manage to beat me to it :) Cheers, Dan -- Dan Diephouse - m: (616) 318 3474 MuleSource Sent from my mobile, apologies for errors due to my large thumbs. -----Original Message----- From: "Benson Margulies" <[EMAIL PROTECTED]> To: [email protected] Sent: 10/11/2007 3:42 PM Subject: RE: schema import question Why wouldn't this be common to JAXB and Aegis? ________________________________ From: Dan Diephouse [mailto:[EMAIL PROTECTED] Sent: Thursday, October 11, 2007 1:52 PM To: [email protected] Subject: Re: schema import question Ah I see. Yeah, there used to be a switch which generates import statements like this: <import namespace="urn:your:namespace"/> Then the tool (wsdl.exe) is responsible for finding the right schema from the wsdl. I think that code is only in the xfire code base though. We would need to add this code to the AegisDatabinding I think :-\ - Dan Benson Margulies wrote: I posted it to a JIRA ... CXF-1103. -----Original Message----- From: Dan Diephouse [mailto:[EMAIL PROTECTED] Sent: Thursday, October 11, 2007 1:40 PM To: [email protected] Subject: Re: schema import question Benson Margulies wrote: I've failed to find a description of what the WSDL would look like when it was 'importing' a schema that was present in-line. I'd like to manually repair one of my CXF-generated WSDLs to see if it makes the Microsoft wsdl.exe tool happier. Can someone clue me in., Can you give an example of a WSDL thats causing problems with wsdl.exe? - Dan -- Dan Diephouse MuleSource http://mulesource.com | http://netzooid.com/blog -- Dan Diephouse MuleSource http://mulesource.com | http://netzooid.com/blog
