[
https://issues.apache.org/jira/browse/AXIS2-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713488#action_12713488
]
Runo Barrdahl commented on AXIS2-4354:
--------------------------------------
Dear Andreas:
Thanks for your prompt reaction.
An extract of the wsdl containing the Policy tag reads as follows:
"
<wsp:Policy wsu:Id="theXXX_WebService_policy">
- <wsp:ExactlyOne>
- <wsp:All>
- <sp:TransportBinding
xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702";>
- <wsp:Policy>
- <sp:TransportToken>
- <wsp:Policy>
<sp:HttpsToken />
</wsp:Policy>
</sp:TransportToken>
- <sp:AlgorithmSuite>
- <wsp:Policy>
<sp:Basic256 />
</wsp:Policy>
</sp:AlgorithmSuite>
- <sp:Layout>
- <wsp:Policy>
<sp:Strict />
</wsp:Policy>
</sp:Layout>
<sp:IncludeTimestamp />
</wsp:Policy>
</sp:TransportBinding>
- <sp:SignedEncryptedSupportingTokens
xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702";>
- <wsp:Policy>
- <sp:UsernameToken
sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/2007
02/IncludeToken/AlwaysToRecipient">
- <wsp:Policy>
<sp:WssUsernameToken10 />
</wsp:Policy>
</sp:UsernameToken>
</wsp:Policy>
</sp:SignedEncryptedSupportingTokens>
- <sp:Wss11
xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702";>
- <wsp:Policy>
<sp:MustSupportRefKeyIdentifier />
<sp:MustSupportRefIssuerSerial />
<sp:MustSupportRefThumbprint />
<sp:MustSupportRefEncryptedKey />
</wsp:Policy>
</sp:Wss11>
- <sp:Trust13
xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702";>
- <wsp:Policy>
<sp:MustSupportIssuedTokens />
<sp:RequireClientEntropy />
<sp:RequireServerEntropy />
</wsp:Policy>
</sp:Trust13>
<wsaw:UsingAddressing />
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
"
In addition, the following standards are referred to in the wsdl:
"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec
urity-utility-1.0.xsd"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata";
xmlns:tns="http://bgonline.se/ws/autogiro";
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing";
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";
xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract";
xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl";
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";
xmlns:wsa10="http://www.w3.org/2005/08/addressing";
xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex";
"
I hope this information will provide information enough, otherwise,
please come back.
For your information, there was a lot of trial and error before I
actually managed to receive a sensible response from the web service
created by Microsoft .NET tools and running on a server for that
purpose.
In one instance, Axis2 threw an exception saying that "... relative
reference... must be absolute ..". This led to that the web service
definition had to be amended to exchange relative references for
absolute ones.
Also, I find that the documentation on how to use Axis2 is quite bried
and did not provide me with answers to a lot of questions that I had.
Apart from that, in my view, Axis2 appears to be an excellent product.
Best Regards, Runo
> wsdl2Java removes policy tag Trust13 attribute
> ----------------------------------------------
>
> Key: AXIS2-4354
> URL: https://issues.apache.org/jira/browse/AXIS2-4354
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.4.1
> Environment: jdk1.5.0_04, WinXP, Eclipse Axis2 1.4.1, Rampart 1.4,
> Addressing 1.4.1 - calling WebService on MS .NET platform
> Reporter: Runo Barrdahl
> Priority: Minor
>
> 1. When using wsdl2Java (batch file command: C:\axis2-1.4.1\bin\wsdl2java
> -uri C:\EclipseLogViewer\BGC_NewAutoGiroWS\wsdl\MandateSearchService.wsdl -d
> xmlbeans -o C:\EclipseLogViewer\BGC_NewAutoGiroWS -p
> com.tieto.bgc.autogiro.ws -ns2p
> bgonline.se.mandatesearchservice.schemas.getmandatelistrequest.v1.0=bgonline.se.mandatesearchservice.schemas.getmandatelistrequest,bgonline.se.mandatesearchservice.schemas.getmandatelistresponse.v1.0=bgonline.se.mandatesearchservice.schemas.getmandatelistresponse,bgonline.se.mandatesearchservice.schemas.getmandaterequest.v1.0=bgonline.se.mandatesearchservice.schemas.getmandaterequest,bgonline.se.shared.schemas.messageTypes.v1.0=bgonline.se.shared.schemas.messageTypes,bgonline.se.mandatesearchservice.schemas.getmandateresponse.v1.0=bgonline.se.mandatesearchservice.schemas.getmandateresponse,impl.bgonline.se.mandatesearchservice.schemas.getmandateresponse.v1.0=impl.bgonline.se.mandatesearchservice.schemas.getmandateresponse
> -u -or) Stub is crea
ted OK.
> 2. However, when executing call to web service exception is thrown. I found
> out. After some fairly lengthy error localisation attempts, I finally found
> that the cause of the exemption was that the policy tag "<Trust13> had lost
> its attribute.
> 3. After manual patching of 2 instances of the policy tag to become
> "<sp:Trust13
> xmlns:sp=\"http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702\"; >"
> execution of the call to the Stub was without any error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
