Re: Writing my own transport

ulatorQuestion q) { >> >> >>return new CalculatorResult(q); >> >> >>} >> >> >> } >> >> >> >> >> >> >> >&

Re: Writing my own transport

- > >> > >> >> > >> >> > >> >> This is deployed as web service: > >> > >> > >> > >> >> > >> >> > >> >> > >> >> >> >>

Re: Writing my own transport

alculatorBean" >> >> address="/" >> >> wsdlLocation="/WEB-INF/wsdl/calculator.wsdl" >> >> serviceName="tns:calc" >> >> xmlns:tns="http://com.sample/Calculator"/> >> >> >>

Re: Writing my own transport

>> >> >> >> >> >> > >> id="calculatorService" >> >> implementor="#calculatorBean" >> >> address="/" >> >> wsdlLocation="/WEB-INF/wsdl/calculator.wsdl" >> >> ser

Re: Writing my own transport

gt; >> xmlns:tns="http://com.sample/Calculator"/> > >> > >> > >> > >> > >> What i want to do, is call the service through the JVM (thus NOT > >> through > >> HTTP)

Re: Writing my own transport

ailto:dk...@apache.org] Verzonden: woensdag 7 mei 2008 6:09 Aan: dev@cxf.apache.org Onderwerp: Re: Writing my own transport Depending on what you need to do, you may not need all of the below classes. For example, the CachedXXXputStream stuff may not be necessary depending on your protocol and cur

Re: Writing my own transport

>> What i want to do, is call the service through the JVM (thus NOT >> through >> HTTP), with plain SOAP XML as input and plain XML as output, including >> custom SOAP Headers, WS-Security headers, and what not. >> >> If i use local transport i am stuck with t

Re: Writing my own transport

jk bericht- Van: Daniel Kulp [mailto:[EMAIL PROTECTED] Verzonden: woensdag 7 mei 2008 6:09 Aan: dev@cxf.apache.org Onderwerp: Re: Writing my own transport Depending on what you need to do, you may not need all of the below classes. For example, the CachedXXXputStream stuff may not be nec

Re: Writing my own transport

Depending on what you need to do, you may not need all of the below classes. For example, the CachedXXXputStream stuff may not be necessary depending on your protocol and current stream implementations. Actually, in most cases, you DON'T want to use that. Instead, use a subclass of t

Re: Writing my own transport

Hi Marcel, Assume the transport you want to implement is AAA, basically you need several class as below AAAConduit extends AbstractConduit, kinda like your transport client AAADestination extends AbstractDestination, your transport destination AAAConduitOutputStream extends CachedOutputStrea

Writing my own transport

I have a service 'service1' listening to HTTP. I would like be able to make a new transport for this service, so i can use a propietary transport protocol to receive the InputStream and send the OutputStream to. The received message is 100% SOAP, so i just want to send it into the CXF marshalling

Writing my own transport

I have a service 'service1' listening to HTTP. I would like be able to make a new transport for this service, so i can use a propietary transport protocol to receive the InputStream and send the OutputStream to. The received message is SOAP, so i just want to send it into the CXF marshalling layer