Hi Mark , > 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.) > Hmm , I do not see any option other than using URLBasedConfigurator to create ConfigurationContext. And drop all your resources into the repository.
Any please create a JIRA then we will try to come up with the proper approach of ding this. Thanks Deepal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
