Re: Possible for Synapse to return non-XML on simple HTTP GET?

[J Bouck]

See the synapse.xml that I have tried, but it still does not work with
HTTPS GET.  If I POST with an xml payload I see the textin sequence
log messages so I know that it's working.  If I GET to
/soap/StockQuoteProxy then the textin sequence log messages never
appear, the faultsequence does not run, synapse hesitates for 10
seconds and then returns the service definition page with the link of
the wsdl (which doesn't work because there is no wsdl defined for the
proxy service).  I am trying to do a simple GET on a synapse proxy.
Any ideas?

<definitions xmlns="http://ws.apache.org/ns/synapse";>
   <sequence name="textout">
        <log level="custom">
                <property name="text" value="textout"/>
                <property name="message"
expression="get-property('MESSAGE_FORMAT')"/>
        </log>
        <property name="RESPONSE" value="true"/>
        <send/>
    </sequence>
    <sequence name="textin">
        <log level="custom">
                <property name="text" value="SYNAPSE textin error"/>
                <property name="message"
expression="get-property('MESSAGE_FORMAT')"/>
        </log>
        <drop/>
    </sequence>
    <sequence name="textfault">
       <log level="full"/>
        <makefault>
                <code value="tns:Receiver"
xmlns:tns="http://www.w3.org/2003/05/soap-envelope"/>
            <reason expression="get-property('ERROR_MESSAGE')"/>
        </makefault>
        <property name="RESPONSE" value="true"/>
        <send/>
    </sequence>
    <proxy name="StockQuoteProxy" transports="https">
        <target inSequence="textin" outSequence="textout"
faultSequence="textfault">
        </target>
    </proxy>
</definitions>

~john


On Wed, Feb 27, 2008 at 11:04 AM, Asankha C. Perera <[EMAIL PROTECTED]> wrote:
> John
>
> > I can write an xslt that outputs text.  What would the synapse.xml
>  > look like to make the response be non-xml (without soap envelope
>  > wrappers, but including the appropriate http headers like mime-types
>  > for the non-xml content)?
>  >
>  Well, I have tried this with non http/s transports such as JMS where
>  this is used frequently.. The XSLT mediator will detect plain text
>  output and automatically wrap it in a text element. Basically the
>  message will always be a SOAP "infoset" within Synapse - a SOAP infoset
>  is usually serialized into XML, but internally its just the model that
>  we keep the "message" as and not in its XML representation.
>
>  So yes, you can continue to set transport headers on this message using
>  the property mediator etc
>
> > I think that I would prefer to write a synapse mediator that would set
>  > the servletresponse (non-xml response payload and http headers).
>  > Would something like that be possible?
>  >
>  sure
>
>  asankha
>