I'll second Lenny's remarks about the docs. I found the Shiro examples to
be more than ample for starting out. After that, I had to pour through the
proper documentation to get a better feel for the specifics of how certain
classes worked, but the docs usually had what I wanted to know. If they
didn't, I just read the source code. In fact, I'd say Shiro was the first
app that really got me to practice reading the source code of a third party
library to better understand it.

I'd say that the two most critical documents to read are the terminology
page (found at http://shiro.apache.org/terminology.html) and the
architecture page (found at http://shiro.apache.org/architecture.html) I
believe they will help you understand the reason why most of Shiro's
classes and features exist.

On Mon, Sep 14, 2015 at 4:16 PM, Sreyan Chakravarty <
[email protected]> wrote:

> Then where should I go for help ?
>
> On Tue, Sep 15, 2015 at 1:44 AM, Lenny Primak <[email protected]>
> wrote:
>
>> Dear Sreyan,
>>
>> I've been watching your threads over time, and seems to me that you
>> expect too much "free help" from this mailing list.
>> I myself taught myself Shiro from the ground up in about 15 days, had a
>> few questions, but mostly figured it out on my own.
>> Shiro is an open source product and has ample documentation, and is very
>> well (and simply!) designed.
>> Please try to understand the concepts yourself, and don't expect people
>> on the mailing list to "hand hold you" through every aspect of Shiro.
>> If you need consulting services, I am sure you can arrange for something,
>> Otherwise, expecting and _demanding_ what amounts to free consulting
>> services, on weekends too, is a bit too much IMHO.
>>
>> On Sep 14, 2015, at 3:58 PM, Sreyan Chakravarty wrote:
>>
>> > I am new to Shiro and am struggling to understand some of its concepts.
>> Is there any way I can attach a debugger to Shiro and check the flow of
>> method calls ?
>> >
>> > I am using Shiro in Tomcat with Eclipse.
>> >
>> > Regards
>> > Sreyan Chakravarty
>>
>>
>

Reply via email to