so you confirm that [filters] do not work with Spring Remoting and instead of create custom filter I should look at subclassing/implementing SecureRemoteInvocationExecutor ?
Jason Eacott wrote: > > they can be (if configured to use a servlet (its normal) > and a servlet filter could be made to work (this is how spring security > implements theirs for example), but it seems like doubling up on the > same task to me since there is already the SecureRemoteInvocationExecutor > > > Narcom wrote: >> I use Spring HTTP-based remoting. >> client example: >> >> <bean id="sampleManager" >> >> class="org.springframework.remoting.httpinvoker.HttpInvokerProxyFactoryBean"> >> <property name="serviceUrl" >> value="http://localhost:8084/SpringRemoting/remoting/secure/sampleManager"/> >> <property name="serviceInterface" >> value="my.samples.shiro.spring.SampleManager"/> >> <property name="remoteInvocationFactory" >> ref="secureRemoteInvocationFactory"/> >> </bean> >> >> <bean id="secureRemoteInvocationFactory" >> >> class="org.apache.shiro.spring.remoting.SecureRemoteInvocationFactory"/> >> >> As I understand Spring remoting based on servlet technology? >> >> >> Les Hazlewood-3 wrote: >>> The filters only work for an incoming servlet request. Are you using >>> HTTP-based remoting? Or Java RMI or some other mechanism? >>> >> > > -- View this message in context: http://n2.nabble.com/Adding-new-custom-filter-to-filters-in-ShiroFilter-tp4188224p4202161.html Sent from the Shiro User mailing list archive at Nabble.com.
