Hi Les,

Thanks a lot for your *very* prompt response :-)

I'm currently holding off applying the IoC pattern, as I've previously seen
it applied with varying results; its the 'javascript' of the java world -
powerful, flexible, and mostly badly used :-)
In fact I've went to shiro in order to simplify and remove spring (and its
security module). Guice is more appealing (as I also liked pico in the early
days of IoC) I'm holding off until I really, really need to.

So, I want to ensure a fairly easy upgrade path for shiro, so will try to
keep my intervention to a minimum

In short I'm going to write either:
An adaptation of the classes as suggested below (basically wrap, lookup and
delegate to the DefaultFilterChainManager and IniShiroFilter),
or
Decorate the Ini class at instantiation in the IniShiroFilter to allow
loading from other sources (which is pretty much done with the configure()
method.  Hmm, this maybe less clean semantically, but it'll get me there
quicker...

Give me a shout if you want any of the code (it might be kinda throw away,
as I'm not using a JDBC database)
-- 
View this message in context: 
http://shiro-user.582556.n2.nabble.com/Database-loaded-urls-section-tp5707379p5708497.html
Sent from the Shiro User mailing list archive at Nabble.com.

Reply via email to