[
https://issues.apache.org/jira/browse/AXIS2C-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar updated AXIS2C-1225:
-------------------------------------
Fix Version/s: 1.6.0
> missing wsa:Action leads to rampart failure
> -------------------------------------------
>
> Key: AXIS2C-1225
> URL: https://issues.apache.org/jira/browse/AXIS2C-1225
> Project: Axis2-C
> Issue Type: Bug
> Components: code generation
> Affects Versions: Current (Nightly)
> Environment: linux fc6
> Reporter: Frederic Heem
> Assignee: Milinda Lakmal Pathirage
> Fix For: 1.6.0
>
>
> Dear,
> The recent modification of WSDL2C has changed the way an action is
> serialized. The fields <wsa:Action> disappeared from the field
> <soapenv:Header>. The side effect is that axis2_msg_ctx_set_op() is not
> invoked to set the operation, later rampart called axis2_msg_ctx_get_op()
> returns NULL in build_policy() and print the message."Cannot find policy.
> Operation is NULL"
> The sec_echo client has the field <wsa:Action> and works fine.
> Here is the SOAP conversation:
> POST /axis2/services/zigbee HTTP/1.1
> User-Agent: Axis2C/1.4.0
> Content-Length: 1907
> Content-Type: application/soap+xml;charset=UTF-8;action="SetDeviceName"
> Host: localhost:9090
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";><soapenv:Header><wsse:Security
>
> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
> soapenv:mustUnderstand="1"><xenc:EncryptedKey
> xmlns:xenc="http://www.w3.org/2001/04/xmlenc#";><xenc:EncryptionMethod
> Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5";></xenc:EncryptionMethod><ds:KeyInfo
>
> xmlns:ds="http://www.w3.org/2000/09/xmldsig#";><wsse:SecurityTokenReference><wsse:KeyIdentifier
>
> EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary";
>
> ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier";>Xeg55vRyK3ZhAEhEf+YT0z986L0=
> </wsse:KeyIdentifier></wsse:SecurityTokenReference></ds:KeyInfo><xenc:CipherData><xenc:CipherValue>BPSRnKtCGpcejTiIHmhLKeZzznIYDjTZTdoVyPM9a0vMFoWU8dS1GfmipdvQpI/+0TJI7BwadsNNeQgJ+2BLdTTK7wuQA0iOHhMoT1/o2oLM3CMrxK44FmAgBk00MBxRttxK2aO4Dsw5ZUi494newW22KJHydyXhUyfU3AQaDzM=</xenc:CipherValue></xenc:CipherData><xenc:ReferenceList><xenc:DataReference
>
> URI="#EncDataID-f8160360-4852-1dd1"></xenc:DataReference></xenc:ReferenceList></xenc:EncryptedKey></wsse:Security></soapenv:Header><soapenv:Body><xenc:EncryptedData
> xmlns:xenc="http://www.w3.org/2001/04/xmlenc#";
> Type="http://www.w3.org/2001/04/xmlenc#Element";
> Id="EncDataID-f8160360-4852-1dd1"><xenc:EncryptionMethod
> Algorithm="http://www.w3.org/2001/04/xmlenc#aes256-cbc";></xenc:EncryptionMethod><xenc:CipherData><xenc:CipherValue>k2Luo60uTyqRlKj4m5T/7uPGpiXt3atjzyVUhAV4/Pa4vNZSmgVrr407Gv9owba6Jnb8KuJlZ206H4qHTJrHY4hBiZfCZv0Ar6+QR1WSd0KPNkOTnl7ZfvL3hnY97OftyKQVlkbR4JTagoVFId63ZX7luERhRfe6IjQfZ/GCIjh78hFXxFq/Mg8wSFBNZghxm5HFlTUg9cfRf5WZJ9illpIApefMGZZCNev/j+QYf2JUiRBcWXujQaKBngWaRgW6aLYhKhJL31aG/CXTPRaakQ==</xenc:CipherValue></xenc:CipherData></xenc:EncryptedData></soapenv:Body></soapenv:Envelope>HTTP/1.1
> 500 Internal Server Error
> Date: Wed Jul 2 17:21:49 2008 GMT
> Server: Axis2C/1.4.0 (Simple Axis2 HTTP Server)
> Content-Type: application/soap+xml;charset=UTF-8
> Content-Length: 795
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";><soapenv:Header></soapenv:Header><soapenv:Body><soapenv:Fault><soapenv:Code><soapenv:Value>soapenv:Sender</soapenv:Value><soapenv:Subcode
>
> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";><soapenv:Value>wsse:FailedCheck</soapenv:Value></soapenv:Subcode></soapenv:Code><soapenv:Reason><soapenv:Text
> xmlns:xml="http://www.w3.org/XML/1998/namespace"; xml:lang="en">Error in the
> Internal
> configuration.</soapenv:Text></soapenv:Reason><soapenv:Detail><wsse:ProblemSecurityHeader
>
> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";>rampc:Policy</wsse:ProblemSecurityHeader></soapenv:Detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
