The com.sun.net.httpserver.HttpServer? It's not a servlet container (although it's fairly simple to add basic support for servlets to it). Shiro typically integrates via servlet filters. However, it's just a simple to embed Jetty into your application, their api is similar to the com.sun one. Why is a plain servlet container undesirable (as opposed to a full JEE container)?
Kalle On Tue, Jul 19, 2016 at 5:29 AM, seanmhogan <[email protected]> wrote: > I'm working on an application made up of many communicating processes, > where > Shiro will be used on the web tier for authentication and authorization. > That is Servlet 3.0 stuff so is straightforward. > > I also plan an interface into the back end where a full servlet container > is > undesirable, but authentication is still required. I could potentially use > Jetty, but I find the simplicity of the web server that comes with Java 6 > and later very attractive. Unfortunately I can't seem to find any > references > or helpful hints for how I might integrate that with Shiro. > > Has anyone tried this? Thanks in advance. > > > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/integration-with-Java-6-embedded-web-server-tp7581137.html > Sent from the Shiro User mailing list archive at Nabble.com. >
