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 "Deepal Jayasinghe (JIRA)" <ji...@apache.org> on 2007/07/24 06:43:31 UTC
[jira] Commented: (AXIS2-2998) custom handler is not executed
[ 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