ALSB 3.0: Problem with Nested Policies in Proxy Service WSDL

Question

Hello,
I'm trying to implement client applications that consume Web Services.
In ALSB, i imported the WSDLs of the services, created business and proxy Services.
Creating web references in .NET and Netbeans is working well, as long as there is no security policy attached to the WSDLs of the proxy services.
When attaching a policy, ALSB nests it inside the WSDL:
<s0:Policy s1:Id="signMessage">
<wssp:Integrity SignToken="false">
<wssp:SignatureAlgorithm URI="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
<wssp:CanonicalizationAlgorithm URI="http://www.w3.org/2001/10/xml-exc-c14n#"/>
<wssp:Target>
and references it, where i want it to have. in this case it's in the request of the service:
<s2:input>
<s4:body use="literal"/>
<wsp:Policy>
<wsp:PolicyReference URI="#signMessage"/>
</wsp:Policy>
</s2:input>
The problem is, that neither .Net (C#) nor Netbeans (Java) correctly import and handle these policies. .Net even mentions in the generated code that the "Policy" element was not handled. So when running my applications, i logically get exceptions that no credentials/tokens or else were delivered from the client side. In general the mentioned IDEs that i'm using support the configuration of those security issues. But when not correctly parsing the WSDL from the Service Bus, they don't work.
I tried many ways to dodge this problem, but without success.
Manually writing policy Statements into the WSDL files is not what i'm searching for as a solution. I want it dynamically.
I hope i could describe my problem clear enough and to get a possible solution.
Thanks

Answer 1

Sorry, found the answer but forgot to update this thread.
The ?WSDL mechanism fails if Enforce WS-I Interoperability is true for the Proxy Service.
While BEA support (and the docs relating to this flag) say this is by design (Only POST not GET is supported by WS-I) personally it seems to me that this rule should apply to operation invocation not a metadata inquiry but there you go...