You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Samisa Abeysinghe (JIRA)" <ji...@apache.org> on 2010/12/22 12:06:18 UTC

[jira] Updated: (RAMPART-236) Error in service method is not properly handled for parameter based WS-Security (issue in RampartReceiver??)

     [ https://issues.apache.org/jira/browse/RAMPART-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Samisa Abeysinghe updated RAMPART-236:
--------------------------------------

    Assignee:     (was: Ruchith Udayanga Fernando)

> 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
>         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.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org