I'm working on a shrink-wrap app that has to inter-operate with other shrink-wrap apps written in .NET with WCF. We've worked out how to get WCF wsdl with policy imported into the Java app and have them converse with each other.
The thing is that the endpoint address is constantly changing, the interface is changing occasionally in development and across releases, and the policy is changing very rarely. Ideally I'd like to have the policy separated from the various interfaces and applied when I configure the endpoint or create a client with the api. When our .NET WCF apps inter-operate with each other, they don't even expose wsdl urls since the interface is known and the policy is fixed by declaring a few options to WCF. Looking at the docs for the WSDL to SOAP tool, I want that to be the answer. I would create a policy enhanced binding from my somehow magically reusable policy and a port. However, I don't see any way to feed policy to that. I'd like to better understand how what I'm doing fits into normal ways of doing SOAP web services before I start trying to do a lot of poorly educated hacking. -- Darrin
