[jira] Commented: (SM-882) Allow text/binary output

["Guillaume Nodet (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/SM-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45912#action_45912 ] 

Guillaume Nodet commented on SM-882:
------------------------------------

It should be possible to add a switch so that the source and / or the result is grabbed from an attachment instead of the content.
We need to make sure it works easily with the binary marshalers used by servicemix-file and servicemix-ftp

> Allow text/binary output
> ------------------------
>
>                 Key: SM-882
>                 URL: https://issues.apache.org/activemq/browse/SM-882
>             Project: ServiceMix
>          Issue Type: Improvement
>          Components: servicemix-saxon
>    Affects Versions: 3.1
>         Environment: servicemix 3.1 , java 1.5
>            Reporter: Hervé Bourzeix
>
> When outputting something else than XML , I got the following exception:
> ERROR - FileComponent                  - Error processing exchange InOnly[
>   id: ID:MON-HBOURZEIX-1214-1173859213020-3:33
>   status: Active
>   role: provider
>   service: {http://www.genesys.com/jbi}pervasive
>   endpoint: writeParam
>   in: Unable to display: org.xml.sax.SAXParseException: Content is not allowed in prolog.
> ]
> javax.jbi.messaging.MessagingException: org.xml.sax.SAXParseException: Content is not allowed in prolog.
>         at org.apache.servicemix.expression.JAXPXPathExpression.evaluate(JAXPXPathExpression.java:114)
>         at org.apache.servicemix.components.util.DefaultFileMarshaler.getOutputName(DefaultFileMarshaler.java:65)
>         at org.apache.servicemix.file.FileSenderEndpoint.processInOnly(FileSenderEndpoint.java:68)
>         at org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:100)
>         at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
>         at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
>         at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
>         at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
>         at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
>         at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
>         at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
>         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
>         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
>         at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
>         at org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMSourceFromStream(SourceTransformer.java:224)
>         at org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMSource(SourceTransformer.java:135)
>         at org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMNode(SourceTransformer.java:289)
>         at org.apache.servicemix.jbi.jaxp.SourceTransformer.toDOMNode(SourceTransformer.java:306)
>         at org.apache.servicemix.expression.JAXPXPathExpression.getXMLNode(JAXPXPathExpression.java:179)
>         at org.apache.servicemix.expression.JAXPXPathExpression.evaluate(JAXPXPathExpression.java:94)
>         ... 13 more
> [Fatal Error] :2:4: Content is not allowed in prolog.
> [Fatal Error] :2:4: Content is not allowed in prolog. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.