For better or worse, the CXF situation is not structured the same way. If you look at the CXFServlet and AbstractCXFServlet, there's nothing along the lines of the XFire controller. Instead, they install managers on the bus that map things to the servlet environment. You can create your own servlet class that makes the same or related arrangements.
As far as JSR-181, SimpleFrontEnd and AegisDatabinding respect some @annotations, but there are cases where the XFire stuff was non-standard-conforming, so your mileage is prone to vary. You can always use .aegis.xml files if you want to stay completely clear of JAX-WS. On Fri, Jan 2, 2009 at 3:35 AM, skiitd <[email protected]> wrote: > > No Benson, I don't see any harm. I'm just curious for the support. The whole > context for my queries is that currently I use JSR181 stand-alone support > and registryListener to map the services in my own servlet instead of > XfireServlet. Further since xfireServletController can also be injected > alone from the spring I customize xFire much more freely and use my servlet > with xfireServletController. > > -- > View this message in context: > http://www.nabble.com/xfire-migration-tp21244688p21249052.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
