axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Daniels (JIRA)" <>
Subject [jira] Commented: (AXIS2-2998) custom handler is not executed
Date Tue, 07 Aug 2007 02:57:59 GMT


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:
>             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,
> 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:
For additional commands, e-mail:

View raw message