Yes isn't it? Initially I thought that I was missing something stupid out and then after countless test projects, I noticed that the duplication only occured when multiple services were published. Now I'm not sure if this is only the case for services manipulating the same objects (although I doubt it). I'll post a test project later on...
Anthony On Thursday, 30 June 2011, Daniel Kulp <[email protected]> wrote: > On Wednesday, June 29, 2011 10:38:05 AM Anthony Webster wrote: >> Hi there, >> >> I'm trying to add support for WS-Policy and I'm getting a rather >> strange behavior. I added the following to one of my two services : >> >> @Policy(uri = "policies/modalitiesSearch.xml", placement = >> Policy.Placement.BINDING, includeInWSDL = true) >> >> When I check the generate WSDL, I see *two* wsp:Policy elements with >> the same id (ModalitiesSearchImplServiceSoapBindingBindingPolicy) and >> *two* <wsp:PolicyReference elements within the binding element again >> refering to the same URI. >> >> I strange thing is that when I comment out the other webservice (which >> has no associated policies), the generated wsdl is normal (only one >> policy declaration). >> >> Any ideas? > > That's very strange. Not sure why another service would affect this at all. > Can you create a small testcase that shows this? Would be interesting to > debug. :-( > > > -- > Daniel Kulp > [email protected] > http://dankulp.com/blog > Talend - http://www.talend.com >
