OK - just deployed Vladimir's changes to the stax instance. They look fine.
I'll take a look at Tomcat and see if I can get that working @Vladimir why don't you work on a new blog for using jetty and container-based authentication. @Vladimir - please create a JIRA item (like this one: https://issues.apache.org/jira/browse/INFRA-3347) to get access to the esme blog. D. On Tue, Mar 29, 2011 at 3:47 AM, Vladimir Ivanov <[email protected]> wrote: > Ethan, > > It shouldn't break existing authentication scheme. New module is mapped to > specific URL (you are right - it's probably better to define this URL in > property file). > > Vladimir > > 2011/3/28 Ethan Jewett <[email protected]> > >> Sounds good to me. I haven't been able to review the code yet, as >> Vladimir requested, but actually the easiest way to get a review is >> probably to commit it and then reply to the commit message requesting >> that people take a look at it :-) >> >> One question: Is this going to break the existing login, or will it be >> optional via a configuration parameter? >> >> Ethan >> >> On Mon, Mar 28, 2011 at 4:44 PM, Richard Hirsch <[email protected]> >> wrote: >> > Vladimir has added an initial version of code for this issue ( >> > https://issues.apache.org/jira/browse/ESME-214) . I'd like to move >> > forward on this issue. >> > >> > My suggestion to get things going again: >> > >> > 1. Vladimir should commit his changes in Boot.scala + UserAuth.scala >> > 2. Dick will test this in Tomcat. >> > 3. We then document this functionality in two blogs - one for jetty >> > and one for Tomcat >> > >> > Any thoughts? >> > >> > D. >> > >> > > > > -- > Best Regards, > Vladimir Ivanov >
