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 "Michele Mazzucco (JIRA)" <ji...@apache.org> on 2007/07/23 16:30:31 UTC
[jira] Created: (AXIS2-2998) custom handler is not executed
custom handler is not executed
------------------------------
Key: AXIS2-2998
URL: https://issues.apache.org/jira/browse/AXIS2-2998
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Environment: linux 2.6.14, java 1.5, axis2 1.1.1, tomcat 5.5.20
Reporter: Michele Mazzucco
Fix For: 1.1.1
Scenario: I have a custom handler which replaces RequestURIBasedDispatcher and deploys services on the fly from a remote repository.
Problem: it used to work with axis2 1.1, but since using axis2 1.1.1 it's not called any more (it looks like there are no errors, apart that the request fails because the service is not available). No log statements from my custom handler are printed, which makes me think that the handler is not called.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2998) custom handler is not executed
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-2998:
------------------------------------
Fix Version/s: (was: 1.1.1)
> custom handler is not executed
> ------------------------------
>
> Key: AXIS2-2998
> URL: https://issues.apache.org/jira/browse/AXIS2-2998
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Environment: linux 2.6.14, java 1.5, axis2 1.1.1, tomcat 5.5.20
> Reporter: Michele Mazzucco
> Assignee: Deepal Jayasinghe
> Attachments: axis2_logs.log, catalina.out, module.xml, node_axis2.xml, qosp_debug.log, QOSPRequestURIBasedDispatcher.java
>
>
> Scenario: I have a custom handler which replaces RequestURIBasedDispatcher and deploys services on the fly from a remote repository.
> Problem: it used to work with axis2 1.1, but since using axis2 1.1.1 it's not called any more (it looks like there are no errors, apart that the request fails because the service is not available). No log statements from my custom handler are printed, which makes me think that the handler is not called.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2998) custom handler is not executed
Posted by "Glen Daniels (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518058 ]
Glen Daniels commented on AXIS2-2998:
-------------------------------------
I believe this is a simple case-sensitivity problem. If you change your module.xml to use <InFlow> and <OutFlow> instead of <inflow> / <outflow>, things should work fine.
I'll open another JIRA that recommends that we should make this check case-insensitive.
> custom handler is not executed
> ------------------------------
>
> Key: AXIS2-2998
> URL: https://issues.apache.org/jira/browse/AXIS2-2998
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Environment: linux 2.6.14, java 1.5, axis2 1.1.1, tomcat 5.5.20
> Reporter: Michele Mazzucco
> Assignee: Deepal Jayasinghe
> Attachments: axis2_logs.log, catalina.out, module.xml, node_axis2.xml, qosp_debug.log, QOSPRequestURIBasedDispatcher.java
>
>
> Scenario: I have a custom handler which replaces RequestURIBasedDispatcher and deploys services on the fly from a remote repository.
> Problem: it used to work with axis2 1.1, but since using axis2 1.1.1 it's not called any more (it looks like there are no errors, apart that the request fails because the service is not available). No log statements from my custom handler are printed, which makes me think that the handler is not called.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Assigned: (AXIS2-2998) custom handler is not executed
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe reassigned AXIS2-2998:
----------------------------------------
Assignee: Deepal Jayasinghe
> custom handler is not executed
> ------------------------------
>
> Key: AXIS2-2998
> URL: https://issues.apache.org/jira/browse/AXIS2-2998
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Environment: linux 2.6.14, java 1.5, axis2 1.1.1, tomcat 5.5.20
> Reporter: Michele Mazzucco
> Assignee: Deepal Jayasinghe
> Fix For: 1.1.1
>
> Attachments: axis2_logs.log, catalina.out, module.xml, node_axis2.xml, qosp_debug.log, QOSPRequestURIBasedDispatcher.java
>
>
> Scenario: I have a custom handler which replaces RequestURIBasedDispatcher and deploys services on the fly from a remote repository.
> Problem: it used to work with axis2 1.1, but since using axis2 1.1.1 it's not called any more (it looks like there are no errors, apart that the request fails because the service is not available). No log statements from my custom handler are printed, which makes me think that the handler is not called.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2998) custom handler is not executed
Posted by "Michele Mazzucco (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518132 ]
Michele Mazzucco commented on AXIS2-2998:
-----------------------------------------
Glen,
I'll try, but it works with older versions up to 1.1.1
> custom handler is not executed
> ------------------------------
>
> Key: AXIS2-2998
> URL: https://issues.apache.org/jira/browse/AXIS2-2998
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Environment: linux 2.6.14, java 1.5, axis2 1.1.1, tomcat 5.5.20
> Reporter: Michele Mazzucco
> Assignee: Deepal Jayasinghe
> Attachments: axis2_logs.log, catalina.out, module.xml, node_axis2.xml, qosp_debug.log, QOSPRequestURIBasedDispatcher.java
>
>
> Scenario: I have a custom handler which replaces RequestURIBasedDispatcher and deploys services on the fly from a remote repository.
> Problem: it used to work with axis2 1.1, but since using axis2 1.1.1 it's not called any more (it looks like there are no errors, apart that the request fails because the service is not available). No log statements from my custom handler are printed, which makes me think that the handler is not called.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2998) custom handler is not executed
Posted by "Glen Daniels (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518136 ]
Glen Daniels commented on AXIS2-2998:
-------------------------------------
That's because older versions (prior to March 15, 2007) of AXIOM used case-insensitive comparisons for the child QName iterator. :)
XML itself (and thus the API) MUST be case-sensitive. But particular applications (Axis2 config) can choose to ignore case if desired.
> custom handler is not executed
> ------------------------------
>
> Key: AXIS2-2998
> URL: https://issues.apache.org/jira/browse/AXIS2-2998
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Environment: linux 2.6.14, java 1.5, axis2 1.1.1, tomcat 5.5.20
> Reporter: Michele Mazzucco
> Assignee: Deepal Jayasinghe
> Attachments: axis2_logs.log, catalina.out, module.xml, node_axis2.xml, qosp_debug.log, QOSPRequestURIBasedDispatcher.java
>
>
> Scenario: I have a custom handler which replaces RequestURIBasedDispatcher and deploys services on the fly from a remote repository.
> Problem: it used to work with axis2 1.1, but since using axis2 1.1.1 it's not called any more (it looks like there are no errors, apart that the request fails because the service is not available). No log statements from my custom handler are printed, which makes me think that the handler is not called.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2998) custom handler is not executed
Posted by "Michele Mazzucco (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michele Mazzucco updated AXIS2-2998:
------------------------------------
Attachment: qosp_debug.log
catalina.out
axis2_logs.log
I'm attaching the logs as well.
> custom handler is not executed
> ------------------------------
>
> Key: AXIS2-2998
> URL: https://issues.apache.org/jira/browse/AXIS2-2998
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Environment: linux 2.6.14, java 1.5, axis2 1.1.1, tomcat 5.5.20
> Reporter: Michele Mazzucco
> Fix For: 1.1.1
>
> Attachments: axis2_logs.log, catalina.out, module.xml, node_axis2.xml, qosp_debug.log, QOSPRequestURIBasedDispatcher.java
>
>
> Scenario: I have a custom handler which replaces RequestURIBasedDispatcher and deploys services on the fly from a remote repository.
> Problem: it used to work with axis2 1.1, but since using axis2 1.1.1 it's not called any more (it looks like there are no errors, apart that the request fails because the service is not available). No log statements from my custom handler are printed, which makes me think that the handler is not called.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2998) custom handler is not executed
Posted by "Michele Mazzucco (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michele Mazzucco resolved AXIS2-2998.
-------------------------------------
Resolution: Fixed
> custom handler is not executed
> ------------------------------
>
> Key: AXIS2-2998
> URL: https://issues.apache.org/jira/browse/AXIS2-2998
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Environment: linux 2.6.14, java 1.5, axis2 1.1.1, tomcat 5.5.20
> Reporter: Michele Mazzucco
> Assignee: Deepal Jayasinghe
> Attachments: axis2_logs.log, catalina.out, module.xml, node_axis2.xml, qosp_debug.log, QOSPRequestURIBasedDispatcher.java
>
>
> Scenario: I have a custom handler which replaces RequestURIBasedDispatcher and deploys services on the fly from a remote repository.
> Problem: it used to work with axis2 1.1, but since using axis2 1.1.1 it's not called any more (it looks like there are no errors, apart that the request fails because the service is not available). No log statements from my custom handler are printed, which makes me think that the handler is not called.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2998) custom handler is not executed
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514843 ]
Deepal Jayasinghe commented on AXIS2-2998:
------------------------------------------
Please try with Axis2 1.3 -RC2 and let us know if the issues is still there. if it is please attach all the necessary data to re-create the issue.
Thanks
Deepal
> custom handler is not executed
> ------------------------------
>
> Key: AXIS2-2998
> URL: https://issues.apache.org/jira/browse/AXIS2-2998
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Environment: linux 2.6.14, java 1.5, axis2 1.1.1, tomcat 5.5.20
> Reporter: Michele Mazzucco
> Fix For: 1.1.1
>
> Attachments: axis2_logs.log, catalina.out, module.xml, node_axis2.xml, qosp_debug.log, QOSPRequestURIBasedDispatcher.java
>
>
> Scenario: I have a custom handler which replaces RequestURIBasedDispatcher and deploys services on the fly from a remote repository.
> Problem: it used to work with axis2 1.1, but since using axis2 1.1.1 it's not called any more (it looks like there are no errors, apart that the request fails because the service is not available). No log statements from my custom handler are printed, which makes me think that the handler is not called.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org