I did a bit of research on this last night and at lunchtime - looks like CXF 2.4 (I think trunk was upgraded to cxf 2.4 a couple of days ago?) has support for this: https://cwiki.apache.org/confluence/display/CXF20DOC/Client+HTTP+Transport+%28including+SSL+support%29
I guess we could probably add this authentication mechanism so the relevant setting can just be picked up from openejb-jar.xml like we do for the other webservice security mechanisms. What do you reckon? I was going have more of a play around with this tonight. Jon On Wed, Jul 20, 2011 at 2:51 PM, Romain Manni-Bucau <[email protected]>wrote: > the context is programatically created, not sure you can modify its > web.xml... > > the handler idea is probably better > > - Romain > > 2011/7/20 rnieto <[email protected]> > > > > > Jean-Louis MONTEIRO wrote: > > > > > > Okay, I got it. > > > Actually, WebServices are deployed in the root context. You need to add > a > > > servlet filter on the root webapp not on the one owning the web > service. > > > That is definitely not a good way, that's why I created a JIRA few > month > > > ago. > > > > > > https://issues.apache.org/jira/browse/OPENEJB-1529 > > > > > > What are you trying to achieve? > > > May be you can use JAX-WS Handlers? > > > > > > Jean-Louis > > > > > > > Odd, I've tried adding it to the web.xml on the webapps\ROOT, web.xml on > > conf and it still seems to be not picking up my filter. Guess I'll have > to > > poke around some more, thanks for the idea though. > > > > -- > > View this message in context: > > > http://openejb.979440.n4.nabble.com/Tomcat-Servlet-Filters-or-Valves-and-OpenEJB-tp3680204p3680800.html > > Sent from the OpenEJB User mailing list archive at Nabble.com. > > >
