Sure, we could leave rampart core compile against servlet api 2.3 from axis2 kernel and exclude it from rampart integration so that Jetty would run with 2.5, but still if all rampart modules are imported in Eclipse IDE as projects, then both servlet api versions are available on the classpath and when running Rampart Jetty-based tests in Eclipse, one gets:
java.lang.SecurityException: class "javax.servlet.ServletRequestListener"'s signer information does not match signer information of other classes in the same package If nobody is using Eclipse to run tests but sticking to command-line then this approach would work. I also tried to find a Jetty version that uses servlet api 2.3 but even the oldest 6.0 is using 2.5. Regards, Detelin On Tue, Jul 15, 2014 at 10:28 PM, Andreas Veithen <[email protected] > wrote: > Yes, that is a very good idea. > > I had a quick look at the patch. I think that we need to refine a bit > the part about the Servlet API versioning. More on this later. > > Andreas > > On Tue, Jul 15, 2014 at 12:36 PM, <[email protected]> wrote: > > Hi again, > > I opened an enhancement request for Rampart to re-enable the transport > > binding integration tests: > > > > https://issues.apache.org/jira/browse/RAMPART-416 > > > > I provided a patch that introduces usage of embedded Jetty 7 web > container > > with SSL support, modifies RampartTest to use that instead of the > UtilServer > > and re-enables transport binding integration tests. > > Please let me know if you have any concerns with it, I will be glad to > > improve it. > > > > Regards, > > Detelin > > > > > > On Mon, Jul 14, 2014 at 12:18 PM, <[email protected]> wrote: > >> > >> Hi Rampart devs, > >> While working on a Rampart extension for Kerberos authentication over > >> transport binding, I was looking into implementing an integration test > in > >> Rampart, but noticed that transport binding (https) tests are not > supported > >> at the moment, since it uses Axis2 SimpleHttpServer which does not > support > >> https. Are there any plans to use a regular web container (e.g. Jetty) > to > >> enable transport binding tests? I can verify if Jetty Maven plugin can > be > >> used for this purpose, but wanted to check whether this has not already > been > >> attempted in the past. Any comments on this are welcome. > >> > >> Thanks, > >> Detelin > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
