Hi Bruce,

We don't have proper tutorials yet - the sample apps are as close to
tutorials as we have.

However, the samples have changed a bit, and we do have a Spring-based
example (without Hibernate) that does use a typical JDBC data source.  We
just used Spring there to simplify our own JDBC code (not wanting to deal
with transaction boundaries and catching JDBC Exceptions).

But even then, that's no substitute for a proper tutorial, and probably with
a simpler 'stack' as you suggest. If you would be willing to write something
in that regard, I'm sure we'd all be forever grateful :)  But I have to ask
- would you consider writing them on the Apache Confluence Wiki for
starters?  Of course we'd be happy wherever they resided, but it'd be nice
if this was part of Ki's documentation so users could find it easily.

In any event, and no matter where they reside, we'd love some help in this
area, so if you can spare the time, please feel free!

Best,

Les

On Wed, Apr 1, 2009 at 4:17 PM, Bruce Phillips <[email protected]> wrote:

>
> I searched through the posts and through the samples provided with the
> download for a basic tutorial that shows how to use JSecurity with a web
> application and a database that is storing the user's information (username,
> password, roles, permissions, etc).
>
> I didn't find a good tutorial.  The web application samples that come with
> the download either don't use a database or use Spring and Hibernate, which
> I think, over complicates learning for someone who won't be using those two
> technologies and isn't familiar with them.
>
> Do you know of a good tutorial?
>
> If not, do you think it would be useful if I created a series of tutorials
> that show how to use JSecurity with a web application and a database that
> stores the user's information?
>
> I've done similar tutorials on my blog (http://www.brucephillips.name/blog)
> for other technologies.
>
> Bruce
> --
> View this message in context:
> http://n2.nabble.com/Basic-Tutorial-That-Uses-A-Database-tp2571323p2571323.html
> Sent from the JSecurity User mailing list archive at Nabble.com.
>
>

Reply via email to