Hi kulp, Thanks for reply. I am already using spring-mvc along with tomcat
and i am using just following dependency which does not brings a hell of
jar files (Really happy to use cxf.).
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-frontend-jaxrs</artifactId>
<version>3.1.3</version>
</dependency>
*One more questtion in case anybody can reply
:http://stackoverflow.com/questions/35849698/convert-a-soap-kind-of-webservice-to-restful-web-service
<http://stackoverflow.com/questions/35849698/convert-a-soap-kind-of-webservice-to-restful-web-service>*
If there is any way to listen on single end point and redirect it to proper
end point. (btw i am using *forward: *to forward it to a proper restful
url.)
Thanks in advance.
Regards,
Laxmi narayan patel.
*Regards,*
*Laxmi Narayan Patel*
*MCA NIT Durgapur (2011-2014)*
*Mob:- 9741292048,8345847473 *
On Tue, Mar 8, 2016 at 1:25 AM, Daniel Kulp <dk...@apache.org> wrote:
> Few comments/thoughts:
>
> 1) I have no idea why the “number of jars” would have any real impact on
> anything. That’s a silly metric for evaluating anything. A single jar
> couple be a monstrous “spaghetti mess” that performs poorly whereas a
> collection of small individual modular jars could be better architected and
> perform better.
>
> 2) If you are doing REST and not soap, replace cxf-rt-frontend-jaxws with
> cxf-rt-frontend-jaxrs. SOAP does bring in more jars as it’s a much bigger
> technology stack.
>
> 3) If you are deploying into a servlet container, you don’t need
> cxf-rt-transports-http-jetty (and thus all the Jetty dependencies). That
> would be for standalone only.
>
>
> Dan
>
>
>
> > On Mar 6, 2016, at 1:38 AM, Laxmi Narayan NIT DGP <nit.dgp...@gmail.com>
> wrote:
> >
> > Hi ,
> > I have to convert a very high end web service application which is
> > written in php to
> >
> > Java. Traffic will be around 0.01 million requests per second. As far as
> i
> > checked after
> >
> > adding
> >
> > <dependency>
> > <groupId>org.apache.cxf</groupId>
> > <artifactId>cxf-rt-frontend-jaxws</artifactId>
> > <version>3.1.5</version>
> > </dependency>
> > <dependency>
> > <groupId>org.apache.cxf</groupId>
> > <artifactId>cxf-rt-transports-http</artifactId>
> > <version>3.1.5</version>
> > </dependency>
> > <dependency>
> > <groupId>org.apache.cxf</groupId>
> > <artifactId>cxf-rt-transports-http-jetty</artifactId>
> > <version>3.1.5</version>
> > </dependency>
> >
> > I got hell amount of jars.
> >
> > I really want to keep it as light weight as possible,
> >
> > i am using spring (i cut down hibernate : i think it will slow down).
> >
> > I am fan of cxf but looks like for just developing restful web service ,
> we
> > do not need
> >
> > that much like when i tried checking jersey and second reason i think
> cxf
> > is more into
> >
> > SOAP based service (btw i jave experienced that if you just return
> > something which
> >
> > looks like json/xml it becomes restful web service). So if cxf is using
> > some security
> >
> > or something to make webservice very high performance or make be fast web
> >
> > service.
> >
> > Basically , If i am gonna use a number of jar files then it should make a
> > sense. If I am
> >
> > going to have the same response and same level from jersey then i will
> use
> > jersey.
> >
> >
> >
> >
> >
> > *Regards,*
> > *Laxmi Narayan Patel*
> > *MCA NIT Durgapur (2011-2014)*
> > *Mob:- 9741292048,8345847473 *
>
> --
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
