Frank et al., Do you know if the scenario in which a WSDL with targetNamespace "a" imports a schema with targetNamespace "b" has been tested? The WSDL2JavaGenerator doesn't seem to handle this scenario. I'm not sure if it is a XSDHelper problem or a WSDL2JavaGenerator problem. - Ron
----- Original Message ---- From: Frank Budinsky <[EMAIL PROTECTED]> To: [email protected] Sent: Thursday, July 13, 2006 2:45:18 PM Subject: Re: How should XSDHelper.define() handle wsdls/schemas with schema imports XSDHelper.define() should also define all the imported schemas. If that's not happing, maybe the imported schemas can't be found so it's failing to resolve. Frank. Ron Gavlin <[EMAIL PROTECTED]> wrote on 07/13/2006 01:16:59 AM: > I have a WSDL which imports a schema, that itself imports two add'l > schemas. When I invoke XSDHelper.define() passing the WSDL as a > parameter, should the nested schema imports be resolved/defined or do > each of these "imported" schemas need to be "defined" explicitly? It > appears the WSDL2JavaGenerator currently expects XSDHelper.define() to > resolve/define the "imported" schemas which does not appear to work. > > Best regards, > > - Ron > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
