axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepal Jayasinghe (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-294) Can't add user defined phases before the PostDispatch phase
Date Tue, 25 Oct 2005 11:16:29 GMT
    [ http://issues.apache.org/jira/browse/AXIS2-294?page=comments#action_12355731 ] 

Deepal Jayasinghe commented on AXIS2-294:
-----------------------------------------

Hi Chamikara,

First of all it's NOT a bug it's a security feature, we had a long discussion before we are
doing so. And we decided not show those system predefined phase to the user, but there can
be instance user want to add handlers to those phase, that is why we are displaying those
phase in axis2.xml (just to show there are phase like that) . 




> Can't add user defined phases before the PostDispatch phase
> -----------------------------------------------------------
>
>          Key: AXIS2-294
>          URL: http://issues.apache.org/jira/browse/AXIS2-294
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>   Components: deployment
>     Reporter: Chamikara Jayalath

>
> I changed the phase order of axis2.xml as following. 
>  <phase name="TransportIn"/>
>  <phase name="PreDispatch"/>
>  <phase name="Dispatch"/>
>  <phase name="userphase1"/>
>  <phase name="PostDispatch"/>
> and started tomcat. 
> Axis2 admin page, Available phases link gives following error.
> javax.servlet.ServletException: Invalid Phase : {0} for the handler {1} does not exit
in axis2.xml or refering to phase in diffrent flow; nested exception is: 
> 	org.apache.axis2.deployment.DeploymentException: Invalid Phase : {0} for the handler
{1} does not exit in axis2.xml or refering to phase in diffrent flow; nested exception is:

> 	org.apache.axis2.deployment.DeploymentException: Invalid Phase : {0} for the handler
{1} does not exit in axis2.xml or refering to phase in diffrent flow; nested exception is:

> 	org.apache.axis2.deployment.DeploymentException: Invalid Phase : {0} for the handler
{1} does not exit in axis2.xml or refering to phase in diffrent flow
> 	org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:70)
> 	org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:164)
> 	org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:211)
> 	org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:805)
> 	org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:696)
> 	org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:605)
> 	org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:677)
> 	java.lang.Thread.run(Thread.java:534)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message