The problem with this is that I don't have an implementor for the endpoint ... the call will be picked up and acted on by my custom Invoker (which will handle all of the operations on all of my web services in a generic fashion).
So ... I'm back to creating a custom ServiceFactoryBean? I.e. I need to create an CXF internal representation of a Service (an org.apache.cxf.service.Service) which is not based on a Java class or WSDL ... On Tue, Jan 27, 2009 at 2:46 PM, Dave Burford <[email protected]> wrote: > Thanks for the response. > > The configuration data will actually be coming from a legacy system (via a > web services call). > > I could write code to update the jaxws:endpoint entries as appropriate > before starting up CXF as Andrew suggests (thanks). > > However, I feel like it would be 'cleaner' to add the services in code - > although doing this with a custom ServiceFactoryBean looks like it would be > pretty complicated. > > Are there any other means to add services in code? I just found a reference > to 'using jaxws API's' so I'll follow that up. > > I may well be missing something obvious ... I'm new to all of this. > > BTW, I've found a simple way to do this using Axis2, but would rather use > CXF ... > > Thanks! > > > On Tue, Jan 27, 2009 at 1:03 PM, Andrew Clegg <[email protected]>wrote: > >> Can't you just setup up multiple jaxws:endpoint entries in your CXF >> config and have them all point to the same implementor? >> >> Or does the config information absolutely *have* to come from a >> different config file of your own design? >> >> Andrew. >> >> 2009/1/27 Dave Burford <[email protected]>: >> > Hello, >> > >> > I would like to be able to expose Services that are based on (my) >> > configuration data, and not WSDL or Java classes. >> > >> > For example, on start up of my server, I may read the configuration and >> add >> > a service called 'Customer' and one called 'Account'. Each will have a >> > couple of operations, which are also defined in the configuration data. >> > >> > When the services are invoked, they will all delegate to the same >> > implementation class. >> > This will get the name of the service and operation along with any >> > arguments, which are then used to 'do the right thing'. >> > >> > I have written an Invoker to act as the generic service implementation, >> This >> > is working OK. >> > >> > Now, I need to figure out how to expose the services. >> > >> > I think I need to create a custom ServiceFactoryBean, which interprets >> my >> > configuration data and exposes the service. >> > >> > Will this work? Is there a better way? >> > >> > Thanks in advance! >> > >> > Dave >> > >> >> >> >> -- >> New site launched: http://biotext.org.uk/ >> >> I am retiring my old email addresses. >> Please use [email protected] where firstname = andrew. >> > >
