Hi list,
is there anybody who knows something about the interoperability of the globus toolkit 4.2.1 with the windows communication framework? Adding a service reference by e.g. http://x.x.x.x:pp/wsrf/services/w7x/codac/services/fields/W7XVacuumFieldsFac tory?wsdl no WS-Addressing is activated. Even inserting <wsaw:UsingAddressing wsdl:required="true"> directly into the according *_binding.wsdl does not cause a WCF client to send the WS-Addressing header. However, when I add the following to my client code, the factory service works: WSHttpBinding wsHttpBinding = new WSHttpBinding(SecurityMode.None); //Tests with globus-start-container -nosec EndpointAddress address = new EndpointAddress("http://x.x.x.x:pp/wsrf/services/w7x/codac/services/fields/W 7XVacuumFieldsFactory"); W7XVacuumFieldsFactoryPortTypeClient factory = new W7XVacuumFieldsFactoryPortTypeClient(wsHttpBinding, address); After having this working, I could create a resource and get back an EndpointReferenceType, for which I don't know how to apply to the instance service. Has anybody already experience in using WCF clients just by importing the wsdl files? If not, do the globus developers intend to make gt4 compatible to the w3c standards being used in WCF? Somewhere I read that WS-Addressing is being enabled via WS-Policy like <wsp:Policy><wsp:UsingAddressing></wsp:Policy>!? In my applications it would be of great importance to have clients being generated just by the wsdl files, at least for Java, C#, C++ and Python with no additional code. Every tiny information about this issue would be useful for me. Thanks, Andreas
