POJO or JAX-WS

[Joshua Partogi <jo...@gmail.com>]

Dear all,

I'm currently evaluating CXF to be used in our team. We are moving
away from another WS Framework since we find it easier to use CXF
because CXF supports Plain POJO out of the box. But now we kind of
stumble on choosing just a Plain POJO or use JAX-WS API. Well both can
accommodate our needs. But now, in production which one makes sense to
use? What are the strength of one compared to the other? Is there any
doc or wiki page on this that I can read? Or perhaps someone else that
has been doing comparison on this would like to share their
experiences?

Thank you in advance

-- 
Not by might nor by power, but by His Spirit.

Read my blog: http://joshuajava.wordpress.com/
Follow me on twitter: http://twitter.com/jpartogi

Re: POJO or JAX-WS

[Sergey Beryozkin <se...@progress.com>]

Actually, I think I've ignored XmlBeans as another databinding option which requires no explicit JAXWS annotations and it's also 
supported by JAXRS. As far sa Aegis is concerned,  it is also the default databinding used by Distributed OSGI.

Cheers, Sergey


> Hi
>
> You can do POJO with JAXWS (java first style) and JAXB involved
> or with Aegis binding which requires no JAXWS annotations.
> On top of it you can also do JAXRS which supports Aegis binding too.
>
> I guess going with explicit JAXWS can you give more options, as far as dealing with more complex requirements is concerned - but 
> if simplicity is the top priority then you might want to go with Aegis support - and you will be able to do both SOAP and 
> (restful) HTTP services
>
> Cheers, Sergey
>
>> Dear all,
>>
>> I'm currently evaluating CXF to be used in our team. We are moving
>> away from another WS Framework since we find it easier to use CXF
>> because CXF supports Plain POJO out of the box. But now we kind of
>> stumble on choosing just a Plain POJO or use JAX-WS API. Well both can
>> accommodate our needs. But now, in production which one makes sense to
>> use? What are the strength of one compared to the other? Is there any
>> doc or wiki page on this that I can read? Or perhaps someone else that
>> has been doing comparison on this would like to share their
>> experiences?
>>
>> Thank you in advance
>>
>> -- 
>> Not by might nor by power, but by His Spirit.
>>
>> Read my blog: http://joshuajava.wordpress.com/
>> Follow me on twitter: http://twitter.com/jpartogi
>>
>
>
> 

Re: POJO or JAX-WS

[Sergey Beryozkin <se...@progress.com>]

Hi

You can do POJO with JAXWS (java first style) and JAXB involved
or with Aegis binding which requires no JAXWS annotations.
On top of it you can also do JAXRS which supports Aegis binding too.

I guess going with explicit JAXWS can you give more options, as far as dealing with more complex requirements is concerned - but if 
simplicity is the top priority then you might want to go with Aegis support - and you will be able to do both SOAP and (restful) 
HTTP services

Cheers, Sergey

> Dear all,
>
> I'm currently evaluating CXF to be used in our team. We are moving
> away from another WS Framework since we find it easier to use CXF
> because CXF supports Plain POJO out of the box. But now we kind of
> stumble on choosing just a Plain POJO or use JAX-WS API. Well both can
> accommodate our needs. But now, in production which one makes sense to
> use? What are the strength of one compared to the other? Is there any
> doc or wiki page on this that I can read? Or perhaps someone else that
> has been doing comparison on this would like to share their
> experiences?
>
> Thank you in advance
>
> -- 
> Not by might nor by power, but by His Spirit.
>
> Read my blog: http://joshuajava.wordpress.com/
> Follow me on twitter: http://twitter.com/jpartogi
>