One of the major complaints of CFMX's implementation of calling and creating webservices hinges around retrieving and creating SOAP headers. Macromedia just released a technote
explaining how to create or process header fields in web services. This TechNote also provides a patch to Apache Axis to allow users to retrieve the response headers from a web service request, as well as a hot fix to allow users to create a SOAP header in a request that has the "mustUnderstand" attribute set to be true.
I have 2 questions, and if you wouldn't mind shedding some light, I'd really appreciate it:
1. What does this hotfix get us? Specifically, what are some examples of where being able to read the SOAP headers is crucial? You suggest that the current implementation has drawn major complaints, but for what?
2. Will there be any sort of hotfix to allow cfinvoke to specify a serviceType from a WSDL that has multiple types specified? The Microsoft MapPoint 3.0 WSDL is a good example of where the inability to specify types is a huge pain in the butt, and renders the product almost useless.
...and is this progress towards WS-Security?
I didn't say that the current implementation has drawn major complaints. Instead I stated that one of the major complaints has been the ability to read SOAP headers :-) It just gives more flexibiliy. I did not have any involvment in this fix so I do not have examples although I will look into it, to try to find worthwhile examples.
In CFMX 6.1 a bug was fixed bug #50814 to handle WSDL's with more than one service. CFMX still does not allow the user to select which service they want to use. This is the issue you are seeing with MapPoint. There is an enhancement request #50815 for this issue.
This fix did not target WS security either.
I wouldn't expect WS-Security support any time real soon either, until WS-S itself stabilizes. That could be a while - I think the current assumption is another 18-24 months. (?)
I have had a specific issue regarding the inability to read soap headers (MX 6.0). My problem was with trying to consume an instant messenging web service. The inability to read SOAP headers meant that state management was impossible. A major drawback for cfmx. I am wondering if anyone knows if this has been fixed?
has this issue been fixed in 7.1? we are having issues with CF recognizing the mustUnderstand attribute in the header. We get the following error:
"Did not understand "MustUnderstand" header(s):"
Any help is greatly appreciated.