You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Justin Schoeman <ju...@expertron.co.za> on 2006/01/30 19:17:28 UTC

Axis2 0.94 and WSDL2Java

Hi all, when using Axis2 0.94 and WSDL2Java to generate both client and 
server, I get the following exception (just the first lines quoted):

org.apache.axis2.AxisFault: org.apache.axis2.AxisFault: Operation Not 
found EPR is http://127.0.0.1:8080/axis2/services/XMLVendService2.0 and 
WSA Action =
         at 
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:46)

Any idea what is wrong? 
http://127.0.0.1:8080/axis2/services/expertron_client/XMLVendService2.0?wsdl

Gives me the WSDL for the service, so it seems to be up at the right place.

Any idea what may be wrong here?

Thanks,

Justin

Re: Axis2 0.94 and WSDL2Java

Posted by Justin Schoeman <ju...@expertron.co.za>.
I see that by simply adding the operation name inside the stub, 
everything works fine.  Do you perhaps have the JIRA ref for this bug?

Thanks,

Justin


Ajith Ranabahu wrote:
> Hi Justin,
> Attach the WSDL please. I've the feeling that this is the codegen bug 
> that we came across some time earlier but have to make sure.
> 
> On 1/31/06, *Justin Schoeman* <justin@expertron.co.za 
> <ma...@expertron.co.za>> wrote:
> 
>     Hi all, when using Axis2 0.94 and WSDL2Java to generate both client and
>     server, I get the following exception (just the first lines quoted):
> 
>     org.apache.axis2.AxisFault: org.apache.axis2.AxisFault: Operation Not
>     found EPR is http://127.0.0.1:8080/axis2/services/XMLVendService2.0 and
>     WSA Action =
>              at
>     org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:46)
> 
>     Any idea what is wrong?
>     http://127.0.0.1:8080/axis2/services/expertron_client/XMLVendService2.0?wsdl
> 
>     Gives me the WSDL for the service, so it seems to be up at the right
>     place.
> 
>     Any idea what may be wrong here?
> 
>     Thanks,
> 
>     Justin
> 
> 
> 
> 
> -- 
> Ajith Ranabahu

Re: Axis2 0.94 and WSDL2Java

Posted by Justin Schoeman <ju...@expertron.co.za>.
Thanks, wsdl and associated xsd files attached.  Big, so tgzip'ed.

-justin

Ajith Ranabahu wrote:
> Hi Justin,
> Attach the WSDL please. I've the feeling that this is the codegen bug 
> that we came across some time earlier but have to make sure.
> 
> On 1/31/06, *Justin Schoeman* <justin@expertron.co.za 
> <ma...@expertron.co.za>> wrote:
> 
>     Hi all, when using Axis2 0.94 and WSDL2Java to generate both client and
>     server, I get the following exception (just the first lines quoted):
> 
>     org.apache.axis2.AxisFault: org.apache.axis2.AxisFault: Operation Not
>     found EPR is http://127.0.0.1:8080/axis2/services/XMLVendService2.0 and
>     WSA Action =
>              at
>     org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:46)
> 
>     Any idea what is wrong?
>     http://127.0.0.1:8080/axis2/services/expertron_client/XMLVendService2.0?wsdl
> 
>     Gives me the WSDL for the service, so it seems to be up at the right
>     place.
> 
>     Any idea what may be wrong here?
> 
>     Thanks,
> 
>     Justin
> 
> 
> 
> 
> -- 
> Ajith Ranabahu

Re: Axis2 0.94 and WSDL2Java

Posted by Ajith Ranabahu <aj...@gmail.com>.
Hi Justin,
Attach the WSDL please. I've the feeling that this is the codegen bug that
we came across some time earlier but have to make sure.

On 1/31/06, Justin Schoeman <ju...@expertron.co.za> wrote:
>
> Hi all, when using Axis2 0.94 and WSDL2Java to generate both client and
> server, I get the following exception (just the first lines quoted):
>
> org.apache.axis2.AxisFault: org.apache.axis2.AxisFault: Operation Not
> found EPR is http://127.0.0.1:8080/axis2/services/XMLVendService2.0 and
> WSA Action =
>          at
> org.apache.axis2.engine.DispatchPhase.checkPostConditions(
> DispatchPhase.java:46)
>
> Any idea what is wrong?
>
> http://127.0.0.1:8080/axis2/services/expertron_client/XMLVendService2.0?wsdl
>
> Gives me the WSDL for the service, so it seems to be up at the right
> place.
>
> Any idea what may be wrong here?
>
> Thanks,
>
> Justin
>



--
Ajith Ranabahu