> Kai, you sort of say that CF doesn't support WS-* but could that might > be writing it off too early. > > In the Java world, is it axis (only) that provides those features? I > think it takes more than that right? Should we expect so much from CF? >
It's not only Axis, but Axis is a common way of doing things (not necessarily the only one or best one), together with extension libs such as WSS4J etc. That being said - obviously one can always handcraft WSDL, SOAP XML data, SOAP headers etc - that's for sure. You could also use pretty much any third party WS solution based on Java (and there are lots) to hook into you CF apps via CFObject and doing whatever you'd have to to get it working. What I'm saying is that the built-in web service engine based on Axis, CFCs and CFInvoke is very limited in what you could achieve with it. > > Just saying, I reckon I reckon it does a pretty ok job. And if you're > using .NET, well thats.not CF's fault. Hehe > Well - it's a bit too easy to put yourself into this point of view. Yes, MSFT might not adhere to W3C Standards re WS, or they might try to inject their own interpretation of things, but after all the reason why WS based on SOAP/WSDL are there is to bridge those technologies, right. So therefore this is not only MSFT's/.NET's fault at all. Cheers Kai >>> >>> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
