Since those are trace messages from beanutils, and you explicitly set org.apache to warn in log4j.properties, I'm still thinking that your logging configuration isn't getting picked up. You might try Googling for logging in glassfish. On May 18, 2012 10:20 AM, "Paulo Pires" <[email protected]> wrote:
> Hi all, > > First of all, thanks to the project contributors for putting such an > effort in this project. > > Now, I'm struggling to get a simple Web application (just JSP 'stolen' > from Shiro samples code) to authenticate against a JDBC realm backed by > MySQL. Everytime I try to log-in the page just reloads again and doesn't > throw any kind of error. > > I've made the project source-code public, so that anyone can look at it, > and eventually it may become the basis for a tutorial on this. You can > check it at https://github.com/pires/simple-shiro-web-app > > I've tried to debug it, but somehow, my log4j configuration is not > working properly. I can see a 'shiro.log' file being generated and with > some output from commons.beanutils, but nothing about Shiro. I only get > error messages in Glassfish 'server.log' when some property in > 'shiro.ini' is wrongly configured. > > Any help will be highly appreciated. > > Thanks! > > -- > Paulo Pires > >
