Why is ServiceClass in services.xml compulsary ?

[Angel Todorov <at...@gmail.com>]

Hello,

I am wondering why the ServicesClass property when describing a
service in services.xml is made mandatory ? Doesn't it depend on the
message receiver to decide how to pass the SOAP request, to where to,
and/or what to call next ? Why is it assumed that the message receiver
actually uses a specific class for the web service business logic and
not some universal factory which only it is aware of ? Thanks.

Regards,
Angel

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org

Re: Why is ServiceClass in services.xml compulsary ?

[Deepal Jayasinghe <de...@opensource.lk>]

hi  Angel ;

No it is not mandatory. and as you have mentioned it is up to the the
MessageReceiver to decide what to do. But if you are planing to use
Axis2 default message receivers then you need to have above parameter.

Thanks
Deepal

> Hello,
>
> I am wondering why the ServicesClass property when describing a
> service in services.xml is made mandatory ? Doesn't it depend on the
> message receiver to decide how to pass the SOAP request, to where to,
> and/or what to call next ? Why is it assumed that the message receiver
> actually uses a specific class for the web service business logic and
> not some universal factory which only it is aware of ? Thanks.
>
> Regards,
> Angel
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org