Introspect WSDL to create WSDLServiceContract
Hi, Do we have the requirement to introspect a WSDL port type to create the corresponding WSDLServiceContract? If so, we'll probably need to add an InterfaceWSDLIntrospector as we do for java. Or do we assume we always perform WSDL2Java (statically with code-generation or dynamically with ASM during runtime) to create a java interface which can be introspected to get the JavaServiceContract? Thanks, Raymond
Re: Introspect WSDL to create WSDLServiceContract
On Aug 29, 2006, at 2:01 PM, Raymond Feng wrote: Hi, Do we have the requirement to introspect a WSDL port type to create the corresponding WSDLServiceContract? If so, we'll probably need to add an InterfaceWSDLIntrospector as we do for java. Yes. Or do we assume we always perform WSDL2Java (statically with code- generation or dynamically with ASM during runtime) to create a java interface which can be introspected to get the JavaServiceContract? The builders should work off the Operations defined in the ServiceContract (perhaps with certain optimizations if they know the IDL) so ultimately there should be no need to convert to JavaServiceContract - I think Jim is working on that (e.g. r438003). -- Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Introspect WSDL to create WSDLServiceContract
I'm in the process of getting rid of the use of Method throughout the code base and moving to ServiceContract. This will give us the ability to plug in the databinding transformers. Since this is a significant change, please bear with me as I convert over - it may take a little while. Jim On Aug 29, 2006, at 2:08 PM, Jeremy Boynes wrote: On Aug 29, 2006, at 2:01 PM, Raymond Feng wrote: Hi, Do we have the requirement to introspect a WSDL port type to create the corresponding WSDLServiceContract? If so, we'll probably need to add an InterfaceWSDLIntrospector as we do for java. Yes. Or do we assume we always perform WSDL2Java (statically with code- generation or dynamically with ASM during runtime) to create a java interface which can be introspected to get the JavaServiceContract? The builders should work off the Operations defined in the ServiceContract (perhaps with certain optimizations if they know the IDL) so ultimately there should be no need to convert to JavaServiceContract - I think Jim is working on that (e.g. r438003). -- Jeremy - 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]
