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 "randy hoffman (JIRA)" <ji...@apache.org> on 2006/03/31 14:38:58 UTC

[jira] Commented: (AXIS2-420) Axis2 will not work correctly unless i hit an invalid EPR first, otherwise it always hits the initial successful EPR.

    [ http://issues.apache.org/jira/browse/AXIS2-420?page=comments#action_12372670 ] 

randy hoffman commented on AXIS2-420:
-------------------------------------

Tried on 0.95 this week and the problem has been fixed.

> Axis2 will not work correctly unless i hit an invalid EPR first, otherwise it always hits the initial successful EPR.
> ---------------------------------------------------------------------------------------------------------------------
>
>          Key: AXIS2-420
>          URL: http://issues.apache.org/jira/browse/AXIS2-420
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>     Versions: 0.94
>  Environment: Axis2 0.94 running as an exploded war file on Tomcat.
> CentOS 4.2, Tomcat 5.5.15, JDK 1.5.0_06, Dell SC420 Server
>     Reporter: randy hoffman
>     Priority: Minor

>
> I created one class with three public methods.  I created a service with three operations in a services.xml file related to the class and methods.
> I created an services archive file and deployed under Tomcat with a CATALINA_BASE type setup.
> I run with REST support and hit the service via a GET or POST from a client.
> Everything seems to work ok only if i hit an invalid endpoint upon startup, for example, right service, wrong operation.  I then recieve a Soap fault and from then on i receive the right operations/errors depending upon my request,
> However, if i ask for a valid service, but invalid operation initially upon startup, i get the correct response, but then, no matter what operation i request, it calls the initial operation again, which is thr wrong operation, but does pass the correct parameters.
> If i ask for an invalid service, it throws an error and seems to put it back to initial startup mode.  That is, if i request a valid service/operation, it will stay on that same operation no matter what operation i request afterwards, even an invalid one, as long as the service is valid.  If i request an invalid operation, but a valid service, it performs as it should afterwards.
> I hope i explainded this well enough.  If not, don't hesitate to contact me.
> Thanks,
> randy hoffman
> randy_hoffman@hotmail.com

-- 
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