Probably discussing it on the dev list is more appropriate,
The reason I'd like to do is that with OSGI-INF style no web application elements are supported, I've debugged a lot into it.
So for now, I use 'webbundle:'protocol to deploy a minimal web application which uses Spring. This is fine for the purpose of running the actual application in OSGI but creates a bit of disconnect in cases when Blueprint is standardized upon for describing endpoints, thus it would be quite perfect if one could always use Blueprint to describe the endpoints and then, optionally, whenever actually needed, add a single web.xml file to the bundle and turn it into a web bundle and get all the pax-web support for JSPs, request dispatchers, etc...
Cheers, Sergey On 21/01/13 18:12, Sergey Beryozkin wrote:
Hi I'd like to use Aries to define CXF endpoints but load them as part of loading a web application, as opposed to using OSGI-INF, so I'd like to do something like (same way it can be done with Spring) <listener> <listener-class> **aries**.web.context.ContextLoaderListener </listener-class> </listener> <context-param> <param-name>contextConfigLocation</param-name> <param-value> WEB-INF/ariesContext.xml </param-value> </context-param> I wonder, if we should basically create an analog of CXFServlet which deals with Spring, something like CXFAriesServlet ? Cheers, Sergey
