Deepal Jayasinghe wrote on 17.06.2009 16:43:
You could do something like below, where you can add a number of
action mapping for the operation and client can send the different
action based on the call. And then at the service you can get the
action that client sends (from the msgctx), and then I hope you can do
the rest based on the action.
Thanks for you answer!
I forgot to mention something in my last email. I planning to create a custom
deployer that creates new operations based on the operations defined in the WSDL
of the actual server (the one my component forwards to). I need to add a
parameter for correlation to the already existing parameters.
The bottom line is that the parameters of these methods are not always the same
and by replacing the structured parameters with some sort of "generic xml string
parameter" I'd loose type safety etc.
So I guess I won't be able to solve this by only evaluating the "action" value.
On second thought, perhaps I won't need the service.xml at all when using a
custom deployer. I'm only starting to find my way through the axis internals so
my ideas may sound weird
I'd also appreciate comments on the idea with the deployer :-)
On Wed, Jun 17, 2009 at 10:34 AM, Jens
Rutschmann<jens.rutschm...@gmx.info> wrote:
Hi all,
I'm looking for a way to reuse a generic java method for multiple web
service operations. The reason for this is that I need to create a component
that forwards the client's request to another web service. Since the
additional steps this component needs to do are always the same I'd like to
use a single generic implementation using AXIOM.
In service.xml when defining an operation I can only specify the name of
existing methods in the service class. Is there any way to map an arbitrary
name to a single method multiple times?
I'd like to avoid creating new classes with stub methods that call the
generic method since that would mean compiling and deploying of new code at
runtime.
Best regards any many thanks in advance,
Jens
