With 2.4.1, this may be easier to achieve than before, but it's not quite
there.
With 2.4.x, support for multiple bus's has been greatly enhanced. Thus, with
a little work, you may be able to have a context with 2 bus objects, one for
the secure and one for the insecure. Then have a servlet work for each.
<cxf:bus name="secure"/>
<cxf:bus name="insecure"/>
<jaxws:endpoint bus="secure" address="/secure/MyService" ..../>
<jaxws:endpoint bus="insecure" address="/insecure/MyService" ..../>
.....
Looking at the code, you would need a subclass of CXFServlet that would
override the
protected void loadBus(ServletConfig sc);
method to look at a servlet init-param to have it lookup the appropriate
spring bean. Actually, if you want to post a patch, a patch to CXFServlet
that would allow configuring the bus id to use would be great (and likely
pretty easy)
Let me know how that works for you.
Dan
On Monday, July 25, 2011 10:59:57 AM Conficio wrote:
> Dan,
> just wondering if you like my example or if there is anything else I could
> provide?
>
> Is there any idea of an alternative (like starting some service per
> CXFServlet and others per Java class?
>
> Kaj
> Still hoping to make multiple CXFServlet configs work.
>
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/separate-CXFServlet-for-private-API-s-tp326
> 1355p4631755.html Sent from the cxf-user mailing list archive at Nabble.com.
--
Daniel Kulp
[email protected]
http://dankulp.com/blog
Talend - http://www.talend.com
