axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michele Mazzucco (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-2998) custom handler is not executed
Date Fri, 22 Feb 2008 19:27:19 GMT

     [ 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


Mime
View raw message