On Wed January 13 2010 2:26:22 pm Coder One wrote: > Can you help me with a snippet on 1 and 2? > > Somethign like the below? > > <wsdl:port name="StockQuoteServicePort" > binding="sqi:MyTransportBinding"> > > <soap:binding style="document" transport=http://acme.com/myTransport/>
That looks right, yea. Dan > > > Thanks > > > > ----- Original Message ---- > From: Daniel Kulp <dk...@apache.org> > To: users@cxf.apache.org > Cc: Coder One <coder_...@yahoo.com> > Sent: Mon, January 11, 2010 1:21:54 PM > Subject: Re: CXF & Spring & Custom Transport Setup > > On Mon January 11 2010 3:20:10 am Coder One wrote: > > I went through the links provided and the JMS transport links below, but > > I am still hazy on how in Spring do I choose to use my custom Conduit and > > custom Destination. That is, where do I tell CXF to invoke my custom > > transport factory to grab my custom Conduit and Destination? I probably > > need to re-read the fine manual :), but would appreciate all pointers... > > > > http://cxf.apache.org/docs/jms-transport.html > > http://cxf.apache.org/docs/using-the-jmsconfigfeature.html > > There are a few ways to do it: > > 1) wsdl first: the namespace of the first extensor element of the > soap:port in the service controls the transport. Thus, put an extensor > using the namespace you registered for your transport. > > 2) If the extensor in (1) is the soap:address, then the transport URI on > the soap:binding element in the binding section should map to your > transports namespace. > > 3) If all that fails, I think it checks the scheme on the url in the > soap:address. Thus, if you have : > <soap:address location="foo://blah.blah/"/> > It iterates over the transport to find the transport that claims to support > the "foo" protocol. > > Dan > > > The XSD for included JMS has a reference to JAXB, but I am using AEGIS, > > would I need to change to AEGIS? > > > > http://cxf.apache.org/schemas/configuration/jms.xsd > > > > Thanks, > > > > > > > > ----- Original Message ---- > > From: Daniel Kulp <dk...@apache.org> > > To: users@cxf.apache.org > > Cc: Coder One <coder_...@yahoo.com> > > Sent: Tue, January 5, 2010 9:10:40 AM > > Subject: Re: CXF & Spring & Custom Transport Setup > > > > > > > > The easiest is to just look at one of the existing transports: > > > > http://svn.apache.org/repos/asf/cxf/branches/2.2.x-fixes/rt/transports/jm > >s/ src/main/resources/META-INF/cxf/cxf-extension-jms.xml > > > > http://svn.apache.org/repos/asf/cxf/branches/2.2.x-fixes/rt/transports/lo > >ca l/src/main/resources/META-INF/cxf/cxf-extension-local.xml > > > > Etc.... > > > > > > Dan > > > > On Mon January 4 2010 6:46:47 pm Coder One wrote: > > > Hi, > > > > > > I am about to test integrate our custom transport (Conduit/Destination) > > > with CXF 2.2.5 and Spring 2.5.6. I'd appreciate all pointers to > > > docs/source sample on how to setup a Spring context file to hook inour > > > custom Conduit and Destination implementation. > > > > > > Thanks, > -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog
