You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Jon Hanshew (JIRA)" <ji...@apache.org> on 2007/09/01 00:17:18 UTC
[jira] Created: (RAMPART-79) setAction in Options does not create a
non-null "Action" element in the SOAP Header
setAction in Options does not create a non-null "Action" element in the SOAP Header
-----------------------------------------------------------------------------------
Key: RAMPART-79
URL: https://issues.apache.org/jira/browse/RAMPART-79
Project: Rampart
Issue Type: Bug
Components: rampart-policy
Affects Versions: 1.3
Environment: Axis2 1.3, Rampart 1.3 RC1 Windows XP Java SDK 1.5
Reporter: Jon Hanshew
Fix For: 1.3
I have tried to use the "setAction()" function of the Options class to set the wsa:Action element in the SOAP header, but it always shows up null. Since I cannot set the wsa:Action element in the header, the service refuses to use the actionMapping setting its the service.xml file and refuses to do the request.
I turned on the debug trace and collected a debug trace for this behavior.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RAMPART-79) setAction in Options does not create a
non-null "Action" element in the SOAP Header
Posted by "Jon Hanshew (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jon Hanshew updated RAMPART-79:
-------------------------------
Attachment: services xxx.xml
CodeSegment.txt
DebugLog.rtf
The debug log shows my attempts to set the Action values in an Options object and the failure to have the data appear in the wsa:Action element in the SOAP header. (Highlighted in red)
The code segment shows how I tried to set the values and call the service.
I have include a services.xml file to show the actionMapping that I have set up and am trying to invoke.
> setAction in Options does not create a non-null "Action" element in the SOAP Header
> -----------------------------------------------------------------------------------
>
> Key: RAMPART-79
> URL: https://issues.apache.org/jira/browse/RAMPART-79
> Project: Rampart
> Issue Type: Bug
> Components: rampart-policy
> Affects Versions: 1.3
> Environment: Axis2 1.3, Rampart 1.3 RC1 Windows XP Java SDK 1.5
> Reporter: Jon Hanshew
> Fix For: 1.3
>
> Attachments: CodeSegment.txt, DebugLog.rtf, services xxx.xml
>
>
> I have tried to use the "setAction()" function of the Options class to set the wsa:Action element in the SOAP header, but it always shows up null. Since I cannot set the wsa:Action element in the header, the service refuses to use the actionMapping setting its the service.xml file and refuses to do the request.
> I turned on the debug trace and collected a debug trace for this behavior.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (RAMPART-79) setAction in Options does not create a
non-null "Action" element in the SOAP Header
Posted by "Jon Hanshew (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jon Hanshew closed RAMPART-79.
------------------------------
Resolution: Invalid
Problem with WSDL. soapAction set to null string in WSDL. ServiceStub sets action to value in WSDL and overrides value in code that calls stub.
> setAction in Options does not create a non-null "Action" element in the SOAP Header
> -----------------------------------------------------------------------------------
>
> Key: RAMPART-79
> URL: https://issues.apache.org/jira/browse/RAMPART-79
> Project: Rampart
> Issue Type: Bug
> Components: rampart-policy
> Affects Versions: 1.3
> Environment: Axis2 1.3, Rampart 1.3 RC1 Windows XP Java SDK 1.5
> Reporter: Jon Hanshew
> Fix For: 1.3
>
> Attachments: CodeSegment.txt, DebugLog.rtf, services xxx.xml
>
>
> I have tried to use the "setAction()" function of the Options class to set the wsa:Action element in the SOAP header, but it always shows up null. Since I cannot set the wsa:Action element in the header, the service refuses to use the actionMapping setting its the service.xml file and refuses to do the request.
> I turned on the debug trace and collected a debug trace for this behavior.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.