If anybody has any comments they would be greatly appreciated.
we have a problem as follows:
We would like to deploy services on the fly, without using a
service-specific implementation class to handle the service action, such
that SOAP messages could be mapped onto a generic java method of the
form
Class foo implements SomeInterface{
Object handler(String name_space,
String method_name,
Object args[]) throws Exception;
}
in a handler class. where the object args in are the corresponding
Deserialised java object (or wrappers) from the body arguments and the
return value is then serialised and sent as a response, as with
conventional RPC.
I looked through the org.apache.axis.providers.* and i don't think any
of them gave this kind of functionality (although please correct me if i
am wrong)
I was thinking about extending RPCProvider, one could notionally see
this being done buy overriding invokeMethod(..), however i'm not sure if
this requires that the invoked java method exists in the service object
(which it does not) or whether operation.getMethod() will just return
null. Likewise the ServiceDesc will need initialising to reflect the
SOAP operations that the service will be providing.
so:
Initially we would be creating a new Provider which extended
RPCProvider, and overrode
initServiceDesc(...)-- to set the service description according to some
external information (or just from WSDL)
invokeMethod(...) to actually invoke the service.
does this sound sane?
regards,
owen
--
---------------------------------------------------------------------
owen cliffe (postgraduate) Email: [EMAIL PROTECTED]
Department of Computer Science Web: http://www.cs.bath.ac.uk/~occ
Univ. Bath, Bath, England BA2 7AY Tel: (+44) 1225 386183
