Hi Nandana,
I use following settings in my service.xml file , only with these settings
I can expose a POJO service called "ExampleService"
<service name="ExampleService">
<parameter name="ServiceObjectSupplier" locked="false">
org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier
</parameter>
<parameter name="SpringBeanName"
locked="false">ExampleService</parameter>
<operation name="CreateUser">
<messageReceiver
class="org.apache.axis2.rpc.receivers.RPCMessageReceiver" />
</operation>
</service>
I think SpringServletContextObjectSupplier is responsible for providing
Speing beans in to service , It would be great if we can use such approach
in Rampart password callback handler also.
Thanks ,
On Tue, Nov 11, 2008 at 2:09 PM, Nandana Mihindukulasooriya <
[EMAIL PROTECTED]> wrote:
> Hi Sagara,
> Can you provide a code snippet of how you access spring beans in
> service level so that we can see whether we can use the same approach within
> the Rampart password callback handler.
>
> thanks,
> nandana
>
>
> On Tue, Nov 11, 2008 at 11:15 AM, Sagara Gunathunga <
> [EMAIL PROTECTED]> wrote:
>
>>
>> Hi guys ,
>> I want to invoke Acegi [1] AuthenticationManger within the handle
>> method of PWCHandler. Is there any way to access Spring beans within
>> the PWCHandler of Rampart module ? (because our identity and access
>> management module based on Acegi ) I use axis2 within the Spring
>> context approach where web service is exposed as a part of a web
>> application.
>>
>> Axis2 provide "ServiceObjectSupplier" and "SpringBeanName" parameters for
>> access Spring beans in service level , is there such mechanism
>> available for Rampart ...? Or any other suggestions ....?
>>
>>
>> [1] - http://www.acegisecurity.org/
>>
>> Thanks ,
>>
>> Sagara Gunathunga
>>
>> Blog - ssagara.blogspot.com
>> Web - http://sagaras.awardspace.com/
>>
>
>
--
Sagara Gunathunga
Blog - ssagara.blogspot.com
Web - http://sagaras.awardspace.com/
