[
https://issues.apache.org/jira/browse/RAMPART-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilina Buddhika resolved RAMPART-236.
--------------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
This has been fixed in the trunk as well as in the 1_6 branch. When there is an
error thrown from the service, it is properly communicated to client as a SOAP
Fault.
If it is a service fault, then it should be secured. But for parameter based
configurations, it is required to include the corresponding handlers in the
in-fault-flow and out-fault-flow which should be included by default.
> Error in service method is not properly handled for parameter based
> WS-Security (issue in RampartReceiver??)
> ------------------------------------------------------------------------------------------------------------
>
> Key: RAMPART-236
> URL: https://issues.apache.org/jira/browse/RAMPART-236
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core
> Affects Versions: 1.4
> Environment: Axis2 1.4, Rampart 1.4, Tomcat 5.0, JDK 1.5, Windows XP
> Reporter: Chinmoy Chakraborty
> Assignee: Thilina Buddhika
> Fix For: 1.6.0
>
> Attachments: rampart_debug.log
>
>
> For parameterbased ws-security enabled services, in normal cases when there
> is no error at the time of invocation (invocation of business logic) of the
> service, it works fine. So far so good. Now when some error happens at the
> time of service invocation it does not return SOAP fault back.
> I guess this a bug in RampartReceiver/(RampartSender?). Please find
> rampart_debug.log. See at line 801.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
