I would recommend using some external security mechanism like Spring
Security or Apache and ip filtering. If that doesn't work, you might
be able to use Spring's RequestContextListener to put the request in a
ThreadLocal.
Matt
On Thu, Mar 19, 2009 at 4:09 AM, Marian wrote:
>>I don't know if it's
>I don't know if it's possible, but I don't think it's a good idea.
>Your web services shouldn't be talking to the Servlet API IMO.
Suppose I want to prevent a user coming from a certain IP to use a certain
method - how could I know his IP? In servlets it's easy -
request.getRemoteAddr() gives tha
On Wed, Mar 18, 2009 at 3:09 AM, Marian wrote:
>>there will be a
>>src/main/webapp/WEB-INF/xfire-services.xml in your project.
>
> Yes, I noticed that (and now I notice that Xfire servlet is actually
> org.codehaus.xfire.spring.XFireSpringServlet, so I presume it uses the Spring
> configuration);
>there will be a
>src/main/webapp/WEB-INF/xfire-services.xml in your project.
Yes, I noticed that (and now I notice that Xfire servlet is actually
org.codehaus.xfire.spring.XFireSpringServlet, so I presume it uses the Spring
configuration); I've tried, but for whatever reason it didn't discover my
