As Benson mentioned, take a look at the JaxWsServerFactoryBean. When you are using spring to configure things with jaxws:server, that is the object that Spring is manipulating. Thus, anything you can configure there should have appropriate options on the bean.
The other option is to create a org.apache.cxf.jaxws.EndpointImpl object directly and configure that. That's the object spring is manipulating when you use jaxws:enpoint. The first option is probably better though. Dan On Wednesday 23 January 2008, Rob Barrett wrote: > that's what i'm looking for - got a url? > > On Jan 24, 2008 12:46 PM, Benson Margulies <[EMAIL PROTECTED]> wrote: > > > Ideally I'd like to achieve all of this programatically - i.e. > > > without having to knock together a big config file. > > > > All that spring config corresponds to plain old Java objects. Some > > of them are even specified by the JAX-WS specification :-) > > > > Beyond the stock JAXWS API, all of CXF can be configured > > programmatically, so you can, indeed, stamp these things out like > > cookies. See the user guide section on non-spring configuration. -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
