Thanks for asking.

I don’t particularly like the standard Java Webapp way of configuring security. It forces you to configure things in your web server (for example in Tomcat with a tomcat-users.xml). It is also not portable, so you have to configure different web servers differently. For example, you can’t use the tomcat-users.xml in Winstone. In Winstone, the equivalence of a tomcat-users.xml are the “Security options”, which are documented here:
http://winstone.sourceforge.net/ (search the page for “Security options”)

What I have found is more powerful and easier is to use, is Spring Security. When using that, everything can be configured inside the webapp and nothing has to be configured manually afterwards, in the web server. The war can also be dropped into any web server without modification.

I have used it with war’s in Winstone too. Works great.

Here’s an example to get you going:
http://www.springbyexample.org/examples/simple-spring-security-webapp.html

And here’s the official website for Spring Security:
http://static.springsource.org/spring-security/site/

/Hugo

http://blog.jayway.com/2009/03/14/executable-jar-with-onejar-maven-plugin/

It’s for Maven projects which need to be built as an executable .jar file. Onejar-maven-plugin collects all dependency jars inside one big executable jar, and makes your application really easy to run. It also works better and simpler than maven-assembly-plugin.

/Hugo

This is a neat use of maven for packaging into the winstone embedded function. A winstone user at one of my clients was asking about a maven plugin the other day, so I’ve forwarded this onto him. I don’t use maven 2 much myself (preferring Ant for speed), but plenty of people do, so your help in extending Winstone is appreciated.

Thanks,

Rick