On Thursday 22 July 2010 10:15:22 am Kannan Ekanath wrote:
> Hi Glen,
> Sorry I should have been more explicit. Yes I have tried the
> Endpoint.publish there is no exceptions in the log and infact I even see
> the log information as,
>
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean INFO - Creating
> Service {http://www.betfair.com/mm2/global/v1}MyService from class
> xx.yy.MyServiceImpl
>
> But inspite of that the end point is not created at all! My code looks like
> below
>
> Endpoint.publish("http://localhost:9001/services/xx";, xxObject);
>
> But when I use SoapUI and fire the endpoint I get a "No resource is
> configured for this url error". But the publish call did not throw any
> exceptions. I debugged the ReflectionServiceFactoryBean.createEndPoints and
> it goes through fine. Can someone tell me what is happening?
Most likely you application context is importing the cxf-extension-servlet and
not the cxf-extension-http-jetty that you would need for the Endpoint.publish
to work outside of a servlet environment. Outside of a normal webapp
container thing, you would normally want the http-jetty transport.
Dan
>
> - Kannan
>
> On 22 July 2010 14:07, Glen Mazza <[email protected]> wrote:
> > Kannan Ekanath wrote:
> > > In such a
> > >
> > > scenario is there any spring configuration which when declared does
> >
> > the
> >
> > > equivalent of this servlet configuration bit?
> > >
> > > --
> > > Regards,
> > > Kannan Ekanath
> >
> > I'm not sure you can avoid the web.xml for a hosted webapp because that's
> > part of the servlet specification. At any rate, to avoid the WAR file
> > and web.xml bit, you can host your webservice via Endpoint or embedded
> > Tomcat or
> > (more commonly) Jetty:
> > http://www.jroller.com/gmazza/entry/writing_junit_test_cases_for
> >
> > HTH,
> > Glen
> >
> > --
> > View this message in context:
> > http://cxf.547215.n5.nabble.com/Exposing-the-web-service-using-CXF-using-
> > Spring-without-Servlet-tp1842248p1842258.html Sent from the cxf-user
> > mailing list archive at Nabble.com.
--
Daniel Kulp
[email protected]
http://dankulp.com/blog
