You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by "Nath, Niraj" <Ni...@cns-inc.com> on 2009/08/11 15:50:13 UTC
axis2 1.0 ( war package ) .. problem with application handler
Hi,
We use axis2 1.0 war package in our application. We have hosted a set of services at our end they all are working fine. We also have a handler inserted for authenticating the clients who call our web services.
Now we have some requirement where we are acting as a client to a set of services hosted somewhere else. We are seeing that the handler which we inserted is coming into play here too & so it's trying to authenticate the outgoing soap request. This is not what we wanted. We only wanted to intercept the soap requests which are coming to our server & not the other way round.
May be we have inserted our phase at the wrong location. Can someone help here to put the phase at the correct location? I'm attaching the axis2.xml file where we are inserting the phase.
The inserted handler is at line 221-224 ( or search for EcamsHandler)..
Appreciate any help. Thanks
Regards
Niraj Nath
Re: axis2 1.0 ( war package ) .. problem with application handler
Posted by Sagara Gunathunga <sa...@gmail.com>.
Deepal/Niraj , sorry for my misunderstanding.
On Tue, Aug 11, 2009 at 8:37 PM, Deepal Jayasinghe<de...@gmail.com> wrote:
> Sagara, nope that did not help..
>
> Niraj:
> When you try to create a client inside the application server like
> tomcat, what happen is, it tries to create the service client with the
> server's configuration context. If you do not know about the
> configuration context, that is the run time of Axis2, which consist of
> all the data.
>
> If you do not want server's configuration for the client, what you
> have to do is not to use the default constructor of the service
> client. Rather create a new configuration context from an axis2.xml
> you want and use that.
>
> You can find more information about this :
> http://today.java.net/pub/a/today/2006/12/13/invoking-web-services-using-apache-axis2.html
>
> On Tue, Aug 11, 2009 at 10:45 AM, Sagara
> Gunathunga<sa...@gmail.com> wrote:
>> Hi Niraj,
>>
>> You have defined your Handlers in the globe level using axis2.xml
>> file, then it will engage in globally in Axis2 that the reason for
>> your issue. One possible solution is remove that handler definition
>> from axis2.xml and deploy your handlers as a Axis2 module[1]
>> separately, where you can define your handler definition in module.xml
>> file instead of axis2.xml .Then you can engage that module only for
>> required services on service.xml file using <module
>> ref="moduleName"/> tag.
>>
>> [1] - http://ws.apache.org/axis2/1_5/modules.html
>>
>>
>> Thanks ,
>>
>>
>> On Tue, Aug 11, 2009 at 7:20 PM, Nath, Niraj<Ni...@cns-inc.com> wrote:
>>> Hi,
>>>
>>> We use axis2 1.0 war package in our application. We have hosted a set of services at our end they all are working fine. We also have a handler inserted for authenticating the clients who call our web services.
>>>
>>> Now we have some requirement where we are acting as a client to a set of services hosted somewhere else. We are seeing that the handler which we inserted is coming into play here too & so it's trying to authenticate the outgoing soap request. This is not what we wanted. We only wanted to intercept the soap requests which are coming to our server & not the other way round.
>>>
>>> May be we have inserted our phase at the wrong location. Can someone help here to put the phase at the correct location? I'm attaching the axis2.xml file where we are inserting the phase.
>>>
>>> The inserted handler is at line 221-224 ( or search for EcamsHandler)..
>>>
>>> Appreciate any help. Thanks
>>>
>>> Regards
>>>
>>> Niraj Nath
>>>
>>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://sagaras.awardspace.com/
>>
>
>
>
> --
> http://blogs.deepal.org
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://sagaras.awardspace.com/
Re: axis2 1.0 ( war package ) .. problem with application handler
Posted by Deepal Jayasinghe <de...@gmail.com>.
Sagara, nope that did not help..
Niraj:
When you try to create a client inside the application server like
tomcat, what happen is, it tries to create the service client with the
server's configuration context. If you do not know about the
configuration context, that is the run time of Axis2, which consist of
all the data.
If you do not want server's configuration for the client, what you
have to do is not to use the default constructor of the service
client. Rather create a new configuration context from an axis2.xml
you want and use that.
You can find more information about this :
http://today.java.net/pub/a/today/2006/12/13/invoking-web-services-using-apache-axis2.html
On Tue, Aug 11, 2009 at 10:45 AM, Sagara
Gunathunga<sa...@gmail.com> wrote:
> Hi Niraj,
>
> You have defined your Handlers in the globe level using axis2.xml
> file, then it will engage in globally in Axis2 that the reason for
> your issue. One possible solution is remove that handler definition
> from axis2.xml and deploy your handlers as a Axis2 module[1]
> separately, where you can define your handler definition in module.xml
> file instead of axis2.xml .Then you can engage that module only for
> required services on service.xml file using <module
> ref="moduleName"/> tag.
>
> [1] - http://ws.apache.org/axis2/1_5/modules.html
>
>
> Thanks ,
>
>
> On Tue, Aug 11, 2009 at 7:20 PM, Nath, Niraj<Ni...@cns-inc.com> wrote:
>> Hi,
>>
>> We use axis2 1.0 war package in our application. We have hosted a set of services at our end they all are working fine. We also have a handler inserted for authenticating the clients who call our web services.
>>
>> Now we have some requirement where we are acting as a client to a set of services hosted somewhere else. We are seeing that the handler which we inserted is coming into play here too & so it's trying to authenticate the outgoing soap request. This is not what we wanted. We only wanted to intercept the soap requests which are coming to our server & not the other way round.
>>
>> May be we have inserted our phase at the wrong location. Can someone help here to put the phase at the correct location? I'm attaching the axis2.xml file where we are inserting the phase.
>>
>> The inserted handler is at line 221-224 ( or search for EcamsHandler)..
>>
>> Appreciate any help. Thanks
>>
>> Regards
>>
>> Niraj Nath
>>
>>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://sagaras.awardspace.com/
>
--
http://blogs.deepal.org
Re: axis2 1.0 ( war package ) .. problem with application handler
Posted by Sagara Gunathunga <sa...@gmail.com>.
Hi Niraj,
You have defined your Handlers in the globe level using axis2.xml
file, then it will engage in globally in Axis2 that the reason for
your issue. One possible solution is remove that handler definition
from axis2.xml and deploy your handlers as a Axis2 module[1]
separately, where you can define your handler definition in module.xml
file instead of axis2.xml .Then you can engage that module only for
required services on service.xml file using <module
ref="moduleName"/> tag.
[1] - http://ws.apache.org/axis2/1_5/modules.html
Thanks ,
On Tue, Aug 11, 2009 at 7:20 PM, Nath, Niraj<Ni...@cns-inc.com> wrote:
> Hi,
>
> We use axis2 1.0 war package in our application. We have hosted a set of services at our end they all are working fine. We also have a handler inserted for authenticating the clients who call our web services.
>
> Now we have some requirement where we are acting as a client to a set of services hosted somewhere else. We are seeing that the handler which we inserted is coming into play here too & so it's trying to authenticate the outgoing soap request. This is not what we wanted. We only wanted to intercept the soap requests which are coming to our server & not the other way round.
>
> May be we have inserted our phase at the wrong location. Can someone help here to put the phase at the correct location? I'm attaching the axis2.xml file where we are inserting the phase.
>
> The inserted handler is at line 221-224 ( or search for EcamsHandler)..
>
> Appreciate any help. Thanks
>
> Regards
>
> Niraj Nath
>
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://sagaras.awardspace.com/