You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Benjamin Schmeling <Be...@gmx.de> on 2006/02/02 20:10:26 UTC
Oneway call to a non existing operation
Hi,
I discovered the following not expected behaviour if I use Sandesha with
oneway web services. If I invoke an operation, that does not exist, no
error will occur, so that the client that uses Sandesha does not know
that its target web service call was not delivered to the application.
I know that it is not a requirement according to the
WS-ReliableMessaging specification, because only the delivery to the
receiver is acknowledged and not the delivery to the application, but in
this case it is a very common situation, because of typing errors in the
operation name. Maybe this error should be considered by Sandesha,
although not mandatory according to the specification.
Thanks,
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: Oneway call to a non existing operation
Posted by Jaliya Ekanayake <jn...@gmail.com>.
Hi Benjamin,
This is robost one-way invocation. Yes, it should be a good idea to support
this as well.
However, if the service is not available or wrong service, sequence will not
complete and there will be an error written to a log file.
Thanks,
Jaliya
----- Original Message -----
From: "Benjamin Schmeling" <Be...@gmx.de>
To: <sa...@ws.apache.org>
Sent: Thursday, February 02, 2006 2:10 PM
Subject: Oneway call to a non existing operation
> Hi,
>
> I discovered the following not expected behaviour if I use Sandesha with
> oneway web services. If I invoke an operation, that does not exist, no
> error will occur, so that the client that uses Sandesha does not know that
> its target web service call was not delivered to the application.
> I know that it is not a requirement according to the WS-ReliableMessaging
> specification, because only the delivery to the receiver is acknowledged
> and not the delivery to the application, but in this case it is a very
> common situation, because of typing errors in the operation name. Maybe
> this error should be considered by Sandesha, although not mandatory
> according to the specification.
>
> Thanks,
>
> Benjamin
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: Oneway call to a non existing operation
Posted by Jaliya Ekanayake <jn...@gmail.com>.
Hi Benjamin,
This is robost one-way invocation. Yes, it should be a good idea to support
this as well.
However, if the service is not available or wrong service, sequence will not
complete and there will be an error written to a log file.
Thanks,
Jaliya
----- Original Message -----
From: "Benjamin Schmeling" <Be...@gmx.de>
To: <sa...@ws.apache.org>
Sent: Thursday, February 02, 2006 2:10 PM
Subject: Oneway call to a non existing operation
> Hi,
>
> I discovered the following not expected behaviour if I use Sandesha with
> oneway web services. If I invoke an operation, that does not exist, no
> error will occur, so that the client that uses Sandesha does not know that
> its target web service call was not delivered to the application.
> I know that it is not a requirement according to the WS-ReliableMessaging
> specification, because only the delivery to the receiver is acknowledged
> and not the delivery to the application, but in this case it is a very
> common situation, because of typing errors in the operation name. Maybe
> this error should be considered by Sandesha, although not mandatory
> according to the specification.
>
> Thanks,
>
> Benjamin
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org