You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by skiitd <su...@gmail.com> on 2009/01/01 21:46:38 UTC
xfire migration
Hi,
I'm planning on migration to CXF from xFire (1.2.4). But I'm not sure about
the following:
1) With xFire I'm using JSR 181 annotations without using JAX-WS stuff. I
basically inject JSR181HandlerMapping and Jsr181WebAnnotations as well as my
service impls in the spring config.
I want to use the same with CXF but am not sure if CXF has support for
JSR181 alone without going into JAX-WS. Simple front-end doesn't seem to use
annotations but then JaxWSServerfactoryBean seems coupled to JAX-ws. Is it
possible to use JSR181 alone? Nothing against JAX-WS though!
2) Is there anything similar to DefaultServiceRegistry and
RegistrationListener?
Cheers,
Surender
--
View this message in context: http://www.nabble.com/xfire-migration-tp21244688p21244688.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: xfire migration
Posted by surenderk <su...@gmail.com>.
Thanks Ben! I guess I can go for JaxWS. As for the registration listener, I
believe i can do with iterating over the servers registered in my servlet.
Surender
--
View this message in context: http://www.nabble.com/xfire-migration-tp21244688p21285099.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: xfire migration
Posted by Benson Margulies <bi...@gmail.com>.
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 <su...@gmail.com> 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.
>
>
Re: xfire migration
Posted by skiitd <su...@gmail.com>.
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.
Re: xfire migration
Posted by Benson Margulies <bi...@gmail.com>.
What harm do you forsee from JAX-WS? CXF will use asm to auto-generate
your wrapper classes etc.
CXF doesn't have a service registry. You just define whatever
endpoints you want.
On Thu, Jan 1, 2009 at 3:46 PM, skiitd <su...@gmail.com> wrote:
>
> Hi,
> I'm planning on migration to CXF from xFire (1.2.4). But I'm not sure about
> the following:
> 1) With xFire I'm using JSR 181 annotations without using JAX-WS stuff. I
> basically inject JSR181HandlerMapping and Jsr181WebAnnotations as well as my
> service impls in the spring config.
> I want to use the same with CXF but am not sure if CXF has support for
> JSR181 alone without going into JAX-WS. Simple front-end doesn't seem to use
> annotations but then JaxWSServerfactoryBean seems coupled to JAX-ws. Is it
> possible to use JSR181 alone? Nothing against JAX-WS though!
>
> 2) Is there anything similar to DefaultServiceRegistry and
> RegistrationListener?
>
> Cheers,
> Surender
> --
> View this message in context: http://www.nabble.com/xfire-migration-tp21244688p21244688.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
>
Re: xfire migration
Posted by surenderk <su...@gmail.com>.
Great! thanks Dan...that helps :-)
--
View this message in context: http://www.nabble.com/xfire-migration-tp21244688p21305926.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: xfire migration
Posted by Daniel Kulp <dk...@apache.org>.
On Thursday 01 January 2009 3:46:38 pm skiitd wrote:
> Hi,
> I'm planning on migration to CXF from xFire (1.2.4). But I'm not sure about
> the following:
> 1) With xFire I'm using JSR 181 annotations without using JAX-WS stuff. I
> basically inject JSR181HandlerMapping and Jsr181WebAnnotations as well as
> my service impls in the spring config.
> I want to use the same with CXF but am not sure if CXF has support for
> JSR181 alone without going into JAX-WS. Simple front-end doesn't seem to
> use annotations but then JaxWSServerfactoryBean seems coupled to JAX-ws. Is
> it possible to use JSR181 alone? Nothing against JAX-WS though!
Already covered.... However, one note: the JSR181 thing in XFire was not
actually JSR181 compliant. Thus, moving it over to JAX-WS might result in
slightly different wsdl's generated and such.
> 2) Is there anything similar to DefaultServiceRegistry and
> RegistrationListener?
If you get the bus, there is a ServerRegistry extension that records the
servers:
bus.getExtension(ServerRegistry.class);
There is also the ServerLifeCycleManager:
bus.getExtension(ServerLifeCycleManager.class)
where you can register your listeners. (via spring is easiest)
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog