I prefer the spring based configuration as all config then be in one place. If i need to find a configuration issue i have to look only one place rather than maintaining multiple config files. Also we can use place holders for properties where values might come from database. If you are comfortable with Spring then using the spring config is very good. On Apr 13, 2015 8:08 PM, "Lenny Primak" <[email protected]> wrote:
> I would use shiro.ini. > It's simper, and when trying to figure out what's wrong, there is only one > place to go (shiro.ini) > instead of figuring out how to go through Spring etc. > > On Apr 13, 2015, at 6:34 AM, Dishant Anand wrote: > > Hi Team, > > I was going to integrate shiro into our company's enterprise project . On > the documentation , I can see there are two ways to do the integration > firstly using the simple shiro.ini file and through the shiro spring > integration . > > On stack overflow and various other forums people were discussing around > these two technique's and I was bit confused as to which kind of > integration to be followed in my application . > > Should i use the simple *ini file *based approach or should i go with > spring based integration . we have configured our project to use CDI and > spring . > > Can somebody please help me on this. > > Thanks and Regards, > Dishant Anand > > >
