-
1. Re: wsHttpEndpoint_policy, jbossws native 3.4.0.GA, jbossas 5.1.0.GA
jjfraney Dec 21, 2010 5:27 PM (in response to jjfraney)ok, so I find that "wsHttpEndpoint_policy" is an id generated by the WCF service. From their wsdl:
<wsp:Policy wsu:Id="wsHttpEndpoint_policy">
....
</wsp:Policy>
I'm attaching the part of the wsdl that defines the policy.
-
is2.wsdl.zip 3.0 KB
-
-
2. Re: wsHttpEndpoint_policy, jbossws native 3.4.0.GA, jbossas 5.1.0.GA
jjfraney Dec 22, 2010 8:36 AM (in response to jjfraney)Ok, I used debugger and single stepped to find the root of the "Unsupported Policy" exception.
org.jboss.ws.extensions.policy.deployer.PolicyDeployer is not finding the namespace in it 'domainDeployerMap'. The namespace it looks for is: http://schemas.xmlsoap.org/ws/2005/07/securitypolicy
So, I guess I will be learning how to introduce this policy to my configuration. Is this the right path? I'm not sure because I have an expectation that this would be already builtin.
-
3. Re: wsHttpEndpoint_policy, jbossws native 3.4.0.GA, jbossas 5.1.0.GA
jjfraney Dec 22, 2010 9:03 AM (in response to jjfraney) -
4. Re: wsHttpEndpoint_policy, jbossws native 3.4.0.GA, jbossas 5.1.0.GA
asoldano Dec 22, 2010 9:31 AM (in response to jjfraney)Hi John,
unfortunately JBossWS-Native does not provide ws-security policy functionalities. That's the reason why the policy engine tells you the policy is not supported.
You should move to JBossWS-CXF for using this features.
Btw, what the other user suggesting in the other thread basically is overriding the whole jaxws provider configuration to use the RI. That's probably going to give you other problems, though, as you already figured out.
-
5. Re: wsHttpEndpoint_policy, jbossws native 3.4.0.GA, jbossas 5.1.0.GA
jjfraney Dec 23, 2010 9:03 AM (in response to asoldano)Thanks.