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 "Chinmoy Chakraborty (JIRA)" <ji...@apache.org> on 2009/08/03 12:05:14 UTC
[jira] Created: (RAMPART-236) SOAP fault in not properly handled
for parameter based WS-Security (issue in RampartReceiver??)
SOAP fault in 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: Ruchith Udayanga Fernando
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.
[jira] Commented: (RAMPART-236) Error in service method is not
properly handled for parameter based WS-Security (issue in
RampartReceiver??)
Posted by "Chinmoy Chakraborty (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739525#action_12739525 ]
Chinmoy Chakraborty commented on RAMPART-236:
---------------------------------------------
Hi Nandana,
Could you please send me the url for latest trunk of rampart-core?
> 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: Ruchith Udayanga Fernando
> 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.
[jira] Updated: (RAMPART-236) SOAP fault in not properly handled
for parameter based WS-Security (issue in RampartReceiver??)
Posted by "Chinmoy Chakraborty (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chinmoy Chakraborty updated RAMPART-236:
----------------------------------------
Attachment: rampart_debug.log
Debug log. See at line 801. You will see 'internal server error'.
> SOAP fault in 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: Ruchith Udayanga Fernando
> 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.
[jira] Commented: (RAMPART-236) Error in service method is not
properly handled for parameter based WS-Security (issue in
RampartReceiver??)
Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738901#action_12738901 ]
Nandana Mihindukulasooriya commented on RAMPART-236:
----------------------------------------------------
Hi Chinmoy,
Can you please try with the latest trunk and Axis2 1.5 ?
regards,
Nandana
> 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: Ruchith Udayanga Fernando
> 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.
[jira] Updated: (RAMPART-236) Error in service method is not
properly handled for parameter based WS-Security (issue in
RampartReceiver??)
Posted by "Chinmoy Chakraborty (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chinmoy Chakraborty updated RAMPART-236:
----------------------------------------
Summary: Error in service method is not properly handled for parameter based WS-Security (issue in RampartReceiver??) (was: SOAP fault in not properly handled for parameter based WS-Security (issue in RampartReceiver??))
> 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: Ruchith Udayanga Fernando
> 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.