I've looked through the code and there seems no straightfoward way to configure
an axis2 client from within an axis2 service.
My intent was to include the axis2_client.xml and the client repository within
the service aar file.
Essentially, I'd have a standard Axis2 webservice that once called, would
internally engage rampart and make several webservice calls to other servers.
Our documentation does not specify how to do something like this.
There are several ways to attempt this....
Option 1. (not very nice)
If I try to use the original messageContext.getConfigurationContext(), then I
fail to load my rampart password-callback class that exists within the aar
file. (I guess that's an obvious ClassLoader gotcha)
Option 2. (preferred)
If I try to create a new configuration context within the aar file, (well, I'd
like to but there seems to be no way access my axis2_client.xml or the client
repository containing the rampart mar files.)
Is there any way to get option 2 to work. My goal here is to make the service
as easy to deploy as possible. The client loves the idea of a single aar file
and some JNDI entries - it would be a shame to not have a self-contained
solution.
If this is better served in the Axis2 User's list, let me know and I'll repost.
Cheers,
Mark B
