That makes perfect sense, thanks. Perhaps I could suggest that the documented example contains just a few extra comments?
John Baker -- Web SSO IT Infrastructure Deutsche Bank London URL: http://websso.cto.gt.intranet.db.com Daniel Kulp <[EMAIL PROTECTED]> 28/04/2008 15:35 Please respond to [email protected] To [email protected] cc John-M Baker/ext/[EMAIL PROTECTED] Subject Re: CXF 2.1, Rest and Spring configuration John, If you are using the CXFServlet, then your servlet container will control what port you are using. Thus, the address should just be the "extension" off of the context from the servlet. Like: address="/blah" If the servlet is configured in the web.xml as "/cxf" and tomcat is on 8080, then the full address to hit would be: http://localhost:8080/cxf/blah Dan On Monday 28 April 2008, John-M Baker wrote: > Sergey, > > Where's the documentation for this: > > <jaxws:endpoint id="userService" > > implementor="com.db.websso.rest.server.ApplicationConfigurationService >Impl" address="http://localhost:9090/applicationConfiguration"; > bindingUri="http://apache.org/cxf/binding/http";> > <jaxws:serviceFactory> > <bean > class="org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean"> > <property name="wrapped" value="true" /> > </bean> > </jaxws:serviceFactory> > </jaxws:endpoint> > > You can see I've passed localhost:9090 in the address parameter, and > while the web app starts with no errors, nothing binds to 9090. And > I've updated web.xml to include the CXFServlet and start Spring. > > I have to say, this does seem like a lot of effort for something > that's so easy in a few lines of code. I'd love to see this much > easier to configure... > > Would appreciate some thoughts. > > > John Baker -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.
