Hi Glen,
> Throwing an exception to do this is (IMHO) bad code. It's expensive, slower,
> non-intuitive (what would you expect "getService()" to do?) and just plain
> annoying for people calling this method.
>
Well inactive service treat as same as service is not there in the
system. So I do n
Hi Deepal:
Deepal jayasinghe wrote:
> Yes, there is a difference. One method is for management other method is
> for dispatching.
> So at the runtime when a message receive we call getService, and if we
> want to activate, inactivate we call other method.
Throwing an exception to do this is (IMHO
Yes, there is a difference. One method is for management other method is
for dispatching.
So at the runtime when a message receive we call getService, and if we
want to activate, inactivate we call other method.
So please do not remove the method.
Deepal
> Hi y'all:
>
> So I'm cleaning up a littl
Hi y'all:
So I'm cleaning up a little code and javadoc, and happened to come across
AxisConfiguration.getService()... which *throws an Exception* if you ask for
an inactive service.
...which is why we have a second method called "getServiceForActivation()"
that simply avoids the check and the exc
