Folks ant elder wrote:
Cool. Is it really necessary to use policy intents when there's an existing wsdl document, i.e. when binding.ws uses a wsdlElement pointing to a wsdl binding? There's already ways of using soap/jms with wsdl so instead of: <binding.ws wsdlElement=" http://helloworld#wsdl.binding(HelloWorldSoapJmsBinding)" requires=" transport.jms"/> it would more likely be : <binding.ws requires="transport.jms"/> Right?
It depends what the WSDL is being used for. If the WSDL does define the binding to JMS, then sure, the WSDL takes precedence.
Your example is the "pure" case where the interface definition comes from the implementation and the WSDL is auto-generated by the runtime.
...ant
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
