Jason, I believe this demonstrates loading an impl class as a RESTful and a SOAP service. I'm looking to load varying RESTful and SOAP implementations under the same http server port. I'll give what you've suggested a whirl and see how it goes with what I'm attempting.
Thanks. dan On Tue, Nov 19, 2013 at 9:53 PM, Jason Pell <[email protected]> wrote: > > https://github.com/pellcorp/cxf/blob/master/JavaFirst/src/test/java/com/pellcorp/server/jaxws/ServiceInvoker.java > > The spring context is > > https://github.com/pellcorp/cxf/blob/master/JavaFirst/src/main/resources/META-INF/jaxrsContext.xml > > I have not had a chance to actually test that I can execute the jaxrs > server, but the wadl displays and there are no errors in console ... > > > > https://localhost:8080/SimpleServiceWithNsServer?_wadl > https://localhost:8080/SimpleServiceWithNs?wsdl > > > On Wed, Nov 20, 2013 at 3:09 PM, Jason Pell <[email protected]> wrote: > > > Cxf with embedded jetty works very well. I will provide some examples in > > a couple of hours or less > > > > Sent from my Android phone > > On 20/11/2013 2:56 PM, "daniel williams" <[email protected]> > > wrote: > > > >> To give an example of what I'm trying to do: I have a platform that > >> initially exposed a standardized internal API. I've had to extend the > >> platform to adapt said API with varying integration points for external > >> service providers. One of those implementations is the API's own > >> internal, > >> standardized RESTful interface. In another example the client is > >> unwilling > >> to integrate with the API that we've exposed and is forcing us to > >> implement > >> their own API which exposes SOAP based methods. When we originally > >> envisioned this we imagined all would adapt to our interface to > integrate; > >> however, this was not completely reasonable. Initially we hosted our > >> services on Grizzly, but now our realized we cannot host SOAP on Grizzly > >> and are looking to find a container that will allow us to host multiple > >> REST and SOAP based services on the same container. > >> > >> If you have an example, or can point to a solution, with Apache CXF I'd > >> greatly appreciate it. > >> > >> Thanks. > >> > >> dan > >> > >> > >> On Tue, Nov 19, 2013 at 8:35 PM, Jason Wang <[email protected] > >> >wrote: > >> > >> > Daniel, I got quite a few Restful services and WS live in the same > maven > >> > module. Some of them share the same common request and response > objects > >> and > >> > exception classes. > >> > I dont think you need to do anything special to make they work. > >> > > >> > Cheers, > >> > > >> > > >> > On Wed, Nov 20, 2013 at 2:12 PM, Aaron Titus <[email protected]> > wrote: > >> > > >> > > I'm not sure if I understand 100% what you are trying to do, but it > >> > sounds > >> > > like this: > >> > > > >> > > http://cxf.apache.org/docs/jax-rs-and-jax-ws.html > >> > > > >> > > Does that page answer the question? > >> > > > >> > > > >> > > > >> > > > >> > > On Tue, Nov 19, 2013 at 6:39 PM, daniel williams > >> > > <[email protected]>wrote: > >> > > > >> > > > Hi, > >> > > > > >> > > > I'd like to host several services under the same Apache CXF > Server. > >> > I'd > >> > > > like to host a few JAX-WS and JAX-RS services. Is this possible? > >> I'll > >> > > > also need to handle this programmatically. > >> > > > > >> > > > My thoughts were to create varying JaxWsServerFactoryBean for each > >> > JAX-WS > >> > > > service to be exposed over a different path (same bind port), and > >> then > >> > > use > >> > > > the JAX-RS analog. However, looking at the Jax-Rs documentation, > it > >> > says > >> > > > that Apache CXF is dependent upon Jetty so I'm not sure that this > >> > > approach > >> > > > would work. > >> > > > > >> > > > Any suggestions and/or code samples would be very helpful. > >> > > > > >> > > > Thanks. > >> > > > > >> > > > Dan > >> > > > > >> > > > >> > > >> > >> > >> > >> -- > >> -dan > >> > > > -- -dan
